Reference

Open your account with clear privacy terms

sattaking explains what account data we collect, why we use it, and how privacy requests move through our support team before you open your account.

Account data useCookie choicesUPI contextPrivacy contact
sattaking Open your account with clear privacy terms
CONTACT PATHS

Reach us about privacy choices

Privacy requests work better when you contact us from the same mobile number or email linked to your account.

Email privacy desk Write to our privacy desk with your registered mobile number or email, the data…
Live chat handoff Use chat when you need help locating the correct privacy contact path.
Account correction request Ask us to correct account details that are incomplete or out of date.
ACCOUNT CARE

Explore how we handle your data

Our privacy work is tied to everyday account operations, not a separate promise hidden in legal text.

Data collection

We collect the data needed to create your account, maintain login access, process transaction checks, respond to support messages and meet legal duties. We do not collect extra personal data just to fill a profile.

Cookie use

Cookies help us remember your session, language choice, device state and security signals. You can clear cookies in your browser, though doing so may require a fresh login and extra account checks.

Payment privacy

For UPI, Paytm, PhonePe and Google Pay, we may store transaction references, status messages and wallet matching data. We do not need your payment app password, PIN or private banking credentials.

Security checks

Login alerts, IP patterns, device changes and failed password attempts may be recorded to protect your account. When a risk flag appears, we may ask you to confirm ownership before access continues.

Retention period

Some records are kept while your account remains active and for a lawful period after closure where required. When data is no longer needed, we delete it or remove personal markers where possible.

Change requests

You can ask us to correct, access or delete personal data linked to your account. We first verify the request, then explain what can be changed and what must stay for legal or security reasons.

Ask privacy questions before you join

These answers explain the practical parts of our Privacy Policy in plain language for India. They cover the data we collect, why payment context appears in account records, how cookies work, and how you can contact us for access, correction or deletion requests. If your situation involves a local legal rule, our support team will explain how that affects the request.

We collect account details you provide, such as name, mobile number, email address, login data and support messages. We may also collect device signals, IP address, cookie choices and payment references linked to your activity.

UPI, Paytm, PhonePe and Google Pay references help us match deposits, check withdrawal requests and resolve transaction disputes. We store reference data and status details, not your app password, PIN or banking secret.

Yes. Contact us from your registered mobile number or email and tell us what needs correction. We may ask for identity clues before changing personal data, so another person cannot alter your account.

We keep data for as long as it is needed for account access, security checks, transaction records, support handling and legal duties. When the reason ends, we delete it or remove personal markers where possible.

Cookies help keep you signed in, remember settings and detect unusual access. You can clear them through your browser, but the next visit may ask for a fresh login or extra security confirmation.

Access is limited by work role. Support can see messages needed to answer you, wallet staff can see transaction references, and security staff can inspect login signals when account protection requires it.

Send a deletion request through the privacy contact path using your registered contact detail. We will verify ownership, explain what can be removed, and identify any records that must remain for legal or security reasons.