Reference

mdgwin Privacy Policy for Your Account

The mdgwin Privacy Policy explains how we collect, use and protect the account details needed to open your lobby access, verify your phone and connect DANA, OVO, GoPay…

Clear data purposesWallet activity contextMobile access choicesContact path included
mdgwin mdgwin Privacy Policy for Your Account
POLICY HELP PATH

Ask About Privacy Policy Changes

A direct support path helps when your account data does not look right or a wallet reference needs checking.

Account contact Use the support route inside your account for a Privacy Policy question, correction request or access query. Include your registered phone or email so we can match the request without asking you to share a password.
Wallet status If DANA, OVO, GoPay or QRIS activity appears unfamiliar, send the transaction reference through support. We check the account record and payment status while keeping your wallet PIN and one-time code private.
Access trouble When phone verification or mobile access stalls, tell us the device path and the last step you completed. We can separate a login issue from a Privacy Policy request before changing any account data.
DATA CONTROL PRACTICE

What We Do With Your Account Data

We handle personal data around specific account actions rather than collecting it without a purpose. Phone verification supports account access, device signals help us identify an active session, and payment references help…

Account details

We use your registered phone, email and verification status to create and maintain account access. If you ask us to correct a name, contact detail or other profile field, we may request a matching account step before making the change.

Device sessions

A mobile browser session may create device and security signals linked to your access attempt. These signals help us identify unusual login behaviour and protect the account without reading unrelated files stored on your phone.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we keep the reference needed to match status and receipts. We do not need your wallet PIN or one-time code to answer a payment query.

Cookies

Cookies can preserve a session, language choice or page setting so the Privacy Policy remains reachable when you move from login to the lobby. You can manage browser cookie controls, although some account steps may then need to be repeated.

Retention choices

We retain account and transaction records only for service, security, dispute or legal needs that apply to the request. When a retention reason ends, we can delete, anonymise or restrict the record where the applicable rules allow.

Your request

Ask us to access, correct or clarify your personal data through the account support route. Tell us which record concerns you, such as a phone verification or QRIS reference, and we will explain the identity check and next step.

Privacy Policy Answers for mdgwin

These Privacy Policy answers focus on the questions you may have before opening an account or while checking an existing record. We explain the practical route for data access, correction, cookies, wallet references and account removal without turning the policy into general lobby copy. If your question involves eligibility or access in Indonesia, it depends on local law.

It covers data used for account creation, phone verification, mobile sessions, cookies, support conversations and payment references. It also explains how we handle requests connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create the account record, complete the required verification step and help distinguish your access request from another session. If you ask for a correction, we may use the verified number to confirm that the request comes from you.

Yes. The Privacy Policy covers the payment references and status information needed to match a DANA or QRIS request with your account. We do not ask for your wallet PIN or one-time code, and payment-provider handling may also apply.

Use the support route available after account access and identify the records you want to see, such as your phone verification history or a GoPay reference. We may ask for an account check before sharing data, and we explain the response path.

You can request a correction through account support and name the field that needs attention, such as your registered email or phone. We check the request against your account before changing it, so another person cannot alter your profile.

Mobile browser cookies can keep a session or page setting available while you move between account access and the Privacy Policy. You can adjust cookie controls in your browser, but disabling them may require you to repeat verification or sign-in steps.

You can send an account removal request through support, and we will explain which records can be deleted or restricted. Some transaction, security or legal records may need to remain for a stated period; access depends on local law.