Reference

mposurga Privacy Policy, Clearly Explained

mposurga Privacy Policy shows how we collect, use and protect the account details connected with DANA, OVO, GoPay and QRIS activity.

Account dataWallet recordsCookie choicesRequest support
mposurga mposurga Privacy Policy, Clearly Explained
REQUEST HELP DIRECTLY

Three Ways To Ask About Your Data

A clear contact path makes a Privacy Policy request easier to resolve. We route account, payment and cookie questions to the right checks instead of asking you to repeat sensitive details in a public message. Use the account contact route, describe the request in plain English, and include only the account detail needed to locate your record.

Team online

Account contact

Ask us to confirm the account data linked to your phone verification step. We may request an account identifier before discussing personal details, so your request reaches the correct record without exposing it through a shared device.

Cashier records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, mention the payment reference and date. We use that pair to check status while avoiding requests for your wallet PIN, password or full banking credentials.

Policy changes

If you want to correct, remove or restrict a data use, send the request through our account support route. We will explain what can change, what must remain for a legal or dispute reason, and what verification is required.

HANDLING YOUR RECORDS

Six Practical Privacy Commitments

Privacy is handled through ordinary account steps rather than hidden settings. We separate login protection from payment references, explain why cookies appear, and keep a route for correction or deletion requests.

Account details

We use your account and phone verification details to identify the correct account, handle sign-in events and respond to requests. We do not need your wallet PIN or banking password to check a DANA, OVO, GoPay or QRIS reference.

Device signals

A mobile browser may send browser type, operating system, language and security events. These signals help us recognise unusual login activity and keep the account path consistent when you move between the lobby and cashier.

Cookie controls

Cookies can remember a session, preserve a selected language or help us understand which page produced a technical error. You can adjust cookie settings in your browser, although removing them may require another login.

Payment matching

We keep transaction references and status details so a deposit or withdrawal query can be checked. The record may show a rail such as QRIS or bank transfer, but it is not a request for your private wallet credentials.

Retention steps

We retain account, security and payment records while they support account operation, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it or reduce its identifying detail.

Change requests

You can ask us to access, correct or delete personal data through the contact route. We may verify your account first, and we will explain if a limited record must stay because of a transaction or legal obligation.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account questions you are most likely to have before opening an account or checking a payment record. We keep the examples tied to Indonesian wallet rails, mobile access and the steps used to verify a genuine request.

The mposurga Privacy Policy covers details such as your account identifier, phone verification status, login events, device signals and support messages. We use them to provide account access, investigate security events and answer requests, with access depending on local law.

We do not need your wallet PIN or password to match a payment. We may retain a reference, amount, date, rail and status for DANA, OVO, GoPay or QRIS so support can check a cashier question without receiving private wallet credentials.

A mobile browser can provide its type, operating system, language and security events. We use these signals to protect sign-in, investigate unusual access and diagnose a page problem. They also help keep your account session working when you move through the lobby.

We keep records while they are needed for account operation, security checks, payment disputes or a legal requirement. After that need ends, we remove the record or reduce identifying details under our retention process; exact timing can depend on the record type.

Use the account support route and state whether you want access, correction, deletion or a restriction on a particular use. Include an account identifier, not a wallet PIN. We may verify phone ownership before replying, and access depends on local law.

You can submit that request through account support, including the payment rail and reference. We assess it against the Privacy Policy and applicable rules. A record may need to remain for a dispute, transaction trace or legal obligation, and we will explain why.

Send the concern through the policy contact route and describe the page, device and issue without sharing your password. For cookies, you can also change browser settings. We may ask for a verified account detail before discussing personal records.