Reference

Privacy Policy for Your coklat168 Account

coklat168 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, use DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
coklat168 Privacy Policy for Your coklat168 Account
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A clear contact route matters when your account record or wallet status does not look right.

Account data request Ask us to identify the personal data connected with your coklat168 account. We may request a phone verification step before disclosing or changing account details, because the request must come from the account holder rather than an unrelated contact.
Wallet record question For DANA, OVO, GoPay or QRIS records, send the transaction reference and approximate time through the account support route. We compare the reference with payment status data and explain what we can see without asking you to share a wallet PIN.
Cookie or access issue Tell us when a browser session repeatedly asks for verification, loses a policy choice or blocks account access. Include your device type and browser version if available, so we can separate a cookie setting from an account-security check.
DATA HANDLING DETAILS

Inside coklat168 Privacy Controls

We keep this Privacy Policy tied to the actions you actually take: account creation, phone verification, sign-in, wallet status checks and support contact.

Account details

We collect details needed to create and maintain your account, such as your contact information and phone verification result. Keeping these fields current helps us connect an access request with the correct account and prevents a change from being applied to the wrong record.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount status and time record for reconciliation. Bank transfer and virtual account checks use the same operational purpose: matching a payment event without requiring your wallet PIN or banking password.

Cookies and sessions

Cookies can preserve a policy choice, keep a sign-in session available and help us notice an unfamiliar browser. Clearing cookies may require phone verification again. You can adjust browser settings, though some account access functions may then need another security check.

Device security

We may use device and session signals to review unusual sign-in activity, including a new browser or repeated access attempts. These signals support account protection; they are not a request for your device passcode. Contact us when a security prompt does not match your activity.

Retention period

We keep account, payment and support records only for operational, security and legal purposes that require them. When a record no longer serves an applicable purpose, our handling process considers deletion, restriction or anonymisation, subject to duties that still apply where local law permits.

Change request

To request correction, access, restriction or deletion of eligible data, use the support contact shown in your account area. State the request clearly and include the account phone detail. We may verify ownership first, then explain the result and any reason a record must remain.

Privacy Policy Questions About Access

These Privacy Policy answers address the account questions we expect before you continue from a mobile browser or choose a local payment route. They explain the practical difference between account data, device signals, cookies and payment references. For a request tied to your own record, use the support contact shown after sign-in and follow the ownership check.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and how to request access or correction where local law permits.

Phone verification helps us confirm that an access or data request belongs to the account holder. It can also appear after cookies are cleared or a new device signs in. We use the result for account security and do not need your wallet PIN to complete that check.

Our Privacy Policy does not ask you to provide a DANA, OVO, GoPay or QRIS password through the account path or support contact. We may retain payment references and status details needed to reconcile an action, while your wallet provider controls its own credentials and account records.

Cookies can remember a policy choice, maintain a browser session and support checks for unusual access. On a mobile browser, clearing site data may remove that choice and prompt phone verification again. Your browser controls can limit cookies, although some account functions may then require another check.

Yes, you can ask about the personal data linked to your account through the support contact shown in your account area. Include the account phone detail and state that the request concerns Privacy Policy access. We verify ownership before explaining which records can be provided.

We retain payment references for as long as they support account administration, reconciliation, security review or a legal duty that applies where local law permits. The exact period can depend on the record type. Contact us for the reason a particular reference remains on file.

Use the account support route to request a correction and identify the field that is wrong. We may complete phone verification before changing it. Our Privacy Policy process checks the request against the account record and tells you when a correction is limited by security or legal requirements.

Related Pages

coklat168 Indonesia FAQ Indonesia DANA Help 511 About Us Account information