Reference

mdg99 Privacy Policy For Your Account

Your mdg99 account details, wallet records and lobby activity are handled under one clear Privacy Policy.

Account dataWallet recordsCookie choicesSecurity requests
mdg99 mdg99 Privacy Policy For Your Account
CONTACT THE POLICY DESK

Get Help With A Privacy Request

A privacy question should not leave you guessing which route to use. We keep account, wallet and data requests close to the same support path used for login or cashier status issues. Tell us the email or phone attached to your account, the device path you used, and the date of the relevant event. Do not send a password, one-time code or full wallet credentials. Where local law permits, we use those details to locate the correct record and respond to your request.

Team online

Account data request

Ask us to locate the personal details connected with your account. Include the registered phone or email and say whether you want access, correction or deletion considered under the Privacy Policy.

Wallet record check

If DANA, OVO, GoPay or QRIS status appears beside the wrong account, send the transaction reference and date through our support route. We can investigate the record without needing your wallet password.

Security concern

Tell us promptly if a new phone, browser or login alert is not yours. We may ask for account details to confirm identity before discussing private records or changing an access setting.

HOW WE HANDLE RECORDS

Cookies, Security And Data Choices

We keep this Privacy Policy practical: it describes the records created by account access, wallet checks and your device path.

Account creation

When you open an account, we record the details needed to create your profile and send account messages. Phone verification helps us connect a confirmed access step with the right account.

Mobile and desktop

A login from a phone, tablet or desktop can create device and browser records. We use these signals for access checks and support investigation, not as a substitute for your account credentials.

Cookies

Cookies can keep a session active and help us see whether the account page, cashier path or lobby loads correctly. Your browser settings may let you remove or restrict them.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to an account. We do not need your wallet password to check that link.

Retention

We keep personal and transaction records only for the stated operational, support or legal need. A retention question can be sent with the account contact details used during registration.

Policy changes

If this Privacy Policy changes, we update the page and identify the affected subject in plain language. You can ask us which section changed before continuing to use your account.

Privacy Policy Answers For mdg99

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or linking a local wallet. We explain the first account step, payment references, cookies, device checks, retention and request routes in direct terms. If your situation is not covered, use the policy contact path with the phone or email attached to your account. Where local law permits, we can assess a specific request against the records involved.

It covers personal details collected during account opening, phone verification, login, wallet status checks, payment reconciliation, cookies, device signals and support requests. It also explains retention, security handling and how you can ask for access, correction or deletion where local law permits.

Phone verification connects a confirmed account step with your profile and helps reduce mistaken or unauthorised access. We use the result for account security and support checks; we do not ask you to provide a wallet password or one-time code through support.

Yes. The Privacy Policy covers payment references and status data from DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. These details help match a payment event with the correct account and resolve a receipt question.

We may record practical device and browser signals, such as the type of device, browser session and security event connected with access. A phone-to-lobby path and a desktop login can therefore produce different access records used for account protection.

You can contact our policy support route with the phone or email registered to your account and describe the record you want to access or correct. We may verify account ownership first, then assess the request where local law permits.

We retain records for the operational, support or legal purpose stated in the Privacy Policy. The period can differ between account details, security events and payment references. Ask us about a particular record using its date and account contact detail.

Send a question through the policy contact route and name the cookie setting or Privacy Policy section you mean. Your browser can also remove or restrict cookies. We will explain the relevant setting or change without asking for your account password.