Reference

doxebet Privacy Policy for India Accounts

This page explains how doxebet handles your account data, device signals, cookies and verification records for India access where local law permits use.

Account dataCookie settingsIndia accessChange requests

explore the lobby Read FAQ

What This Policy Covers Locally

doxebet Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our policy applies to the personal data you submit on doxebet and to the records created when you sign in, move between pages or use wallet methods that are available in India. Where local law permits access, we collect only what is needed to run your

1
account, confirm identity, answer support requests and keep audit trails for security and dispute handling. That can include your name, contact details, device signals, session logs and the transaction trail linked to UPI, Paytm, PhonePe or Google Pay when those rails are used with your account.
2
Cookies help us keep you signed in, remember settings and spot misuse, while retention periods depend on the reason for the record and any legal duty that applies in your state or territory. If access is not permitted where you are, the site should not be
3
used there. You can still ask for correction, deletion or a copy of the record through the contact route below, and we will act where local law allows.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

REQUEST CHANNELS

How To Reach Privacy Support

Questions about this Privacy Policy should come through the contact paths tied to your account, because that lets us confirm the right record before we act.

In-account form Send your privacy request from the help area after sign-in. That keeps the request linked to the right account and gives us the details we need to answer access, correction or deletion questions under local law.

Support desk thread If you already have a message open, reply in the same thread so we can keep one record of your request, avoid duplicate checks and explain any step that still needs verification.

Verified follow-up For sensitive requests, we may ask for an extra check before we release a copy or make a change. That protects your account and helps us avoid acting on the wrong record.

STORAGE CHECKS

Cookies, Retention and Account Safety

We keep this policy focused on the records that matter for account handling, security and lawful retention.

Collection scope

We collect the details you enter for your account, plus device and session signals that help us protect sign-in and trace errors. We keep the scope narrow and use the record only for the stated account purpose.

Cookie control

Cookies remember your login state, page choices and repeat visits, which reduces extra steps and helps us spot misuse. You can clear or block them in your browser, though some settings may reset.

Security checks

If a change request looks sensitive, we may ask for OTP confirmation or another verification step before we act. That keeps account access tied to you and reduces the chance of someone else changing your record.

Retention window

We keep data only while the account is active, while a request is open, or while law requires a record. Payment trails linked to UPI, Paytm or PhonePe may stay longer for audit or dispute handling.

Change requests

You can ask us to correct contact details, update consent choices or close the account record where local law permits. We will say what can be changed, what must remain and why the limit applies.

Contact route

For privacy matters, use the signed-in support form or reply to the same message thread. That lets us trace your request, check the right account and send the result through the same route.

Common Privacy Questions You May Ask

These questions cover what we collect, how we use it and how you can ask for changes. If your request is about a copy, correction or deletion, start from the signed-in contact path so we can verify the right account before we respond. We keep the process simple, but we still check identity for sensitive requests and we follow the limits that local law sets for your location.

We collect the details you enter for registration and support, plus device and session signals that help us protect sign-in and trace errors. We keep the scope narrow and use the record only for the stated account purpose.

Yes, where local law permits. After verification, we can share the relevant account record and explain what we are able to disclose, what must stay private and why any item cannot be released.

Cookies remember your login state, page choices and repeat visits, which reduces extra steps and helps us spot misuse. You can clear or block them in your browser, though some settings may reset.

We keep payment trails only as long as needed for account handling, audit needs or dispute checks. Records linked to UPI, Paytm, PhonePe or Google Pay may stay longer if law requires it.

Use the signed-in contact form and tell us what should change. We may ask for a verification step first, then we will update the record where local law and account rules allow.

Use the support route tied to your account, or reply in the same thread if one is already open. That keeps the request linked to the right record and helps us answer faster.

We keep data only while the account is active, while a request is open, or while law requires retention. When those reasons end, we remove or archive records under the applicable rule.

doxebet Privacy Policy for India Accounts

How To Reach Privacy Support

Cookies, Retention and Account Safety

Collection scope

Cookie control

Security checks

Retention window

Change requests

Contact route

Common Privacy Questions You May Ask

01 What personal data do you collect?

02 Can I ask for a copy of my record?

03 How do cookies affect my session?

04 Do you keep payment records?

05 How can I correct my details?

06 Who should I contact about privacy?

07 How long do you keep my data?

Related Pages