Reference

com168 Privacy Policy for Your Account

Our Privacy Policy explains how com168 handles the account, device and wallet details connected with your access to Blackjack, slotbingo and other lobby areas.

Account dataWallet recordsPhone verificationPolicy requests
com168 com168 Privacy Policy for Your Account
PRIVACY CONTACT

Where Privacy Questions Go

A clear contact route matters when a wallet receipt, phone detail or device record does not look right.

Account request Open the signed-in support route and ask about a specific Privacy Policy matter, such as a phone detail, device entry or payment reference. We check the account step before discussing records, helping keep your request connected to the correct com168 account.
Wallet receipt For a DANA, OVO, GoPay or QRIS question, include the receipt reference and approximate request time. That gives our support team a focused way to trace the status without asking you to share a wallet password, card secret or unrelated personal detail.
Access route If phone verification or a mobile browser session prevents account access, use the contact route displayed on our site. Tell us which step stopped, whether you used mobile or desktop, and the policy question you need answered.
DATA HANDLING

How com168 Handles Account Data

We handle Privacy Policy requests around the same account steps you use to reach the lobby: phone verification, wallet selection and device access.

Account details

We may handle your phone number, verification result, account identifier and selected settings to create and protect your account. Phone verification is checked before account access, while the Privacy Policy explains why each account detail is needed for that step.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can produce a reference, amount, status and time record. We use these details to match the transaction to your account and resolve a receipt question, not to request wallet credentials.

Cookies and sessions

A mobile browser or desktop session may store cookies or similar identifiers so your signed-in path remains connected and security checks can detect unusual changes. You can manage browser cookie settings, though disabling them may interrupt the policy or account request path.

Account security

We use phone verification, session checks and account matching to reduce the chance that one person can discuss another person’s records. Do not send a wallet PIN or password in a support message; our Privacy Policy does not require those secrets.

Retention choices

We retain data only while it supports an account purpose, a security review, a payment dispute or a legal requirement. When the relevant purpose ends, we delete, anonymise or restrict the record where practical, subject to duties that may require continued storage.

Change request

You can ask us to correct an inaccurate phone detail, clarify a wallet record, request a copy of available account data or ask about deletion. Send the request through the account support route so we can verify your identity before making a change.

Privacy Policy Questions Before You Open

These Privacy Policy answers focus on the account and payment details you are most likely to ask about before opening an account with com168. We explain the practical path for phone verification, mobile sessions, wallet records and requests to correct or remove data. If a matter concerns eligibility or access in Indonesia, the answer may depend on local law. For a case-specific response, use the support route and identify the account step or transaction reference involved.

The com168 Privacy Policy covers account details, phone verification, device and session records, cookies, wallet references, support messages and retention. It explains why we use each category, how we protect account discussions and how you can ask for access, correction, clarification or deletion where applicable.

We do not need your DANA, OVO, GoPay or QRIS password or wallet PIN for a policy request. We may receive a transaction reference, status, time and account match from a payment action. Never place wallet secrets in a support message or receipt attachment.

Phone verification helps connect an account request to the person seeking access and gives us a security check before discussing account data. The result may be stored with the account record. We use it for account access and protection, not as a reason to request unrelated phone content.

When you use a mobile browser, we may record session and device signals needed to maintain the signed-in path, protect the account and identify unusual access. Cookies can support that process. You may adjust browser settings, but some policy or account steps may then stop working.

Yes. Send a clear request through the signed-in account support route, naming the data category, such as a phone detail, device entry or wallet reference. We verify the account first, then explain what can be copied or corrected and whether local law affects the request.

We keep records while they are needed for account support, security checks, a payment dispute or a legal duty. A DANA, QRIS, bank transfer or virtual account reference can therefore remain after a session ends. When the purpose ends, we delete, anonymise or restrict it where practical.

Use the support route shown inside your account or on the com168 site. Include the policy topic, the affected account step and a safe reference such as a receipt number. If you cannot sign in, state that clearly; do not send a password or wallet PIN.