Reference

mpo04 Privacy Policy For Your Account

Our Privacy Policy explains how mpo04 handles the details you provide when you open an account, sign in, use the casino lobby, or select DANA, OVO, GoPay and…

Account dataWallet recordsCookie choicesAccess requests
mpo04 mpo04 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help Beside Your Account Path

A clear contact route matters when you want to understand a data record, so we keep privacy questions close to the account and cashier areas. Tell us which account step or payment reference needs attention, and avoid sending a full password or wallet PIN. Our team can explain what we hold, why a security check appeared, and where a correction request should go. The same route can help if a QRIS receipt, device sign-in, or phone verification record looks unfamiliar.

Team online

Account privacy request

Use the account support path to ask what personal details we hold or to request a correction. Include your registered phone number and the subject of your request, but never include your password, wallet PIN, or a complete payment credential.

Payment record question

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, share the transaction reference and approximate date. We use those details to locate the relevant entry without asking you to disclose more wallet information than the request requires.

Access and security concern

If a sign-in, phone verification step, or device record does not look familiar, contact support through your account path before changing other details. We can review the security event and explain the next account action where local law permits.

YOUR DATA HANDLED

What Happens To Your Account Data

We handle account data in defined stages: collection during registration, use during sign-in and cashier checks, protection while the account is active, and retention only for an operational or legal reason.

Registration details

When you open an account, we use the details you submit to create your profile and provide account access. Phone verification may be required before access continues, helping us connect the request to the correct account instead of relying on an unconfirmed contact.

Cashier references

A DANA, OVO, GoPay, or QRIS transaction can produce a reference, amount, status, and timestamp in the account record. Bank transfer and virtual account entries may carry matching details so we can investigate a cashier question without exposing another person's data.

Device and session data

We may record device type, browser signals, sign-in time, and session events to protect account access. Returning from a mobile browser to the lobby can create a new security event, especially after you clear cookies or change devices.

Cookies and choices

Cookies help remember a session and support account navigation between the lobby and cashier path. You can adjust cookie controls in your browser, but refusing necessary cookies may sign you out or require phone verification again during a later access attempt.

Retention and deletion

We retain records for as long as needed to operate the account, resolve a payment or security question, and meet applicable legal duties. Ask us whether a particular record can be removed or shortened; the answer can depend on local law and its purpose.

Changes to your data

If your phone detail, account name, or contact record is wrong, contact support with the correction you want and enough context to locate the account. We may verify ownership before making a change, and we explain the result through the account support path.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. We keep the wording practical: what is collected, how access checks work, what payment references mean, and how you can contact us. If your situation involves a legal request or an unusual security event, send the account context through support so we can assess the correct path.

The mpo04 Privacy Policy covers account details, phone verification, sign-in and device events, cookies, cashier references, and support requests. It explains how we use those records to provide account access, investigate security issues, handle payment questions, and respond to requests where local law permits.

Phone verification helps connect an account access request to the person who controls the registered contact. We may use the result when you open an account, return from a new device, or request an account change. It is not a request for your wallet PIN or password.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account entries. These records help us match a cashier request and answer a payment question without requesting unnecessary wallet credentials.

We may collect device type, browser signals, sign-in time, session events, and security indicators linked to your account access. These details help us identify unusual activity and explain why a new phone verification step appeared. Browser cookie controls can affect how long your session remains connected.

Contact support through your account path and state which detail is incorrect, such as a phone or contact record. Add your registered phone number and relevant context, but not your password or wallet PIN. We may verify account ownership before applying a correction, and the result depends on local law.

We keep account, security, and payment records for the period needed to operate the account, resolve disputes or access concerns, and meet applicable legal duties. The exact period can vary by record type. You can ask support about a specific entry and whether deletion or restriction is available.

Use the account support route and identify the approximate time, device, and action you do not recognise. Do not send a password, wallet PIN, or full payment credential. We can explain the security event and outline the next account step where local law permits.