Reference

How We Handle Your Data

This page explains what zx6r collects when you create an account, why we use it, and when we may keep or delete it.

Account dataCookie useData requestsLocal law

When This Policy Applies

zx6r Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This policy applies to account creation, account access, support messages, and any payment step that touches your profile. We may collect details you give us directly, such as name, contact number, chosen username, and identity documents, along with device, cookie, and session data that helps us

1
keep sign-in and support records in order. If you send a request from India, we process it under the law that applies to your location and the records we must keep for security, tax, dispute handling, and fraud checks. Where local law permits, you may ask
2
for access, correction, or deletion. Some records must stay for a fixed period even after you close the account, and we will tell you why when that applies. This can include activity tied to UPI, Paytm, PhonePe, or Google Pay when those rails are used in
3
a supported flow.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

HELP PATHS

Where to Send Privacy Requests

For privacy requests, use the same contact paths we keep open for account holders: email, in-account message, or the form tied to your profile.

Email Support Send your request from the address linked to your account so we can confirm ownership before sharing stored data, changing details, or closing a thread. We reply with the next step and any verification we need.

In-Account Message If you can still log in, use the message panel inside the account. It keeps the conversation tied to your profile and helps us match a correction, access request, or deletion request to the right record.

Contact Form Use the form on the site when you cannot reach the inbox. Add the phone number or email on the account, the change you want, and any date range that helps us find the record faster.

HANDLING RULES

How We Keep Data in Order

We store profile data, transaction logs, and support threads separately from cookie signals so each record serves a clear purpose.

Data Collection

We collect only the details you submit or that your device sends during sign-in, plus support and verification records. That lets us confirm your account, answer requests, and keep a clear trail of changes.

Cookies

Session cookies help keep you signed in, remember language choices, and protect the handoff between pages. You can clear them in browser settings, though some parts of the site may ask you to sign in again.

Security Checks

When you ask for a sensitive change, we may ask for a code or matching account details before we act. We do this to reduce mistaken edits and to stop someone else from changing your record.

Retention

We keep records only for as long as needed for support, security, dispute handling, tax, or legal duties. After that, we remove or mask them in line with the law that applies.

Your Requests

You can ask to see, correct, or delete the details linked to your account. Send the request through the contact path on this page, and we will check your identity before making a change.

Contact Trail

We keep the request thread so you can follow what was asked, what was changed, and when we replied. That record helps us answer repeat questions without asking you to explain the same matter again.

Privacy Questions We Hear Most

These questions cover access, correction, deletion, cookies, and how we handle stored records. If your situation is different, send the request through the contact path above and we will answer using the details tied to your account. Where local law permits, we can explain what we hold and why some records stay for a fixed time. That keeps the process clear without making you repeat the same points.

We collect the details you give during sign-up, the contact fields linked to your profile, and the device or session signals needed to keep the account secure. We may also store support messages and verification records.

Cookies help us keep you signed in, remember language choices, and route you between pages without losing the session. You can clear them in your browser, but some actions will ask for sign-in again.

Yes. Send the request through email, in-account message, or the site form tied to your profile. We may ask for a match to the account before sharing stored details, and local law can affect timing.

Yes. Tell us which field is wrong and send the correct version, along with the mobile number or email on the account. We update the record after verification and keep a trail of the change.

We keep records only as long as needed for support, security, dispute handling, tax, or other legal duties. When that period ends, we remove or mask the data unless the law asks us to keep it longer.

Use the same contact path listed here and mention that your request is about this policy. If local law permits, we can explain what we hold, what we can change, and what must stay on file.

How We Handle Your Data

Where to Send Privacy Requests

How We Keep Data in Order

Data Collection

Cookies

Security Checks

Retention

Your Requests

Contact Trail

Privacy Questions We Hear Most

01 What data do you collect from my account?

02 Why do you use cookies?

03 Can I ask for a copy of stored data?

04 Can I correct my details?

05 How long do you keep records?

06 Who should I contact about this page?

Related Pages