Reference

megawin777 Privacy Policy For Wallet Accounts

Our Privacy Policy explains how megawin777 handles your account details, wallet records and device activity when you use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
megawin777 megawin777 Privacy Policy For Wallet Accounts
PRIVACY CONTACTS

Privacy Help Through Your Account

A clear contact path matters when a receipt, login record or personal detail looks incorrect.

Account request form Use the privacy form after login to request access, correction or deletion of eligible account data. We may ask for an account step before releasing records to the right person.
Cashier status path When DANA, OVO, GoPay or QRIS history needs checking, attach the payment reference from your cashier record. This helps us locate the correct transaction without broad device access.
Login support route If you cannot reach your account, use the support link on the login screen and state that the request concerns privacy. We will use account details to verify the request before discussing records.
DATA CONTROL STEPS

Aviator Sessions And Account Security

Our handling process connects privacy controls to real account events rather than treating every device action alike.

Account collection

We collect the details needed for account creation, phone verification, sign-in protection and support. A request connected with Aviator or another lobby title is handled as account activity, not as a reason to read unrelated phone content.

Cookie controls

Cookies can keep your session open, retain a language or display setting and help identify repeated failed access. You can manage browser cookie choices, although removing them may require you to sign in again.

Mobile sessions

On a mobile browser, we record technical session signals such as browser type, time and access route. We do not need your photo library, contact list or microphone for ordinary account access.

Payment matching

A DANA, OVO, GoPay or QRIS receipt is matched with the account reference and payment status supplied for that transaction. This limits reconciliation to the record needed to resolve the wallet question.

Retention rules

We retain account, payment and support records only for the period needed for the stated service, security checks or legal duties. When a record is no longer needed, we remove or anonymise it under our process.

Change requests

You can request a copy, correction or eligible deletion through the privacy area in your account. We may confirm your phone or account step first, then explain any record that must remain.

Privacy Policy Questions For Indonesia

These answers cover the privacy questions we hear before account access, especially around Indonesian wallets, mobile sessions and requests for personal records. If your situation is specific, send the request through the account privacy path with the relevant reference.

It covers account details, phone verification, payment references, cookies, device session data, support records, retention and requests to access or change eligible personal data.

These rails can create payment records linked to your account. We use the selected wallet or QRIS reference, status and related transaction details to match receipts and resolve cashier questions.

No. Ordinary access does not require your contacts, photos or microphone. We may record limited technical signals from your mobile browser, including session time, browser type and access route.

Open the privacy request area after signing in, describe the record you need and include the account email or phone detail. We may confirm your account step before sending a response.

Yes. Send the incorrect field and the requested correction through the account privacy form. We check the request against your account before changing details connected with login or wallet records.

Retention depends on the purpose of each record, including payment matching, security and legal duties. When the purpose ends, we remove or anonymise the record under our internal process.

Use the privacy support route on the login screen and explain that you need a data request. Include a safe account reference, not a password, so we can begin identity checking.