Reference

mdg186 Privacy Policy for Your Account

mdg186 Privacy Policy explains how we handle the account details and wallet records used to reach casino rooms, sports markets and local payment steps.

Account dataWallet recordsCookie choicesContact requests
mdg186 mdg186 Privacy Policy for Your Account
CLEAR CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact route matters when you need a copy, correction or explanation of your account data. We direct privacy requests through the support path beside the cashier area, so a question about a DANA receipt, phone verification or a login record can be connected to the right account. Include your account identifier and the request you want us to process; we may ask for an account step to confirm that the request comes from you.

Team online

Account privacy request

Use the support path beside the cashier to ask what account data we hold, why it is used, or which records relate to your login and phone verification.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference needs clarification, send the payment receipt or status detail through support so we can locate the relevant record.

Access correction

Ask us to correct an account detail through the same route. We may confirm your phone verification or another account step before changing or sharing private data.

DATA HANDLING DETAILS

How We Keep Policy Understandable

We explain our privacy work in practical terms because your account path includes login, wallet checks and device access.

Account security

Phone verification helps us connect an account request to the correct person. We also use login records and device signals to notice unusual access before discussing wallet or profile data.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference is retained to trace a payment status and resolve a receipt question, not to create unrelated marketing profiles.

Cookie choices

Cookies and similar browser settings can keep your session active, remember selected preferences and help us understand errors. You can adjust browser controls, although some account functions may then need another login.

Device behaviour

On mobile, we may record browser type, operating system and access time when you move from login to the lobby. These signals help protect the account without reading unrelated files on your device.

Retention process

We keep account, payment and support records only while they serve access, security, dispute handling or legal duties. When a record is no longer needed, we delete it or restrict its use.

Policy changes

If this Privacy Policy changes in a meaningful way, we will place the updated wording on this page. Check the page before opening a new account or sending a fresh privacy request.

Privacy Policy Answers for mdg186

These Privacy Policy answers address the account and payment questions you are most likely to have before using mdg186. They cover access, data copies, cookies, wallet records and requests for changes, with the same local-law wording used across our policy.

It covers data collected for account creation, phone verification, login security, wallet status, payment receipts, cookies and support requests. It also explains why we use those records, how long we retain them and how you can ask about correction or access.

We use phone verification to connect account access and privacy requests to the correct account. It also helps us investigate unusual login activity. We do not treat the verification record as permission to use unrelated personal data.

Yes. The Privacy Policy covers references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use them to match a payment event, check a receipt and respond to an account support request.

Send a request through the support path beside the cashier and state that you want a copy of your account data. Add your account identifier. We may complete phone verification or another account step before releasing private records.

You can request a correction through the same support route. Describe the field that is wrong and the replacement detail. We check the request against your account before making a change, especially when it affects wallet or payment records.

Cookies can support login sessions, remember preferences and help us identify page errors. Your browser lets you adjust cookie controls. If you block necessary cookies, you may need to log in again or lose parts of the account path.

Account access and eligibility depends on local law. We apply the Privacy Policy to data handled through an account, while the availability of access, payment steps and certain services may vary where local law permits.