Reference

Open Your Privacy Policy Before Account Access

One clear privacy file covers your account setup, DANA, OVO, GoPay and QRIS wallet records, and session logs from Baccarat, Aviator and Buffalo King.

Account data explainedDANA and QRIS contextCookie choicesPrivacy contact paths
mpo55 Open Your Privacy Policy Before Account Access
CONTACT PATHS

Contact Us About Your Privacy Choices

Privacy questions need a channel that verifies you before we discuss records. Use live chat, WhatsApp, or email, and include only your username until our team asks for the next account step. From mobile, open Profile > Privacy Requests to ask for correction, export, or deletion where local law permits. Our privacy desk is available every day, 09:00 to 02:00 WIB, with email follow-up kept inside your account case.

Team online

Live chat

Open live chat from the footer or wallet page between 09:00 and 02:00 WIB. Ask for the privacy desk, share your username only, and we will verify the account before discussing records.

WhatsApp support

Message the WhatsApp support line listed inside your account menu for privacy questions about DANA, OVO, GoPay or QRIS references. We confirm account ownership first, then keep the reply tied to your case.

Email requests

Send longer privacy requests to [email protected] with your username, contact email, and the data action you need. We answer from the same case thread so your request history stays easy to check.

DATA CARE

Protect Your Data Inside The Lobby

A Privacy Policy should match how the account actually works. We separate identity records, wallet references, login security events, cookie settings, and lobby activity so each privacy request can be handled by…

Account setup records

We store the details you enter during account creation, including username, phone number, email if added, and password status. Passwords are protected in our systems, and support cannot read your password.

Wallet privacy

DANA, OVO, GoPay and QRIS references are kept with transaction IDs, time stamps, status changes, and account username. We use those records to reconcile payments and answer privacy questions about wallet activity.

Cookie controls

Cookies help keep you signed in, remember language choices, and protect sessions on the device you use. You can clear browser cookies or open Profile > Privacy Requests to ask about stored cookie-related records.

Security alerts

New-device login events, failed password attempts, IP changes, and session time stamps help us detect account access risk. If something looks wrong, support verifies you before discussing any privacy or security record.

Retention rules

We keep account, wallet, support, and session records only as long as needed for service, disputes, fraud checks, and lawful duties. After that period, records are deleted, anonymised, or separated from direct account identity.

Change requests

You can ask us to correct contact details, check stored account data, or request deletion where local law permits. Start from Profile > Privacy Requests so the team can verify ownership before making changes.

Ask About Your Privacy Policy Rights

These questions focus on what you share with us, why we collect it, and how you can control it. Read them before you open an account or before you send a privacy request. If your case involves a wallet record, include whether it relates to DANA, OVO, GoPay or QRIS so we can locate the right privacy file.

We collect the account details you provide, such as username, phone number, password status, device data, IP address, and wallet reference if you connect DANA, OVO, GoPay or QRIS for account activity.

We keep payment references to match deposits and withdrawals with your account, trace disputed transactions, prevent wallet misuse, and answer privacy requests. The record normally includes status, time, amount, rail name, and transaction ID.

Yes. Open Profile > Privacy Requests and choose correction, then tell us which field is wrong. We verify account ownership first, because changing phone, email, or wallet data affects privacy and account access.

Cookies keep your session active, remember display choices, and help detect unusual login patterns. You can clear them in your browser settings, though you may need to sign in again afterward.

We keep records for the period needed to run the account, handle disputes, secure payments, answer support cases, and meet lawful duties. When that need ends, we delete or anonymise eligible records.

Only staff who need the data for support, payment reconciliation, account security, or privacy requests can access it. We use role-based access and case logs so account record checks are traceable.

The policy explains data handling; access itself depends on local law. If access is available where local law permits, we still ask you to read the policy before sharing account or wallet details.