Reference

Privacy Policy For Your chilli6 Account

chilli6 Privacy Policy sets out what we collect when you open an account, use the casino lobby or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet activityDevice accessPolicy requests
chilli6 Privacy Policy For Your chilli6 Account
REQUEST A PATH

Privacy Questions Near Account Help

A clear contact path helps you act on this Privacy Policy without sending sensitive details to the wrong place.

Data access request Ask us which account, device, wallet reference or support records relate to your request. Include your registered phone number and a short description so we can locate the correct chilli6 account without asking you to disclose a password.
Correction request If your name, phone number or account detail is inaccurate, send the existing entry and the replacement detail through account support. We may ask for phone verification before changing the record, helping prevent another person from altering your account data.
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, share the payment reference and date rather than wallet credentials. We use the receipt and status trail to check the matching account record and respond safely.
HANDLING YOUR DATA

Inside chilli6 Privacy Controls

We keep this Privacy Policy practical by linking each data use to an account action. Phone verification supports account security; device and connection details help us investigate unusual sign-ins; payment references help…

Account security

Phone verification and sign-in records help us confirm that the person requesting account access is connected with the registered account. We may review unusual device or connection activity before discussing private records or changing account details.

Cookies and sessions

Cookies can keep a session active, remember selected settings and help the lobby load correctly on your device. You can manage browser cookie controls, although turning them off may require repeated sign-ins or limit certain account functions.

Payment references

For DANA, OVO, GoPay and QRIS, we handle reference numbers, status and receipt details needed to match a transaction. We do not ask for your wallet password or card-style secret, and payment records remain tied to account checks.

Device records

Mobile and desktop access can create device, browser, connection and security-event records. We use these details to diagnose sign-in problems, protect the account and understand whether a request is linked to your normal access path.

Retention approach

We retain account, transaction and security records only while they support the stated purpose or a legal requirement. When a record is no longer needed, our handling follows the applicable deletion or restriction process, where local law permits.

Change requests

You may ask about access, correction, deletion or restriction through the account support path. We verify the request before acting, explain any lawful reason for keeping a record and identify the next contact step when another team must respond.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from people deciding whether to open chilli6 access. They explain the data connected with phone verification, mobile use, local payment references, cookies, security checks and contact requests. If your case involves eligibility or a record that must be retained, the answer may depend on local law. Use the account support path for a request tied to your own account.

The chilli6 Privacy Policy covers account details, phone verification, device and connection data, cookies, payment references, security logs and support messages. It also explains why we use those records, how retention works and how you can request access, correction or deletion where local law permits.

We may collect your name, registered phone number, login details, account activity, device information, connection details and security events. When you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account, we may retain payment references and status needed to match the transaction.

Phone verification helps us confirm account ownership before access or a record change. It supports security when you sign in from a new device or request account help. We use the verification result for that operational purpose and do not need your wallet password to perform the check.

Yes. The Privacy Policy covers device, browser and connection details created when you use the mobile or desktop path. We use them to diagnose sign-in issues, identify unusual access and protect account records. Cookie controls can affect session settings and may require you to sign in again.

We use DANA and QRIS reference numbers, receipt details and transaction status to connect a payment with the correct account. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. We do not request your wallet password as part of this matching process.

You can contact account support to request access to eligible records or ask for a correction. Include your registered phone number and describe the record, without sharing a password. We may verify your identity first, and some records may remain where retention is required by local law.

Retention varies by record type and purpose. Account, payment and security details may remain while they support account administration, transaction checks, security or a legal duty. When the purpose ends, we follow the applicable deletion or restriction process where local law permits.