Reference

mybet Privacy Policy In Plain English

mybet explains how we collect, use and protect your account, device and payment details under this Privacy Policy.

Account dataWallet statusDevice controlsPolicy requests
mybet mybet Privacy Policy In Plain English
CONTACT PATHS

Get Privacy Policy Help Directly

A clear support route helps you deal with a privacy question without placing sensitive wallet details in the wrong message.

Account request Ask through the support contact linked to your account when you want to know…
Wallet question For a privacy question connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual…
Device concern If a mobile or desktop sign-in looks unfamiliar, contact support from the account path…
HANDLING DETAILS

How mybet Handles Your Records

Your Privacy Policy questions are handled alongside the account steps that create each record.

Account collection

We collect account details you enter, including contact details used for phone verification.

Cookie controls

Cookies and similar browser records can keep your session recognised and help us understand whether a sign-in is continuing on…

Wallet records

A DANA, OVO, GoPay or QRIS reference can show that a payment step was created, pending or matched.

Account security

Phone verification and sign-in checks help protect your account when access comes from a new device.

Retention choices

We keep records only for the operational, security or legal purpose that requires them, subject to local requirements.

Change requests

You can ask us to correct account details, explain our use of a device record or provide a copy of…

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions you may have before opening an account or contacting support. We keep the wording practical: what we collect, why a device record appears, how payment references are used and how you can request a change. If your situation is not covered, use the account support route and avoid sending private wallet credentials.

The mybet Privacy Policy covers account details, phone verification, device and session records, cookies, payment-status references and support requests. It explains why we use each category, how retention is considered and how you can ask for access, correction or clarification where local law permits.

We collect the details needed to create and secure your account, including contact details used for phone verification. We can also record sign-in time, device type and security events. We use those records to provide account access and handle a Privacy Policy request.

Yes. The Privacy Policy includes payment references and status records for DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. These records help us trace a cashier event; they are not a request for your wallet PIN or password.

A device record helps us recognise an account session, investigate an unfamiliar sign-in and keep the correct account open on mobile or desktop. The record can include device type, session time and security events. You can ask support to explain a specific entry.

Contact us through the support path linked to your account and describe whether you want a copy, correction or explanation. Complete the requested phone verification so we can protect your records. We respond according to the request type and local requirements.

Retention depends on why a record exists, such as account security, payment reconciliation, support or a legal requirement. The Privacy Policy does not treat every record as permanent. Ask support about a specific account or payment reference and we will explain the applicable period.

You can ask us to delete or restrict eligible data through the account support path. We first verify the request and then explain what can be removed. Some records may need to remain for security, payment reconciliation or local legal requirements where local law permits.