Reference

jati88 Privacy Policy for Indonesian Accounts

Our Privacy Policy explains how jati88 handles the details you provide when opening an account, signing in, checking Blackjack or Mahjong Ways, and using DANA, OVO, GoPay or…

Account detailsWallet referencesCookie choicesRequest access
jati88 jati88 Privacy Policy for Indonesian Accounts
CONTACT YOUR WAY

Privacy Help Beside Account Support

A clear request path matters when you want to check or change personal data. Sign in first when possible, then use the support contact route displayed inside your account and state that your request concerns the Privacy Policy. Add the account phone or email, the relevant date and a short description of the issue. For wallet questions, include the DANA, OVO, GoPay or QRIS reference without sending your password or one-time code.

Team online

Access request

Ask us to confirm the personal data connected with your account. We may request an account detail or verification step before sharing anything, so another person cannot obtain your records.

Wallet query

For a payment-status question, provide the relevant DANA, OVO, GoPay or QRIS reference and date through the account support route. We use those details to locate the correct record.

Correction request

Tell us which account detail needs changing and why. We will explain any verification needed before editing phone, email or profile data used for account access.

DATA HANDLING

What jati88 Keeps And Why

We keep each data decision tied to an account task rather than collecting details without a reason. The Privacy Policy covers sign-in protection, payment matching, cookie operation, retention and requests from you.

Account security

We use sign-in records, verification events and device signals to protect your account. Never share your password or one-time code; our support route should not need either item.

Device behaviour

A phone, tablet or desktop may send browser type, device identifiers and session data. This helps keep your login active while you move between the lobby and account pages.

Cookies

Cookies can remember a session and selected settings. You can control browser cookies, though disabling them may require repeated sign-in or affect pages that depend on an active session.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us connect a payment status with the right account. We do not ask you to send a wallet password through support.

Retention

We retain account and transaction records for operational, dispute and legal needs. When a record is no longer needed, we remove it or separate it from your identity.

Your requests

Use the account support contact to ask for access, correction or a question about this Privacy Policy. We may verify you first to protect the account from an unauthorised request.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or using local wallet rails. We explain what data is involved, how to reach us and what happens when you use a different device. If a request concerns eligibility or access, the result depends on local law and where local law permits.

It covers account details, sign-in records, device and browser signals, cookies, payment references, transaction status, retention and requests to access or correct data connected with your account.

Yes. When you use DANA or QRIS, we may retain the transaction reference, date and status needed to match the payment with your account and answer a wallet-status request.

Device and browser signals help maintain your session, identify unusual sign-in behaviour and show account pages correctly. They may be recorded when you move from a phone lobby to another device.

Sign in where possible and use the support contact route shown in your account. Describe the access request and provide the account phone or email; we may verify your identity first.

Yes. Send a correction request through the account support route, identify the inaccurate phone, email or profile detail, and complete any verification needed before we make the change.

We keep records while they support account operation, payment matching, disputes or legal needs. After that period, we remove them or separate them from direct account identification.

The policy still explains handling of data already connected with your account, but service access and eligibility depends on local law. It applies where local law permits.