Reference

Privacy Policy for your 6yu account

6yu explains how your account data, wallet records, device signals and cookie choices are handled before you open an account or return to the lobby.

Account data scopeCookie choicesUPI record carePrivacy contact
6yu Privacy Policy for your 6yu account
CARE CHANNELS

Contact paths for privacy requests

Privacy requests should reach the team that can check your account record without moving you through unrelated queues. Use the channel that matches your request, and include the mobile number or email linked with your account so we can locate the correct record. For safety, we may ask for verification before we disclose, correct or erase data. If your request concerns a payment reference, include the UPI, Paytm, PhonePe or Google Pay receipt ID.

Team online

Privacy email

Send a message through the privacy email shown inside your account area. Mention whether you want access, correction, erasure or cookie help, and avoid sending card photos or unrelated documents unless we ask.

Account chat

Open chat from the account menu when you need help matching a privacy request to your mobile number, email or wallet record. The team can raise a privacy ticket after confirming basic account details.

Payment record query

For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction reference and date. We use those details only to trace the matching wallet entry and respond to your request.

DATA PRACTICE

Data care across wallet and lobby

Our Privacy Policy is written around the records we actually handle: account fields, login events, cookie choices, game session logs, wallet entries and messages you send to us.

Account fields

We collect account details such as your name, mobile number, email, login credentials and verification status.

Cookie choices

Cookies help keep you signed in, remember language or region choices and measure page performance.

Wallet records

UPI, Paytm, PhonePe and Google Pay references are stored with your wallet history so we can confirm transactions, investigate failed…

Security signals

We log device type, IP address, browser data and access times to spot unusual account activity.

Retention periods

We keep account and wallet records only for operational, legal, tax, dispute and security needs.

Change requests

You can ask us to correct outdated details, provide a copy of your data or erase records where the law…

Privacy questions before you join

These answers explain the main privacy points you may want to check before you create an account or send a request. They focus on data collection, account access, payment records, cookies, retention and your choices. If your question is tied to a specific wallet entry or login event, contact us with the relevant date and account identifier so we can trace it accurately.

We collect the details needed to create and protect your account, such as name, mobile number, email, login data, verification status, device signals and wallet references. We use them for account access, security and privacy request handling.

We store transaction references, timestamps and wallet status so we can match credits, withdrawals, reversals and support queries. These records also help us respond when you ask for a copy, correction or explanation of payment data.

Yes. Send a request from your account email or verified mobile number and tell us which field is outdated. We may ask for verification before changing details, especially where wallet or identity records are involved.

You can ask us to erase data where the law allows. Some records may need to be kept for tax, security, dispute, fraud prevention or legal reasons, and we will explain any retained category in our reply.

Yes. Cookies are covered because they affect login sessions, language choices, security checks and page measurement. You can manage many cookies through your browser, but essential session cookies may be required for account access.

Privacy requests are handled by staff who need access to answer them, such as account support, security or payment operations. Access is limited by role, and identity checks are used before data is shared or changed.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy requests are handled under applicable legal duties, which may affect verification steps, retention periods and what we can erase.