Reference

Privacy Policy for your q000 account

Privacy controls for your q000 account cover identity checks, UPI, Paytm, PhonePe, Google Pay records, cookies and game-session logs in one clear policy.

UPI data contextPaytm privacy recordPhonePe wallet careGoogle Pay handling
q000 Privacy Policy for your q000 account
CONTACT PATHS

Three ways to ask privacy questions

Privacy requests need a clear route, so we separate them from routine account messages.

Privacy email desk Send your privacy request from the email linked to your account. Include your account name, the data area involved, and the action you want, such as access, correction or deletion assessment.
Signed-in account chat Use account chat after signing in when your question concerns cookies, login alerts or recent device activity. Our team can see the account context without asking you to repeat private details.
Verification request lane If a privacy request affects withdrawals or KYC records, we may ask for a fresh identity match. This protects your wallet while we assess what can be changed or removed.
ACCOUNT SAFETY

Six privacy controls we use daily

Our privacy work sits inside account operation, not away from it. The same controls that protect login access also shape how we read payment references, game-session logs and…

Collected data

We collect account details, device data, payment references and session records when you use Live Blackjack, Fishing War or other…

Payment records

UPI, Paytm, PhonePe and Google Pay references are used to match deposits, withdrawals and refund checks.

Cookie choices

Cookies help keep you signed in, remember basic settings and detect unusual access.

Account security

Login alerts, device checks and one-time passcodes help us spot account misuse.

Retention periods

We keep account and wallet records for as long as needed for law, dispute handling, fraud prevention and tax or…

Correction requests

You can ask us to correct account data that is wrong or out of date.

Seven privacy answers before account setup

Before you open your account, read these answers so you know how your data is handled from the first login. They cover account records, payment references, cookies, correction requests, retention and local-law access. If your concern is specific, contact us through the privacy email desk or signed-in account chat.

We collect the details needed to create and protect your account, including contact data, identity-check records, device signals, login history and wallet references. We use this data for access, security, payments and legal duties.

We keep payment references, transaction times, amounts and status messages so deposits and withdrawals can be matched to your account. Full wallet passwords or banking credentials are not stored by us.

Cookies help keep your session active, remember basic settings and detect unusual access patterns. Game-session logs may record room entry, time and device data, but they are handled under this Privacy Policy.

Yes. Send a correction request from your linked email or signed-in chat. We may ask for identity proof, and some payment or KYC records may stay unchanged where legal records require it.

Retention depends on the record type. Account, payment, dispute and fraud-prevention records may be kept for legal and audit duties, while data no longer needed is removed or anonymised.

Only staff who need to handle your request can access the related account data. We log internal actions, limit permissions by role, and keep payment data separate from general support messages.

Access and eligibility depend on local law and are available where local law permits. If a rule affects your account, we may adjust access while keeping required records under this Privacy Policy.