Reference

Privacy Policy for cm bet Accounts

cm bet Privacy Policy shows what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS for wallet activity.

Account dataWallet recordsCookie choicesAccess requests
cm bet Privacy Policy for cm bet Accounts
HELP WITH RECORDS

Get Clear Answers About Your Data

A specific support route helps you resolve a privacy question without sending sensitive account details into an unrelated message. Start with the support link in your account area and state whether your request concerns login records, a DANA receipt, a QRIS reference, or a correction to your profile. If you are in Surabaya or elsewhere in Indonesia, include the account email or phone identifier shown on your account, but never send a password or full wallet PIN.

Team online

Account data request

Use the account support path when you want to ask what personal details are linked to your cm bet profile. We may ask you to complete the account verification step before discussing records, so a request is matched to the correct account.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the date, amount reference shown to you, and the wallet name. The cashier support path lets us locate the related entry while reducing the need to send a screenshot containing unrelated private details.

Privacy change request

Ask support to correct a profile detail, explain a cookie choice, or raise a deletion question through the account help route. We review the request against account ownership and any record we must retain for security or a legal duty.

CONTROL YOUR DETAILS

What We Do With Account Data

Privacy controls work best when each data use has a visible reason. We separate account details from device signals used to protect sign-in, keep wallet references tied to…

Collection at account opening

When you create an account, we collect the details needed to establish access and contact you about account matters.

Device and sign-in signals

A phone or desktop session can send browser, device and sign-in signals that help us spot an unusual access pattern.

Cookies and session memory

Cookies can keep a session active, remember a language or help us understand which privacy page section you opened.

Wallet and cashier matching

When you use QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, we retain the reference needed to match…

Retention and deletion

We keep a record only for as long as its account, security, dispute or legal purpose requires.

Access and correction route

You can ask to access or correct eligible account details through support after we confirm account ownership.

Answers Before You Open An Account

These Privacy Policy answers focus on the questions Indonesian account holders commonly ask before using cm bet. They explain what is collected, how wallet and device records are handled, and how to contact us when you want to access, correct or remove eligible data. If your question concerns a specific account event, use the support path with the smallest useful set of details.

The cm bet Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet references, support messages, retention and privacy requests. It applies when you open an account, sign in, check a cashier status or contact support, subject to access that depends on local law.

We keep the reference connected to a DANA or QRIS event so we can match a payment question to the correct account and cashier record. The reference is not your wallet PIN. If you need a correction or deletion assessment, contact support with the displayed reference.

Yes. The Privacy Policy covers OVO and GoPay references handled during an account or cashier request, along with DANA and QRIS records. We use these details for matching, status checks, dispute handling and security. We do not ask you to send your wallet password or PIN.

We may receive browser, device and sign-in signals from the phone or desktop session used to access your account. These signals help identify unusual access and protect the account. They do not give us permission to inspect unrelated files, photos or messages on your device.

Use the support link inside your account and ask for an access request under the Privacy Policy. State whether you need profile details, sign-in records or wallet references. We may verify account ownership first, then explain the records available and the next step under local law.

You can request correction or deletion of eligible details through the account support route. Tell us which profile field or record is affected, and we will assess it against account security, dispute handling and legal retention needs. Where local law permits, we will explain the result clearly.

Cookies can support a signed-in session, remember a setting and help us measure page behaviour. Your browser provides controls for removing or blocking them. Necessary cookies may be needed for account access, so changing those settings can sign you out or interrupt the account path.