Reference

Privacy Policy for your q10 account

Our Privacy Policy tells you how account details, payment references, device data and cookie choices are handled when you open the lobby or manage your profile.

Account data clarityUPI contextCookie choicesPrivacy request paths
q10 Privacy Policy for your q10 account
CONTACT PATHS

Reach us about privacy requests

Privacy questions should reach the right team with enough detail to identify your account safely.

Privacy email Send account data requests to our privacy inbox with your registered email, mobile number and a short request summary. We verify ownership before discussing personal records or making changes.
Account chat Use account chat for quick privacy questions about cookies, login alerts or payment references. If your request needs deeper checks, we move it to email so the record stays clear.
Payment privacy queue For UPI, Paytm, PhonePe or Google Pay privacy concerns, share the transaction reference only. We compare it with wallet records and never ask for your PIN or wallet password.
ACCOUNT SAFETY

How we handle your privacy

We design privacy checks around real account actions: sign-in, wallet updates, support conversations, cookie choices and game session records.

Data collection

We collect details needed to create and protect your account, such as mobile number, email, login records, device signals, KYC checks where required and wallet references linked to your activity.

Cookie choices

Cookies help keep sessions active, remember language choices and detect unusual login patterns. You can manage browser settings, though some security and account functions may need essential cookies.

Payment records

UPI, Paytm, PhonePe and Google Pay references help match deposits and withdrawals to your wallet. We store transaction IDs and status markers, not your UPI PIN or wallet password.

Account security

We use login checks, device signals and support verification to reduce unauthorised access. If something looks unusual, we may pause sensitive actions until ownership is confirmed.

Retention rules

Some data can be changed or removed after verification, while records tied to disputes, security checks, payments or legal duties may need to stay for a defined period.

Change requests

You can ask us to correct profile details, check stored records or raise a deletion request. We explain what can be changed, what must stay and why.

Privacy questions before you join

Before you open an account, you should know what data is needed and how your choices work. These answers focus only on the Privacy Policy: collection, cookies, payment references, account access, retention and contact routes for correction or deletion requests.

We collect account details such as mobile number, email, login records, device signals and verification material where required. We also keep wallet and session records needed for security, support and account history.

Yes. The policy covers payment references from UPI, Paytm, PhonePe and Google Pay when they connect to your wallet activity. We use references and status markers, not your UPI PIN or wallet password.

Cookies support sign-in, session continuity, language choices and security checks. You can manage browser settings, but blocking essential cookies may affect account access or require repeated verification during sensitive actions.

Yes. Contact us from your registered email or account chat and tell us what needs correction. We verify ownership first, then update details that can be changed under the policy.

You can raise a deletion request through support. Some records may need to remain for payment matching, disputes, security checks or legal duties, and we explain any retention reason in our reply.

Access is limited to teams that need the data for account support, security checks, payment matching, verification or legal handling. Sensitive requests require extra checks before data is shared or changed.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests remain available through support even if access rules affect account activity in your location.