11Tiger responsible play

Every fantasy-cricket platform the desk tracks exposes three limits: a deposit limit, a loss limit and a session limit. The deposit limit caps the total amount that can be added in a chosen window. The loss limit caps net loss across the same window. The session limit caps time spent in the platform.

The recommended setup is conservative: a daily deposit limit below the entertainment budget, a weekly loss limit that triggers a forced pause rather than a warning, and a session limit at one match-card deadline at a time. Refunds are disabled once the loss limit trips. Re-entry requires a 24-hour cool-off.

A cool-off is a short lockout — typically 24 hours, 7 days or 30 days. The reader can request it from the platform’s responsible-play settings and from the support channel. The platform cannot undo a self-imposed cool-off.

Self-exclusion is a long lockout — typically 6 months or longer. The reader cannot log in, deposit, withdraw to a card or UPI, or be re-marketed to during the exclusion. Re-entry at the end of the exclusion requires an active request from the reader, not a default lapse. The desk treats self-exclusion as the highest-leverage guardrail and recommends the 6-month minimum for readers who feel they have lost control.

Three contacts to keep somewhere a phone or wallet does not lose. The platform’s own support channel. The payment-method support channel (bank or UPI helpline). The national or state helpline for problem gambling.

The desk publishes the helpline list on this page and on the contact page. The helpline list is updated when state-level resources change; the desk’s own loss-prevention materials sit alongside the platform’s, not in place of them.

A working checklist for the reader who lands on this page to set limits or to escalate a responsible-play concern. The limits are easy to set in advance and impossible to set once the bank balance has shifted; the checklist is a quick way to confirm the discipline is in place before the next fixture card.

Three questions to ask before the next match card. Is the daily deposit limit set below the entertainment budget? Is the weekly loss limit set to trigger a forced pause rather than a warning? Is the session limit set at one deadline at a time? Where any of those is “no”, the discipline is not yet in place.

What the desk does well. The page lists each limit ladder and each escalation contact in plain language. The 6-month self-exclusion default is published as the minimum rather than as a suggestion.

What the desk is still working on. A reader-side worksheet the desk cannot reach. A public table of state-by-state helpline numbers updated on the desk’s monthly cadence.

A reading cadence the desk recommends. Read the page once on a quiet afternoon before placing a first paid entry. Re-read the limits ladder on every second paycheque.

The responsible-play guardrails on this page are the deck’s working default. A reader who has not yet set a deposit limit should set one before placing a paid entry. The daily limit is the easiest and the most-overlooked. The weekly loss limit is the guardrail the deck weights highest; a weekly loss limit that triggers a forced pause rather than a warning is the working default.

The session limit is the third guardrail. A session limit at one match-card deadline at a time keeps the reader’s attention on the next contest rather than on a refresh-and-edit cycle. The discipline compounds across a season; a reader who has set the three limits in advance rarely overrides them in the moment.

Self-exclusion is the highest-leverage guardrail and the one most readers under-use. A 6-month exclusion with re-entry only on active request is the deck’s default. The exclusion cannot be undone by the platform; the re-entry request is the reader’s only path back. Where the reader feels they have lost control, the exclusion is the cleanest reset.

Three escalation contacts sit alongside the guardrails. The platform’s own support channel. The payment-method support channel. The national or state helpline for problem gambling. The deck publishes the published escalation contacts on this page and updates the list when state-level resources change.

The responsible-play guardrails on this page are the desk’s working default. The desk does not publish a personal-finance recommendation. The deposit limit, the loss limit and the session limit are platform-side tools; the reader’s own discipline is the deciding factor.

The desk does not have visibility into the reader’s bank balance. A loss limit the reader sets without referencing the entertainment budget may be too high. The desk recommends reviewing the loss limit on every second paycheque and re-setting the limit when the entertainment budget shifts.

The desk does not override the platform’s own responsible-play policies. Where the platform publishes a stricter default than the desk’s working default, the platform’s default prevails; the desk publishes the platform’s published default rather than republishing a softer one.

Three caveats the desk publishes on the responsible-play page. The deposit, loss and session limits are platform-side tools; the reader’s own discipline is the deciding factor. The desk does not publish a personal-finance recommendation.

The second caveat: the loss limit and the self-exclusion may differ between platforms. The desk publishes the platform’s published default rather than republishing a softer one; the platform’s default prevails where the two differ.

The third caveat: the responsible-play guardrails may not catch a problem until after the boundary has been crossed. The desk publishes the escalation contacts on the contact page and updates the list when state-level resources change.

A reader who has found a partner-brand-controlled behaviour the desk has not named is welcome to send the corrections email; the next responsible-play-page refresh reflects the new caveat.

The responsible-play desk closes its read with a note on the guardrails. The deposit, loss and session limits are the platform-side tools; the reader’s own discipline is the deciding factor. The desk does not publish a personal-finance recommendation.

The three escalation contacts the desk publishes are the platform’s own support channel, the payment-method support channel and the national or state helpline for problem gambling. The desk keeps the list current; the list is updated on the news desk when state-level resources change.

The two habits that hold are deposit before play and time cap. A weekly contest budget set before the first match and never topped up between matches is the deck’s working default.

The loss-ledger habit the deck recommends is a weekly ledger of net result in a notebook or spreadsheet the desk cannot reach. The ledger is the early-warning system; a reader who keeps the ledger rarely misses the discipline.

The deck’s coverage area is published on the about page. A reader who wants a different area of coverage is welcome to send a corrections email with a proposed coverage-area addition.