Reference

Privacy Policy for mega111 Account Data

Andar Bahar, Rocket Crash and Royal Fishing sit behind one clear account path, and our Privacy Policy explains how we handle the details that make that path work.

Account dataWallet recordsMobile cookiesPhone verification
mega111 Privacy Policy for mega111 Account Data
PRIVACY SUPPORT PATH

Where Privacy Questions Meet Support

A clear contact path matters when a phone check, wallet reference or account detail needs correction.

Account request Use the account support path to ask what personal data we hold, why a…
Wallet reference If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt number…
Access concern When login access stalls, contact us through the route named in the Privacy Policy…
MOBILE SECURITY DETAILS

Mobile Security and Data Retention

The Privacy Policy follows the account journey from phone verification to the mobile lobby, rather than treating every detail as one broad record.

Data collection

We collect details you submit during account opening, such as contact data and phone verification status, plus records created when…

Cookie controls

Cookies can retain sign-in preferences and basic session settings on your device.

Account security

We use phone verification and account checks to reduce unauthorised access.

Payment records

A DANA, QRIS, bank transfer or virtual account reference can help us reconcile a cashier request.

Retention timing

Records stay available while needed for account operation, security checks, support handling or legal duties.

Change requests

To request correction, deletion or a copy of relevant personal data, follow the contact route in the Privacy Policy and…

Privacy Policy Questions for mega111

These Privacy Policy answers address the searches we hear most often before an account is opened: what data is collected, how wallet references are handled, what cookies do and how to request a change. We keep the answers tied to the actual account path, including phone verification, mobile access and Indonesian payment references. If your situation is unusual, use the contact route named in the policy.

It covers account details, phone verification, device cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to confirm account access and help protect the account from unauthorised sign-ins. The Privacy Policy explains its purpose, related checks and retention approach.

Yes. It explains how we use a QRIS or DANA receipt reference to match an account request, check payment status and answer support questions without requesting your private wallet PIN.

You can request correction, deletion or a copy of relevant data through the contact route stated in the Privacy Policy. We may verify your account details before processing the request.

Cookies may retain session preferences and basic sign-in settings on Android or iPhone. Clearing browser data removes those stored settings, so you may need to complete the account path again.

We retain payment references only while they support account operation, reconciliation, security, support or legal duties. The Privacy Policy describes the retention process, including later removal or anonymisation.

Use the support contact path shown in your account and identify the record involved, such as a phone check or GoPay receipt. Eligibility and access depend on local law.