Reference

mpo4 Terms & Conditions for Your Account

Clear Terms & Conditions help you understand account access, wallet checks and the rules around titles such as Super Sic Bo and Aviator before you open an account…

Account accessWallet verificationPolicy changesSupport route
mpo4 mpo4 Terms & Conditions for Your Account
HELP WITH TERMS

Account Help for Terms Questions

A clear contact path matters when a Terms & Conditions question affects account access or a wallet status.

Account help route Use the help link inside your signed-in account for questions about a clause, verification…
Wallet status check For DANA, OVO, GoPay or QRIS concerns, send the payment reference and displayed status.
Policy clarification If a wording change is unclear, quote the section title and date shown on…
SECURITY PRACTICES

Security Rules for Aviator Accounts

Our Terms & Conditions work alongside practical account controls: phone verification before access, session checks and records of policy-related requests.

Data handling

We use account details, phone verification results and payment references to operate the agreement, check requests and respond to policy questions. We do not treat a wallet label as permission to skip account checks.

Cookie choices

Cookies may preserve your session and remember settings connected with the Terms & Conditions page. Clear them through your browser when needed, though this can require you to sign in and verify again.

Account security

Keep your phone access and sign-in details private. If an account step looks unfamiliar, pause the request and contact support through the signed-in help route before continuing.

Record retention

We retain policy, verification and transaction records for the period needed to operate the agreement, resolve disputes and meet applicable legal duties. The retained record can include a payment reference.

Correction requests

Ask us to correct an inaccurate account detail by sending the registered phone number, the affected field and a short explanation. We may request verification before changing the record.

Contact ownership

Use the account help route for data, cookie, retention or Terms & Conditions requests. Quoting the relevant section helps us send the question to the appropriate support contact.

Terms & Conditions Questions for mpo4

The questions below address the policy points most likely to matter before you open an account. Each answer focuses on Terms & Conditions, account steps, local payment records and the route for requesting clarification. If your case involves a specific transaction, keep its reference ready so support can check the wording against the account event.

They cover account creation, phone verification, access, wallet references, lobby use, policy changes, data handling, cookies, records and the process for raising a question or correction request.

Access depends on local law and the eligibility details connected with your account. Check the current Terms & Conditions before opening an account, and stop if your location or status does not permit access.

DANA and QRIS appear as payment context in an account record. A matching reference may be required, and wallet processing does not remove phone verification or any other condition stated in the terms.

Keep the displayed status and transaction reference, then use the account help route. We compare OVO or GoPay details with your account record before explaining which Terms & Conditions clause applies.

Yes. Send the registered phone number, the field needing correction and the reason through the support route. We may verify ownership first, then assess the request under our data and account terms.

We publish the current wording on this policy page and identify its effective date. Review the page before using the account after a change; activity already completed follows the version shown at that time.

Quote the decision, relevant section and account reference through the signed-in help route. We can review the recorded details and explain the next step, subject to where local law permits access.