Responsible play · Limit-setting, self-exclusion, support

A reader-side toolkit for limits, time-out and self-exclusion

A quiet, mature resource page: age notice, time-out limits the player can self-impose, deposit caps, session timers, self-exclusion, jurisdictional helpline numbers and warning-signs. The desk does not publish promotional CTAs on this page.

Reading time · 7 min Last reviewed · 2026-08-10 Source-led · MeitY/PROG Act 2025

Section 01 · Frame

Why this page is a toolkit, not a banner

The desk publishes the responsible-play controls the reader can self-impose on a reviewed operator: a daily deposit cap, a weekly deposit cap, a session timer, a time-out window and a self-exclusion request. The desk treats the controls as a reader-side toolkit, not a promotional surface.

The MeitY/PROG Act 2025 notice is the canonical source for the framework that governs the controls. The national helpline 1800-599-0019 is published as a reference, not a recommendation. The desk does not invent or paraphrase the number; the citation is the original government notice.

An ink-bordered editorial photograph of the responsible-play toolkit spread — Responsible play · toolkit spread, not a banner

For the rules that govern a settled hand, the rules chapter is the right page. For the platform-by-platform controls a reader can self-impose, the section below is the right page.

Limit-setting checklist

Six controls the reader can self-impose on a reviewed operator

Control · 01

Daily deposit cap

Set a daily deposit cap that is below the per-hand stake unit multiplied by the number of hands the reader plans to play. The cap is enforced by the operator at deposit time.

Control · 02

Weekly deposit cap

Set a weekly deposit cap that matches the reader's monthly entertainment budget divided by four. The cap is enforced by the operator at deposit time.

Control · 03

Session timer

Set a session timer that closes the lobby after a stated number of minutes. The timer is enforced by the operator at lobby close.

Control · 04

Time-out window

Set a time-out window (24 hours to 30 days) during which the reader cannot log in. The window is enforced by the operator at authentication.

Control · 05

Self-exclusion

File a self-exclusion request (6 months to permanent) that closes the account and blocks re-registration on the operator's verification dashboard. The request is irreversible inside the requested window.

Control · 06

Stake unit downshift

Move down a stake ladder (e.g. from 10-rupee Points to 1-rupee Points) for a stated period. The downshift is enforced by the operator at table join.

Section 02 · Self-exclusion flow

The three-step flow that closes the account

Self-exclusion on a reviewed operator is a three-step flow: a written request submitted through the in-app help center, a verification step that confirms the requester is the account holder, and a confirmation screen that names the exclusion window (6 months, 1 year or permanent). The request is irreversible inside the requested window.

Step 01 · Written request. The reader submits a written self-exclusion request through the operator's in-app help center. The request must include the account email, the registered phone number and the requested exclusion window.
Step 02 · Verification. The operator's verification desk confirms the requester is the account holder. The verification step usually routes through the operator's KYC field set (PAN last-4, Aadhaar last-4).
Step 03 · Confirmation. The operator issues a confirmation screen that names the exclusion window and the date the window ends. The desk recommends screenshotting the confirmation screen.

Section 02 · How the desk uses the toolkit on a session

The five-row session check the desk runs before and during a play session

The desk treats the responsible-play toolkit as a five-row session check. The first row is the deposit cap; the desk asks the reader to set a deposit cap at the start of the session and to refuse any session where the operator does not surface a deposit-cap field at sign-in. The second row is the session timer; the desk asks the reader to set a session timer at the start of the session and to stop the session at the timer's first alert, not at the timer's final alert.

The third row is the loss limit; the desk asks the reader to set a loss limit at the start of the session and to stop the session when the loss limit is reached, not when the deposit cap is reached. The fourth row is the break reminder; the desk asks the reader to set a break reminder at the start of the session and to take the break the reminder surfaces, not the break the reader schedules in the lobby. The fifth row is the self-exclusion option; the desk asks the reader to know where the self-exclusion option is reachable from the lobby and to use the option at the end of any session where the session timer surfaced more than once.

The desk's standing rule is that no session is complete without all five rows being set at the start of the session. The desk refuses to publish a "responsible-play compliant" claim that is not sourced to the operator's responsible-play page; the desk asks the reader to confirm the operator's five-row toolkit against the operator's help center before the first session and to re-confirm against the operator's most recent help-center update before each subsequent session.

For the per-session confirmation, the desk asks the reader to read the operator's responsible-play block at the start of the session and to refuse any operator that buries the deposit-cap field in a help-center article. The desk treats a buried deposit-cap field as a friction observation; the operator is recorded as friction-observed against the deposit-cap row and the verdict chip is stamped with the date of the check.

Detail block · the operator's responsible-play surface

Six items the desk expects on the operator's responsible-play page

Deposit cap — daily, weekly and monthly caps that the reader can set from the lobby without contacting support.
Session timer — a session-length alert that the reader can set from the lobby and that fires at the start of the alert, not at the end of the session.
Loss limit — a loss-limit field that the reader can set from the lobby and that stops the session when the limit is reached.
Break reminder — a break-reminder field that the reader can set from the lobby and that fires at the start of the break, not at the end of the break.
Self-exclusion — a self-exclusion option reachable from the lobby, not buried in a help-center article, with a minimum six-month exclusion window.
Grievance officer — a grievance-officer contact reachable from the lobby, with the officer's name, email and a stated acknowledgement turnaround.

Reader questions

Four questions the desk keeps answering on the responsible-play surface

