Reference

Privacy Policy for mpoid Accounts

mpoid Privacy Policy explains how we collect, use and protect the details connected to your account, wallet activity and device access.

Account detailsWallet recordsCookie choicesAccess requests
mpoid Privacy Policy for mpoid Accounts
CONTACT OUR TEAM

Privacy Help Near Your Account

A clear contact route matters when your Privacy Policy question involves an account or wallet record. We ask you to use the support route shown after login and include the phone number or account identifier connected with your request. That lets us check the correct profile without asking you to send a wallet password or full payment credentials. Support can help with access requests, correction requests, cookie questions and payment-record clarification.

Team online

Account support

Use the signed-in support channel for a Privacy Policy request linked to your profile. Include your verified phone number, the subject of the request and the account step where the question arose, so we can reduce back-and-forth.

Wallet status

For DANA, OVO, GoPay or QRIS records, send the date, amount reference and visible status rather than your wallet PIN. We can explain which record mpoid holds and which detail remains with the payment provider.

Privacy requests

Request data access, correction or deletion through the contact path in your account area. We may ask for phone verification before discussing personal data, helping prevent another person from receiving your account details.

DATA HANDLING

What We Keep And Why

We handle Privacy Policy matters through defined account steps rather than vague promises. Phone verification helps us match a request to your profile; device signals help identify unusual sign-in activity; and payment…

Account details

We use your account name, contact details and phone-verification state to provide access and respond to requests. If a detail changes, contact us through the account path and tell us which field needs correction.

Device signals

Browser, device and session signals help us notice unusual access and protect your profile. They are not a substitute for your password, and we do not ask you to reveal wallet PINs when checking a payment issue.

Cookies

Cookies can remember sign-in preferences, support page state and policy choices on your device. You can adjust browser settings or contact us about cookie use, although some account functions may then require extra steps.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may help us match a transaction status. We use the reference for checking, while wallet credentials and bank login details stay outside our account records.

Retention

We keep personal data for the period needed to operate the account, resolve disputes, prevent misuse and meet legal duties. When those reasons end, handling follows the deletion or anonymisation process described in our Privacy Policy.

Your requests

You can ask for a copy, correction or permitted deletion of personal data by contacting support. We may verify your phone or account ownership first, then explain the result, any lawful exception and the next available step.

Privacy Policy Questions Answered

These Privacy Policy answers address the searches we hear most often from Indonesian customers before they open an account. They explain what we collect, how wallet references are handled, how to request a copy and why phone verification may be needed. If your situation is not covered, contact us through the signed-in support path with the smallest useful detail.

The mpoid Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can request access or correction where local law permits.

It covers the transaction references and status details we receive for DANA, OVO, GoPay and QRIS. We use those details to match an account or investigate a status. Your wallet PIN, bank login and full payment credentials are not requested through our support process.

Send a data-access request through the support route available after login. Include your verified phone number and the account email or identifier connected to the request. We may complete an ownership check before explaining which records we can provide under applicable law.

Yes, you can ask us to correct inaccurate account or contact details through support. State the field that is wrong and the replacement value. We may request phone verification, and we will explain if a payment or legal record cannot be changed.

Cookies can retain policy choices and sign-in state, while device and session signals help us detect unusual access. You can change cookie settings in your browser or ask support about them. Disabling some cookies may make sign-in or account checks require extra steps.

Retention depends on the reason for keeping a record, such as account operation, payment checks, dispute handling, misuse prevention or legal duties. Our Privacy Policy explains the applicable periods and processes. Contact us with a specific record if you need a tailored answer.

You can submit a deletion request through the account support path. We first verify ownership, then assess the request under applicable law. Some records may need to remain for a dispute, payment reconciliation, misuse prevention or legal duty, and we explain that result.