Reference

Open sattta Privacy Policy for India

This page explains how sattta handles your account data, device details, cookie signals and payment records when you open an account or contact us.

Account dataCookie choicesPayment recordsLocal law
sattta Open sattta Privacy Policy for India
REQUEST CHANNELS

Explore privacy contact paths today

If you want to ask about access, correction, deletion or a consent change, write from the email linked to your account or use the contact form in your account area.

Email us Send your privacy query from the email address linked to your account, or include enough account details for us to verify you. We use that channel for access, correction, deletion and consent questions.
Account form If you are logged in, use the contact form in your account area for faster routing. It lets us tag the request to the right record set and keep the conversation in one thread.
Written request For formal written notices, ask support for the current postal address. We will tell you the route for paper requests and the proof we need before any record is changed.
HANDLING STANDARDS

Switch to careful data handling

We keep this policy practical: collect only what is needed, limit who can see it, and separate routine support from formal account checks.

Data minimisation

We ask for basic account details, contact fields and payment references only when they are needed to open, verify or…

Cookie control

Cookies and similar tools help keep you signed in, remember language choices and measure whether pages load correctly.

Security checks

When you log in from a new device or try a sensitive change, we may ask for extra confirmation.

Payment trace

Transaction references from UPI, Paytm, PhonePe or Google Pay are retained so we can match deposits, withdrawals and support messages.

Retention windows

Records stay only as long as needed for service, security, tax, audit or legal duties.

Your requests

You can ask to see, correct or delete eligible records.

Open common privacy questions here

These common questions focus on how your data is handled, how long it stays with us and how you can ask for updates. The short version is simple: we keep what we need to run your account, protect it from misuse and respond to formal requests. If access is available where local law permits, the same rules apply across the account flow.

We usually start with the details needed to open and service your account: contact fields, login setup, device signals and any payment reference you add. We keep the list tight and use it only for the stated purpose.

Cookies help remember session state, language choice and whether a page loaded correctly. They also let us spot repeated errors or unusual access patterns, so we can keep the account flow readable and stable.

Only when a service partner or payment rail must handle the request, or when a legal demand requires a reply. We do not hand over extra data if a smaller record is enough for the task.

We keep each record for the time needed to run the account, settle a dispute, complete security checks or meet law and tax duties. After that, the record is removed, masked or archived in line with its type.

Yes. Send the correction request from your account email or through the form in your account area. We may ask for confirmation first, then update the field that can be changed and explain any item that must stay.

You can ask, and we will check whether the record is still needed for legal, security or support reasons. If removal is allowed, we act on the eligible parts and tell you what could not be erased.

Use the email linked to your account or the contact form in the account area. If you need a written route, ask support for the current address and include enough details for us to locate the record.