Reference

pm200 Privacy Policy for Wallet Data

pm200 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS for a wallet action.

Account clarityWallet recordsCookie choicesAccess requests
Browse Our Lobby Read FAQ
pm200 pm200 Privacy Policy for Wallet Data
CONTACT YOUR WAY

Get Privacy Help Near Account Support

A clear contact path matters when a privacy request and a wallet record meet. We ask you to use the support route connected to your account so we can confirm which profile…

Account request Send a privacy question through the account support path and identify the email or phone detail linked to your pm200 profile. This lets us check the correct record before discussing access, correction or deletion requests.
Wallet receipt For a DANA, OVO, GoPay or QRIS question, include the transaction reference and approximate date. We use those particulars to locate the relevant payment record without asking you to send an unnecessary full wallet history.
Access concern If a sign-in or device detail appears unfamiliar, contact support from the account route and describe the device path you used. We can review the access concern and explain which policy purpose relates to the check.
CONTROL YOUR RECORD

Keep Account And Cookie Choices Clear

We explain our handling in plain terms so you can decide what to share before account access.

Data collection

We collect account details you submit, access events from the device you use, and transaction references created when you choose a wallet rail. The Privacy Policy explains why each category is needed rather than treating every detail as interchangeable.

Cookie settings

Cookies can remember a language or sign-in setting and may help us understand a page path. You can manage available browser controls, although removing necessary cookies may affect account access or require you to sign in again.

Account security

Phone verification before account access helps connect a sign-in to the correct profile. We may compare device and access signals when activity looks unusual, and we use that check to protect your account rather than to expand the policy purpose.

Retention timing

We keep account and wallet records for as long as needed for the stated service, security, dispute and legal purposes. When a record no longer serves those purposes, our retention process addresses removal or further restriction.

Request changes

You can ask us to correct inaccurate account details, explain a data use, or consider an eligible deletion request. We may ask for account confirmation first so a private record is not changed after an unverified message.

Policy contact

Use the account support route for privacy questions and describe the specific record or purpose you are challenging. We will assess the request under the Privacy Policy and applicable local requirements, including where local law permits.

Privacy Policy Answers For pm200 Accounts

These Privacy Policy answers address the questions we expect before account opening or a wallet action. They cover the records created by login, phone verification, cookies and Indonesian payment rails, while keeping the focus on your data choices. If your situation is not listed, use the account support path and tell us which part of the policy you want clarified.

It covers account details, phone verification, device and access signals, cookie settings, support messages, and wallet records from DANA, OVO, GoPay or QRIS. It also explains purposes, retention, security handling, your available requests and the contact route for policy questions.

We keep relevant references, status details and account identifiers so we can match a DANA or QRIS action to your profile, check a receipt and investigate a stalled status. The Privacy Policy limits that handling to stated operational, security, support and legal purposes.

Yes. Send a correction request through the account support path and identify the profile detail you believe is wrong. We may confirm your account first, then assess the requested change against the Privacy Policy, available records and local requirements.

The policy explains cookies that remember settings or support access paths on your phone. Browser controls can remove or restrict some cookies, but necessary settings may be required for sign-in. We do not treat cookie preferences as permission to use unrelated account data.

Contact us through the account support route and specify which information you want reviewed for removal. We first confirm the request, then check whether the record must remain for account security, wallet reconciliation, disputes or legal duties described in the Privacy Policy.

The policy is written for Indonesian account access, including wallet activity from places such as Semarang. Any access or eligibility question depends on local law. If a local requirement affects your request, contact support and state your location and the policy issue.

Use the account support path and describe the device, sign-in time and access route you recognise or do not recognise. We may ask for account confirmation before discussing the record, then explain the relevant security handling under the Privacy Policy.

Related Pages

pm200 Indonesia Local Payment Options Account information About Us Access guide