Responsible use guidance

Effective: 2026-08-28. Use /contact/ for private, no-email support.

This product profile is built from a published snapshot of the publisher’s public content. The snapshot is the only source we cite on these routes; we do not pull in additional claims from social posts, third-party listings, advertisements or outside reviews. Where the snapshot does not publish a value, the row is labelled Not published and we invite you to verify the answer at the publisher’s own page or through the support inbox.

These routes are written for shortlisting visitors and audit-minded readers, not for legal professionals. They explain what the verification profile does, what it stores, what it routes and how to make choices about cookies and consent. They are kept in plain language by design. Where professional legal advice matters for your decision, treat this as background and consult a qualified lawyer.

How we treat unverifiable claims

Shortlisting visitors ask us about licence numbers, regulator filings, payment processors, retention windows and security audits. We do not publish any of those because the snapshot does not publish them. The honest answer is “not in source” rather than a confident guess. Where you need that information for an operating decision, contact the publisher directly.

What these routes will never do

These routes will never ask you for credentials, never display a checkout, never publish a direct APK, never invent a regulator approval, never copy a third-party publisher’s branding and never mislead you into believing the company behind these pages operates any app shown in the directory. The verification profile does not transact.

Our stance

Treat money spent on apps in the library as the cost of entertainment, not as an investment. Set a budget you can absorb as a loss and stop when you reach it.

Tools the publisher exposes

The publisher of any app listed in the library exposes deposit limits, cooling-off periods, reality checks and self-exclusion. Use them before, not after, a session starts.

External help

If you or someone you know is losing control, contact the Indian helplines published by the responsible-use authorities. We do not publish a phone number we cannot verify.

Verification

We display this guidance because it is part of a real product. We do not display contact details that the staged source did not prove.

What this route does

This route frames the principles. It does not include direct phone numbers or email addresses for specific helplines, because we cannot verify any we have not seen published by a competent authority.

What visitors should do

Set a deposit limit before your first session. Use a cooling-off period after a long session. Treat chasing losses as a warning sign. Self-exclude the moment play stops being enjoyable.

For audit-minded readers

Every recommendation on this route is sourced from the publisher’s own responsible-use page or from a responsible-use authority we can name. We do not cite media coverage or social posts for these recommendations.

Related routes

For the publisher’s responsible-use tools, use /Login/playnow. For terms of use, see /terms/. For privacy, see /privacy/.

Budgeting before your first session

Open the publisher’s deposit-limit tool and set a daily, weekly and monthly ceiling before placing a bet. The most reliable budget is one set before you commit.

Cooling-off after a long session

Schedule a cooling-off period at the end of every session. Cooling-off blocks play for a window you choose; it is one of the most effective tools exposed by the publisher.

Reality checks

Switch on reality checks inside the app. The publisher surfaces a soft prompt at a fixed interval; treat that prompt as a stop signal rather than a suggestion.

Self-exclusion

If a session stops being enjoyable, self-exclude. Self-exclusion is reversible only after the window you choose; it is the right tool when budget and reality checks no longer hold.

External help

If you or someone you know is losing control, contact the Indian helplines published by responsible-use authorities. We do not invent contact details we cannot verify.

For audit-minded readers

We cite the publisher’s own responsible-use page and the responsible-use authorities we can name. We do not cite media coverage or social posts for these recommendations.

A short visitor’s reading order

If you have thirty seconds, read the ‘our stance’ section. If you have three minutes, read the tools the publisher exposes. If you have ten minutes, read the rest of the route, then open the publisher’s deposit-limit tool inside the app.

Why a responsible-use route

The product is a verification profile for a real product. A real product is used by real visitors, and a real visitor may need external help. The route exists to point at the principles and the publisher’s own tools, without inventing helpline numbers the snapshot did not publish.

What the publisher exposes

The publisher exposes deposit limits, cooling-off periods, reality checks and self-exclusion inside the app. These four tools are the most reliable levers an individual has. Set a budget, use a cooling-off, switch on reality checks, and self-exclude the moment play stops being enjoyable.

What we will never invent

We will never invent a phone number or email address for a specific helpline. We will never claim the publisher offers counselling if the snapshot does not. We will never imply that a third-party website is the source of authoritative help.

What the editorial desk will not do

The editorial desk will not publish content on responsible-use from third-party media coverage of the publisher. The desk will only cite the publisher’s own page and the responsible-use authorities we can name. This rule is part of the editorial discipline.

Submitting a correction

If you spot a number on this route that disagrees with the publisher’s own responsible-use page, send a short message through /contact/ with the route URL and the disputed claim. The desk reviews and publishes a correction.

A working visitor’s checklist

Before your first session, set a deposit limit inside the publisher’s app. Open the responsible-use tool on the publisher’s onboarding screen and configure daily, weekly and monthly ceilings. Set a cooling-off period at the end of every session. Switch on reality checks. Treat each prompt as a stop signal rather than a suggestion.

What the publisher exposes

The publisher exposes deposit limits, cooling-off periods, reality checks and self-exclusion inside the app. The publisher also exposes a session-history view and a transaction log. The combination of those tools is what gives a shortlisting visitor real control over their play.

Editorial archive and audit trail

Each recommendation on this route corresponds to a tool the publisher exposes inside the app. We do not invent tools we cannot verify. When the snapshot is silent on a specific tool, we say so rather than recommending an unverified one.

What we mean by ‘Not published’

When the snapshot is silent on a particular helpline number or external counselling service, we say so. We do not cite media coverage, social posts or out-of-date advisories. Honest silence is the best service when a helpline number is critical.

What happens when the source changes

If the publisher amends the responsible-use tools, the desk republishes this route. The audit trail in the editorial archive keeps the prior version for reference.

Beyond this article

Reading the route on a small screen

The route is single-column on mobile. The recommendations remain readable because each section is a short heading plus a short paragraph. Use a larger viewport for the publisher’s in-app tools.

What about responsible-use at the publisher’s site

Each recommendation on this route pairs with a tool the publisher exposes inside the app. The publisher’s own responsible-use page is the source of record for the exact wording and the exact triggers. Verify there before relying on it on the day you act.

Why we do not list third-party helplines

The site does not list a phone number or email address for a specific helpline unless the publisher has published it. Doing otherwise would mislead a visitor into contacting a third party on this product profile’s credibility.