Reference

Open your crickbet privacy terms clearly

We explain how crickbet handles account details, login records, cookies, device checks, and payment references such as UPI, Paytm, PhonePe, and Google Pay before you open an account.

Account dataCookie choicesUPI referencesIndia privacy contact
crickbet Open your crickbet privacy terms clearly
CONTACT ROUTES

Check where to ask privacy questions

Privacy requests work faster when you contact us from the same email, mobile number, or account area linked to your profile.

Account email Send privacy requests through the help address shown in your account area. Include your registered mobile number, the request type, and any payment reference you want us to check, but avoid sharing card photos.
In-account chat Use in-account chat when you need quick routing for cookie, login, or device questions. Our team may ask verification questions before discussing account data, so keep your mobile and email access ready.
Privacy request form For correction or deletion requests, choose the privacy category in the contact form. We acknowledge the request, explain any records we must keep, and confirm the next action in writing.
ACCOUNT CARE

Browse how we protect account data

Our privacy process covers collection, storage, sharing, retention, and correction in one account flow.

Data we collect

We collect account details you submit, login records, device signals, cookie IDs, and payment references.

Cookie controls

Cookies help keep sessions active, remember language choices, and spot unusual login patterns.

Payment privacy

UPI, Paytm, PhonePe, and Google Pay references are stored with wallet records so deposits and withdrawals can be matched.

Access security

When a new device signs in, we may use one-time codes, IP checks, and session controls.

Retention periods

Some records stay longer because tax, dispute, and anti-fraud duties require them.

Request handling

You can ask to update, access, or delete eligible data.

Start with common privacy questions

These answers explain common privacy choices connected with your account, payment references, cookies, and support requests. They do not replace the full Privacy Policy, but they help you understand what we collect and why. If your request involves access, correction, deletion, or wallet records, contact us from your linked account channel so we can verify the request before acting on it.

We collect details you provide, such as name, mobile number, email, login credentials, and verification records. We also store device signals, IP data, cookies, and wallet references needed to run and secure your account.

Payment references are used to match deposits, withdrawals, refunds, charge queries, and account ownership checks. We keep them with wallet records and do not display your UPI ID or app receipt publicly.

Yes, you can ask us to correct eligible account data. We may request proof that the change is valid, especially for mobile number, email, payment reference, or verification details linked to wallet activity.

You can request deletion of eligible data. Some records may remain when law, dispute handling, fraud prevention, tax duties, or payment reconciliation require retention for a defined period.

Cookies help keep your session active, remember preferences, measure site performance, and detect unusual login behaviour. You can clear them through your browser, but some account actions may require fresh verification.

Only teams and service providers with a defined need can access account data, such as support, payments, security, hosting, or compliance handling. Access is limited by role and checked through internal controls.

Some privacy and account checks can depend on local law, payment partner rules, or regulator requests. Access and eligibility are available where local law permits, and records may be handled to meet those duties.