Reference

Privacy controls for your 1sattamatka account

When you open your 1sattamatka account, our Privacy Policy explains what data we collect, why we need it, and how payment records linked to UPI, Paytm, PhonePe and…

Account data explainedCookie choicesUPI privacy contextContact path included
1sattamatka Privacy controls for your 1sattamatka account
CONTACT ROUTES

Reach us about your privacy choices

Privacy questions should reach the right desk without forcing you through unrelated account chat.

Privacy email Send privacy requests to the email shown on 1sattamatka.
Live support handoff If you contact chat first, ask for a privacy handoff and avoid sharing full…
Payment record help For UPI, Paytm, PhonePe or Google Pay concerns, share the transaction reference and date…
DATA CARE

How we handle your account data

Our privacy work sits inside the same account systems that handle login, wallet activity and support replies.

Account details

We collect details you provide during account creation, such as mobile number, email, login name and verification data. These records help us manage access, reply to you, and prevent another person from changing your profile.

Payment references

UPI, Paytm, PhonePe and Google Pay records may include transaction IDs, timing, amount, status and linked wallet movement. We use these records to confirm deposits, process withdrawals and handle payment disputes.

Cookies and device data

Cookies help keep you signed in, remember basic choices and spot unusual access attempts. Device data such as browser type, IP range and session timing may be used to protect your account.

Game activity records

When you open Aviator, Fishing War, Football Strike or a live table, session records may show timing, stake actions and wallet movement. We keep these records to settle disputes and maintain account history.

Retention periods

We keep account and payment data only for business, legal, tax, security or dispute needs. When records are no longer required, we delete, anonymise or separate them from direct account identifiers.

Change requests

You can ask us to access, correct or delete eligible data. We may keep certain records if a payment issue, legal duty, security check or unresolved account matter requires retention.

Privacy Policy questions before you join

Before you open an account, it is worth knowing how your data moves through the service. These answers focus only on privacy: what we collect, how payment details are handled, how cookies work, and how you can contact us. If local rules affect access, availability depends on the law where you are located.

We may collect your mobile number, email, login details, verification records, device signals, cookie choices, wallet history and support messages. The exact data depends on the account action, payment method and security checks involved.

We keep payment references to match deposits and withdrawals with your wallet, resolve failed transfers, answer payment questions and meet record duties. We do not need your full banking credentials for these checks.

Yes. Contact the privacy email or support handoff with the detail that needs correction. We may verify your identity first, especially if the change affects login access, wallet records or payment confirmation.

Cookies help with login sessions, language choices, security checks and basic site measurement. You can adjust browser settings, but some account and wallet functions may not work correctly if essential cookies are blocked.

Payment providers may receive transaction details needed to process or confirm UPI, Paytm, PhonePe or Google Pay activity. We share only what is needed for the payment, dispute handling, safety checks or legal duties.

Write to the privacy contact with your account mobile number and deletion request. We will review what can be removed and explain any records that must remain for payment, legal, tax or security reasons.

Yes. Account access, available features and some privacy handling steps may depend on local law. We provide access where local law permits and may adjust requests if a local rule requires a different process.