Reference

Privacy choices for your India account

When you open an account with satkamatka for Speed Baccarat, Wild Fireworks, Crash Game or wallet activity, this Privacy Policy explains what data we collect and why.

Account dataUPI recordsCookie choicesPrivacy requests
satkamatka Privacy choices for your India account
CONTACT PATHS

Where to ask privacy questions

Privacy questions need a clear route, not a general chat loop. Use the contact path that matches your request so we can verify the account, locate the record and reply with the right context. We may ask for extra details before changing, sharing or deleting account data.

Team online

Account privacy help

Ask us about the profile details linked to your account, including name, mobile number, email, login history and verification status. We will check account ownership before sharing or changing any personal record.

Payment data queries

For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction time, amount and visible reference. We use those details to trace status records without asking for your bank PIN.

Cookie and device requests

If you want to discuss cookies, device identifiers or browser storage, tell us the device type and browser used. We can explain what is stored, why it helps security and how choices work.

HANDLING RULES

Privacy handling behind the account

Our privacy work sits behind every account action: login, wallet checks, table access, support messages and security alerts.

Data we collect

We collect account details, contact data, login signals, device identifiers, wallet references and support messages. Game choices such as Fishing God or Bingo may create session records used for security and account history.

Why we use it

We use data to create your account, keep login access safe, process wallet records, answer support messages, detect misuse and meet legal duties. We do not ask for private banking passwords or card PINs.

Cookies and storage

Cookies help remember your session, language, device checks and safety prompts. Some cookies are needed for account access, while others help us understand errors, page load issues and repeated failed logins.

Account security

Security records can include IP address, device type, failed login attempts and verification results. If activity looks unusual, we may pause sensitive changes until you confirm account ownership through support.

Retention approach

We keep personal data only for account operation, dispute handling, legal duties, fraud checks and support records. When a record is no longer needed, we delete it or reduce it where practical.

Your request route

You can ask to access, correct or erase eligible personal data. We may retain records required for legal, security or transaction reasons, and we will explain the reason in our reply.

Questions about your privacy policy rights

These answers explain how privacy requests work after you open or use an account. They focus on account data, payment references, cookies, security checks and contact routes. For any request, we verify account ownership before sharing or changing personal data.

We collect details needed to operate your account, such as contact data, login records, device signals, wallet references and support messages. We also keep security logs when you access games or request account changes.

No. For UPI, Paytm, PhonePe and Google Pay, we store transaction references, amounts, timestamps and status signals. Your private banking PIN, app password and bank login details are not collected by us.

Contact support with your registered mobile number or email and the request you want to make. We will verify account ownership, locate eligible records and reply with the data or an explanation.

Yes, you can ask us to correct eligible account details if they are inaccurate. For security, we may need proof that the account belongs to you before changing contact, identity or wallet records.

Cookies can remember your session, device checks and page preferences. They also help us detect failed logins or technical errors. You can manage browser storage, but some account functions may need cookies.

Some records may remain where legal duties, transaction checks, disputes, fraud prevention or account security require retention. We will reduce or delete eligible records when those reasons no longer apply.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests are handled within applicable legal requirements, including verification steps before account data is shared.