Reference

Privacy Policy for India Accounts

Your account profile, UPI, Paytm, PhonePe and Google Pay records, device data and cookie choices are covered here so you can see how mysattakings handles privacy before you…

India privacy termsUPI data contextCookie choicesAccount request path
mysattakings Privacy Policy for India Accounts
REQUEST PATHS

Three Paths for Privacy Requests

Privacy questions should reach the team that can trace account records without exposing your data in public chat.

Account email Send privacy requests from the email linked to your account so we can match…
Live chat handoff If you start in chat, ask the team to move the matter to a…
Security escalation Use the security route if you notice an unknown login, changed contact detail, or…
CARE STEPS

Six Ways We Handle Privacy

Our privacy handling is designed around practical account events: opening an account, logging in, using payments, changing devices, contacting support and closing records when retention no longer applies.

Account data

We collect details you provide during account setup, such as name, contact data and login credentials.

Payment records

UPI, Paytm, PhonePe and Google Pay references may be stored with transaction status, timestamps and account links.

Cookie settings

Cookies help keep you signed in, remember language or region choices and detect unusual access patterns.

Security logs

We record login time, device type, browser signals and IP data to detect suspicious access and protect your account.

Retention checks

Some records must remain for tax, dispute, fraud prevention or legal reasons, even after you ask for deletion.

Change requests

You can ask us to access, correct or erase personal data, subject to verification and legal retention needs.

Privacy Questions Before You Join

These answers explain the privacy choices you may want to check before opening an account. They focus on what we collect, why we need it, how payment references are handled, when cookies apply and how you can contact us for changes. If a request affects wallet records, security logs or legal retention, we may verify your identity before taking action.

We collect account setup details such as your name, contact data, login credentials, device signals and region context. We also record activity needed for security, payments, support requests and legal record keeping.

We store payment references, transaction status, timestamps and account links so wallet activity can be matched and checked. Full sensitive payment credentials should not be sent to support unless we request them through a safer route.

Yes. Contact us from your linked email and ask for data access. We may verify account control first, then provide the relevant records or explain why some records cannot be shared due to legal or security reasons.

Yes. Tell us which detail needs correction and share enough account proof for verification. Some changes, especially contact or payment-linked updates, may need extra checks before we update the record.

You can request deletion, and we will act where we can. Some records may remain for dispute handling, fraud prevention, tax, security or other legal duties until the required retention period ends.

Cookies and similar tools help with login sessions, language choices, fraud checks and service performance. You can adjust browser settings, though essential cookies may still be needed for secure account access.

Use the account email path or ask chat to move your concern to a privacy request thread. Include your username, request type and a brief description, but avoid sharing sensitive documents until asked.