Reference

Privacy Policy for Wallet and Account Data

Your account details, DANA, OVO, GoPay and QRIS records, device logins, and lobby choices such as Blackjack or Mahjong Ways are covered in this Privacy Policy.

DANA data contextOVO record handlingGoPay account checksQRIS transaction tracesDevice login records
macan88 Privacy Policy for Wallet and Account Data
CONTACT PATHS

Contact Us About Your Privacy Data

Privacy requests should reach the team that can read your account record, not a general inbox.

Live Chat privacy intake Use Live Chat from the lobby footer any time, including late Jakarta sessions. We can confirm which data we hold, record your privacy request, and tell you what account proof is needed next.
Private ticket follow-up For phone changes, wallet-name checks, or deletion requests, we move the case into a private ticket. We use ticket replies to avoid exposing DANA, OVO, GoPay, or QRIS references inside open chat.
Account center request Go to Account > Help > Privacy Request after login when you want a copy, correction, or update. The form adds your account ID, device type, and recent login time to the case.
ACCOUNT SAFETY

Data Controls Around Your Account

We handle privacy data through account steps you can see: registration, wallet matching, login checks, cookie choices, and support tickets.

Registration details

When you join, we collect details needed to create your account, such as contact data, login credentials, and account status. We use them to keep access tied to you and to send service messages.

Wallet verification

DANA, OVO, GoPay and QRIS records are checked against your account profile before wallet-related changes. We store references needed for reconciliation, dispute handling, and support follow-up, not public display.

Device login records

A new phone browser or large-screen browser can create a device record with time, IP range, and session status. We use this to spot unusual access and help you recover control.

Cookie handling

Cookies keep you signed in, remember language and lobby layout, and help separate your session from another account on the same browser. You can clear cookies, but you may need to log in again.

Retention controls

We keep account and payment records while they are needed for service operation, account disputes, fraud checks, and legal duties. After that period, we delete, mask, or separate records from active tools.

Correction requests

If your phone number, email, or wallet name changes, send a privacy request from Account > Help. We ask for proof before editing data so another person cannot redirect your account.

Privacy Questions Before You Open Account

Before you share account details, you should know what we collect, why we need it, and how to reach us when something changes. These answers focus on the privacy steps we apply around registration, wallet records, cookies, device access, and support cases. If your request involves eligibility or access, the outcome depends on local law.

We collect the account details needed to create and manage your profile, including contact data, login credentials, account status, and security records. We also record device and session details when you log in.

We keep payment references so our team can match your wallet activity, answer disputes, and verify account ownership. These records help us separate your wallet history from another account with similar details.

Yes. Send the request through Account > Help > Privacy Request after login. We will ask for identity proof before changing phone, email, or wallet-name data tied to your account.

Cookies remember your session, language setting, and lobby layout. They also help us identify whether a new browser is trying to access your account. Clearing cookies may sign you out.

We record session activity for account operation, security checks, and support context. If you open Blackjack, Mahjong Ways, or Crash Games, that activity may appear in account logs linked to your session.

You can ask for a copy through Live Chat or Account > Help > Privacy Request. We verify identity first, then provide available account data in a format our support team can safely share.

We keep records while they are needed for account service, wallet reconciliation, dispute handling, security checks, and legal duties. When no longer required, we delete, mask, or separate them from active systems.