Reference

Privacy Policy For Your mgdwin Account

mgdwin Privacy Policy explains how we collect, use and protect the details connected to your account, including phone verification, device access and wallet records.

Account recordsCookie choicesWallet privacy
mgdwin Privacy Policy For Your mgdwin Account
PRIVATE HELP ROUTES

Get Policy Help Near Your Account

A clear contact route matters when you want to ask what we hold, why a record appears or how to request a correction.

Account privacy request Ask us to identify the account details linked to your phone verification or sign-in record. Include your registered contact and the subject of your request so we can check ownership before discussing personal data.
Wallet record question If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference looks unfamiliar, send the receipt number through the account support path. We use that reference to locate the relevant payment record without requesting your wallet password.
Access and cookie help When a device sign-in, cookie choice or account page behaves unexpectedly, tell us which device path you used, such as mobile browser or desktop browser. That detail helps us separate access troubleshooting from a request about stored data.
DATA HANDLING

What You Can Check And Change

Privacy is easier to use when each record has a clear reason. Our handling process separates account access, payment checking and site preferences so a request can be directed to the right…

Account details

We use your registered contact and phone verification status to create and maintain account access. If a detail is wrong, request a correction through the account support contact. We may ask for a matching account step before changing information tied to sign-in.

Payment references

A wallet choice or bank reference helps us trace a deposit or receipt question. DANA, OVO, GoPay and QRIS details are handled for the relevant account and payment task. We do not need your wallet PIN or banking password to check a reference.

Cookies and devices

Cookies can retain preferences and help the browser keep an account session working. Device signals may support sign-in checks, including when you move from a mobile browser to desktop. You can clear browser cookies, although this may remove saved preferences from that device.

Account security

Phone verification helps us distinguish an account holder from an unfamiliar sign-in. Keep your password and verification code private, and contact us if an account page shows activity you do not recognise. We will use the available account checks before discussing or changing records.

Retention periods

We keep records only for the time needed for account operation, payment checking, security review or a legal requirement. Transaction references may remain longer than browser preferences because they can be needed to answer a receipt question or resolve an account dispute.

Requests and contact

You can ask about access, correction, deletion or the use of your details through the support contact shown in your account. Describe the request plainly and provide a matching account detail. We may need to confirm ownership before completing a change or disclosing records.

Privacy Policy Answers For mgdwin

These Privacy Policy answers address the account questions you are most likely to have before opening or using mgdwin in Indonesia. They cover the practical records behind phone verification, browser access, payment references and contact requests. If your situation is different, use the support contact shown inside your account and describe the exact record or action you want checked.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each type of record, how long it may remain and how you can ask about access, correction or deletion.

Phone verification helps connect an account request to the correct contact and supports account security during sign-in. We may use the verification status when you ask about personal records or request a change, but you should never send us your verification code or password.

Yes. The Privacy Policy includes payment references connected with DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account references. We use those details to match a receipt, check a payment status or answer an account question, not to request your wallet PIN.

Cookies can remember browser preferences and help maintain a sign-in session. Clearing them may remove saved choices and require another account step on that device. You can ask about cookie use through the account support contact, especially if a mobile browser behaves differently from desktop.

You can request access to, or correction of, personal details connected with your account. Use the support contact shown inside your account, name the record you want checked and provide a matching account detail. We may confirm ownership before releasing or changing it.

Retention depends on why the record exists. Payment references may be kept for account support, receipt checks, security questions or a legal requirement, while some browser preferences can disappear sooner. We remove or anonymise records when the stated purpose no longer requires them.

You may ask us to delete eligible account data through the support contact shown in your account. Some records may need to remain for payment reconciliation, security or a legal requirement. We will explain the applicable result after checking your request and account ownership.