Reference

jawa11 Privacy Policy For Your Account

The jawa11 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse VIP Baccarat Circle or use DANA, OVO, GoPay…

Account dataWallet detailsCookie choicesAccess requests
Explore the lobby Read FAQ
jawa11 jawa11 Privacy Policy For Your Account
REQUEST A HAND

Get Privacy Help Near Account Support

A clear support path matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Start from your signed-in account support route and include the email or phone detail linked to your profile, plus the subject of your request. We may ask for an account step or verification detail before discussing personal data. For a receipt or status question involving QRIS, DANA or a bank transfer, share only the reference needed to locate the record.

Team online

Account support route

Use the support path connected to your jawa11 account when you need a copy, correction or explanation under this Privacy Policy. Include your registered contact detail and a short description so we can locate the correct profile without asking you to send a wallet password.

Wallet data question

For DANA, OVO, GoPay or QRIS records, give us the transaction reference and date shown in your account. We use that narrow detail to check payment status, separate wallet data from login data and respond to a Privacy Policy request.

Access or deletion request

Ask through account support if you want to access, amend or remove personal data covered by this Privacy Policy. We first confirm that the request belongs to you, then explain any data we must retain for security, payment records or where local law permits.

DATA HANDLING

How We Handle Your jawa11 Details

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account identity

When you create an account, we store the contact and profile details needed to provide access. A phone verification step may be required before account access, helping us reduce mistaken matches and handle a Privacy Policy request with the correct account holder.

Device and sessions

Your browser or mobile device can send session, language, network and security event details. We use these signals to keep a sign-in active, detect unusual access and investigate an account request; they are not a substitute for your wallet credentials.

Cookies

Cookies can remember a session, maintain selected settings and help us understand whether a page request works. You can adjust cookie controls in your browser, although changing them may interrupt sign-in or require you to repeat an account step.

Payment references

We record the reference, status, amount and method needed to reconcile a wallet or transfer action. This can include QRIS, DANA, OVO, GoPay, BCA, BRI, Mandiri, BNI, bank transfer or virtual account details without requesting your wallet PIN.

Security checks

We may compare sign-in activity, phone verification and device signals when an account change or payment status request appears unusual. These checks protect your profile and help us decide what confirmation is needed before personal data is disclosed.

Retention and changes

We retain records only for the period linked to account operation, dispute handling, security, payment reconciliation or legal duties. To request a correction or ask what remains stored, contact account support and identify the record you want us to examine.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions we expect before you continue. They explain the practical route for checking data, changing details, managing cookies and asking about retention. If your request concerns access or eligibility, the outcome depends on local law. Use the account support path when a question involves a specific profile, device session or payment reference.

It covers account creation, phone verification, sign-in sessions, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains our purposes, retention approach, security checks and the route for personal data requests.

We may collect contact and account details, verification results, session and device signals, cookie settings, support messages and payment references. The exact data depends on the action you take. We do not need your DANA, OVO or GoPay wallet PIN to match a payment record.

Phone verification helps us connect account access and later privacy requests with the correct person. It can also support security checks when you sign in from a new device or ask to change profile details. Access or eligibility depends on local law and the applicable account step.

Use the support route attached to your account and state whether you want access, correction or deletion. Include your registered contact detail and the relevant record, such as a QRIS reference or device session. We confirm identity first and explain any limits required for security or law.

Yes. Cookies and similar session data can keep you signed in, remember page choices and help us identify technical errors on a mobile browser. You can adjust browser controls, but blocking required cookies may end the session or send you back through phone verification.

Retention varies by record. We keep data while it supports account access, security checks, payment reconciliation or an open request, then follow applicable legal requirements. A request through account support can ask which category applies to your profile and why a record remains.

Yes. Send the transaction reference and date through account support rather than your wallet password or PIN. We can check the related status and explain the data held for that payment. The response and any access restriction depend on local law and identity confirmation.

Related Pages

jawa11 Indonesia Account information Access guide FAQ VIP Baccarat Circle