Reference

Open mpoatn Privacy Policy Access

mpoatn Privacy Policy sets out how we use your account, device and payment details when you open the lobby from Indonesia.

Account dataWallet recordsMobile sessionsPolicy requests
mpoatn Open mpoatn Privacy Policy Access
REQUEST A HAND

Contact Us About Privacy Policy

A clear contact route helps you ask about the Privacy Policy without explaining your whole account history. Start from the support path linked in your account area, especially when a phone-verification question, wallet reference or cookie setting needs attention. Include the email or phone detail connected to your account and the request you want handled. We use those details to locate the right record, while access remains subject to local law.

Team online

Account privacy path

Use the support route inside your account when you want to ask how phone verification, sign-in records or a mobile session are handled. We may ask you to confirm the account detail before discussing personal data, so a request reaches the correct account.

Wallet data query

For a DANA, OVO, GoPay or QRIS question, send the payment reference shown in your account area rather than your wallet password. We can check the status record and explain what was stored for matching, receipt handling or account support.

Policy change request

Ask us to correct an account detail, explain a cookie choice or clarify retention through the same support path. Tell us which record concerns you, and we will confirm the next step after checking your account identity.

HOW WE HANDLE DATA

Protect Your Account Data On Mobile

Privacy is handled through practical account controls rather than broad promises. We separate sign-in checks from payment references, limit staff access to records needed for support, and use session controls when you…

Account details

We collect the details needed to create and maintain your account, including your phone number for verification. If a detail is incorrect, contact us through the account support path and describe the correction without sending a password or wallet PIN.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt with the correct account. We use the reference and status result for that purpose, not as a reason to request your wallet password.

Cookies and sessions

Cookies can remember settings and help maintain a sign-in session on your mobile browser. You can clear browser cookies through your device settings, though doing so may require another phone verification step when you return.

Account security

Phone verification helps us check account access before personal details are discussed. Keep your password and wallet credentials private, sign out on shared devices, and contact support if a session remains open after you leave the account.

Retention choices

We retain account, payment and support records only while they serve account operation, security or legal needs where local law permits. When a record no longer has that purpose, our process removes it or separates it from direct account identity.

Your request route

You can ask what personal data we hold, request a correction, question a payment reference or ask about removal. Send the request through account support with enough detail to identify you, and we will explain any legal reason a record must remain.

Browse Privacy Policy Answers

These Privacy Policy answers cover the questions we expect before account access: what we collect, why payment references appear, how mobile cookies work and how to request a change. If your situation is not covered, use the support path in your account and mention the relevant device, phone-verification step or payment rail.

It covers account details, phone verification, sign-in and device sessions, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security steps and how to request access or correction.

We use your phone number for the account verification step and to help match you with the correct account when support handles a data request. We do not need your wallet password for this check. Keep your number current so access questions can be resolved.

Yes. The Privacy Policy covers payment references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records help match receipts to your account and answer payment-status questions.

Cookies can retain selected settings and support a sign-in session when you use a mobile browser. Clearing them in your device or browser settings may sign you out and trigger phone verification again. Our policy explains why those session details are used.

Yes. Use the support route in your account, identify the detail you believe is wrong and explain the correction. We may verify your phone or another account detail before changing the record, so personal data is not altered on an unconfirmed request.

We keep account, payment and support records while they are needed for account operation, security or legal duties where local law permits. After that purpose ends, we remove the record or separate it from direct account identity under our retention process.

Sign out of the affected device, change your account password and contact support through the account path. Mention whether the session appeared on mobile or desktop and avoid sending wallet credentials. We can then check access records and explain the next security step.