Reference

cie188 Privacy Policy For Your Account

The cie188 Privacy Policy explains what we collect when you open an account, browse Lightning Roulette Room or use DANA, OVO, GoPay and QRIS at the cashier.

Account dataWallet recordsCookie choicesRequest access
cie188 cie188 Privacy Policy For Your Account
REQUEST SUPPORT

Get Help With Privacy Requests

A clear account route helps you raise a Privacy Policy request without sending sensitive details through an unrelated channel. Start from the account help link and include the email or phone identifier attached to your cie188 account, plus the request you want handled. We may ask for an account check before discussing records, especially when your request concerns a DANA receipt, QRIS reference or a device used in Yogyakarta. Do not send a wallet PIN or full payment password in your message.

Team online

Account help link

Use the help path inside your account when you need a copy of personal data, a correction or an explanation of a Privacy Policy entry. Add your account identifier and a short description so we can route the request without asking you to repeat wallet details.

Cashier privacy query

For a DANA, OVO, GoPay or QRIS record that appears under the wrong account, choose the cashier-related support path and include the transaction reference. We check the account match first, then explain what can be corrected and what must remain for security records.

Security concern

If you think another device has reached your account, contact us through account support and state the approximate access time and device type. We can guide an access check without asking for your password, wallet PIN or one-time verification code.

DATA HANDLING

How We Handle Account Data

Our Privacy Policy is tied to practical account actions rather than vague categories. We separate account identifiers from payment references where our systems allow, limit access to records needed for support or…

Account details

We collect details such as your contact identifier and verification status when you open or maintain an account. We use them to connect your requests to the right account, confirm access and answer Privacy Policy questions, rather than to create an unrelated profile.

Device signals

A phone or desktop can send browser type, session time and basic device signals when you access the lobby. We use this data for sign-in checks and account protection. It does not give us access to other files, contacts or applications on your device.

Cookies

Cookies can keep a session working, remember a selected language or help us identify repeated sign-in attempts. Your browser controls which cookies remain. Removing them may require you to sign in again, but it does not erase account records already needed for a privacy request.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference numbers and status records. We use those references to match a cashier event to your account and investigate a discrepancy without requesting your wallet password.

Retention period

We retain account, security and payment references only for the period needed for account operations, dispute handling, fraud checks or legal duties where local law permits. A closure request starts a review of what can be removed and what must remain.

Policy changes

When we change this Privacy Policy, we place the revised wording on this page and show the updated date or notice where appropriate. You can ask support which section changed, why it changed and how the update affects your account data.

Privacy Policy Answers For cie188

These Privacy Policy answers address the searches we hear most often before an account is opened. Each answer points you toward a practical step, from checking a cookie setting to asking for a copy or correction of account data. If your question concerns local access, remember that eligibility depends on local law.

The cie188 Privacy Policy covers account identifiers, verification details, device and browser signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. It explains why we use each category and how you can ask about it.

Open the account help link and request a copy of the personal data connected with your account. Include your contact identifier and the scope you want checked, such as sign-in records or QRIS references. We may verify account control before sending details.

Yes, ask through the cashier privacy query and provide the reference number, payment name and account identifier. We compare the record with the account history before changing anything. Do not include a wallet PIN, password or one-time verification code in the request.

Yes. The Privacy Policy covers basic device and browser signals created when you open Aviator Mobile Play or another lobby page on a phone. These signals support sign-in checks and security review; they do not provide access to unrelated files or contacts.

Cookies can keep your session active, remember a language choice and help identify repeated access attempts. You can manage them in your browser settings. If you remove required cookies, you may need to sign in again, while existing account records remain subject to the policy.

We keep account, security and payment references for the period needed for account operation, dispute handling, security checks or legal duties where local law permits. If you close your account, ask support which records can be removed and which must remain.

Use the account help link and name the section or wording you want clarified. We can explain the change, its purpose and the account data it affects. The current Privacy Policy remains on this page, with an update notice when wording is revised.