The d11 India responsible-play surface is composed of three entry points: an 18+ age reminder on the public lobby, a jurisdiction reality note in the app footer, and a self-exclusion intent flow reached from the account settings tab. Each of these is verified against the staged sponsor dataset; the public HTML surface exposes a link to the responsible-use page rather than a copy of the in-app flow.

The 18+ marker is the simplest of the three. It appears as a fixed banner on the public surface and inside the app shell before the lobby loads. The reference desk treats the banner as verified because the public HTML carries it on every page and the in-app capture shows the same string.

Verification pending: the exact wording of the in-app 18+ reminder inside the d11 India app is not exposed on the public surface. The reference desk assumes the wording matches the staged banner; a reader who needs the exact in-app string should consult the d11 India app settings page directly.

This reference is part of a verified article on the d11 India reference desk. Where verification could not be completed from a single primary source, the section is tagged verification pending at the bottom.

The d11 India product surface operates under a Curacao operator licence, with verification pending from public sources. The reference team flags this in the d11 India footer and on every signpost CTA. The reader is responsible for confirming jurisdiction eligibility before opening an account.

In India, the public-gambling law is a state subject and varies across states. The d11 India reference team does not offer legal advice on state-level eligibility. Where a state restricts real-money gaming, the in-app lobby enforces the restriction server-side and the team notes the restriction as verification pending.

Self-exclusion on the d11 India surface is reached from the account settings tab inside the app. The intent flow carries a cooldown selection, a confirmation screen, and an in-app acknowledgement. The public HTML does not expose the flow directly; the responsible-use page links out to the support reference instead.

A reader who wants to self-exclude should open the d11 India app, go to account settings, and follow the responsible-play intent flow. The reference desk cannot trigger the flow on the reader behalf, and the public surface cannot confirm the flow completed without the reader checking the app.

Verification pending: the exact list of self-exclusion cooldowns and the platform-side enforcement window are not exposed on the public surface. The reference desk surfaces the entry point and leaves the in-app details to the in-app confirmation screen.

This reference is part of a verified article on the d11 India reference desk. Where verification could not be completed from a single primary source, the section is tagged verification pending at the bottom.

Three items on the responsibility surface remain verification pending: the exact in-app 18+ reminder wording, the state-by-state jurisdiction enforcement list, and the self-exclusion cooldown options. Each is tagged below and on the responsible-use page so the reader knows what is verified and what is not.

The desk publishes this distinction rather than guessing because the difference between verified and pending is the difference between a source and a hypothesis. The reader contract on the d11 India desk is: verified links to a source, pending admits it does not.