Reference

mega388 Privacy Policy For Your Account Data

Our Privacy Policy shows how we handle the account details, device signals and wallet references connected with mega388.

Account detailsWallet referencesDevice recordsPolicy requests
mega388 mega388 Privacy Policy For Your Account Data
HELP PATH

Where To Ask About Your Data

A clear support route matters when a Privacy Policy question concerns your own account. Open the help link inside your account beside the cashier path, then include the phone number on the account and the payment reference involved. We use those details to locate the right record without asking you to send a wallet password or full card details.

Team online

Account request

Ask us to confirm which account details are linked to your verified phone. We may request an account step before discussing records, so private details reach the right person.

Wallet status

For DANA, OVO, GoPay or QRIS questions, include the receipt reference and date. We can trace the stored status while keeping your wallet password and private sign-in codes out of the request.

Change request

Use the same in-account support route to ask for a correction, copy or removal of eligible details. We explain the next step and any legal reason a record must remain.

ACCOUNT SAFETY

Cookies, Devices And Account Security

We keep this Privacy Policy practical by separating service records from sensitive credentials. Your phone verification, sign-in device and wallet reference help us protect the account, while cookies preserve a usable session…

Account details

We use your verified phone number and account settings to identify your account, apply requested changes and respond to Privacy Policy questions. We do not ask for your wallet password through support.

Device signals

Browser type, device details, sign-in time and approximate location signals help us spot unusual account access. These checks can apply whether you use a phone browser or a desktop path.

Cookie choices

Session cookies keep your sign-in path working and remember selected settings. You can manage cookies through your browser controls, although restricting them may interrupt account access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references let us match a receipt with the correct account. We retain status details, not your wallet password.

Retention period

We keep account, security and transaction records only for the period needed for service, dispute handling, fraud checks or legal duties. After that period, records are removed or anonymised.

Request changes

You can ask for a copy, correction or eligible deletion through the in-account support route. We first confirm account control and explain any restriction that depends on local law.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the searches we hear most often about account records, wallet references, cookies and removal requests. If your situation is different, use the support path beside the cashier after signing in, and include only the details needed to identify your account.

It covers account details, phone verification, device signals, cookies, payment references and support requests connected with your account. It also explains retention, security steps and your available data requests.

No. We use transaction references and status details from DANA, OVO, GoPay or QRIS to match a payment. Your wallet password and private sign-in codes should never be sent to support.

Sign in, open the support link beside the cashier path and ask for an account data copy. Include your verified phone number, then complete any account check required where local law permits.

Device type, browser details, sign-in time and approximate location signals help us identify unusual access. These records support account security on both mobile browsers and desktop sessions.

We retain payment references and account security records for service needs, dispute handling, fraud checks or legal duties. Once no longer needed, records are removed or anonymised under applicable requirements.

Yes. Use the in-account support route to request a correction, copy or eligible deletion. We confirm account control first and explain any record that must remain because of local law.

Session cookies support sign-in and saved settings, while limited measurement cookies help us understand page performance. Browser controls let you restrict cookies, though some account steps may stop working.