Reference

Privacy Policy for your India account

Baccarat, Maharajah, Football Strike, Aviator, Bingo and Fishing God each create account activity, payment checks and support records, and this Privacy Policy explains how sattakingnews handles that data.

UPI data usePaytm recordsPhonePe checksGoogle Pay contextIndia privacy contact
sattakingnews Privacy Policy for your India account
CONTACT ROUTES

Privacy contact paths in India

Privacy requests should come from the same mobile number, email, or account channel you use with us, so we can verify the request without exposing your data. We may ask for a short match check before sharing, correcting, restricting, or deleting account records. If your issue relates to a payment reference, include the UPI, Paytm, PhonePe, or Google Pay transaction ID, but never send a PIN, OTP, or full bank password.

Team online

Email privacy desk

Send us the mobile number or email linked to your account, the request you want handled, and any screenshot that shows the issue. We confirm receipt before changing privacy data.

Account chat check

Use the chat inside your account when you can still log in. It lets us match your request to account records, payment references, and device history without asking for extra personal detail.

Security escalation

If you think another person has accessed your account, contact us quickly. We may pause sensitive privacy changes while we check logins, device records, wallet activity, and payment references.

HANDLING STANDARDS

How we manage privacy requests

We treat privacy work as part of account safety, not as a separate formality. Each request is checked against your account channel, recent login pattern, and any payment…

Data we collect

We collect account contact details, login records, device signals, wallet actions, game activity, and support messages.

Cookie use

Cookies and similar tools keep you signed in, remember language and device choices, and help us spot repeated failed logins.

Payment privacy

For UPI, Paytm, PhonePe and Google Pay, we store transaction references, status, amount, time, and account match data.

Account security

We monitor unusual login patterns, device changes, failed password attempts, and wallet movement.

Retention period

We keep records while your account is active and for required periods after closure when legal, tax, payment, dispute, or…

Change requests

You can ask us to correct contact details, update consent choices, or close parts of your record where the law…

Questions on your account data

These answers explain how we handle common privacy requests connected with account access, wallet records, cookies, support chats, and game activity. They are written for India account holders and do not replace legal terms that may apply to your state or location. When eligibility or access is discussed, it depends on local law and is available where local law permits.

We collect contact details, login records, device signals, wallet actions, payment references, game activity, and support messages. We use this data to run your account, verify requests, handle disputes, and protect access.

Payment references help us confirm deposits, withdrawals, refunds, failed transactions, and account ownership. We store transaction status, time, amount, and match data, but we do not need your banking password, PIN, or OTP.

Yes, you can contact us from your account email, mobile number, or chat channel and ask for a copy. We verify your identity first so your data is not sent to another person.

Send a correction request through account chat or the privacy email path. We may ask for a short verification check before changing contact details, especially if recent logins or wallet activity look unusual.

We keep records while needed for account operation, payment checks, disputes, security, tax, and legal duties. When those reasons no longer apply, we delete the data or make it anonymous where possible.

Cookies help keep your session active, remember device choices, and detect failed access attempts. You can adjust browser controls, but some account functions may not work correctly if required cookies are blocked.

Use the email or chat path linked to your account and include the request type, account mobile number, and any relevant payment reference. Do not send OTPs, PINs, or full bank passwords.