Reference

Privacy Policy for Your India Account

Your starbet privacy choices sit beside the account flow, covering sign-in data, device checks, cookies and payment records from UPI, Paytm, PhonePe and Google Pay.

India account dataUPI privacy contextCookie choicesContact routes
starbet Privacy Policy for Your India Account
HELP ROUTES

Privacy Help Through India Channels

Privacy requests should reach the team that can verify your account safely. Use the signed-in help form when you can, because it lets us match your request to the right account without…

Signed-in help form Send privacy requests from your account area when possible. We can confirm ownership through your current session, check recent sign-in activity and reply without asking you to share extra identity data in open email.
Email contact If you cannot access your account, write to the email address listed in the footer. Mention your registered mobile number or email, describe the privacy request clearly and avoid sending card images or full payment screenshots.
Payment privacy query For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction reference only if needed. We use it to trace wallet records, not to request your PIN, password or full bank details.
ACCOUNT CARE

Controls for UPI and Account Data

Our privacy work covers the full account path: registration, sign-in, wallet checks, game session logs, cookies, device security and support replies.

Account data we collect

When you create an account, we collect details such as name, mobile number, email, login records and device data.

Payment record handling

UPI, Paytm, PhonePe and Google Pay references are used to match wallet activity with payment status.

Cookies and device checks

Cookies help keep you signed in, remember privacy choices and detect risky access patterns.

Game session privacy

Activity in Roulette, Tower, Football Strike, Spribe Aviator, Bingo or Fishing God may create session records.

Retention and removal

Some records are kept for legal, tax, fraud prevention or dispute reasons.

Requests and changes

You can ask to access, correct or remove eligible personal data.

Privacy Questions Before You Join

These answers explain the practical parts of the Privacy Policy before you create or manage an account. They cover what data we collect, how payment references are handled, how cookies work, when we keep records and how you can ask for access or changes. For anything personal to your account, contact us through a verified route.

We collect data needed for your account, such as name, mobile number, email, sign-in records, device signals, cookie IDs, payment references and account activity. We use it for access, security, wallet accuracy and legal duties.

Payment references help us match wallet activity with your account and investigate failed or delayed transfers. We do not need your UPI PIN, bank password or private wallet passcode for any privacy request.

Yes, you can ask for a copy of eligible personal data through the signed-in help form or footer email. We may verify your identity first and may withhold records that affect security or legal duties.

You can request corrections when your personal data is wrong or outdated. Some changes, such as mobile number or payment-linked details, may need extra verification so we protect the account before making updates.

Retention depends on the record type and the reason it was collected. Account, payment, security and dispute records may be kept while legal or operational needs apply, then deleted or anonymised when no longer needed.

Cookies remember sign-in status, device checks and preference choices. You can manage many cookies through your browser, but blocking essential cookies may affect account access, security checks or the way privacy settings are saved.

Access and eligibility depend on local law and are available where local law permits. If a location rule affects your account, privacy records may still be kept where needed for security, legal or dispute reasons.