Reference

Open the jco69 Privacy Policy

Our Privacy Policy explains how jco69 handles your account details, login records, device signals and payment references when you use our Indonesia service.

Account dataCookie choicesWallet recordsPhone checks
jco69 Open the jco69 Privacy Policy
HELP PATHS

Reach Support About Privacy

A clear contact route matters when a data request meets an account or wallet question. We keep privacy help close to the same account path used for login checks and payment status, so you can identify the record that needs attention without sending unnecessary details.

Team online

Account access

If your phone verification or sign-in record looks incorrect, contact us through the account support path. Include the account identifier you can safely share, and we can locate the relevant record without asking you to send a password or full wallet credentials.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, tell us the date, amount and status shown in your account. We use those details to find the payment record and respond to a privacy or correction request.

Data requests

To ask what personal data we hold, request a correction or question retention, use the support contact shown in your account area. We may ask for a verification step before discussing private records, helping keep another person from accessing your details.

DATA PRACTICE

Switch On Clear Privacy Controls

Our handling process is designed around practical account events rather than broad collection. We separate routine access signals from payment references, limit support replies to verified account context and explain the steps…

Account details

We may handle details such as your account identifier, phone verification result and login activity because those records support access and account protection. We ask you to keep passwords and wallet credentials private; support will not need either one to discuss a policy request.

Cookie settings

Cookies and similar browser signals can keep your session connected and help us understand whether a page loads correctly. You can manage available browser permissions, although changing them may affect login continuity or require another account verification step.

Device security

We may record device or browser characteristics when they help identify an unusual sign-in. If you move between a phone and desktop, a fresh verification request can appear; that step protects your account and is not a request for your wallet password.

Payment references

A payment record can contain a rail name such as DANA, OVO, GoPay or QRIS, plus a reference, timestamp and status. Bank transfer and virtual account records may be checked in the same way when we answer a matching, correction or access request.

Retention periods

We retain records for as long as they support account operation, security checks, dispute handling or a legal requirement that applies to the service. When a record is no longer needed for those purposes, our process calls for deletion or further restriction where applicable.

Policy changes

If this Privacy Policy changes, we place the updated wording on this page and show the effective date or related notice where applicable. You can ask support which section changed, why it changed and what action, if any, is needed on your account.

Browse Answers About Privacy

These answers focus on the searches we hear most often about the jco69 Privacy Policy. They explain the account, device and payment records involved, while the full policy remains the reference for applicable requests and local access conditions.

The jco69 Privacy Policy covers account details, phone verification, login activity, device signals, cookies and payment references. It also explains why we use those records, how retention works, how security checks operate and how you can contact us about access, correction or deletion.

We use phone verification to help confirm that the person opening or accessing an account controls the stated contact path. A verification result may be retained with account security records. If the result is wrong, contact support through your account area and request a correction.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We may use a reference, timestamp and status to match an account event, answer support questions and address a data access or correction request.

Cookies can keep your session connected and help us identify page or login problems. Browser settings may let you restrict them, but doing so can interrupt account continuity or trigger another verification step. We do not ask you to share browser credentials when discussing cookie choices.

You can ask us to correct personal data that appears inaccurate or incomplete. Use the privacy contact route in your account area, describe the field that needs attention and provide safe account context. We may verify your identity before changing a private record.

Retention depends on whether a record is needed for account operation, security, payment matching, dispute handling or a legal requirement. The Privacy Policy explains this approach rather than promising one period for every record. You can contact us to ask about a specific data category.

Access or eligibility depends on local law. The Privacy Policy applies to the personal data handled when the service is available to you, including account and device records. If you are unsure about access from your location, check the account notice or contact support before proceeding.