Reference

Privacy Policy for Your cie189 Account

cie189 Privacy Policy explains how we handle your account details, phone verification, wallet references and device access from the first account step onward.

Account dataWallet referencesCookie choicesAccess requests
Explore The Lobby Read FAQ
cie189 Privacy Policy for Your cie189 Account
CONTACT ROUTES

Where To Ask About Your Data

A clear support route helps you resolve a Privacy Policy question without guessing which team to contact. From your account, send a request about a phone verification record, a DANA or QRIS reference, a cookie choice or a correction to your details. Include the account phone number and the subject of your request, but do not send a wallet password or security code. We use the account step to confirm that a data request belongs to you.

Team online

Data request

Ask for the account details linked to your cie189 access, the purpose for holding them and the categories of records connected with your login or support history.

Correction request

If your phone detail, wallet reference or verification status appears incorrect, tell us which entry needs attention and provide the account step where you saw the mismatch.

Access concern

For a locked session or unfamiliar device record, use the support path shown after login so we can check the account event without asking for your wallet password.

HANDLING PRACTICES

How We Handle Account Data

We keep our privacy approach practical: collect what an account action needs, use it for a stated purpose and limit access to the records required for that task.

Account details

We use your phone number and verification result to create the account path, confirm an access request and connect support replies to the correct account rather than to an unverified message.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain transaction references and status details needed to match a cashier event without requesting your wallet password.

Cookies and devices

Cookies and device signals help keep a session active, remember selected settings and identify unusual access. You can clear browser cookies, though this may require phone verification again on the next login.

Account security

We use login records, phone verification and device checks to investigate unfamiliar access. Never place a one-time code, wallet password or full payment credential in a support message.

Retention approach

We keep account, payment-reference and support records only for the operational, security and legal purposes described in this Privacy Policy, then remove or restrict them when that purpose ends.

Changes and contact

To request access, correction or clarification, contact us through the account support route with the relevant record and account phone detail. We may ask for verification before changing or disclosing data.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the searches we hear most often before account access. They cover the records created by phone verification, local wallet activity, cookies, device checks and contact requests. Where access or eligibility is involved, the answer remains subject to local law and the policy wording shown on this page.

It covers account details, phone verification, login and device records, cookie settings, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security controls and how to request access or correction.

We use your phone number to create the account path, complete phone verification and connect a support request to the correct account. It can also help us investigate unfamiliar login activity. We do not ask you to place a wallet password in a support message.

No. When you use DANA, OVO, GoPay or QRIS, we handle the payment reference and status needed to match the account action. Bank transfer and virtual account records are handled in the same way; your wallet password remains outside our requested account details.

Use the support route shown after login and state that you want an account-data request. Include your account phone detail and the record you want checked, such as a device event or QRIS reference. We may verify your identity before sending or changing account data.

Yes. Send a correction request through account support and identify the inaccurate phone detail, verification status, wallet reference or support record. Explain where the mismatch appears. We may ask for an account check first, so a change is applied to the right record.

Cookies can keep your session active and retain selected settings on the mobile browser. Clearing them may sign you out and trigger phone verification again. Our Privacy Policy explains this use, while access to the account and lobby depends on local law.

We retain account, payment-reference and support records for the operational, security and legal purposes described in the Privacy Policy. When a purpose ends, we remove or restrict the record according to our handling process. You can ask support which category applies to your request.

Related Pages

cie189 Indonesia cie189 Casino Account information About Us Ceme Online Room