Reference

mg4d Privacy Policy, Made Clear

mg4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse Sic Bo or Aviator, and use DANA, OVO, GoPay…

Account dataWallet recordsDevice choicesContact requests
mg4d mg4d Privacy Policy, Made Clear
HELP WITH RECORDS

Get Policy Help Beside Your Account

A clear contact route matters when a Privacy Policy request concerns a wallet reference, an old device or an account detail you no longer recognise.

Account request Ask us to confirm which account details we hold, such as your registered phone…
Wallet reference For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate…
Policy contact Use the support link beside the cashier path for a Privacy Policy question, correction…
DATA CONTROL DETAILS

What We Keep Under mg4d Privacy Policy

We separate operational records from the details needed to answer your request. Account security, wallet matching and device checks each serve a different purpose, while retention depends on the record and the…

Account details

We may hold your name, phone or email, account identifier and verification result so we can create access, send account notices and answer ownership requests. The details you submit during account opening are connected to your account rather than treated as a public profile.

Device signals

When you sign in from a phone, tablet or desktop browser, we may record device type, browser data, session time and security signals. These records help us recognise unusual access and protect the account without needing access to your private device content.

Cookie choices

Cookies and similar storage can keep your session working, remember selected settings and help us understand which policy page was opened. You can manage browser storage through your device settings, although clearing it may require you to sign in again.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions, we retain references, status events and account matching details. We do not need your wallet password to check a receipt, and we use the record to resolve the related account request.

Retention choices

We retain personal data only for the operational, security or dispute reason connected to it, then remove or restrict it when that need ends, subject to legal duties. A retention question should identify the record type, such as sign-in, verification or payment.

Change requests

You can ask us to correct incomplete account details, explain a data use, or provide access to personal records where local law permits. Include your account contact and the requested change; we may verify ownership before making an update or sharing a copy.

Privacy Policy Questions About mg4d

These Privacy Policy answers address the account, device and payment questions you are most likely to have before opening an account. Each response points to a practical next step, while any access or eligibility decision depends on local law and applies where local law permits.

The mg4d Privacy Policy covers account details, verification, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works, and how you can request access or correction for records connected with your account.

Yes. Our Privacy Policy covers the account-side reference and status for DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records. We use these details to match a transaction with your account and investigate a receipt without requesting your wallet password.

We may use phone, tablet or browser details to keep a session working and identify unusual sign-in activity. The Privacy Policy distinguishes these security signals from private device content; we do not need access to your photos, files or unrelated applications.

You can contact us through the account support route and request access to personal data connected with your account where local law permits. Include your registered phone or email and the record you want, such as verification, sign-in or payment activity.

Send a correction request through the support link beside the cashier path, identifying the incorrect account detail and the replacement. We may confirm ownership first, then update the record when the request is valid and where local law permits.

Retention depends on why a record exists. Security events, verification details and payment references can need different periods for account operation or dispute handling. The Privacy Policy lets you ask about a specific record rather than receiving an unclear general timeframe.

Use the support path attached to your account and label the request as a Privacy Policy question. Mention whether it concerns account access, a device session, DANA or QRIS status, or a data correction so we can route the request accurately.