Reference

How we protect your data

Our Privacy Policy explains what we collect when you open an account, verify your wallet, use UPI, Paytm, PhonePe or Google Pay, contact support, or browse the lobby.

Account dataWallet checksCookie controlsSupport records
sattazone How we protect your data
CONTACT PATHS

Three ways to reach privacy support

Privacy questions should not feel buried inside general account support. We keep separate routes for data access, correction and deletion requests, so your message reaches the right team with the right context.

Email request Write to our privacy mailbox from the email linked to your account. Tell us whether you want access, correction, deletion or cookie help, and we will verify ownership before changing any record.
Live chat handover Start with chat if you are already signed in and need quick routing. The agent can raise a privacy ticket, confirm basic account details, and tell you what proof is needed next.
Account message Use the message option inside your profile for requests tied to wallet references or login history. This helps us connect the request to your account without asking for extra personal data.
DATA HANDLING

Six checks inside our privacy process

We handle privacy requests through a fixed internal process rather than ad hoc replies.

Collection limits

We collect account details, contact data, device signals, wallet references and support messages only when they help us run, secure, verify or maintain your account under this Privacy Policy.

Cookie choices

Cookies help keep you signed in, remember settings and detect unusual access. You can manage many cookie settings through your browser, though some changes may affect account screens.

Account security

Login activity, IP patterns and device details are checked for unusual access. If a request looks risky, we may pause account changes until we confirm it came from you.

Retention periods

We keep records only while needed for account service, payment tracing, safety checks, dispute handling or legal duties. When retention is no longer required, we remove or anonymise data.

Data correction

If your email, mobile number, name spelling or address data is wrong, send a correction request. We may ask for supporting proof before updating fields linked to wallet checks.

Request tracking

Each privacy request gets logged with its status, response date and outcome. This helps us answer follow-up questions without asking you to repeat the same details again.

Answers about your privacy rights

These answers explain how our Privacy Policy works in everyday account situations. They cover the data we collect, why we keep certain records, how to contact us, and what happens when you ask for access, correction or deletion. If your request involves legal eligibility, availability depends on local law and where local law permits.

We collect the details needed to create and maintain your account, such as name, contact details, login records, device signals and verification data. We also keep wallet references linked to account activity.

Payment references help us match deposits, withdrawals, refunds, disputes and support requests to the right account. We use these references for tracing and verification, not for unrelated outreach.

Yes. Send a privacy request from your registered email or signed-in account area. We will verify ownership first, then share the data we can provide under applicable legal and security rules.

Contact privacy support with the field that needs correction and the right value. For changes connected to payment checks, we may request proof before updating the account record.

You can ask us to delete data, and we will assess the request under this Privacy Policy. Some records may be retained where needed for legal duties, disputes, payments or safety checks.

Cookies do not store full payment details. They mainly support login sessions, preferences and security checks. Wallet references are handled in account systems with access controls, not ordinary browser cookies.

Use the privacy email, signed-in account message or chat handover route. Share your registered contact detail, request type and a short explanation so we can verify and respond correctly.