Reference

Legal Terms Before You Join

Clear account rules, payment records and access checks sit in one Legal page, so you know how we handle your account before you open it.

Indonesia access termsDANA record checksOVO account matchingGoPay and QRIS logs
mdgtoto Legal Terms Before You Join
CONTACT ROUTES

Three Ways To Reach Legal Support

Fast legal help needs the right channel from the start. Use live chat for account access questions, email for document-based requests and the account message center…

Live chat account checks Open live chat from the lobby footer when you need a legal access check…
Email document requests Send document-based legal requests through the contact email shown in your account area.
Account message center Use the message center after login when you want a traceable thread for data…
DATA HANDLING

Six Controls Behind Our Legal Policy

Your legal rights are easier to act on when our records are structured. We separate login events, payment references, support chats and cookie choices so a request can be checked without exposing…

Account identity match

We compare your registered name, phone number and wallet label before changing legal account data. This helps prevent another person from altering records tied to your DANA, OVO, GoPay or QRIS activity.

Cookie choice record

Cookie settings help us remember session state, device fit and security prompts. You can clear cookies in your browser, but a fresh login may ask for added checks before account access continues.

Payment reference storage

Wallet references are kept with account records so we can trace disputed deposits or withdrawals. We use transaction IDs, time stamps and rail names rather than asking for wallet passwords or private PINs.

Security alert path

If your login pattern changes, we may pause sensitive account actions and ask for confirmation through support. The check can include device type, last successful login and the payment rail last used.

Retention by purpose

We keep legal, payment and security records only for account operation, dispute handling and compliance with applicable requests. When a record is no longer needed, we remove or separate it from active service files.

Correction request route

Ask support to correct account data when your phone number, wallet label or spelling is wrong. We will explain which proof is needed and whether a payment record must remain unchanged.

Questions About Your Legal Rights

These answers cover the legal points you are most likely to check before opening or managing an account with us. They focus on access, data, wallet records and contact steps, not general lobby use. If your case involves a specific DANA, OVO, GoPay or QRIS receipt, keep the reference ready before contacting support.

Access depends on local law and is available only where local law permits. We may limit account creation, login or payment actions when location, device signals or applicable rules require an access check.

We use your registered name, phone number, login history, support messages and wallet references. For payment-related checks, we compare DANA, OVO, GoPay or QRIS records with the account that made the request.

Contact support from your logged-in account or email the address shown in the account area. Tell us which field is wrong, provide the registered phone number and wait for our proof request before changes are made.

Support sees the details needed to solve the case, such as rail name, time stamp and transaction reference. We do not ask for your DANA, OVO, GoPay or QRIS PIN in any legal check.

We keep records for account operation, dispute handling, security checks and applicable requests. Retention can differ by record type, but payment references and access logs may remain longer than marketing preferences.

Send your username, registered phone number, wallet rail, transaction reference and the exact date or time. Screenshots can help, but never include private wallet PINs or device passcodes in your message.

Support first checks identity and account ownership, then routes the case to the team that handles data, payment or access records. We reply through the same channel so the request history stays complete.