Reference

mxbet Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect details connected with your mxbet account, including phone verification, device access and wallet activity.

Account dataWallet recordsDevice checksPolicy access
mxbet mxbet Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Beside Your Cashier

A clear contact route helps you ask about personal data without explaining your whole account history.

Account request Use the account support contact path to ask which personal details we hold, how…
Wallet question For a DANA, OVO, GoPay or QRIS privacy query, attach the transaction date, rail…
Access concern If your account page shows an unfamiliar device event, contact support through the account…
DATA PRACTICE

Inside mxbet Data Handling

Our handling process follows the practical questions you face when opening an account from a phone: what is collected, why it is needed and how long it remains useful.

Collected details

We may hold your account name, phone number, verification outcome, support messages, login timestamps and device or browser signals. Payment records can include DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We collect only the details needed for account operation, security checks, support and legal duties.

Cookie choices

Cookies and related signals can keep your session open, remember a language or region setting and help us detect repeated failed logins. If you clear browser storage on your Android or iPhone, you may need to verify your account again. Ask support which cookie category relates to your concern.

Account protection

Phone verification helps connect an account request to the correct person before account details are discussed. We also examine login time, device pattern and unusual wallet activity. Never share your password or one-time code; if a new device looks unfamiliar, request an account check through support.

Storage period

We retain records for as long as they serve account operation, dispute handling, security review or a legal requirement. A QRIS receipt, wallet status or verification event may therefore remain after a session ends. You can ask why a particular record is retained and when the applicable period ends.

Your request

You may ask for access to your personal data, correction of an inaccurate phone or account detail, clarification of processing, or deletion where the law allows. We may request an account check before acting, so one person cannot obtain or alter another person’s records.

Policy contact

Send a privacy request through the account support contact path and label the subject clearly. State the action you want, the relevant account phone number and any useful date or reference. We will explain whether the request can be completed, requires more detail or is limited by local law.

Privacy Policy Questions From Indonesia

These answers address the searches we hear before an Indonesian customer opens an account or checks a wallet record. They focus on mxbet Privacy Policy access, account data, device behaviour and payment references. If your case includes a specific transaction or login event, use the account support path so we can check the correct record.

The mxbet Privacy Policy covers account details, phone verification, login and device signals, support messages, cookies and payment references. It explains why we use each category, how we restrict access, how long records may remain and how you can request access, correction or deletion where local law permits.

Phone verification helps us confirm that an account request comes from the correct account holder before we disclose or change personal data. It can also support login protection when a new handset or browser appears. We will not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers cashier references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We may retain the rail, timestamp, amount and status needed to match a receipt, resolve a dispute or meet a legal requirement.

Use the account support contact path and ask for a personal data access request. Include your registered phone number through that secure route, identify the account record you need and provide a useful date range. We may complete an account check first to prevent disclosure to another person.

You can ask us to correct an inaccurate name, phone detail or account record through support. Explain what appears wrong and provide the updated detail without sending a password or wallet PIN. We may request verification before changing the record, and some payment entries must remain unchanged for audit purposes.

Cookies and device signals help maintain your login session, remember selected settings and identify unusual access. Clearing browser data on an Android or iPhone can remove those settings and trigger phone verification again. Contact support if you want a particular cookie or device signal explained.

You may request deletion through the account support contact path, and we will assess which records can be removed where local law permits. Some verification, payment or dispute records may need to remain for security or legal reasons. We will explain the reason if a record cannot be deleted.