Reference

Privacy Policy For Your jet123 Account

VIP Baccarat, Crash Games and wallet records sit behind one account, so our Privacy Policy explains exactly how we handle the details you share with us.

Account dataWallet recordsCookie choicesPhone verification
Explore Our Lobby Read FAQ
jet123 Privacy Policy For Your jet123 Account
ACCOUNT HELP

Get Privacy Help From Your Account

A clear contact route matters when a privacy question is linked to a login, wallet status or phone check. Sign in to your account and use the available support channel, giving us the email or phone detail attached to your profile plus the transaction reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without exposing unrelated account data.

Team online

Privacy request

Send a request through account support when you want to ask what personal data we hold, why we use it or whether a correction can be made. Include your account contact detail so we can confirm the request belongs to you.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, share the relevant payment reference rather than a wallet password or security code. We use the reference to compare account records and payment status while limiting the details shown in the reply.

Access concern

If phone verification or a sign-in check blocks your privacy request, tell support which account step stopped you. We may ask for matching account details before discussing personal data, helping prevent another person from receiving your records.

DATA PRACTICE

Six Controls Behind Your Account Data

We handle privacy as part of the account path, not as a separate promise on a page. The controls below describe what we do with sign-in events, payment references, cookies, support conversations…

Data we receive

We may receive contact details, phone verification results, sign-in events, device details and messages you send through support. Payment activity can add a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, while the payment provider handles its own records.

Why we use it

We use account data to create access, confirm the account holder, keep sign-ins safer, match payment status and answer support requests. We do not need the contents of your wallet password to check whether a QRIS or wallet reference reached the correct account.

Cookie choices

Cookies and similar device storage can remember sign-in preferences, help a page load correctly and support security checks. You can manage cookie settings in your browser, although blocking some storage may require you to repeat account steps or sign in again.

Account security

Phone verification and sign-in activity help us identify unusual access before account details are discussed. Keep your password and one-time codes private, and contact support from the account route if a device you no longer control was used to sign in.

Record retention

We keep personal data only for as long as needed for the stated account, security, support and legal purposes. Payment references may remain after a wallet action is complete when they are needed for reconciliation, disputes, audits or a legal duty.

Requests and corrections

You can ask about access, correction or deletion of eligible personal data through account support. We may verify your phone or another account detail first, then explain what can be changed and what must remain for security or legal reasons.

Privacy Policy Questions For jet123

These answers cover the searches we hear most often about the jet123 Privacy Policy. They focus on account access, local wallet references, cookies, device security and requests for changes. If your situation involves eligibility or service access, the outcome depends on local law. For a record-specific answer, use the support path connected to your account.

The jet123 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access, how long records may remain and how you can request access or a correction.

We do not need your DANA or QRIS password to match a payment status. Our records may contain a transaction reference, amount or status supplied for reconciliation, while your wallet credentials stay with the relevant payment service. Never send a password or one-time code through support.

Use the support route inside your account and state which detail appears incorrect. Include the account phone or email used for access, but do not include a password. We may verify ownership first, then confirm whether the requested correction can be applied to the relevant record.

You can ask us to delete eligible personal data through account support. Some records may need to remain for account security, payment reconciliation, dispute handling or a legal duty. We will explain the result for your request rather than removing a record without checking its purpose.

Cookies can keep a sign-in preference, help security checks work and support page functions on your phone or computer. You can change browser cookie settings, but blocking required storage may sign you out or make phone verification repeat when you return.

We use phone verification, sign-in activity and account details to check access before discussing personal records. If you lose control of a device, change your account password where available and contact support through the account route so we can address the access concern.

Yes. Account access and eligibility depend on local law, including where local law permits the relevant service. Privacy requests can also have local requirements, so we may ask for account verification and explain which rights or retention rules apply to your location.

Related Pages

jet123 Indonesia Account information FAQ About Us VIP Baccarat