Reference

Privacy Policy for DANA and QRIS Accounts

mdgwin’s Privacy Policy explains how we handle the account details, wallet records and device signals connected with your access to our Indonesia service.

Account dataWallet recordsCookie choicesDevice security
mdgwin Privacy Policy for DANA and QRIS Accounts
PRIVACY HELP DESK

Get Privacy Help Near Cashier

A clear contact route matters when a wallet record or account detail looks unfamiliar. Start from the support path beside the cashier area in your account, describe the issue, and include the…

Account support Use the support link beside your account and cashier path when you need help with a Privacy Policy question. Include your account contact and the payment reference, but do not send a password or one-time verification code. We use those details to locate the right record.
Wallet status check For a DANA, OVO, GoPay or QRIS concern, share the displayed status and transaction reference through account support. We can explain which data was used to match the payment, whether a review is pending, and what further detail may be needed.
Data request route Ask through the same support path if you want a copy, correction or deletion request considered. We may need to confirm account ownership before discussing personal data, so your records are not disclosed to the wrong person.
CONTROL YOUR RECORDS

Device, Cookie and Account Controls

We keep privacy practical by linking each data use to a visible account action. A login from a new mobile browser may create a security signal, while cookies can remember session preferences…

Data we collect

We may handle account contact details, phone verification results, login events, device signals and payment references. When you use QRIS or a bank transfer, the record helps us identify the account action without requiring us to store your wallet password or banking password.

Cookie settings

Cookies can keep your session active, remember a selected language or help us identify a broken page on a mobile browser. You can adjust cookie controls in your browser. Turning some cookies off may require another login or limit parts of the account path.

Account protection

Phone verification supports the account access step, while login and device signals help us spot unusual activity. Keep your password and verification code private. If a session looks unfamiliar, use account support beside the cashier path so we can check the event.

Record retention

We keep account and payment records for as long as needed to operate the requested service, investigate security matters or meet a legal duty. When a purpose ends, we remove, anonymise or restrict the record according to our internal handling process.

Your requests

You can ask us to explain a data use, provide a copy, correct an error or consider deletion. A request may require account ownership checks, and we may keep a limited record of the request so we can show how it was handled.

Who to contact

Our account support route handles Privacy Policy questions, including cookie choices, device signals and wallet references. Send the affected account contact and a short description through support; never include a password, PIN or one-time code in your message.

Privacy Policy Questions About mdgwin

These Privacy Policy answers focus on the account actions you are most likely to question before opening an account or checking a wallet record. We explain what is collected, why a payment reference appears, how mobile access is handled and where to send a request. If your situation is not covered, use the support path beside the cashier area and mention the relevant account step.

The mdgwin Privacy Policy covers account details, phone verification, login events, cookies, device signals and payment references. It explains how we use those records for account access, wallet matching, security and required retention, including actions connected with DANA, OVO, GoPay and QRIS.

We record a DANA or QRIS reference so we can match the payment action with your account, display its status and investigate a stalled cashier step. The reference supports reconciliation; it does not require us to collect your wallet password or banking password.

The Privacy Policy allows us to handle browser, device and login signals that help protect your account and keep a mobile session working. A new device may prompt an account check. The same rules apply when you move from a mobile browser to a computer.

Yes. Send a copy, correction or deletion request through the account support path beside the cashier area. We first confirm account ownership, then explain what we can provide or change. Some records may remain when security or legal duties require continued retention.

Cookies can remember your session settings and help us identify page or login problems. You control them through your browser settings. If you block necessary cookies, you may need to log in again or encounter limits in the account path.

Use the support route inside your account, positioned near the cashier path, and describe the Privacy Policy concern in plain English. Include the relevant payment reference or device event when useful. Do not send your password, PIN or one-time verification code.

Yes. Account access and eligibility depends on local law, and our service is available where local law permits. The Privacy Policy still explains our data handling for an account inquiry, but it does not change the legal conditions that apply in your location.