Reference

Privacy Policy for your z1000 account

This Privacy Policy explains how z1000 handles the account details you share, the cookie data our site creates, and records linked with UPI, Paytm, PhonePe and Google Pay.

Account dataCookie choicesUPI record carePrivacy requests
z1000 Privacy Policy for your z1000 account
CONTACT ROUTES

3 ways to reach privacy support

Privacy requests work faster when they come through a channel we can verify. Use the email linked to your account for formal requests, signed-in chat for quick checks, and the account data…

Email privacy desk Write to our privacy desk from the email linked to your account. Include the account ID, the data area you mean, and a phone number only if you want a call back.
Signed-in chat In-account chat lets us confirm you are signed in before we discuss cookie settings, payment references or security alerts. Please avoid sending full UPI IDs unless we specifically ask for a masked sample.
Account data request For correction, access or deletion requests, send the exact change you want and any matching documents. We may ask for identity checks before changing records tied to withdrawals, disputes or legal duties.
PRIVACY CONTROLS

6 privacy controls inside z1000

A privacy rule only helps if you can see how it works inside your account.

Data collected

We collect account details you type, device data created by your browser, game round logs, wallet records and messages you…

Cookie choices

Cookies help keep you signed in, remember language choices and spot repeated failed login attempts.

Account security

Login checks, session timeouts and device signals help us detect account misuse.

Payment records

UPI, Paytm, PhonePe and Google Pay references are handled as financial records, not public profile data.

Retention periods

Some records are kept while your account stays active; others stay longer when tax, fraud, dispute or legal duties require…

Change requests

You can ask to access, correct, export or delete data by contacting privacy support.

Privacy Policy questions for India accounts

Use these answers when you want a plain explanation before opening your account or sending a privacy request. They focus on the data we collect, cookies, payment references, access controls and the time we keep records. If your case depends on a state rule, court order or banking requirement, our privacy team will explain the applicable path in writing. You can come back to this page whenever our policy changes.

We collect the details you enter, such as name, phone, email, login credentials, KYC material where required, device signals and wallet records. We use them for account access, security checks, payments and legal record duties.

Yes, transaction references may be stored with time stamps, amounts, status messages and account links. This helps us trace deposits, withdrawals, failed transfers and disputes without asking you to repeat the same payment details.

Cookies keep sessions active, remember basic choices and help detect repeated login failures. Optional cookies, where used, are handled through consent controls so you can change your choice without affecting core account access.

Yes. Contact privacy support from your linked email or signed-in chat and ask for account data access. We verify identity first, then share the data we can release under local law.

Send the exact detail that needs correction and attach proof when the change affects KYC or wallet records. We update editable fields after checks and tell you if a legal record cannot be changed.

You can ask for deletion through privacy support. We remove data that is no longer required, but payment, security, dispute or legal records may need to stay for a defined retention period.

Only teams that need the request for verification, account checks, legal handling or technical action can access it. We do not publish your request, and routine replies use masked payment references where possible.