Reference

megawin777 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the lobby from a mobile device.

Account dataWallet recordsCookie choicesAccess requests
megawin777 megawin777 Privacy Policy for Your Account
HELP WITH RECORDS

Get Privacy Help Beside Account Support

A privacy question should not disappear into a general account queue. Start from the support link shown near your account and cashier area, then include the phone number or account identifier linked to your request. We use that detail to locate the correct record without asking you to send a wallet password. If a DANA, OVO, GoPay or QRIS reference is involved, attach only the transaction reference needed for checking.

Team online

Account route

Use the support path beside your account area for access, correction or deletion requests. Include your registered phone detail so we can match the request safely.

Wallet check

For DANA, OVO, GoPay or QRIS questions, send the transaction reference rather than a password or full wallet credentials. We use the reference to trace status.

Device access

If privacy controls look different on Android, iPhone or desktop, tell us the device and browser path. We can then explain the cookie or account setting shown.

CONTROL OVER DATA

What Our Privacy Process Covers

We keep this Privacy Policy tied to real account actions rather than broad promises. Opening an account, completing phone verification, checking a wallet reference and returning through the same device each create…

Account details

We may hold your name, phone number, login identifier and verification result so we can connect account access with the correct person and respond to account requests.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference records. These help match an account action without storing your wallet password.

Cookies and devices

Cookies and device signals help remember a session, protect sign-in and show suitable settings on Android, iPhone or desktop. You can manage browser cookies through your device.

Account protection

Phone verification and sign-in checks help us distinguish an account holder from an unfamiliar access attempt. Never send a password, wallet PIN or one-time code in a request.

Retention periods

We retain account, transaction and support records for the period needed to operate the service, resolve disputes and meet applicable legal duties, then review whether continued storage is needed.

Change requests

Ask us to access, correct or remove eligible data through the account support path. State the request clearly, and we may verify account ownership before making a change.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before account access. They explain wallet references, cookies, phone verification, device records and the route for requesting a copy or correction. If a question involves eligibility or a data right that varies by location, the answer depends on local law.

It covers account details, phone verification, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

No. We use transaction references and status details to match an account action. You should never send a DANA password, QRIS credential, wallet PIN or one-time code to support.

Phone verification helps connect account requests to the right account and helps us investigate unfamiliar sign-in activity. We record the verification result rather than asking you to disclose private codes.

Cookies can keep a session active, remember selected settings and support account protection. Your browser or device controls can remove or restrict cookies, although some account functions may then require another sign-in.

Yes, where local law permits. Use the account support path, identify the registered phone detail and state that you want an access request. We may verify ownership before releasing records.

Send a correction request through support with the specific account field or transaction reference you believe is wrong. We check the source record and update eligible details after confirming account ownership.

You can request removal where local law permits, but some account, transaction or support records may need to remain for disputes, security checks or legal duties. We explain the result of our assessment.