Reference

p200m Privacy Policy For Your Account

p200m Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity in Indonesia.

Account clarityWallet dataCookie choicesPolicy access
p200m p200m Privacy Policy For Your Account
CONTACT THE DESK

Privacy Policy Help When Account Status Stalls

A direct support route helps you understand a Privacy Policy request without sending sensitive details through an unsuitable channel.

Account privacy request Ask us to locate the personal data linked to your account. Include your registered phone number and the subject Privacy Policy request so we can verify ownership before discussing account records.
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the payment reference rather than a wallet password or full security code. We use the reference to trace status without asking you to expose private credentials.
Access and correction If your account details are outdated, contact our support channel with the requested change and a clear reason. We may ask for phone verification before changing identity or payment-linked information.
OUR DATA PRACTICE

Inside p200m Privacy Policy Controls

We keep the Privacy Policy practical by connecting each data practice to an account task you can recognise.

Account data

We may hold your phone number, account identifiers, verification outcome and sign-in history so we can provide access and handle account requests. We use the minimum details needed for the stated account purpose.

Device signals

Your mobile browser or desktop session can produce security signals such as device type, session time and network details. These help us detect unusual sign-ins without requiring a separate application download.

Cookies

Cookies can remember your selected settings and support page operation. You can manage browser cookie controls, though refusing some cookies may affect sign-in flow or the way policy pages load.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions can leave references, amounts and status results. We use those records to match account activity and resolve receipt questions.

Retention

We keep records only for the period connected with account security, payment matching, support handling or a legal requirement. When a record is no longer needed for those purposes, our process addresses its removal or restriction.

Your request

You can ask for access, correction or clarification through the support path. State the account phone number and requested action, and we will explain any identity check or lawful reason that affects the response.

Privacy Policy Questions For p200m

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording tied to real p200m steps, from phone verification and mobile sessions to DANA, OVO, GoPay and QRIS records. If your situation is not covered, contact support with your account reference; access remains subject to local law.

The p200m Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can ask for access or correction through our support path.

We use your phone number to create and secure the account, support verification and connect account requests to the correct record. Before discussing private account data or changing identity details, we may ask you to complete a phone verification step.

Yes. Privacy Policy covers payment references, wallet status, receipt details and reconciliation results connected with DANA, OVO, GoPay and QRIS. We use these records to match an account action, investigate a missing status and answer a payment support request.

You can request access to personal data linked with your account by contacting support through the channel displayed on p200m. Include your registered phone number and describe the request. We may verify account ownership before releasing private records.

Send a correction request through support and identify the account field that needs changing. We may request phone verification or another account check, especially when the change affects sign-in, payment matching or the identity details used for account security.

Cookies can keep page settings and support the sign-in path on your mobile browser. They can also help us understand policy-page access and diagnose loading problems. Your browser controls can restrict cookies, but some account functions may then behave differently.

Retention depends on why a record exists. Account security, payment matching, support handling and legal requirements can require different periods. When the relevant purpose ends, our process addresses deletion or restriction, subject to any remaining lawful need to retain the record.