Reference

Privacy Policy for Your Indonesia Account

Your Speed Baccarat, Aviator, and DANA wallet activity all create data points, so our Privacy Policy explains what we collect before you open your account.

DANA privacy contextOVO data checksGoPay wallet recordsQRIS payment logs
mpo222 Privacy Policy for Your Indonesia Account
PRIVACY CONTACTS

Contact Us About Your Privacy

A privacy question should reach a real support path, not a dead mailbox. We keep three contact routes open for account data requests, cookie questions, wallet record checks, and correction requests. Before we change stored details, we may ask you to confirm your registered phone, last payment rail, or the device shown under Account > Security > Active Devices.

Team online

Live Chat

Use the chat bubble inside the lobby from 09:00 to 02:00 WIB for quick privacy questions. We can confirm where to find cookie settings, active sessions, and wallet record summaries after you verify your account.

WhatsApp Privacy Desk

Message our WhatsApp line from the registered phone number when you need a data correction or account access check. We may ask for your last DANA, OVO, GoPay, or QRIS reference to match the request.

Email Request

Send detailed privacy requests to [email protected], especially if you need a written response about stored account data. Include your username, registered phone, request type, and the date range you want checked.

ACCOUNT CARE

Controls Behind Your mpo222 Account

Privacy protection works through small checks you can see during normal use. We separate login data, wallet records, cookie choices, and support messages so each request can be…

Registration Data

When you create an account, we collect the details needed to identify you inside the wallet and support systems.

Payment Privacy

For DANA, OVO, GoPay, and QRIS, we store transaction references, time stamps, channel names, and status results.

Device Sessions

You can check signed-in devices through Account > Security > Active Devices.

Cookies

Cookies help us keep you signed in, remember language settings, and measure page errors.

Data Retention

We keep account and wallet records only for operational, dispute, security, and legal needs that apply to our service.

Correction Requests

If your phone number, email, or name is wrong, contact us before making wallet requests.

Privacy Questions Before You Join

Before you open an account, you may want to know exactly what happens to your data. These answers focus on account privacy, wallet records, device sessions, cookie settings, and how to reach us. If your question involves access or eligibility, local law decides whether the service is available to you.

It covers the data you give us during registration, the device and login records created when you access the lobby, wallet references from DANA, OVO, GoPay, or QRIS, and support messages linked to your account.

No. We store payment references, channel names, status results, and time stamps needed to reconcile your wallet activity. Your wallet PIN, app password, and bank login details stay outside our account system.

Open Account > Security > Active Devices after logging in. You can compare device names, recent access times, and location signals, then contact us through live chat if a session does not look familiar.

Yes. Contact live chat, WhatsApp, or [email protected] with your username, registered phone, and the field that needs correction. We verify the account first to protect you from unauthorized data changes.

We use cookies to keep sessions active, remember basic preferences, detect login errors, and understand which pages need technical fixes. You can clear cookies in your browser, but another login check may follow.

We share limited data only when needed for payment processing, fraud checks, account service, technical hosting, or lawful requests that apply to us. We do not sell your account profile to outside advertisers.

Simple corrections can often be handled during support hours after verification. Requests that involve account history, wallet references, or multiple devices may take longer because we check the data trail before replying.