Reference

mpo300 Privacy Policy and Your Account

Our Privacy Policy explains how mpo300 handles your account details, device access and wallet records when you browse casino rooms or sports markets.

Clear data purposesWallet record contextAccount access choicesIndonesia policy scope
mpo300 mpo300 Privacy Policy and Your Account
CONTACT ROUTE

Get Help With Privacy Requests

A clear contact path matters when you want to ask about the Privacy Policy, correct an account detail or question a wallet record. Start from the support route linked to your account and include the email or phone detail used at registration, plus the relevant transaction reference. We use those checks to locate your request without exposing account data to the wrong person.

Team online

Policy questions

Use the account support route to ask how we collect, use or retain a specific detail. Include the section or practice you are asking about, and we will keep the reply tied to your Privacy Policy request rather than discussing unrelated account activity.

Correction requests

If your phone detail, name or account record needs correction, tell us which field is inaccurate and provide the account sign-in detail used for verification. We may ask for an account step before changing anything connected with DANA, OVO or another wallet.

Wallet records

For a question about QRIS, bank transfer or virtual account data, attach the payment reference and date shown in your account. We use that narrow reference to check status records while avoiding a request for your wallet password or private login code.

SECURITY PRACTICE

How We Handle Personal Data

Privacy work follows the same account path you use on a phone or desktop: sign in, complete the requested verification step, then contact us about a record.

Account details

We use registration details to create and maintain your account, confirm the requested phone step and connect you with the correct support record. Please keep your sign-in details private; support will not need your password to answer a Privacy Policy question.

Device signals

A mobile browser and a desktop browser can generate different session, browser and device signals. We use those signals to recognise unusual access and protect the account path, including when you move from login to a lobby containing Papua Paradise Megaways.

Cookies

Cookies and similar browser storage can keep a session active, remember selected settings and help us understand whether a page request belongs to your current visit. You can manage browser storage through your device settings, although some account steps may then need to be repeated.

Payment records

A DANA, OVO, GoPay or QRIS status record can show a reference, amount status and time needed to match an account action. We use that record for reconciliation and support, not as a reason to request your wallet PIN or unrelated financial details.

Retention

We retain account, security and transaction records for as long as needed for the purpose described in the Privacy Policy, account protection and applicable legal duties. When a record is no longer needed, our handling follows deletion or other permitted disposal steps.

Policy changes

If our data practice changes, we will place the updated Privacy Policy on this page and show the revised date or wording where applicable. To ask what changed, contact us through your account support route and identify the section you want us to explain.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you may have before opening an account with mpo300. They also explain how to reach us when a record needs correction or when you want more detail about access, retention or local eligibility.

It covers account details, phone verification, login and device signals, cookies, support requests and payment status records. It also explains why we use those details, how long records may be retained and how you can contact us about a correction or access question.

Yes. The Privacy Policy explains that DANA and QRIS records may contain a reference, status and time linked to an account action. We use those details to match and resolve a payment question, and we do not ask for your wallet PIN.

Use the support route connected with your account and state the exact field that needs correction, such as a phone detail. Include the sign-in detail used at registration so we can verify the request before changing information attached to your account.

Device and browser signals help us recognise the current session, identify unusual access and protect the login path. A mobile browser and desktop browser may create different signals, especially when you move from login to a lobby or account page.

Yes. Send a retention question through account support and identify the record involved, such as a login event or virtual account status. Our answer follows the purpose, account protection needs and legal duties described in the Privacy Policy.

Access depends on local law and is available where local law permits. The Privacy Policy does not change local eligibility rules. If you are unsure about access from Indonesia, check the applicable local position before opening an account or submitting account details.

Start with the support contact path inside your account and describe the privacy concern in specific terms. For a wallet matter, add the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so we can locate only the relevant record.