Reference

Privacy Policy for your saataking account

Your saataking account connects lobby activity, account access, and UPI, Paytm, PhonePe payment records under one Privacy Policy, so you can see what data we collect before you…

UPI data carePaytm record accessPhonePe privacy checksCookie choices
saataking Privacy Policy for your saataking account
CONTACT ROUTES

Three ways to reach privacy help

Privacy questions need a clear route, not a maze. Use the same name and account email you used with us so we can match the request safely.

Privacy email Write to our privacy inbox with your account email, request type, and the date range involved. We may ask one verification question before sharing account data or making a privacy change.
Account help desk Use live help after you sign in if the request concerns cookie choices, login sessions, or a recent payment record. Our team can raise a privacy ticket without asking for sensitive codes.
Payment record query For UPI, Paytm, PhonePe, or Google Pay privacy requests, send only the UTR or transaction ID. We use that reference to locate records while keeping unrelated wallet data out of view.
ACCOUNT SAFEGUARDS

Six controls around your data

We treat the Privacy Policy as an operating rule for account data, not a page kept aside.

Data we collect

We collect account details, contact fields, device signals, session logs, wallet references, and support messages. We avoid asking for extra documents unless a security check, payment issue, or legal duty requires it.

Cookie choices

Cookies help us remember your session, protect sign-in attempts, and understand basic page performance. You can change browser settings, though some account functions may need essential cookies to work.

Login protection

We monitor unusual sign-in patterns, repeated failed attempts, and device changes. If we see a risk, we may pause access until you confirm the account through the contact details already on file.

Payment privacy

UPI, Paytm, PhonePe, and Google Pay references are used to match wallet activity with your account. We keep payment records separate from support chat unless you ask us to investigate a specific transaction.

Retention periods

We keep account and payment records only as long as needed for service, dispute handling, security, and legal duties. When retention is no longer needed, records are deleted or de-identified where practical.

Correction requests

You can ask us to update contact details, correct a payment reference, or delete data that is no longer needed. We verify your identity first so another person cannot change your account record.

Privacy Policy questions before you join

These answers explain how the policy works in common account situations. They cover data rights, payment references, cookies, device access, support contact, and record changes. If your question needs account-specific handling, contact us with your account email and the relevant date range.

We collect the details needed to create and protect your account, such as name, contact fields, login records, device data, wallet references, and support messages. Extra checks may apply where law or payment safety requires them.

We keep transaction references so deposits, withdrawals, refunds, and payment disputes can be matched to your account. These references also help us answer privacy requests without exposing unrelated banking or wallet data.

Yes, you can request a copy through our privacy email or signed-in help route. We verify your identity first, then share the account data we can release under applicable law and security rules.

Cookies help keep you signed in, protect account sessions, and measure basic site performance. You can adjust browser settings, but turning off essential cookies may affect sign-in, wallet display, or support access.

Access is limited to teams and service partners who need the data for account support, payment processing, security checks, or legal duties. We do not publish your personal account records on public pages.

Send a correction request with your account email and the field that needs changing. We may ask for verification before updating contact details, payment references, or records linked to previous support conversations.

Yes. Account access, eligibility checks, and some privacy rights depend on local law and are available where local law permits. If a rule affects your request, we will explain the account-specific reason.