Reference

mega404 Privacy Policy for Your Account

Our mega404 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move from your phone login into the lobby.

Account clarityWallet dataDevice securityYour requests
mega404 mega404 Privacy Policy for Your Account
CONTACT ROUTES

Get Help With a Privacy Request

A clear contact path helps you control the data attached to your mega404 account.

Account request Ask for access, correction or removal by naming the account contact you used during…
Payment record For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date.
Login concern If a phone login or verification step looks unusual, contact support before opening another…
SECURITY PRACTICE

Six Checks Behind Our Data Handling

Our privacy process follows the actual steps you take: account creation, phone verification, wallet selection and return to the lobby on mobile or desktop.

Account collection

We request contact and verification details when you open an account, then use them to confirm that the person requesting access matches the account record.

Cookie choices

Cookies and similar session tools help keep your login active, remember basic preferences and measure page errors. Your browser settings can restrict them, though some account steps may not work.

Mobile signals

When you move from phone login to the lobby, we may record device type, browser version and session time. These signals help identify unusual access, not read files on your device.

Wallet separation

DANA, OVO, GoPay and QRIS records normally arrive as payment references and status results. We use those details to reconcile activity and do not request your wallet PIN.

Storage period

We retain account, support and transaction records only for the period needed for security, dispute handling, legal duties and account administration. After that, deletion or anonymisation may follow.

Change requests

You can ask what data we hold, request a correction or ask about deletion through support. We may need identity checks, and the result depends on local law.

Privacy Policy Answers for mega404 Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened. You can ask for more detail through support, especially when a payment reference, phone verification record or device session needs checking. Our reply may require an ownership check and depends on local law.

It covers account details, phone verification, login events, device signals, cookies, payment references and support records collected when you use mega404. It also explains your access, correction and deletion request paths.

No. Our payment flow uses transaction references and status details for DANA, OVO, GoPay and QRIS. We do not ask for or need your wallet PIN or password to match a payment.

Device type, browser details and session timing help us recognise unusual login behaviour and protect your account. We use these signals for security and troubleshooting, not to read files stored on your phone.

Contact support using the route shown on our site and identify the phone number or email linked to your account. We verify ownership, then explain which records can be provided under local law.

Yes. Send the incorrect detail and the replacement through support, using your registered account contact. We check ownership before making a change, and some transaction records must remain accurate for legal or security reasons.

We keep payment references and related account records for the period needed for reconciliation, disputes, security and legal duties. The exact period can vary by record type and depends on local law.

We may update the Privacy Policy when our data practices or legal duties change. We will place the current wording on this page, so check it again before opening an account or submitting a new request.