Reference

Open Your Privacy Choices Clearly

Your s680 account privacy choices cover login records, cookies, UPI, Paytm, PhonePe and Google Pay references, plus the way support checks identity before changing account details.

India account dataUPI privacy contextCookie choicesSupport verification

Browse Lobby Read FAQ

Explore s680 Privacy Rules for India

s680 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy explains what account data we collect, why we use it, when we share it with service providers, and how you can ask us to correct or remove details linked to your profile. We use personal data to create your account, secure sign-ins, process

1
wallet records, answer privacy requests, and keep transaction evidence required by applicable law. Payment references from UPI, Paytm, PhonePe and Google Pay are treated as account data, not as public material. We do not publish your name, payment handle or game session history. Where local law
2
requires a different retention period, access rule or disclosure step, we follow that requirement. Access to any part of the service depends on local law and is available where local law permits.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Browse Contact Routes for Privacy Requests

Privacy requests need a clear trail so we can protect your account from mistaken changes.

DATA CARE

Switch Privacy Controls With Care

We apply this policy inside the account flow, wallet records and support desk rather than treating privacy as a separate form.

Account data collected

We collect details you give during account setup, such as mobile number, email, login name and region. We also keep device, session and security markers needed to recognise suspicious access attempts.

Payment privacy

UPI, Paytm, PhonePe and Google Pay references are used to match wallet activity with your account. We store transaction IDs, amounts and timestamps, while sensitive payment credentials remain with the payment provider.

Cookie controls

Cookies help keep you signed in, remember language choices and measure page errors. You can adjust browser settings, though some account functions may ask you to sign in again after cookies are cleared.

Game session records

Session records may show whether you opened Blackjack, Wolf Pack, Football Strike, Cash or Crash, Bingo or Fishing War. We use those records for account history, dispute checks and fraud prevention.

Retention approach

We keep account and transaction data only for business, security and legal reasons. When the reason ends and law allows, we delete, anonymise or separate data from your live account profile.

Change requests

You can ask us to correct account details, close unnecessary records, or explain the data linked to your profile. We respond after ownership checks and may decline changes restricted by law.

Explore Your Privacy Questions

These answers explain how the Privacy Policy works when you create an account, use local payment methods, contact support or ask for changes. They are written for India account holders in plain language. If your request involves access or eligibility, the answer may depend on local law and is available where local law permits.

We collect the details needed to create and protect your account, such as mobile number, email, login name, region and device markers. We also record acceptance of policy terms and security checks tied to sign-in activity.

We use payment references to match deposits, withdrawals and wallet queries with your account. Transaction IDs, timestamps and amounts help support investigate issues, while sensitive payment credentials remain handled by the relevant payment provider.

Cookies may remember sign-in status, language choice and basic session activity. Game session records can sit separately in account logs, helping us manage disputes, security checks and service errors without making your profile public.

Yes, you can ask us to correct account details that are inaccurate or outdated. We will confirm ownership first, then update records we control unless a legal duty requires us to keep the earlier version.

We keep privacy request records long enough to show what was asked, how identity was checked and what action was taken. Retention periods may vary where law, dispute needs or payment records require a longer trail.

Access is limited to trained staff who need the data for support, security, payment matching or legal response. We avoid sharing personal data across teams unless the request is connected to your account or wallet record.

If local law changes how access or eligibility works, we may need to restrict certain account functions or request extra checks. We apply this only where required and keep privacy requests available where local law permits.

Open Your Privacy Choices Clearly

Browse Contact Routes for Privacy Requests

Switch Privacy Controls With Care

Account data collected

Payment privacy

Cookie controls

Game session records

Retention approach

Change requests

Explore Your Privacy Questions

01 What data do you collect when I create an account?

02 How are UPI, Paytm and PhonePe references used?

03 Do cookies track my game choices?

04 Can I ask s680 to correct my account data?

05 How long do you keep my privacy request records?

06 Who can see my account data inside the team?

07 What happens if local law affects my access?

Related Pages