Reference

mpl77 Privacy Policy For Your Account

The mpl77 Privacy Policy explains what account, device and wallet details we use when you access Dragon Tiger, Aviator or other lobby categories.

Clear data purposesWallet status contextAccount access choicesIndonesia policy scope
Explore Lobby Read FAQ
mpl77 mpl77 Privacy Policy For Your Account
HELP WITH DATA

Three Clear Routes For Privacy Requests

A privacy question should not leave you searching through the lobby. We keep the support path close to the account and cashier areas so you can identify the record involved, explain the…

Account access If phone verification blocks your account, tell support that the request concerns access data. We can use the registered account details to locate the issue without asking you to post private credentials or a wallet PIN.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference through the account support route. We use that reference to check status while keeping the wallet credential itself outside the request.
Privacy changes To ask for a copy, correction or deletion of eligible account data, state the change clearly and identify your account. We may ask for an account check before acting so another person cannot alter your records.
DATA PRACTICES

Six Practical Safeguards Behind This Policy

Privacy work is part of the account flow, not a separate page with vague promises. We separate identity checks from payment references, use device signals to help spot unusual access and keep…

Account details

We collect details needed to create and maintain your account, including a phone number used for verification. We do not need your wallet PIN for an account check, and you should never send that PIN to support.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us match a cashier event to your account. Bank transfer records may show BCA, BRI, Mandiri or BNI as the originating rail, without exposing your banking password.

Device signals

When you move from a phone browser to desktop, we may record device and sign-in signals linked to access security. These signals help us investigate an unexpected session without changing the Privacy Policy purpose of the data.

Cookies

Cookies can keep an account step, language setting or session state available while you move between the lobby and support. Browser controls may remove them, although clearing session cookies can require you to verify your phone again.

Retention

We keep account and transaction records for the period needed to provide support, protect access, resolve a payment status question or meet a legal duty. When that purpose ends, records are removed or handled under the applicable retention rule.

Your requests

You can ask what eligible data we hold, request a correction or ask how deletion applies to your account. Send the request through support with enough account detail for us to verify ownership, and we will explain any local-law restriction.

Privacy Policy Answers For mpl77 Accounts

Searches about the mpl77 Privacy Policy usually concern account creation, wallet records, phone verification and device access. These answers keep the focus on what we collect, why we use it and how you can ask for a change. If your situation is unusual, use the account support route and mention the exact policy question.

The mpl77 Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support records. It also explains how we handle data connected with lobby activity, such as Dragon Tiger or Aviator, when that detail is needed to resolve an account or status question.

We use your phone number for account creation and a clear verification step before account access. It helps us distinguish your request from another person’s request. We do not ask you to send a phone verification code or wallet PIN through a public channel.

Yes. The Privacy Policy covers the payment reference and status details needed to match DANA or QRIS activity with your account. It can also cover OVO, GoPay and bank transfer references, while wallet PINs, banking passwords and unrelated account data stay outside support requests.

You can request a correction through the account support route. State which detail is wrong and provide enough registered account data for an ownership check. We may ask for phone verification before changing it, and any restriction depends on local law.

Send a deletion request through support and identify the account connected with it. We first check ownership, then assess whether the record is still needed for a payment receipt, security matter, open support case or legal duty. Access depends on local law.

Cookies may keep your session, language choice or account step available in a mobile browser. They can support the path from login to the lobby, but clearing them may sign you out or require phone verification again. Your browser settings control cookie removal.

Use the account support route for questions about the mpl77 Privacy Policy, a device record, a wallet reference or a data change. Include the policy topic and registered account details through that route, never a password or wallet PIN. We respond with the next applicable step.

Related Pages

mpl77 Indonesia Access guide paitonsdy Dragon Tiger Account information