Reference

Privacy Policy for cricketx account data

cricketx brings Blackjack, Sic Bo, Football Strike and wallet access into one account, and this Privacy Policy explains how the account data behind that flow is collected, used…

Account dataUPI contextCookie choicesPrivacy contact
cricketx Privacy Policy for cricketx account data
CONTACT ROUTES

Three ways to reach privacy support

Privacy questions deserve a clear route, not a maze. Use the channel that matches your need, include the email or mobile number linked to your account, and tell us whether you want…

Privacy email Write to [email protected] with your account email, request type and a short description. Do not send payment passwords or full UPI PINs; we will ask only for verification details we need.
Account chat Open chat after logging in if your request is linked to deposits, withdrawals, cookies or login history. The team can tag the case for privacy handling and confirm the next step.
Profile request form Use the account profile form when you need a name, mobile number or saved address checked. We compare your request with existing records, then tell you what can be changed.
ACCOUNT SAFEGUARDS

Six data controls we keep visible

Our privacy work follows the account journey: open, verify, deposit, browse, withdraw, contact, close. Each step creates a limited record, and each record has a purpose.

Data collection

We collect details you type, device signals, location cues, cookie IDs and account activity.

Payment records

UPI, Paytm and PhonePe data is used to match transfers with your wallet and verify withdrawal requests.

Cookie choices

Cookies help keep you signed in, remember language settings and detect risky access patterns.

Account access

Login checks may use passwords, one-time codes, device history and account signals.

Retention periods

We keep records only as long as needed for account operation, dispute handling, fraud checks, tax or legal duties.

Change requests

You can ask us to access, correct or review deletion of selected account data.

Privacy questions before you open an account

Before you open an account, it is fair to ask what happens to your data. These answers explain how we handle account setup, payments, cookies, rights requests and support checks under this Privacy Policy. If your situation needs a closer look, contact us and we will route it to the right team.

We collect account details, contact data, identity-check records, device signals, wallet activity, cookie IDs and support messages. We use these records to operate your account, verify requests, handle disputes and meet legal duties.

We use payment references to match deposits, verify withdrawal requests, trace failed transfers and respond to disputes. We do not ask for your UPI PIN, payment app password or unrelated bank login details.

Yes. Send a request through privacy email, account chat or the profile form. We may verify your identity before sharing records, and some legal or security files may be withheld where required.

Open the profile form or contact support with the account email and the field that needs correction. We may ask for proof if the change affects withdrawals, identity checks or account security.

Retention depends on the record type. Account, payment, dispute and security logs may be kept while needed for service, audits, fraud checks or legal duties, then deleted or anonymised where practical.

Only teams that need the case can view it, such as privacy support, security, payments or legal advisers. Internal access is role based, and request actions are logged for later checking.

Yes. Access depends on local law and is available where local law permits. We may check location, eligibility details and identity records before allowing account activity or processing certain privacy requests.