Reference

mega5000 Privacy Policy for Your Account

The mega5000 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity in Indonesia.

Account dataWallet recordsDevice controlsPrivacy requests
mega5000 mega5000 Privacy Policy for Your Account
CONTACT OUR TEAM

Privacy Help Through Three Clear Routes

A direct support route helps you resolve a privacy question without guessing which team to contact. We can connect your request with the account record, payment reference or device session you mention, while limiting the details shared during the conversation. Use the route that matches your need, and include only the minimum account details required for us to locate the matter. If you are in Makassar or elsewhere in Indonesia, the same privacy request process applies where local law permits.

Team online

Account support

Ask through our account support channel when you need to check phone verification, sign-in records or a correction to your profile. We may ask you to confirm an account detail before discussing private records, so another person cannot request changes on your behalf.

Wallet enquiries

For a privacy question involving DANA, OVO, GoPay, QRIS or a bank transfer reference, send the relevant transaction date and masked reference. We use that information to locate the record without asking you to disclose a wallet password or full payment credential.

Support messages

Our support messaging route is suitable for access, cookie or data-use questions that do not fit a payment case. Keep your message specific, and we will explain the next identity check, the records involved and the steps available under applicable local law.

SIX DATA PRACTICES

What We Do With Your Private Details

Privacy is handled through practical account steps rather than broad promises. We separate identity details from ordinary device signals where our operational process allows, restrict internal access to people who need it…

Account collection

When you open an account, we collect the details needed for account access and phone verification. A clear account path helps us match your request to the right record, while Secure Account Access lets us review sign-in protection without exposing unrelated account activity.

Payment records

A DANA, OVO, GoPay or QRIS action can create a reference, amount and status record for reconciliation. Virtual account and bank transfer details may also appear in our payment history, but we do not need your wallet password to check whether a reference is linked to your account.

Device signals

When you move from login to a mobile lobby, we may receive browser, device and session signals that help identify repeated access or a broken page. These signals support security and troubleshooting; they are not a request for contacts, photos or unrelated files on your device.

Cookies

Cookies can keep a session active, remember a language or help us see whether account pages respond correctly. You can manage cookies through your browser settings. Removing them may require you to verify your phone again or reset preferences when returning to the account area.

Retention choices

We retain account, support and payment records only for operational, security or legal needs that apply to the record. Retention can differ between a phone verification event, a wallet receipt and a support message. Ask us which category applies and we will explain the available basis.

Changes and access

You may contact us to ask what personal details we hold, correct an inaccurate record or ask about deletion where local law permits. We verify the requester first, record the request, and explain whether a legal or security reason requires part of the record to remain.

Answers About the mega5000 Privacy Policy

These Privacy Policy answers address the searches we receive most often from Indonesian account holders. They cover the point at which data is collected, how wallet references and devices are treated, and what you can ask us to change. If your situation is not listed, contact support with a short description and avoid sending passwords or complete payment credentials.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer use. It also explains retention, access requests and correction steps where local law permits.

Our Privacy Policy does not require your DANA or GoPay password for a wallet status check. We may receive a transaction reference, status and related account details from the payment flow, while your wallet credentials remain handled through the relevant payment channel.

Phone verification links account access to the person making the request and helps us detect unusual sign-in activity. It also gives support a practical way to confirm which account you mean before discussing private records or changing profile details.

Yes. Send a correction request through account support and identify the record that appears wrong. We may ask you to confirm your phone or another account detail, then explain the correction step and any reason a record cannot be changed under applicable local law.

Cookies may remember your session setting, language choice or page state when you move from mobile login to the lobby. You can remove or restrict them in your browser. After removal, the site may ask you to verify your account again.

The period depends on the record and the operational, security or legal reason for keeping it. Phone verification, QRIS receipts and support messages may follow different retention periods. Contact us with the record type, and we will explain the applicable retention position.

You can ask about deletion through our support route. We first verify your identity, identify the records involved and check whether local law permits removal. Some account, payment or security records may need to remain for a defined operational or legal reason.