Reference

Privacy Policy for Your mega 111 Account

mega 111 Privacy Policy gives you a clear view of how we handle account details, wallet records, device signals and cookies.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
mega 111 Privacy Policy for Your mega 111 Account
CONTACT ROUTES

Reach Us About Your Data

A direct support route helps you resolve a privacy question without sharing more than needed. Start from the account support contact shown near the cashier path and include the email or phone linked to your account, plus a short description of the request. We may ask for an account step or payment reference to locate the correct record, but do not send wallet passwords, one-time codes or full card details.

Team online

Privacy request

Ask us to access, correct or remove account data where local law permits. Include your registered contact detail and the specific record you want checked, so our team can match the request without asking you to repeat private details in a public channel.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction date, amount and account contact through our support route. We use that narrow set of details to trace the record and avoid requesting your wallet password or one-time code.

Access concern

When a sign-in or phone-verification step raises a privacy concern, tell us which device path you used and when the issue appeared. We can review the account event while keeping sensitive login credentials out of the support conversation.

DATA PRACTICES

See How mega 111 Handles Data

Privacy work is part of each account step, from phone verification to a return visit on mobile or desktop.

Account details

We collect the contact details you submit during account creation and phone verification. This lets us connect sign-in activity with the correct account and send account-related replies. You can ask us to correct an inaccurate contact detail through the privacy support route.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can identify a payment record, but it does not give us your wallet password. We use the reference to match cashier status, investigate a receipt question and maintain an accurate account history.

Device signals

When you move from phone login to the lobby, we may record device type, browser details and security events. These signals help us notice an unusual access pattern and protect the account. They are not used to read unrelated files stored on your device.

Cookies

Cookies can keep a session working, remember a selected setting and help us understand which policy page path brought you to an account step. You can manage cookie permissions in your browser, although turning some off may interrupt sign-in or saved preferences.

Retention

We keep account, payment and support records for as long as needed for the stated service purpose or an applicable legal duty. When that period ends, we remove or anonymise the record where permitted, rather than keeping it without an operational reason.

Your requests

You may ask what account data we hold, request a correction, ask about use or seek deletion where local law permits. We may verify ownership through the registered phone or email before acting, which prevents another person from changing your private account record.

Ask About Privacy Policy and Access

These answers address the searches we hear most often about the mega 111 Privacy Policy. They cover account creation, wallet records, cookies, device activity, correction requests and contact options. If your situation is unusual, use the privacy support route with only the details needed to identify your account.

The mega 111 Privacy Policy covers data connected with account creation, phone verification, sign-in, device activity, cookies, wallet references and support messages. It also explains retention and your request options. Service access and any privacy right depend on local law.

We use your phone number to complete the account verification step, connect you with the correct login record and respond to account requests. It can also help us identify an unusual sign-in event. We do not ask you to send one-time codes through support.

Yes. The Privacy Policy covers payment references from DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use those references to match cashier status or receipt questions, not to obtain your wallet password.

You can contact our privacy support route to ask what account data is held or to correct an inaccurate detail where local law permits. Use your registered email or phone and describe the requested change. We may verify account ownership before responding.

Cookies can maintain your session, remember a setting and connect a mobile browser with the correct account step. Browser controls let you change cookie permissions. If you disable required cookies, phone verification, login or the return from cashier to lobby may not work.

We retain account, wallet and support records for the operational purpose described in the Privacy Policy or for an applicable legal period. After that need ends, we remove or anonymise them where permitted. The exact period can vary by record type and local law.

Use the account support contact shown near the cashier path and label your message as a privacy request. Include the registered contact detail and the issue in plain English. Do not include passwords, one-time codes or complete wallet credentials in your message.

Related Pages

mega 111 Indonesia mega 111 Casino Account information About Us Live Blackjack Royal