Reference

mpo1220 Privacy Policy for Your Account

Your mpo1220 Privacy Policy access starts with a clear account path: we explain what we collect when you open an account, use DANA or QRIS, and enter titles…

Clear data purposesWallet record detailsAccount access choicesPolicy contact path
mpo1220 mpo1220 Privacy Policy for Your Account
HELP WITH YOUR RECORDS

Privacy Questions Meet Our Support Team

A direct support route helps when your Privacy Policy question concerns an account field, wallet reference or access record.

Account access If you cannot open the account area, contact support through the available account channel and mention Password Reset Help. We check the account identifier and phone verification status before discussing stored details or changing an access route.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the transaction date and reference only. We use those details to locate the record without asking you to reveal a password or security code.
Policy requests You can ask what personal data we hold, request a correction, or ask about removal where applicable. Support is available from 08:00 to 23:00 WIB, and we may verify your account before releasing or changing information.
HOW DATA IS HANDLED

Inside mpo1220 Privacy Controls

We separate account operation from the information needed to answer a specific request. Your Privacy Policy rights are explained below through the practical steps we use for login, wallet matching, device security…

Account details

We collect details such as your account identifier, phone verification status and contact details when needed for access. We use them to maintain the account, respond to your requests and connect an authorised person with the correct record.

Payment references

A wallet or bank record can include a method name, amount reference, time and status. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references help us reconcile activity without needing your wallet password or banking login.

Cookies and sessions

Cookies and similar session tools help keep your account area signed in during a visit, remember security choices and measure page performance. You can adjust browser settings, although disabling necessary cookies may interrupt login or policy access.

Device security

We may retain device type, browser details, IP-related signals and session times to identify unusual access. These checks can apply when you move from mobile login to the lobby or return on desktop, helping us protect account ownership.

Retention timing

We retain account, payment and support records for as long as needed for account operation, dispute handling, security checks or legal duties. When a record no longer serves one of those purposes, we delete it or remove its link to you.

Changes and contact

To request access, correction or an eligible deletion, contact support using the account-linked channel and describe the specific record. We may ask for phone verification or another ownership check before making a change to your personal data.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account steps Indonesian customers ask about most: wallet records, mobile sessions, phone verification, cookies and requests for data access. We keep each answer tied to how our account and support process works, and access depends on local law.

The mpo1220 Privacy Policy explains the personal data we collect, why we use it, how we protect account access, how cookies work and when records are removed. It also sets out how you can contact support about access, correction or an eligible deletion request.

Phone verification helps us connect an account request with the person who opened the account and reduce unauthorised access. We may use the verification status when you reset access, ask about personal records or request a change to account details.

Yes. The Privacy Policy covers payment references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use method, time, reference and status details to reconcile an account event, while you should never send a wallet password or banking login.

We may store device type, browser details, session time and security signals connected with account access. This can apply when you log in on mobile, open the lobby, or return on desktop. We use these records to investigate unusual access and protect your account.

You can contact us through the account-linked support channel and ask what eligible personal data we hold. Describe the account record or date involved. We may verify ownership before responding, and the available request depends on local law and applicable retention duties.

Send a correction or eligible deletion request through support from the contact route connected with your account. Include the field or record you mean, not a password or security code. We first check ownership, then explain what can be changed or removed where local law permits.

We keep records while they are needed for account operation, payment matching, security checks, dispute handling or legal duties. After that need ends, we delete the record or remove its connection to you. A specific timing can depend on the record and local law.