Reference

cempakabet Privacy Policy Explained

cempakabet Privacy Policy explains what we collect when you open an account, access Baccarat or Garuda Gems, and use DANA, OVO, GoPay or QRIS.

Account dataWallet activityCookie choicesSecurity requests
cempakabet cempakabet Privacy Policy Explained
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not leave you guessing, especially when it concerns phone verification or a wallet record.

Policy questions Send a request through our support channel when you need the Privacy Policy explained…
Wallet records For DANA, OVO, GoPay or QRIS concerns, share the date, amount reference and visible…
Account access If phone verification or sign-in stalls, tell us which device path you used and…
DATA HANDLING DETAILS

What We Do With Personal Data

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Account details

We may store your contact details and verification status so the correct account opens after sign-in. Check your profile path first, then ask support to correct a detail that no longer matches you.

Device signals

A browser or phone can create sign-in and security signals. We use them to investigate unusual access, including a change from mobile login to desktop, rather than treating every device change as misuse.

Cookie controls

Cookies can keep a session active or remember a selected setting. You can manage browser cookie controls, although removing them may require another sign-in before the account path works.

Cashier records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can remain linked to transaction history. We use that link to check status and investigate a receipt question.

Retention choices

We retain records for the period needed for the stated account, security or transaction purpose, subject to applicable rules. Ask us which category a record belongs to before requesting a change.

Your requests

You may contact us about access, correction, deletion or an explanation of processing where local law permits. Include enough account detail for matching, while leaving passwords and wallet PINs out.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain the practical points: what we collect, why payment references appear, how cookies affect sign-in and how to ask for a change. If your situation is different, contact support with a safe account identifier and we will direct the request.

It covers account details, phone verification, sign-in and device signals, cookies, cashier references, support requests and retention. It also explains how we handle DANA, OVO, GoPay, QRIS and bank transfer records.

Phone verification helps connect you with the correct account and supports safer access after sign-in. We may retain its status so a later login does not create a conflicting account record.

Yes. The Privacy Policy covers transaction references and visible status linked to QRIS, DANA, OVO and GoPay. We use those records to match cashier activity and investigate a receipt or status question.

Cookies may keep your session active or remember a setting on the device you use. If you remove them, you may need to sign in again before reaching the account path.

You can contact support with the account email or phone number connected to the record and describe the correction. We may ask for a safe verification step before changing account information.

Send a deletion request through our support channel and identify the relevant account record. We assess the request against retention duties and local requirements, then explain what can be changed.

The policy is available through the cempakabet account area and this page. Account access and eligibility depends on local law, including the rules that apply in your Indonesian location.