Reference

mega1888 Privacy Policy

The mega1888 Privacy Policy explains how we collect, use, protect and retain data connected with your account, including details used for DANA, OVO, GoPay and QRIS status checks.

Account dataWallet recordsCookie choicesDevice security
mega1888 mega1888 Privacy Policy
CONTACT THE TEAM

Privacy Help Through Your Account Route

A clear contact path helps you ask about the Privacy Policy without sending account details through an unverified route.

Account support Use the account support route for questions about the Privacy Policy, data held against…
Wallet record help For a DANA, OVO, GoPay or QRIS reference, include the payment rail and transaction…
Access questions If your privacy request comes from a new phone or a browser you do…
HANDLING YOUR DATA

Six Practical Privacy Commitments

Privacy work is part of the account path, not a separate promise hidden from your daily use.

Data collection

We collect details needed for account access, verification, support and transaction matching. This can include your phone number, contact details, device identifiers, browser data and wallet references. We aim to request data that serves a stated account or legal purpose rather than collecting unrelated personal details.

Cookie settings

Cookies and similar browser tools help keep your session connected, remember selected settings and identify unusual sign-in behaviour. You can manage browser cookie controls on your phone or desktop, although disabling required cookies may interrupt login or prevent the site from linking your account session correctly.

Account protection

We use phone verification before account access and may ask for additional confirmation when a login pattern changes. Keep your password and one-time code private, sign out on shared devices and contact support if a session appears unfamiliar. These steps reduce the chance of another person reaching your records.

Retention periods

We retain account, support and wallet records for as long as needed for the purpose described in this Privacy Policy, account administration or a legal requirement. When a record no longer has a valid purpose, we assess it for deletion or secure removal, subject to local law.

Correction requests

You can ask us to correct inaccurate account data by contacting support through your account route. State which field is wrong and provide the corrected value; we may verify your identity before changing it. A corrected phone number can affect future login and wallet-status checks.

Deletion requests

You may ask whether your personal data can be removed, with the outcome depending on local law and records we must retain. Send the request from your account contact route, identify the account clearly and avoid attaching passwords, wallet PINs or unnecessary identity documents.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before you create an account or continue using mega1888 from Indonesia. They cover the data connected with login, wallet references, cookies, device behaviour, correction requests and contact steps. If your situation is not covered, use the support route attached to your account and describe the specific record or privacy action you need.

The mega1888 Privacy Policy covers account details, phone verification, device and browser records, cookies, support requests and wallet references linked to DANA, OVO, GoPay or QRIS. It also explains how we use, protect, retain and respond to requests concerning those records.

We use your phone number to create and protect your account, complete phone verification before access and connect support requests to the correct record. It can also help us investigate a login or wallet-status question. Keep the number current and request a correction through account support.

Yes. The Privacy Policy applies when you connect from a phone, tablet or desktop browser. We may record device type, browser settings and session activity to maintain login security. On mobile, cookie controls or a new device can change how verification is requested.

We use the payment rail and reference details needed to match a DANA or QRIS activity with your account and answer a status question. We do not need your wallet PIN or one-time code for support. Send only the requested reference through the account contact route.

You can contact us through the support path connected with your account and ask what data is held or request a correction. We may verify your identity first. The response and available action depend on local law, the record type and any retention requirement.

We keep account, support and transaction-related records for the period needed for account administration, security, dispute handling or a legal requirement. Retention can differ by record type and depends on local law. When the purpose ends, we assess the record for secure removal.

Use the support link available through your account and state that your request concerns the Privacy Policy. Include your account contact detail and the specific question, such as cookie use, device access or deletion. Do not send your password, wallet PIN or one-time code.