Reference

cmbet Privacy Policy For Your Indonesia Account

Our cmbet Privacy Policy explains how we handle the details connected with your account, device, wallet activity and support requests.

Account data explainedWallet records clarifiedYour privacy choices

Explore Our Lobby Read FAQ

What The Privacy Policy Covers

cmbet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

The Privacy Policy describes the information we receive when you create an account, verify your phone, sign in, contact support or use wallet and cashier functions. This can include contact details, device identifiers, login events, payment references and records needed to match a DANA, OVO, GoPay,

1
QRIS, bank transfer or virtual account transaction to your account. We use these details to provide account access, detect unusual activity, answer status questions and keep accurate records. We do not treat a payment reference as permission to use unrelated personal details. Where local law permits,
2
the policy applies to your use from Indonesia, including access from Jakarta and other locations. If local rules affect eligibility or data handling, those rules apply. Read the current wording before opening an account and contact us if any part needs clarification.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY SUPPORT ROUTES

Get Help With Your Privacy Request

A clear support route helps when a privacy question is tied to login or wallet status.

Account request Use the account support route to ask what personal details are linked with your profile. Include your registered phone details and request type so we can locate the relevant Privacy Policy process.

Wallet record For DANA, OVO, GoPay or QRIS questions, mention the payment reference and date shown in your cashier history. We use those details to check the matching record without asking for your wallet password.

Access concern If login or phone verification stalls, contact support through the account path and explain the device step involved. We can separate an access issue from a request to change or remove personal data.

DATA HANDLING DETAILS

How We Put Privacy Policy Into Practice

We apply the Privacy Policy to everyday account events rather than treating it as a page kept apart from your activity.

Account details

We use your account details to create the profile, complete phone verification and connect your requests with the correct record. We do not need your wallet password to check a DANA or QRIS reference.

Device signals

A browser or mobile device may provide sign-in time, session and security signals. These help us identify unusual access while you move from login to the casino lobby or cashier path.

Cookie settings

Cookies and similar storage can support sign-in continuity, page preferences and security checks. Your browser controls may let you clear or restrict them, although some account steps may then need repeating.

Wallet references

Payment records can show a method such as OVO, GoPay, bank transfer or virtual account, together with a reference and status. We use this limited context to reconcile account activity.

Retention periods

We keep account, security and transaction records only for the period needed for the stated service, dispute handling or applicable legal duties. When a record is no longer needed, our process addresses its removal.

Change requests

Ask us to correct details, explain a record or discuss a deletion request through account support. Tell us which field or event concerns you, and we may verify ownership before making a change.

Answers About cmbet Privacy Policy

These Privacy Policy answers address the searches we expect before you open an account from Indonesia. They cover the data connected with login, wallets, devices, cookies and support. If your question concerns a specific payment reference or account event, include that detail when you contact us so we can respond to the correct record.

It covers account details, phone verification, device and login signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone details to create and verify your account, connect support requests with the right profile and help protect access. We may request an ownership check before discussing private account records.

Yes. The policy explains how sign-in time, session details and selected device security signals may be handled when you use a mobile browser or desktop path to access your account.

We may retain the payment method, reference, date and status needed to match a DANA or QRIS event with your account. We do not need your wallet password to investigate that record.

Yes. Contact account support and identify the field or event that appears incorrect. We may verify account ownership first, then assess the correction under the current Privacy Policy and applicable local rules.

Retention depends on why the record exists, including account operation, security checks, disputes or legal duties. The Privacy Policy explains the purpose-based approach rather than promising one period for every record.

Yes. Access and eligibility depend on local law. Before opening an account, check whether the service is available to you in Indonesia and read the Privacy Policy that applies to your access.

cmbet Privacy Policy For Your Indonesia Account

Get Help With Your Privacy Request

How We Put Privacy Policy Into Practice

Account details

Device signals

Cookie settings

Wallet references

Retention periods

Change requests

Answers About cmbet Privacy Policy

01 What does the cmbet Privacy Policy cover?

02 Why does cmbet need my phone details?

03 Does the Privacy Policy cover mobile device data?

04 How are DANA and QRIS records handled?

05 Can I ask cmbet to correct my account data?

06 How long does cmbet keep personal data?

07 Does access to cmbet depend on local law?

Related Pages