Reference

Privacy Policy for your 1zon account

Your account, wallet, UPI, Paytm, PhonePe and Google Pay activity, cookies, and support chats are covered by this Privacy Policy, so you can see what we collect and…

Account data scopeUPI privacy contextCookie choicesRequest channels
1zon Privacy Policy for your 1zon account
CONTACT ROUTES

Privacy contact paths when you need us

Privacy requests work better when they start from a channel already linked to your account. Use the email address, mobile number, or in-account chat connected to your profile so we can match your request to the right record. Please keep payment screenshots cropped to the necessary reference details and avoid sending unrelated personal data.

Team online

Privacy email

Write to [email protected] from the email on your account. Include the mobile number, payment reference if relevant, and the exact privacy request, so our team can locate the right record without asking twice.

In-account chat

Open chat after logging in if your request relates to cookies, device access, wallet records, or a recent support conversation. We may ask one security question before changing privacy settings.

Profile request form

Use the account panel to update contact details, change communication choices, or request a data check. The panel keeps your request tied to your login session and reduces identity mismatch issues.

POLICY PRACTICE

How we handle account data

We treat privacy as part of daily account operations, not as a separate document that sits outside the product.

Account creation data

When you open an account, we collect contact details, login credentials, device signals, and region markers.

Payment privacy records

UPI, Paytm, PhonePe, and Google Pay references are stored as transaction records, not as full banking profiles.

Game activity logs

Round IDs for Lightning Roulette, Bar Bar Bar, Football Strike, Kabaddi Crash, Bingo, and Fishing War may be logged with…

Cookies and devices

Cookies remember your session, language choice, security state, and basic site performance.

Retention and deletion

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

Request verification

Before acting on correction, access, or deletion requests, we may verify your email, mobile number, recent login, or payment reference.

Privacy Policy questions before you join

These answers explain the privacy choices available before and after you open an account. They focus on data collection, payment records, cookies, access requests, corrections, and account closure. If your request depends on local law, we will tell you what we can action and what extra verification is needed.

We collect data you provide during account setup, login, payment checks, support chats, and gameplay records. This may include contact details, device signals, transaction references, cookie data, and security events tied to your account.

Yes. Send a request from the email or mobile number connected to your account. We may verify identity first, then share the account data we can provide under applicable law and security duties.

Yes, you can ask us to correct contact details or account records that are inaccurate. Some payment and security records may need supporting proof before we change them, especially where audit duties apply.

We use payment references to match deposits, process withdrawals, resolve wallet disputes, and meet record duties. We do not need your full bank profile for routine wallet matching inside the account.

Cookies help keep you signed in, remember settings, protect sessions, and measure site performance. Some cookies are necessary for login and wallet safety, while browser settings may let you block others.

Retention depends on the record type. Account, wallet, security, and dispute records may be kept while required for operations, legal duties, tax records, fraud prevention, or unresolved privacy requests.

After closure, we restrict active account use and keep only records needed for security, disputes, tax, payment history, or legal duties. When those reasons end, we delete or de-identify records where practical.