Reference

Open 6zt Privacy Policy in India

Speed Baccarat, Moon Goddess and Kabaddi Crash sit inside an account flow where 6zt explains what data we collect, why we keep it, and how you can ask…

India privacy scopeUPI record handlingCookie choicesRequest changes
6zt Open 6zt Privacy Policy in India
CONTACT ROUTES

Check 6zt privacy contact paths

Privacy questions need a clear route, not a long search through the lobby.

Privacy email Send personal data requests to [email protected] with your registered email or mobile number.
Account chat Use in-account chat when you can still log in and need help with cookies…
Wallet queries For privacy questions linked to UPI, Paytm or PhonePe records, include the date, amount…
DATA CARE

Browse our data care practices

We treat privacy work as part of account operations. The same care that checks a withdrawal request also protects login records, device signals, payment references and support messages.

Account data

We collect profile details such as name, mobile number, email, login history and verification status.

Cookie choices

Cookies help remember sessions, language settings, fraud signals and basic site analytics.

Security checks

We use device data, IP logs, failed login records and payment reference checks to spot account misuse.

Retention periods

We keep account and wallet records for as long as needed for service, disputes, legal duties and audit checks.

Change requests

You can ask us to correct profile details, update contact data, or consider erasing records where the law allows.

Partner access

Payment, hosting, analytics, fraud and customer care partners may handle data for us under defined tasks.

Discover privacy answers before joining

Before you open an account, it helps to know what happens to your data from the first login to a wallet request. These answers focus on personal data, cookies, payment records, access checks and contact routes. If your question is specific to your account, send it through the privacy email or in-account chat so we can verify you before replying.

We collect contact details, login records, device signals, verification status and wallet references. We use them to create your profile, protect access, match payments, respond to requests and meet legal duties.

We keep masked payment references to match deposits, withdrawals, refunds and disputes with your account. These records also help us answer wallet privacy questions without exposing full payment details.

Yes, you can ask us to correct contact details or profile data that is wrong. We may ask for verification first and may keep certain records where payment, dispute or legal rules require it.

Cookies keep you signed in, remember basic settings, support chat flow and help us detect unusual access. You can manage browser cookies, but some account and wallet functions may need them.

Only staff or service partners with a work reason can access personal data. Examples include payment matching, fraud checks, hosting, analytics, support replies, legal requests and account recovery.

Retention depends on the record type and legal need. We keep data while your account is active, during disputes, for required audits, and for safety checks, then delete or reduce it where practical.

Yes. Access and eligibility depend on local law and are available where local law permits. We may use location, verification and account records to apply the right privacy and access checks.