Reference

Open With A Clear Privacy Policy

cie66 Privacy Policy explains how we handle your account details, phone verification, cookies and payment records when you use our Indonesia service.

Account dataWallet recordsCookie choicesAccess requests
cie66 Open With A Clear Privacy Policy
CONTACT OPTIONS

Reach Us About Privacy Questions

A clear contact path helps you act on the Privacy Policy instead of searching through account screens. Send our support desk the email or account identifier connected with your request, explain whether you need access, correction or deletion, and avoid sharing a password or one-time phone code. We use the account trail to confirm which record your request concerns.

Team online

Account privacy request

Ask the support desk to locate the personal data linked to your account. Include your registered contact detail and the request type, such as access or correction, so we can check the right record without asking for your password.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the transaction date, amount and wallet name through the support path. We can compare the payment record with your account history while keeping secret wallet credentials out of the conversation.

Security concern

Tell us promptly if your phone, login or account activity looks unfamiliar. We may ask for account details already on file before discussing records, and we can direct you through a phone verification step to reduce the chance of disclosure to another person.

DATA PRACTICE

Explore The Controls Behind Our Policy

The Privacy Policy is connected to everyday account controls, not kept as a separate legal page. We separate identity details from payment references where practical, use security checks before discussing private records…

Account details

We use the contact and identity details you submit to create your account, complete phone verification and respond to account requests. Keeping those details accurate helps us connect your privacy request with the correct account rather than another record.

Payment references

DANA, OVO, GoPay and QRIS activity can create references such as status, amount, time and account match. We use these details to trace a missing payment or withdrawal check, while the Privacy Policy does not ask you to send a wallet PIN.

Cookies

Cookies can preserve your signed-in session, remember a display choice and help us identify technical faults. Your browser settings provide a way to remove or block cookies, although some account steps may then need to be repeated.

Device security

We may log device and browser signals, failed login events and unusual session changes to protect your account. When you return from a mobile browser to the lobby, these signals help us distinguish a normal device path from activity that needs an extra check.

Record retention

We keep personal and payment records for the period needed to operate the account, investigate disputes, protect security and meet applicable legal duties. After that need ends, records are deleted or changed so they no longer identify you where practical.

Request changes

You can ask for a copy, correction, restriction or deletion of personal data through the support desk. We may confirm your identity using details already connected to the account, and some records may remain where a legal or security duty requires them.

Check Answers About Privacy Policy

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account or asking us to change your records. We keep the wording direct, including what we collect, how we confirm requests and what access wording applies in Indonesia.

It covers account details, phone verification, login and device events, cookies, payment references and support requests connected with your use of cie66. It also explains retention, security checks, data requests and the circumstances in which we may share records.

We record the payment reference, status, time and account match so we can trace a DANA or QRIS deposit, investigate a stalled cashier status or check a withdrawal. We do not need your wallet PIN or secret authentication code for that purpose.

Yes. Contact the support desk with the contact detail linked to your account and ask for an access request. We may confirm your identity before releasing records, and the response can exclude data that would expose another person or weaken account security.

Send a correction request through the account support path and identify the field that needs changing. We may check the requested detail against your phone verification or account record, then update it where appropriate. Payment history may need a separate operational explanation.

We retain data while it is needed for account operation, payment tracing, security, dispute handling or legal duties. When those purposes end, we delete or anonymise records where practical. Exact timing can differ by record type and depends on local law.

You can submit a deletion request through support and tell us which account it concerns. We assess the request under the Privacy Policy and applicable law. Some payment, security or dispute records may remain for a required period before removal or anonymisation.

The policy page can be read from supported locations, but account access and eligibility depends on local law. If you are unsure whether the service is available to you, contact support before sending identity or payment details.