Reference

mp1221 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an mp1221 account, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data categoriesWallet record handlingCookie choicesAccount access rights
mp1221 mp1221 Privacy Policy For Your Account
REQUEST SUPPORT

Open A Privacy Request Through Account Help

A clear support route helps you ask about the Privacy Policy without sending sensitive details to the wrong place.

Account access If you cannot reach your account, use the account help path and include the contact detail attached to your login. We check ownership before discussing stored records, so another person cannot request your account data through a simple message.
Wallet status For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the payment reference shown in your account. We use it to locate the transaction record without asking you to share a wallet password or secret code.
Data changes To request a correction, access copy, or deletion assessment, state the exact account detail involved and the result you want. We may confirm your identity first, then explain what can be changed or retained where local law permits.
DATA PRACTICES

Browse The Privacy Steps Behind Your Account

We keep this Privacy Policy practical by describing the records created at each account step rather than treating privacy as a general statement.

Account records

When you create or access an account, we may store contact details, verification status, login events, and support messages. These records help us confirm that a privacy request comes from the account owner and resolve access questions.

Device signals

Your browser or phone can provide technical signals such as device type, operating system, language, IP area, and session time. We use these signals to protect sign-in activity and understand whether a request relates to your current account session.

Cookie controls

Necessary cookies help keep your account session connected while you move between pages. Where optional cookies are used, your browser settings can restrict them; changing those settings may affect saved preferences but does not erase account records.

Payment matching

A DANA, OVO, GoPay, or QRIS reference can appear beside an account action so we can match the correct wallet event. We do not ask for your wallet PIN, one-time code, or full secret credential in a support request.

Retention checks

We assess account, security, support, and payment records according to their purpose. When a record is no longer needed, we remove or separate it where possible, while certain records may remain when a legal or dispute obligation applies.

Change requests

You can contact us through the account help route to ask what data we hold, request a correction, or ask about removal. Include your account contact detail, but do not send a password or wallet security code with the request.

Get Answers About Privacy Policy Access

These Privacy Policy answers address the searches we expect when you are deciding whether to open an mp1221 account or checking an existing account record. We keep each answer tied to a real step: account access, device use, cookies, payment references, and requests sent through support. If your case involves a local requirement, the outcome depends on local law.

The mp1221 Privacy Policy covers account details, verification records, device and browser signals, cookies, support messages, and payment references. It explains why we use each category, how we protect access, and how you can ask about correction, access, or removal where local law permits.

We use DANA, OVO, GoPay, or QRIS references to match a wallet event with the correct account and investigate a status question. We do not need your wallet PIN or one-time code for that process, and you should not include either in a support request.

Yes, you can send an access request through the account help path. Include the contact detail connected to your account and describe the records you want. We may verify ownership before responding, then explain the available format and any limits that depend on local law.

Use account help to name the incorrect detail and provide the corrected value. We may ask you to complete an account verification step before making a change. Payment references and security records can have separate retention needs, so we will explain any part that cannot be edited.

We use necessary cookies or similar session tools to keep sign-in activity connected and protect page access. Your phone or browser settings can restrict optional cookies. Blocking necessary session tools may affect account access, but it does not automatically remove stored account or payment records.

Retention depends on why the record exists. Account, support, device, security, and payment records are kept while needed for access, matching, dispute handling, or legal duties. We assess removal when the purpose ends, subject to limits that depend on local law.

Start with the account help route connected to your mp1221 access screen. Select the privacy or data request reason, identify the account contact detail, and describe the action you want. Do not send your password, wallet PIN, or one-time code with the request.