Reference

Your privacy choices before the lobby

Your account, wallet, and lobby activity sit under one privacy policy before you use DANA, OVO, GoPay, or QRIS on mega 55.

DANA data scopeOVO recordsQRIS receiptsDevice controls
mega 55 Your privacy choices before the lobby
REQUEST PATHS

Reach us about privacy requests

Fast privacy support starts with the account detail you can confirm. Use the same email or phone linked to your account, then tell us whether you want access, correction, deletion, cookie help, or a session check. Our team answers through live chat, email, and the account center, with live chat staffed daily from 10:00 to 22:00 WIB. We may ask for a one-time code so we do not expose your data to another person.

Team online

Live chat privacy routing

Open live chat from the bottom corner between 10:00 and 22:00 WIB. Tell us the email or phone on your account, and we will route privacy access or correction requests to the account team.

Email privacy desk

Send privacy questions to [email protected] with your registered email, request type, and a recent login device. We do not ask for your password, wallet PIN, or full DANA, OVO, GoPay details.

Account device checks

Use Account > Security > Devices to see active sessions before you contact us. If one looks unfamiliar, choose sign out, change your password, then send us the time and device name.

ACCOUNT SAFETY

Controls behind your data trail

Privacy works only when account, wallet, and device records are handled with clear steps. We separate payment references from login credentials, keep session records for security checks, and restrict privacy request handling…

Account data

We collect the fields needed to create and maintain your account, such as registered email, phone, username, password hash, and verification status. Extra identity checks may apply before a withdrawal request is released.

Payment records

For DANA, OVO, GoPay, and QRIS, we store transaction references, amounts, timestamps, and account matching results. We do not store wallet PINs or full credentials from your payment app.

Device activity

Login records include IP address, browser type, device label, and session time so we can spot unusual account access. You can clear old sessions through Account > Security > Devices.

Cookie controls

Cookies keep your session active, remember language preference, and measure page errors. On Android Chrome, adjust them through Settings > Site settings > Cookies; on Safari, use Settings > Safari > Advanced.

Lobby records

When you open Live Casino, Aviator, Super Bingo, or Mega Fishing, we record session IDs, game timestamps, and wallet movements. These records help reconcile account balance and support disputed rounds.

Retention requests

We keep account and transaction records only for operational, security, and legal needs. To ask for correction, access, or deletion, email [email protected] and include your registered email plus request category.

Privacy questions we answer every day

Your privacy request should not feel like a maze. The answers below explain what we collect, how wallet references are handled, how you can ask for a copy of your records, and what happens when you change account details. If your case involves a device you no longer control, start with Account > Security > Devices, then message us so we can help protect the account while handling the privacy request.

We collect account fields you submit, device and login records, cookie choices, wallet transaction references, and support messages. We use these to create your account, protect sessions, reconcile wallet activity, and answer your privacy requests.

No. For DANA, OVO, GoPay, and QRIS, we keep references such as transaction time, amount, and matching result. Your wallet PIN, one-time code, and full payment app credentials stay outside our systems.

Email [email protected] from your registered email and write data access in the subject. We may ask you to confirm a one-time code or recent login device before sending account records.

Open Account > Profile to update editable fields such as phone or email, then confirm the code we send. For locked fields, contact support so we can check account ownership before making a change.

We use cookies for login state, language preference, security checks, and error measurement. You can change browser cookie settings, but blocking essential cookies may sign you out or stop wallet pages from loading.

Retention depends on the record type. Session logs are shorter, while payment and withdrawal records may be kept longer for reconciliation, fraud checks, and legal needs that apply where local law permits.

Access to some account functions depends on local law. When a privacy request concerns restricted account activity, we still process the request, but we may need extra verification before sharing or changing records.