Reference

Open your Privacy Policy choices

bitstarz privacy policy sets out how we collect account details, KYC files, device signals, cookies and wallet records from the moment you open an account.

Account data clarityCookie choicesIndia support pathsUPI record context

browse lobby Read FAQ

Explore bitstarz Privacy Policy scope

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

At bitstarz, this Privacy Policy is written to show what we collect, why we collect it and how long we keep it. Account details, device data, cookie signals, KYC files, chat transcripts and wallet references are handled for account operation, security checks, service replies, payment reconciliation

1
and legal duties. We do not sell your personal data. Where we use service providers, we restrict the purpose and require privacy and security terms. Access and eligibility depend on local law and are available where local law permits. If a law, regulator or court requires
2
a different handling step, we will follow that duty and keep the record of the request. You can ask us to access, correct or delete data, and we will explain any retention duty that prevents immediate deletion.

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

CONTACT ROUTES

Check your privacy contact routes

Your privacy request should reach us through a channel that can identify you without exposing extra data.

ACCOUNT CONTROLS

Control account data with bitstarz

Our handling rules are built around clear collection, limited access and documented retention. The policy covers account creation, KYC, wallet records, cookies, gameplay logs and support messages without turning those records into…

Data minimisation

We collect the data needed to create and protect your account, run wallet checks, answer service questions and meet legal duties. Extra files are not requested unless a specific verification or dispute step needs them.

Payment records

UPI, Paytm, PhonePe and Google Pay references may be stored with time, amount and status so the wallet ledger can be checked. We use those records for reconciliation, fraud checks and privacy request matching.

Cookie controls

Cookies help keep you signed in, remember language choices and measure page health. You can manage browser settings, and our policy explains which cookies are necessary and which support analytics or account safety.

Gameplay logs

Round IDs from Roulette, Leprechaun Riches, Football Strike, Spribe Aviator, Bingo or Fishing War may link to your account. We keep such logs to resolve disputes, audit results and answer data access requests.

Retention windows

We keep account data only for the periods needed for service delivery, legal duties, dispute handling and security checks. When a record is no longer required, we delete it or make it non-identifying.

Security controls

Access to personal data is limited by role, with password controls, device checks and internal logging. If we need to contact you about a privacy matter, we use account-linked channels.

Ask Privacy Policy questions before joining

Privacy questions usually arise before you open an account or when you change a device, payment app or document. The answers below explain what you can request, how we verify requests and why some records must be kept for legal or security reasons. If your case needs a personal reply, contact us from the account email so we can match the request safely.

Yes. Send a request from your account email or through signed-in chat, and tell us the scope you want. We may verify your identity before releasing files, especially where wallet or KYC records are involved.

Payment references from UPI, Paytm, PhonePe and Google Pay are handled as account data. We keep status, time and reconciliation fields so transactions can be matched, checked and answered when you raise a privacy request.

Cookies keep sessions stable, remember basic choices and help us spot account risk. Some are required for the site to work; others support measurement. You can adjust browser controls, though some account features may need cookies.

Yes. If your name, contact detail or document record is wrong, contact us from the account email. We will explain the correction step, ask for proof where needed and update the record when checks are complete.

Retention depends on the record type. Wallet logs, KYC files, security events and service messages may follow different periods because legal duties, disputes and fraud checks do not all end at the same time.

Only teams and service providers with a clear need can access personal data. We use role controls and logging, and we require external providers to handle data under privacy and security terms.

Access and eligibility depend on local law and are available where local law permits. Privacy requests can still be raised through the stated contact paths, and we will explain any legal limits that apply.

Open your Privacy Policy choices

Check your privacy contact routes

Control account data with bitstarz

Data minimisation

Payment records

Cookie controls

Gameplay logs

Retention windows

Security controls

Ask Privacy Policy questions before joining

01 Can I ask for a copy of my data?

02 How does the policy cover UPI and wallet data?

03 Why do you use cookies?

04 Can I correct account data?

05 How long do you keep my data?

06 Who can see my personal data?

07 What if local law affects account access?

Related Pages