Reference

mpoapi Privacy Policy for Your Account

mpoapi Privacy Policy explains what we collect when you create an account, verify your phone, open Baccarat or Aviator, and use DANA or QRIS.

Clear data purposesPhone check explainedWallet records coveredMobile access included

Explore Our Lobby Read FAQ

How DANA and QRIS Data Fits

mpoapi Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies when you open an account, complete phone verification, sign in from a mobile browser, browse Baccarat or MotoGP Betting, or check wallet activity. We may record account identifiers, verification results, device signals, session events, and transaction references needed to operate those steps.

1
DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records may include a reference number, amount, status, and time; we do not describe those records as permission to use a wallet outside its own rules. We use access and transaction data to match your account, investigate
2
a stalled status, protect sign-in, and respond to a data request. Our service and this policy apply where local law permits, and eligibility depends on local law. If wording changes, we place the current policy on this page and identify the effective date.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where Privacy Questions Reach Us

A privacy question should reach the account support route rather than sit inside a wallet status thread.

Account contact path Open the support route from your signed-in account and ask about a Privacy Policy request, phone verification record, device event, or account detail.

Wallet status query If a DANA, OVO, GoPay, or QRIS reference appears incorrect, send the transaction reference through the account support path so we can match the record.

Identity check We may ask you to confirm account details before releasing records or changing them; this step helps prevent another person from accessing your private account data.

SIX DATA CONTROLS

Six Controls Behind mpoapi Privacy Policy

We handle Privacy Policy requests through practical controls tied to the account journey. A phone check connects a request to the correct account, device signals help us spot unusual sign-in activity, and…

Account records

We use your account identifier, phone verification result, and sign-in history to provide access to the correct account and answer requests about stored account data.

Device signals

A mobile browser or desktop session can create device and session signals. We use them for sign-in protection and account checks, not as a substitute for your permission.

Cookie choices

Cookies can keep a session active and remember basic page settings. You can manage browser cookie controls, although disabling them may affect account access or policy page display.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us match a payment status to your account when you ask for support.

Retention approach

We retain account, verification, session, and transaction records only for the period needed for stated purposes, account support, dispute handling, or legal duties.

Change requests

Ask us to access, correct, or clarify eligible personal data through the signed-in support route. We confirm identity first and explain any limit required by local law.

Privacy Policy Questions About Your Account

These Privacy Policy answers cover the account steps Indonesian customers usually ask about before opening access. They explain phone verification, mobile sessions, wallet references, cookies, retention, and the contact route for requests. If your question concerns a record not listed here, use the account support path and include enough detail for us to locate it.

It covers account details, phone verification, device and session signals, cookies, wallet references, support requests, retention, and changes to your records when you access the service where local law permits.

We use the verification result to connect access and privacy requests to the correct account. It also helps us prevent another person from changing or receiving your account records.

Yes. The Privacy Policy covers transaction references linked to DANA, QRIS, OVO, GoPay, bank transfer, or virtual account activity, including status, time, amount, and account matching.

You can request access, correction, or clarification through the signed-in account support route. We confirm your identity first, then assess the request and explain any restriction required by local law.

A mobile browser may create session and device signals when you sign in or move between pages. We use those signals for account protection and handle them under the Privacy Policy.

We keep records for the period needed for the stated account purpose, support, dispute handling, or legal duties. A retention request can be sent through the account contact route.

Use the contact path displayed on your signed-in account beside the cashier area. Include your account email or phone and the record you are asking about so we can verify and respond.

mpoapi Privacy Policy for Your Account

Where Privacy Questions Reach Us

Six Controls Behind mpoapi Privacy Policy

Account records

Device signals

Cookie choices

Wallet matching

Retention approach

Change requests

Privacy Policy Questions About Your Account

01 What does the mpoapi Privacy Policy cover?

02 Why does mpoapi collect my phone verification result?

03 Does the Privacy Policy cover DANA and QRIS activity?

04 Can I ask mpoapi to correct account data?

05 How does Privacy Policy apply on a mobile browser?

06 How long does mpoapi keep my personal data?

07 Where do I send a Privacy Policy request?

Related Pages