Reference

Privacy Policy For mt777 h5

mt777 h5 Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account clarityCookie choicesWallet recordsDevice access
mt777 h5 Privacy Policy For mt777 h5
CONTACT OUR DESK

Privacy Questions Have A Clear Route

A direct support request is the quickest way to ask about your Privacy Policy rights or an account record.

Account request Use our support path to ask for a copy of account data or to…
Wallet receipt For a DANA, OVO, GoPay, or QRIS question, send the payment reference and approximate…
Access concern If a sign-in or phone verification step looks unfamiliar, contact us from the account…
DATA HANDLING DETAILS

What We Do With Your Account Data

Privacy Policy choices should be understandable when you move from a mobile login to the lobby.

Collected details

We may receive your phone or contact detail, verification result, sign-in time, browser type, device signal, support message, and payment…

Cookie controls

Cookies can retain a session and help us see whether an account page loads correctly on your phone.

Account security

Phone verification and sign-in signals help us distinguish your account from an unfamiliar device.

Payment matching

A wallet reference helps us connect a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account status with the correct…

Retention timing

We retain account, security, support, and payment records for as long as needed for the purpose collected, account protection, dispute…

Your requests

You can ask what personal data we hold, why we use it, or whether a correction or deletion is available…

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions you are most likely to have before using mt777 h5. They cover the mobile device path, local wallet references, cookies, retention, and requests for account records. Access or eligibility depends on local law, and our support route remains available when a policy question is tied to a receipt or sign-in event.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references. The Privacy Policy explains why we use each category, how we protect account access, how long records may remain, and how you can request a copy or correction.

We may store a payment reference, status, date, and account match for a DANA or QRIS request. We do not need your wallet password for a receipt check. The Privacy Policy describes this use so you can understand what is recorded and why.

Contact our support path using the account contact detail and write that you want an account data request. We may verify ownership before releasing records. Where local law permits, the Privacy Policy allows requests for access, correction, deletion, or processing limits.

Device and browser signals help us recognise a sign-in pattern and identify an unfamiliar access attempt. They can include browser type, device characteristics, and session timing. We use them for account protection and troubleshooting, not as a replacement for your phone verification.

You can block or clear cookies through your browser controls. The Privacy Policy explains that session cookies support sign-in continuity, so disabling them may sign you out or make you repeat an account step. You can still contact support about cookie-related access issues.

We keep records for the period needed for the stated account, security, support, or payment purpose, and for any lawful requirement that applies. The Privacy Policy does not promise one fixed period for every record because retention depends on its type and purpose.

The same Privacy Policy applies to supported account access in Semarang, Makassar, and other Indonesia regions, subject to local requirements. Eligibility depends on local law. If your location or account step creates a question, send support the relevant screen or request details.