Reference

Open mega177 Privacy Policy for Clear Data Choices

Our mega177 Privacy Policy shows how we collect, use and protect account, wallet and device details when you access the lobby from Indonesia.

Account recordsWallet detailsDevice accessRequest support
mega177 Open mega177 Privacy Policy for Clear Data Choices
REQUEST A PATH

Ask About Privacy Policy Through Your Account

A clear account route helps you ask about the Privacy Policy without sending sensitive details to an unknown address. Sign in, open the account help area and describe whether your question concerns access, wallet records, cookies or a correction request. If you are in Makassar and a login issue blocks that route, use the payment-status help path shown near the cashier so we can locate the right account record.

Team online

Account access

Use the account help area when you need a copy of personal data, an explanation of a verification record or help reaching the Privacy Policy request path after sign-in.

Payment record

If a DANA, OVO, GoPay or QRIS receipt is linked to the wrong account detail, include the receipt reference through cashier support so we can check the matching record.

Device question

Tell us whether you used a mobile browser or desktop device when requesting access, correction or deletion. This helps us separate device logs from your account details.

HOW WE HANDLE DATA

Explore Data Controls Behind Your Account

Privacy work is easier to understand when each record has a defined purpose. We separate account identity, wallet references, device events and support messages so a request can be checked against the…

Account details

We may hold your phone number, verification result and account activity needed to provide access. We use these details for account administration, security checks and replies to Privacy Policy requests.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can identify a payment record. We use those references to reconcile receipts and answer account questions.

Cookies and devices

Cookies and device signals can help keep your session active, remember security settings and detect unusual access. You can review browser controls when using a mobile browser or desktop.

Account security

Phone verification comes before account access, and security checks may compare sign-in details with previous device activity. Do not share verification codes when asking about your personal data.

Retention periods

We retain records only for the operational, dispute, security or legal purpose connected to them. When a retention need ends, the record is removed, restricted or separated from active account use.

Changes and requests

You can ask us to correct inaccurate account data, explain a wallet reference or review a cookie-related concern. Send the request through account support with enough detail to locate it.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers cover the questions we expect before account creation: what we collect, why wallet records appear, how device access is handled and how you can request a change. If your situation is not listed, open the account support route and describe the specific record.

It covers account details, phone verification, wallet references, device activity, cookies, support messages, retention and requests to access or correct personal data when you use mega177.

DANA and QRIS may appear in payment records connected with your account. We use those references to reconcile receipts, investigate status questions and respond to requests about transaction data.

The policy covers technical details such as browser type, device signals and sign-in events. These records help maintain account security and distinguish a mobile browser session from desktop access.

Sign in, open the account help area and request the relevant record. If access is blocked, use the cashier support path and provide the account reference without sharing your verification code.

Yes, you can ask us to correct inaccurate account or wallet information. Include the affected record and a safe way to identify your account so we can check the source before changing it.

We keep records for the operational, security, dispute or legal purpose connected to them. Once that purpose ends, we remove, restrict or separate the data from active account use.

Access and eligibility depends on local law. The policy explains our data handling for supported access, while your location and applicable rules may affect whether account access is available.