Reference

Privacy Policy For Your cendol66 Account

cendol66 Privacy Policy explains how we collect, use and protect details connected with your account, wallet status and device access.

Account clarityWallet data carePolicy access
cendol66 Privacy Policy For Your cendol66 Account
ASK ABOUT PRIVACY

Get A Clear Answer About Your Data

Privacy questions should not leave you guessing about the next account step. Use the support path shown after sign-in, or contact the support route attached to your account when you need help with a phone record, wallet reference, device sign-in or policy request. Include the email or phone detail linked to your account and a short description of the request. We use those details to locate the right record without asking you to send a full password or wallet PIN.

Team online

Account privacy path

Open the account support area and select the privacy request route. We can help you understand which profile details are stored, why phone verification appears, and what confirmation we need before discussing account data.

Wallet record check

If your question concerns DANA, OVO, GoPay or QRIS, mention the payment rail and the relevant receipt reference. We use that context to separate a wallet-status query from a request about your personal account data.

Access concern

For an unfamiliar sign-in or device concern, contact support through the account path as soon as possible. We may ask for account-linked details to confirm ownership, then explain the security action available under this Privacy Policy.

DATA HANDLING

Know What We Keep And Why

We handle Privacy Policy requests around the records that make account access work, rather than treating every device or payment detail the same way.

Account details

We may hold your account contact details, phone verification result and sign-in history so we can provide access and respond to ownership questions. We use the minimum context needed for the requested account action and do not ask for your password in a support message.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can appear in an account record when you use that rail. We use the reference to match status and receipts; payment credentials remain with the relevant payment service.

Cookies and devices

Cookies and device signals can remember a session, support basic preferences and flag an unusual sign-in. You can clear browser cookies, but doing so may require another account check before the lobby or wallet status appears again.

Account security

Phone verification before account access helps us distinguish an account holder from an unknown sign-in. Keep your password and one-time codes private, and tell support through the account route if a device or contact detail no longer belongs to you.

Data retention

We retain records only for the period needed for account operation, security checks, dispute handling or a legal requirement. A deletion request may not remove records tied to an open issue, and we explain the reason when a record must remain.

Changes and requests

You can request access, correction or clarification through the support path linked to your account. State the request clearly and provide an account-linked contact detail so we can confirm ownership before changing or disclosing personal data.

Answers About cendol66 Privacy Policy

These Privacy Policy answers address the searches we hear most often from people checking account access in Indonesia. Each answer points to a practical action: review the data purpose, protect a sign-in, identify a wallet reference or contact support. Where access or retention depends on circumstances, we explain that limit instead of promising an outcome that the policy cannot provide.

The cendol66 Privacy Policy covers account details, phone verification, sign-in and device signals, support messages, cookies and payment references. It explains how we use those records for account access, security, receipt checks and requests to correct or clarify your personal data.

We use phone verification to help confirm that the person requesting account access or a data change controls the account contact detail. It is not a request for your password. If the phone number is outdated, contact support through the account privacy path.

Yes. The Privacy Policy covers the payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to check status or receipts, while the payment service handles its own credentials and separate privacy terms.

Use the support route shown in your account and ask for a personal data access request. Include the account-linked email or phone detail, but never send a password or wallet PIN. We confirm ownership first, then explain the records available under the Privacy Policy.

You can ask us to correct an inaccurate account contact detail, phone record or other personal data through support. Describe the exact change and provide an account-linked contact. We may retain the earlier record when it relates to security, a payment dispute or a legal requirement.

We keep data for the time needed to operate your account, protect sign-ins, resolve payment or support matters, and meet a legal requirement. A deletion request may therefore be limited while an account remains open or an unresolved issue still needs its record.

The policy is written for account access from Indonesia, including supported use in Makassar and other areas. Availability and eligibility depend on local law. Where local law permits access, the same account, device, cookie and payment-reference practices described here apply to your use.