Reference

How 20bet Handles Your Privacy

Live Blackjack, Taj Mahal, Football Strike and UPI wallet actions create account records, and this Privacy Policy explains how 20bet collects, uses and protects that data.

India account dataUPI privacy contextCookie choicesKYC record care
20bet How 20bet Handles Your Privacy
CONTACT ROUTES

Three Ways To Ask About Data

Privacy questions should reach the team with enough detail for a proper reply, but never more personal data than needed.

Account privacy email Use the privacy contact listed inside your account area for access, correction or deletion requests. Include your registered email and a short request summary so we can route it without asking for repeated details.
Live chat privacy handoff Chat can help you find the right privacy path, but sensitive requests may move to email. That keeps identity checks, attachments and written replies in one place for clear handling.
Payment data queries For UPI, Paytm, PhonePe or Google Pay questions, share only the transaction reference and date. We match that to wallet records without asking you to reveal full banking details.
CONTROL CHECKS

Six Privacy Controls We Use

We treat privacy as an account operation, not a separate promise on paper. The same checks that protect your sign-in, wallet activity and KYC status also shape how…

Data collection points

We collect details through account forms, KYC uploads, sign-in records, game activity and payment references.

Cookie handling

Cookies help keep your session active, remember basic preferences and measure page errors.

KYC privacy checks

Identity documents are reviewed only for verification, legal duties and account safety checks.

Payment record matching

UPI, Paytm, PhonePe and Google Pay references are used to match deposits and withdrawals to your wallet.

Retention approach

We keep account data only for as long as needed for service, legal, security and dispute reasons.

Change requests

You can ask to access, correct or delete personal data where the law allows.

Your Privacy Questions Answered Clearly

These questions explain how the Privacy Policy works in everyday account situations, including KYC, cookies, payments, access requests and deletion. If your question depends on a specific transaction or document, contact us through the account area so we can check the record securely. Eligibility and account access depend on local law and are available where local law permits.

We collect account details, contact data, KYC documents, sign-in records, device signals, game activity, payment references and support messages. The exact data depends on what you use and what verification is required.

KYC documents help confirm that the account belongs to you and support legal, payment and security checks. We use them for verification and dispute handling, not for unrelated public sharing.

For UPI, Paytm, PhonePe and Google Pay, we store transaction references, status updates and wallet matching data. We do not ask you to send full bank credentials through chat or email.

Yes, you can request correction where the law allows and where the data can be changed. We may need proof before updating identity, phone, email or payment-linked details.

You can request deletion through the privacy contact path in your account. Some records may be retained for legal, security, payment dispute or audit reasons before deletion can be completed.

Cookies support sign-in sessions, preference storage, traffic measurement and error checks. You can manage them in your browser, but blocking certain cookies may prevent parts of the account area from loading.

Use the privacy contact shown inside your account area or ask chat to route the request. Include your registered email and request type, but avoid sending unnecessary documents unless requested.