Reference

Privacy Policy For DANA And QRIS Records

Our mp007 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 transaction.

Account recordsWallet activityCookie choicesPolicy requests
mp007 Privacy Policy For DANA And QRIS Records
HELP WITH PRIVACY

Request Help From Your Account

Privacy questions should have a clear route, so we keep policy support close to the account help area rather than sending you through unrelated pages. You can ask what record we hold, why a wallet reference appears, or how to request a correction. Include your account contact and the relevant date so we can locate the right entry without asking for your full wallet credentials. In Surabaya and across Indonesia, requests remain subject to where local law permits.

Team online

Account help route

Open the account help route and select the privacy subject when you need access, correction, or deletion assistance. We use your verified account contact to match the request, while you should never send a DANA, OVO, GoPay, or QRIS PIN.

Payment record check

If a wallet record looks unfamiliar, share the date, amount reference, and rail name through account support. We can compare the stored transaction status with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records.

Access request

Ask for a copy of the personal data linked to your account through the same support path. We may verify ownership before responding, because releasing account or device records to the wrong person could expose your account.

DATA PRACTICES

How mp007 Handles Account Data

We separate the records needed to run account access from the signals used to protect a sign-in session.

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification before access.

Device signals

A mobile or desktop sign-in can create device, browser, language, and connection records.

Cookie controls

Cookies can remember a session choice and help pages load the account path you selected.

Wallet references

We store payment references and status details rather than your wallet PIN.

Security checks

We use account contact checks, sign-in records, and device signals to protect access.

Retention requests

We keep personal data only while it supports account operation, security, dispute handling, or a legal need.

Privacy Policy Questions For mp007

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the connection between account access, device behaviour, cookies, and local wallet records without asking you to share sensitive credentials. If your question concerns a specific record, use the account help route and mention the date or account step involved.

The mp007 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references. It explains why we use each category, how long we retain it for an operational purpose, and how you can request access or a correction.

Yes. The Privacy Policy covers the account-linked reference and status for DANA, OVO, GoPay, and QRIS activity, along with bank transfer or virtual account records. We do not need your wallet PIN to investigate a receipt, status mismatch, or account question.

Open the account help route, choose the privacy subject, and ask for the records linked to your account. Include your verified contact and a useful date range. We may confirm account ownership before sending a copy or discussing device, cookie, or wallet details.

You can request a correction through account support when a profile detail, phone record, or payment reference is inaccurate. Tell us which entry is wrong and provide the correct detail. We review the request against account records before applying a change.

On mobile, cookies can keep a sign-in session and remember the route from account access to the lobby. Browser settings let you remove or block them, but required cookies may be needed for phone verification and secure account continuity.

We retain personal data while it is needed for account operation, security checks, payment reconciliation, dispute handling, or a legal requirement. When that purpose ends, we remove or anonymise the record where applicable, subject to local law and unresolved requests.

Yes. Your rights to access, correct, restrict, or delete data depend on local law. We respond where local law permits, verify the account holder before disclosure, and explain if a record must remain for security, dispute, or legal reasons.