Does the operator share deposit-cap data with the credit bureau?

No. The operator's deposit-cap field is set on the operator's domain and the operator does not publish the field's value to a credit bureau. The desk asks the reader to confirm the operator's deposit-cap data-handling rule against the operator's privacy notice and to refuse any operator that does not publish a privacy notice for the deposit-cap field.

Can a reader raise the deposit cap mid-session?

The operator's standing rule is that the deposit cap is set at the start of the session and is not raised mid-session. Where the operator allows a mid-session raise, the desk records the operator as friction-observed and asks the reader to verify on the operator's responsible-play page. The desk treats a mid-session raise as a friction observation because the raise happens after the reader has lost focus on the cap.

What does the desk record when the operator buries the deposit-cap field?

The desk records the operator as friction-observed against the deposit-cap row and stamps the verdict chip with the date of the check. The desk asks the reader to verify the deposit-cap field against the operator's responsible-play page and to escalate to the operator's grievance officer where the field remains buried across two separate checks.

Is the self-exclusion option reversible?

The operator's self-exclusion option is reversible only after the exclusion window expires. The minimum exclusion window is six months; the operator does not allow a mid-window reversal. The desk asks the reader to confirm the operator's exclusion-window rule against the operator's responsible-play page before opting in.

\n\n

Family controls

Age verification and parental controls the desk expects every operator to publish

Family · 01

Age verification at registration

Every reviewed operator must verify the player's age at registration, not at deposit time. The verification step usually routes through the PAN field, which carries the player's date of birth.

Family · 02

Parental controls on the device

The desk recommends parental controls on the device (Google Family Link, Apple Screen Time) in addition to the operator's age-verification step. Device-level controls block the lobby at the OS layer.

Family · 03

Family-member self-exclusion

A family member may file a self-exclusion request on behalf of a player who is unable to file one themselves. The request must include the player's account email and the family member's signed declaration.

Verified support channels

Reach a counsellor before the next hand

The desk publishes the verified national helpline as a reference, not a recommendation. The line is staffed by trained counsellors who can route a reader to a state-appropriate support channel. The desk does not invent or paraphrase the number; the citation is the original government notice.

India helpline1800-599-0019 · 24×7
GamCare (UK)0808 8020 133 · gamcare.org.uk
BeGambleAwarebegambleaware.org
National Council on Problem Gambling (US)1-800-522-4700 · ncpgambling.org

For adult readers only. Skill-game editorial · real-money play requires jurisdiction eligibility. The desk does not operate a cash table and does not publish promotional CTAs on this page.

Signals of harm

Five signals the desk treats as worth pausing for

Signal · 01

Chasing a loss

Returning to a cash table within 24 hours to recover a settled loss is the single most-cited signal of harm in responsible-play literature. The desk recommends a 72-hour pause.

Signal · 02

Stake unit creep

Moving up a stake ladder (e.g. from 1-rupee Points to 10-rupee Points) without a stated reason is a signal that the per-hand stake is no longer matching the reader's entertainment budget.

Signal · 03

Session length growth

A session that grows from 30 minutes to 3 hours without a stated reason is a signal that the session timer is not being enforced by the reader at lobby close.

Signal · 04

Deposit outside budget

A deposit that exceeds the reader's stated weekly entertainment budget is a signal that the deposit cap is not being enforced. The desk recommends a 30-day time-out window.

Signal · 05

Borrowing to deposit

Using a credit line, a personal loan or a family-member's funds to make a deposit is a signal of harm. The desk recommends a permanent self-exclusion request.

Deposit cap math · the desk's working frame

How the desk reads a deposit cap against a 100-hand sample

The desk's working frame for a deposit cap is the 1-sigma band of the per-hand score across a 100-hand sample, multiplied by the table size. A reader who plays a 4-player 13-card Points table at stake unit 0.10 rupees sees a 1-sigma band of approximately 4 rupees per hand across 100 hands; the desk's working cap is the table's per-hand stake unit times 100, which is 10 rupees at stake unit 0.10. A reader whose deposit cap is below 10 rupees for the same table is over-capped; a reader whose deposit cap is above 40 rupees for the same table is over-stretched.

The frame is conservative. The desk reads the 1-sigma band as the most-likely outcome band, not the worst case; a reader who draws a 2-sigma loss across the same 100 hands would lose approximately 16 rupees per hand, not 4. The desk refuses to publish a 2-sigma cap as the working frame because a reader who treats the 2-sigma cap as the working cap will not be able to fund a single hot streak, let alone a cold one.

The frame is per-format. The 1-sigma band at a 13-card Points table is not the 1-sigma band at a 21-card Points table; the 21-card variant has a wider band because the hand size adds variance to the discard-tracking work. The frame is also per-table-size: a 6-player table has a wider band than a 2-player table because the opponent set is larger. A reader who switches formats or table sizes must re-read the cap against the new frame, not carry the old cap forward.

The desk's standing rule across the frame is that a deposit cap is set before the first deposit, not after the first loss. A cap set in response to a loss is a chasing frame, not a working cap. The desk's strategy chapter walks through the per-hand expected value that a working cap is meant to bound.

The desk also publishes a session-timer rule: a session timer is set to the per-hand expected value divided by the per-hand score variance, rounded up to the nearest 15 minutes. The rule is meant to bound the time-on-table, not the number of hands. A reader who treats the session timer as a hands counter will end the session at a different point in the variance cycle than the rule intends.