Reference

JAVO88 Privacy Policy For Your Account

JAVO88 Privacy Policy explains how we handle the details you provide when opening an account, using DANA or QRIS, and browsing the lobby from your phone.

Account clarityWallet recordsCookie choicesSecurity controls
JAVO88 JAVO88 Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About Your Data

A direct support route helps you ask about the Privacy Policy without explaining your concern across several teams.

Account request Ask us to confirm which account details are linked to your login. We may request a phone verification step before discussing private records or changing contact details.
Wallet enquiry For DANA, OVO, GoPay, QRIS or bank transfer records, send the reference and date through support. We use those details to locate the correct payment entry.
Cookie question Tell us which cookie setting you want clarified or changed. Our support path can explain essential browser storage and the effect of clearing selected cookies.
CONTROLLED DATA USE

How We Handle JAVO88 Account Data

Privacy Policy controls are applied around the moments that create account records: opening access, confirming a phone, signing in on mobile and checking a wallet status.

Account collection

We collect details needed to create and protect your account, including contact data and phone verification status. We do not ask for unrelated personal details to let you reach the lobby.

Mobile signals

When you sign in through a mobile browser, we may record device type, browser path and login time. These signals help us spot unusual access without reading unrelated content on your phone.

Cookie settings

Essential cookies support sign-in and selected account settings. You can clear optional browser storage through your device settings, although some saved preferences may then need to be selected again.

Payment matching

DANA, OVO, GoPay and QRIS references are matched with account activity to resolve status questions. We use the payment identifier and timing rather than keeping unnecessary wallet credentials.

Retention period

We keep account, security and payment records only for the period required for support, fraud checks and legal duties. When a record is no longer needed, our process removes or anonymises it.

Change requests

You can ask us to correct contact details, explain a record or close account access through support. We verify the request first, then confirm what action was taken and why.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. Each answer points to the same support path, so you can move from a search result to a clear request without discussing unrelated account features.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, retention, security handling and the steps available when you request access, correction or removal.

No. We use payment references, status and timestamps to match DANA or QRIS activity with your account. Wallet credentials remain with the relevant payment service rather than our account records.

Use the support link beside the account area and request a copy or explanation of your records. Include your account contact detail, then complete any phone verification needed to protect your data.

Mobile browser type, device signals and login timing can help identify unusual access. We use these details for account security when you move from sign-in to the lobby on your phone.

Yes. Send a correction request through support with the detail that needs changing. We may verify your phone or account contact before updating records linked to your account.

We retain payment references for the period needed to resolve wallet status, security checks and legal duties. After that need ends, records are removed or anonymised under our retention process.

Yes. Privacy requests and account access depend on local law. We apply the available process where local law permits and explain any required verification or restriction through support.