Reference

Privacy Policy for your India account

Lightning Roulette, Galaxy Wild and Football Strike all create account, wallet, device and gameplay records; this Privacy Policy explains how durabet handles that data for India.

Account data scopeCookie choicesUPI privacy contextRights request path
durabet Privacy Policy for your India account
CONTACT ROUTES

Three privacy contact paths

Every privacy request should include your account email or mobile number, the date range you mean, and the action you want from us.

Email privacy desk Write to the privacy address on durabet.
Live chat privacy queue Use chat for quick privacy routing, not for sending one-time passwords or full wallet…
Account settings route From your account area, update simple profile details or ask for a privacy action…
ACCOUNT CARE

Six controls behind your data

The controls below describe how we put this Privacy Policy into daily work. We separate account data from wallet references, restrict support access by role, and keep cookie records tied to browser…

Data collection map

We link each data field to a purpose: account creation, login safety, payment matching, support or legal duty. If a field is not needed for those purposes, we aim not to collect it.

Cookie choices

Cookies remember session status, language, device signals and security checks. Where a cookie is optional, your browser choice is respected, and you can clear or change those settings through your device.

Payment references

For UPI, Paytm and PhonePe, we store transaction IDs, status codes and timing details needed to match wallet events. We do not ask for wallet PINs or one-time passwords.

Account security

Login alerts, device checks and password reset flows help protect access to your account data. Support can verify identity, but it should never ask you to reveal private authentication codes.

Retention windows

Some data must stay for tax, dispute, fraud or account-safety duties. When that reason ends, we delete, anonymise or restrict records according to the policy and local law.

Correction and removal

You can ask us to correct inaccurate details, provide a data copy or delete eligible records. We first confirm identity, then explain what can be changed and what must remain.

Privacy questions before you join

These answers focus only on this Privacy Policy and your account data. They explain what we collect, how payment references are handled, how to ask for a copy or correction, and how cookies affect access. For any request, contact us through the privacy path and include enough account detail for identity checks.

The policy covers account details, login records, device data, cookies, payment references and messages you send to support. It also explains how we use that data for access, wallet matching, security and legal duties.

We use transaction IDs, status codes and timestamps to match your wallet activity with provider confirmations. We do not need your UPI PIN, Paytm passcode or PhonePe one-time password for a privacy request.

Yes. Send a request from the account email or verified mobile number so we can confirm identity. We will share eligible data in a usable format unless a legal restriction applies.

You can ask us to correct inaccurate name, contact or address details. If the change affects identity checks or withdrawals, we may request proof before updating records tied to the wallet.

We keep data only for the period linked to account operation, payment disputes, fraud checks, tax duties or legal requests. After that, records are deleted, anonymised or restricted where the law allows.

Cookies help maintain your session, remember basic choices and support security checks. You can manage browser cookies on your device, though some account and wallet functions may need essential cookies.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy requests can still be sent, and our reply will explain any local constraint that affects your account.