What responsible play means on khelo bet24

Deposit caps on khelo bet24 are configurable from the wallet settings screen. A cap lowered takes effect on the next deposit; a cap raised has a 24-hour cooling-off window before it is applied, to prevent reactive raising.

Self-exclusion closes the account for a stated period and revokes marketing consent for the same duration. Re-entry at the end of the period requires a fresh KYC and a 24-hour reflection window before the first stake. The exclusion can be lifted only at the end of the stated period.

Self-exclusion is applied per account, not per device or per IP. The exclusion blocks new sign-ups with the same KYC identity for the exclusion period. The exclusion is logged in the support agent queue as a responsible-play event.

Reality checks surface the elapsed session time and the net position every 60 minutes by default. The interval is configurable from 30 to 180 minutes. Reality checks cannot be silenced for the entire session; the minimum interval is 30 minutes.

Session timers run on the lobby client and on the wallet screen. A timer warning fires at 30 minutes before the configured logout. A hard logout ends the session at the chosen logout interval; re-login is required to continue.

The session ledger on the wallet screen captures three numbers: stake total, win total and net position. Each number is visible in real time and is updated as bets settle. The session ledger resets at logout.

The responsible-play rules on khelo bet24 surface at six points during the first session. Each surface is a place the reader is asked to confirm a setting or to acknowledge a rule. The surfaces are not buried in the footer; they sit in the wallet screen and the withdrawal screen, where the reader will see them.

The first surface is the sign-up form. The reader confirms age (18+) and residency in a supported state. The confirmation is captured before the account opens. Foreign-currency top-ups are blocked at this point because the wallet is INR-only from creation.

The second surface is the deposit rail. The reader sets the daily, weekly and monthly cap before the first deposit. The defaults are ₹5,000 / ₹25,000 / ₹100,000. Lowering a cap is instant; raising a cap has a 24-hour cooling-off window. The asymmetry prevents reactive raising in the heat of a session.

The third surface is the first session itself. The reality-check interval fires at the configured cadence (default 60 minutes, configurable from 30 to 180). The interval cannot be silenced for the entire session; the minimum is 30 minutes.

The fourth surface is the withdrawal screen. The KYC document set is required before the first withdrawal. The responsible-play exclusion check fires here: if the account is in a self-exclusion period, the withdrawal proceeds (the reader's money is theirs) but new stakes are blocked.

The fifth surface is the support queue. Responsible-play queries route to a specialist team inside the same agent queue. The team handles cooldown requests, exclusion period reviews and the cooling-off window for cap raises.

The sixth surface is the deletion path on /delete-account/. Account closure is final after the cooling-off window (default seven days). The data deletion follows the published retention policy on /privacy/.

The cap windows on khelo bet24 are rolling, not calendar-aligned. A daily cap of ₹5,000 means the reader cannot deposit more than ₹5,000 in any 24-hour rolling window. A weekly cap of ₹25,000 means any 7-day rolling window. A monthly cap of ₹100,000 means any 30-day rolling window.

The rolling window math matters because it lets the reader deposit early in the day without losing the cap later in the day. The trade-off is that a deposit at 11:50 PM does not reset at midnight; it resets 24 hours after the deposit timestamp.

The cap windows are visible from the wallet screen. The reader can see the next reset timestamp for each cap. The cap cannot be raised above the default without the 24-hour cooling-off window; the window is the asymmetry that prevents reactive raising.

Where the cap is hit, the next deposit is blocked at the rail. The reader sees the next reset timestamp on the wallet screen and can choose to wait or to lower the cap. Lowering the cap is the recommended action; raising it after a hit is the discouraged path.

The responsible-play bundle exposes three levers that change the reader's relationship with the lobby. The levers are not interchangeable; each solves a different problem and the reader should pick the lever that matches the situation.

Cooling-off is a reversible time-out from 24 hours to six weeks. The login page accepts credentials but the lobby remains locked. The wallet is read-only and the withdrawal remains available. The cooling-off is the right lever for a short break after a bad session or a stress event.

Self-exclusion is a stronger lever. The exclusion period runs from six months to five years. The account is locked for the period, the marketing consent is revoked for the same period, and re-entry at the end requires a fresh KYC and a 24-hour reflection window. The exclusion is the right lever for a longer break or a pattern of behaviour the reader wants to interrupt.

Deletion is final. The closure request opens a seven-day cooling-off window (configurable from 24 hours to 30 days). After the window, the account closes and the data deletion follows the published retention policy on /privacy/. Anti-money-laundering records are retained for the statutory period; aggregated analytics are retained with no PII. The deletion is the right lever when the reader is exiting the product for good.