Reference

Open the jco69 Privacy Policy

jco69 Privacy Policy tells you how we handle the details used for account access, wallet checks and mobile sessions, including DANA, OVO, GoPay and QRIS activity.

Account clarityWallet recordsDevice choicesCookie controls
Explore Home Lobby Read FAQ
jco69 Open the jco69 Privacy Policy
CONTACT OUR TEAM

Contact us about Privacy Policy

A clear contact path helps when you want to ask what a record means or request a correction. Sign in first where possible, then use the account support route and include the phone number or email attached to your profile. We may ask for a simple account check before discussing private details. This protects you when a wallet status, QRIS reference or device sign-in needs attention.

Team online

Account request

Use the support route from your signed-in account to ask about personal data held for your profile. Include the relevant account step, such as phone verification or a sign-in event, so we can locate the right record.

Wallet question

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and status shown in your account. We use those details to check the payment trail without asking you to reveal a wallet password.

Correction request

Tell us which profile detail appears wrong and what should replace it. We may request account verification before changing a phone number, email address or other detail connected with access.

DATA HANDLING

See how we protect your records

Privacy Policy is supported by ordinary account controls rather than vague promises. We separate profile details from wallet references, use sign-in checks before discussing private records, and keep access requests tied to…

Account security

Phone verification can be required before account access, especially when a sign-in pattern changes. We use that step to connect a request to the correct account and reduce the chance of private details being disclosed to someone else.

Cookie choices

Cookies may keep your session active and remember basic site settings. Device signals can help identify an unusual login. You can adjust browser cookie controls, although some account functions may not work as intended afterward.

Payment references

We record the reference and status needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet password to investigate whether a payment step reached your account.

Retention periods

We retain records for as long as needed for the stated account, security and dispute purposes, or where applicable duties require it. When a record is no longer needed, our handling process moves it toward removal or secure restriction.

Access requests

You can ask what personal data is associated with your account, request a correction, or ask how a record is used. Send the request through account support, and we may verify ownership before replying.

Policy contact

Privacy questions belong with our account support route, not in a wallet reference field. Include your registered contact detail and the wording of your request so we can assess access, correction or deletion options accurately.

Find answers about Privacy Policy

These Privacy Policy answers cover the account actions you are most likely to ask about before opening an account or returning from a mobile device. We explain the records connected with wallet activity, cookies, phone verification and requests for access or correction. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, keep that reference ready when contacting support.

It covers account details, phone verification, sign-in events, device signals, cookies, wallet references and support requests. It also explains why we use those records, how long they may be retained, and how you can ask for access or a correction.

Yes. Privacy Policy covers the reference, status, time and related account link for DANA, OVO, GoPay and QRIS activity. Bank transfer and virtual account records may also be handled for matching and support, without requiring your wallet password.

Phone verification helps connect account access and data requests to you. We may ask for it before entry or before discussing private records, particularly when a device or sign-in pattern changes. Access depends on local law and account checks.

Cookies can retain a session and basic settings, while device signals may help identify unusual sign-in activity. You can change browser cookie controls, but refusing necessary cookies may affect account access or the way the site remembers your choices.

You can contact account support to ask what personal data is linked to your profile and how it is used. Include your registered contact detail and a clear request. We may verify account ownership before providing private records.

Send a correction request through the signed-in account support route and identify the detail that is wrong. For a phone number or email change, we may complete an ownership check before updating the record connected with account access.

We retain records while they serve account access, security, support or dispute purposes, and longer where applicable duties require it. When retention is no longer needed, the record moves toward removal or secure restriction under our handling process.

Related Pages

jco69 Indonesia Lightning Roulette Access guide FAQ bolabom