Reference

Open our Privacy Policy

Our Privacy Policy explains how we collect, use, protect and update data linked to your account, wallet and device on satsport11.

Account dataUPI privacyCookie controlsContact choices
satsport11 Open our Privacy Policy
CONTACT ROUTES

Check your privacy contact choices

Privacy questions should reach the right team without making you repeat the same details. Use the contact path that matches your request, and include your registered mobile number or email only when…

Email privacy desk Write to our privacy inbox for access, correction, deletion or cookie questions. Share the account identifier you used to join, describe the request clearly, and avoid sending card images or extra identity files unless we ask.
Live support handoff If you start in chat, ask for a privacy handoff and we will route the request to the team that handles account data. Chat agents can confirm receipt but may not change sensitive records directly.
Account security help Use this route if you suspect unwanted access, a changed mobile number, or an unfamiliar withdrawal request. We pause sensitive actions while checks are completed and explain what privacy data was affected where possible.
DATA PRACTICE

Browse our privacy handling standards

Our privacy work follows the account journey: join, verify, deposit, withdraw, contact support and close an account. Each step uses only the data needed for that purpose.

Account records

We store the details needed to run your account, such as contact data, login status, verification outcome and account settings. These records help us confirm access, protect your wallet and answer your privacy requests.

Payment data

For UPI, Paytm, PhonePe and Google Pay, we receive transaction references, amounts, status updates and timing. We do not need your full banking credentials, and payment partners handle their own processing steps.

Cookies and device logs

Cookies help keep you signed in, remember basic choices and detect unusual account activity. Device logs can include browser type, IP address, session time and error events used for security and service repair.

Security access

Internal access is limited to teams that need data for support, payments, risk checks or privacy responses. We use role controls, activity logs and extra checks before sensitive account changes are accepted.

Retention periods

We keep personal data only for account operation, transaction records, dispute handling, security checks and legal duties. When records are no longer needed, we delete, anonymise or restrict them according to the record type.

Change requests

You can ask to correct contact details, access data we hold, or request deletion where applicable. We may retain limited records when required for payment history, dispute files or legal compliance.

Discover answers about this policy

These answers explain the main privacy choices linked to your account. They focus on data collection, use, sharing, retention and contact steps rather than general lobby activity. If your question is account-specific, contact us from the email linked to your profile.

We collect data you provide during account use, such as name, mobile number, email address, payment references and support messages. We also collect device, cookie and session data needed for security, wallet checks and account access.

Payment data helps us confirm UPI, Paytm, PhonePe or Google Pay transaction status, match deposits to your wallet and check withdrawal requests. We use references and status updates, not your full banking credentials.

Yes. Send a request from your registered email or through support, and we will verify that it is you. We then provide the account data we can share under applicable law and security rules.

Contact support with the detail that needs correction, such as email spelling or mobile number. For sensitive changes, we may ask for extra checks before updating records so your account is not altered by another person.

We share only the data needed to process or confirm transactions, resolve failed payments and handle disputes. UPI, Paytm, PhonePe and Google Pay may also apply their own privacy terms to their processing.

Retention depends on why the data was collected. Account, payment and security records may be kept for transaction history, dispute handling, fraud prevention and legal duties, then deleted, anonymised or restricted when no longer required.

Use the privacy email path or ask support to route your message to the privacy team. Include your registered contact detail, describe the concern clearly, and avoid sending extra documents unless we request them.