Reference

Privacy Policy for your 5q1 account

Turbo Blackjack, Diamond Strike, Crash X and wallet actions create account records, and this Privacy Policy explains how 5q1 collects, uses, stores and shares that data across the…

Account data useCookie choicesUPI contextRequest channels

Browse the lobby Read FAQ

How our policy treats India data

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

This Privacy Policy sets out how we handle personal data when you create an account, enter Turbo Blackjack, browse Diamond Strike, check Crash X rounds, use cookies, contact support or manage wallet activity. We collect account identifiers, login records, device signals, session logs, risk-check data and

1
payment confirmation details needed to run your account and respond to privacy requests. Where UPI, Paytm or PhonePe is used, we handle confirmation data linked to the transaction rather than asking you to share full payment credentials with our chat team. We may share limited data
2
with payment processors, verification partners, security vendors and authorities where law requires it. Access and eligibility depend on local law and are available where local law permits. If India law gives you a data right, we explain how to contact us and what we need to
3
verify the request.

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

REQUEST CHANNELS

Where to send privacy requests

Privacy questions should reach a channel that can verify you without exposing extra data.

ACCOUNT CONTROLS

Turbo Blackjack data, cookies and controls

Our privacy work is built around records you can recognise: account sign-in, device checks, cookies, game session logs, wallet confirmations and support messages.

Collection boundaries

Turbo Blackjack, Bingo and Fishing War sessions create time, stake, result, device and risk-check data.

Cookie choices

Cookies help keep you signed in, remember language choices and measure page faults.

Payment data handling

UPI, Paytm and PhonePe confirmations are used to match wallet events with your account.

Security checks

We use login alerts, device signals and risk scoring to spot account misuse.

Retention windows

Some data is removed when it is no longer needed, while transaction, dispute and legal records may stay longer.

Request handling

When you ask to access, correct or delete data, we record the request, verify your account and explain the action…

Privacy Policy questions before you join

These answers focus on how the Privacy Policy works when you create an account, use the lobby, manage wallet activity or contact us. They explain what data we collect, why we use it, how payment references are handled and how you can ask for access or correction. If your case involves a legal deadline or a disputed transaction, contact us with your account email and the relevant reference.

It covers account details, login records, device signals, cookies, game session logs, wallet references, support messages and verification records. It also explains when we may share limited data with processors or authorities.

We do not sell your personal data. We use it to run your account, process wallet events, answer requests, meet legal duties, prevent misuse and keep records needed for disputes.

Payment references help us match deposits or withdrawals to your account. We use confirmation data and transaction IDs, not your full payment password, and privacy requests can include those references.

Yes, you can ask for a copy of personal data linked to your account. We will verify you first, then share available records where India law allows and no exception applies.

Contact us with the account email, the detail that needs correction and a clear replacement value. We may request proof before changing identity, address or payment-related records.

Retention depends on the record type. Session logs may be shorter, while transaction, tax, security and dispute records can remain longer where law or operational need requires.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy rights, verification steps and response timing may also vary by applicable India rules.

Privacy Policy for your 5q1 account

Where to send privacy requests

Turbo Blackjack data, cookies and controls

Collection boundaries

Cookie choices

Payment data handling

Security checks

Retention windows

Request handling

Privacy Policy questions before you join

01 What data does this Privacy Policy cover?

02 Do you sell my account data?

03 How do UPI, Paytm and PhonePe records fit in?

04 Can I ask for access to my data?

05 How do I change incorrect account details?

06 How long do you keep my data?

07 Does local law affect account access?

Related Pages