Reference

Privacy Policy for Your mpv123 Account

Our Privacy Policy explains what we collect when you open an mpv123 account, use DANA or QRIS, and move through the lobby from a phone or desktop.

Clear data purposesWallet activity contextAccount access requestsCookie choices
Browse The Lobby Read FAQ
mpv123 Privacy Policy for Your mpv123 Account
HELP WITH PRIVACY

Reach Us About Your Data

A clear contact path matters when you cannot identify a wallet record or need to ask what an account field means.

Privacy request Ask us to explain, correct or remove personal data through the account support path. We may request a verification step before discussing records connected with your mpv123 account, especially when the request concerns wallet activity or phone details.
Wallet record query If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount reference and linked account detail through support. We use those details to locate the relevant record without asking you to disclose a password or one-time code.
Access assistance When your phone verification or login step stalls, contact us through the same support route and describe the device path you used. We can check the account state and explain which Privacy Policy request steps apply where local law permits.
DATA HANDLING DETAILS

What We Do With Policy Requests

We keep this Privacy Policy practical by separating account operations from questions about your personal data.

Account data

We may handle your account name, contact detail and phone verification status to create access and respond to account requests. We use these fields for the stated account purpose rather than treating every page visit as a request for extra personal detail.

Payment records

A wallet or bank record can show the selected rail, transaction reference and status needed to match a cashier event. This may include DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI context when supplied during a transfer.

Cookies

Essential cookies help keep your session and account path working between login, verification and the lobby. Where optional cookies are available, we explain their purpose through the relevant page controls so you can make a clear choice.

Device signals

We may receive browser, device and connection signals to keep sessions consistent and identify unusual account access. On mobile, these signals help us distinguish a return to the same account path from a new sign-in that needs further checking.

Retention

We retain account and payment records for the time needed to operate the account, resolve disputes, protect access and meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows the deletion or restriction rules that apply.

Change requests

You can ask about access, correction, deletion or a restriction through account support. Tell us which data you mean and use the contact detail connected to your account; we verify the request before sharing or changing records where local law permits.

Privacy Policy Answers for mpv123

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. We focus on the data path you can actually recognise: phone verification, mobile sessions, payment references, cookies and requests sent through support. If your situation is different, contact us with the account detail and date involved. We will explain the next step and apply the rules that depend on local law.

It covers personal data used for your account, phone verification, wallet and bank transfer records, device signals, cookies and support requests. It also explains why we use each category, how we protect account access and how you can ask about, correct or restrict relevant records.

Phone verification helps us connect account access with the contact detail you provide and identify requests that involve your account. If the verification step fails, use the account support path rather than sending a one-time code. Any access decision depends on local law.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. We use those details to reconcile an account event and respond to a wallet question, not to request your password or full payment credentials.

You can send an access request through account support using the contact detail linked to your account. Describe the records you want, such as phone verification or a QRIS reference. We may verify your identity first, and the response depends on local law and applicable exceptions.

Contact us through the account support route and name the field that needs correction. Include the linked phone or email detail and explain what is inaccurate. We review the request against the account record before changing it, with the result determined where local law permits.

Essential cookies support the mobile path between login, phone verification and the lobby. Optional cookies, where available, are described through the page controls that accompany them. Clearing cookies can end a session or require another account check, so keep your login details private.

We keep records for the period needed to operate your account, investigate payment questions, protect access, resolve disputes and meet legal duties. The period can differ by record type, including DANA, bank transfer and verification data. Deletion requests are assessed under the rules that apply.

Related Pages

mpv123 Indonesia Live Blackjack Diamond Account information Access guide Live Casino Mission