Reference

Open Your Privacy Policy View

Turbo Blackjack, Live Dragon Tiger and UPI wallet access create account data we explain plainly in this Privacy Policy, from sign-in records to payment checks.

Account data explainedUPI privacy contextCookie choicesIndia access wording
4bet Open Your Privacy Policy View
CONTACT ROUTES

Browse Your Privacy Contact Routes

Privacy questions need clear routing, not a generic chat loop. Use the paths below when you want to inspect account data, correct a contact field, ask about cookies, or raise a security…

Email privacy desk Write to [email protected] with the mobile number or email linked to your account. We use those details only to locate your profile, check ownership and reply to the privacy request. If you write from another address, we may ask ownership proof.
In-account help Open the help panel after sign-in and choose the privacy query option. That route carries your account ID automatically, so we can check your request without asking for extra copies first or moving data across channels.
Security report If you think your login, payment data or device record has been misused, tell us through [email protected]. We may pause risky access while we check the account trail and reply through your verified contact route.
DATA CARE

Check How We Handle Data

Our policy work is practical: collect what the account needs, protect it during use, and remove or detach it when retention is no longer required.

Account data we collect

When you open an account, we collect contact details, login records, device signals and wallet references. We keep the fields tied to account creation, security checks, payments and support handling, rather than collecting data unrelated to account operation.

How we use it

We use your data to run sign-in, keep the wallet tied to you, confirm payment routes and answer privacy requests. We do not sell your personal data to outside ad lists, and service vendors receive only task-linked fields.

Cookies on your device

Cookies help remember session state, language choice and fraud signals when you return. You can adjust browser settings, but some account checks may need cookies to keep access stable and reduce repeated verification prompts.

Account security checks

We compare login location, device pattern and payment trail when an access attempt looks unusual. If the match fails, we may ask for a fresh code or extra ownership proof before exposing account or wallet data.

Retention and deletion

Some records stay for legal, fraud-prevention and payment reconciliation needs after account closure. When a record is no longer needed, we delete it or detach it from your profile so it no longer identifies you directly.

Change requests

Ask us to correct contact details, update consent choices or explain a data entry tied to your profile. We may need identity proof before making changes that affect account control, wallet access or security settings.

See Your Privacy Policy Answers

These answers explain the privacy points you are most likely to ask before or after you open an account. They focus on account data, payment references, cookies, sharing, retention and correction requests. If your case involves a court order, payment dispute or location-based access question, contact us so we can check the exact record. We will answer using the contact route already linked to your profile when possible.

We collect contact details, sign-in records, device data, payment references and support messages connected to your account. The exact fields depend on how you access the site, verify ownership and use UPI, Paytm or PhonePe.

UPI, Paytm, PhonePe and Google Pay records help match wallet activity to your account, handle reversals and answer payment privacy questions. We store references needed for reconciliation, not unnecessary bank account content or private payment credentials.

Yes. You can contact us to update consent choices, correct contact details or ask how a data field is used. We may verify ownership before making changes that could affect account access, wallet control or security settings.

Cookies record session state, device signals and preference choices so your account can stay secure while you move through pages. You can manage browser cookies, but some checks may be needed for sign-in and fraud prevention.

We share data only where needed for payment processing, identity checks, fraud prevention, technical hosting, support handling or legal duties. Each recipient must use the data for the agreed purpose, not unrelated outreach or data resale.

Retention depends on the record type. Payment, security and legal records may stay longer than support chat text. When a record is no longer needed, we delete it or detach it from your profile.

Access and eligibility depend on local law and are available where local law permits. Location signals may be checked to apply those rules, protect the account and keep activity aligned with this Privacy Policy.