Reference

Terms & Conditions for Your Account

Live Blackjack Table, Spaceman Crash Play and Fishing War Mobile Play sit behind one clear account path, and our Terms & Conditions explain how that access works.

Clear account stepsWallet checks explainedPolicy access in EnglishLocal-law wording
miototo88 Terms & Conditions for Your Account
POLICY HELP PATHS

Terms & Conditions Help for Wallet Questions

A clear support route helps when a clause affects your account or wallet status. Start from the account support path and include the exact policy point, your registered phone number and any relevant receipt reference. We can then separate a Terms & Conditions question from a DANA, OVO, GoPay or QRIS status check without asking you to repeat the full account story.

Team online

Account access

If you cannot complete phone verification or reach the account area, send the policy question through the account support path. We use the registered details to match the request and explain which Terms & Conditions step applies before access can continue.

Wallet status

For a DANA, OVO, GoPay or QRIS record connected to a policy question, include the payment reference and account phone number. We check the status against the account record rather than asking you to send wallet credentials or a private password.

Policy changes

When you want to question a revised clause, quote the heading or wording you mean and tell us the date you saw it. Our support path lets us identify the published version and explain whether the change affects account access, wallet checks or lobby use.

ACCOUNT RECORD PRACTICE

How Terms & Conditions Handle Your Records

We apply the Terms & Conditions through account controls rather than vague promises. Phone verification, wallet matching and login checks help us connect a request to the right account, while policy wording…

Account details

We use the account details you submit to create the account, confirm phone access and respond to policy requests. Entering a current number matters because an unmatched number can pause a verification step or make it harder to connect a DANA or QRIS record.

Cookies and sessions

Cookies and session records can keep your signed-in path working between the login page and lobby. Our Terms & Conditions explain that browser settings may affect this function, so clearing cookies can require you to complete phone verification again.

Login security

Keep your password and phone access private, and sign out on a shared device. If your login looks unfamiliar, use the account support path promptly; we may ask account questions before discussing wallet status or changing access details.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account records, we compare the payment reference with the account record. The Terms & Conditions do not ask you to disclose a wallet password, card PIN or private security code.

Record retention

We retain account and policy-request records for the period needed to administer the account, resolve a dispute or meet a local-law requirement. If you ask why a record remains, quote the account step or payment reference so we can locate it.

Correction requests

You can ask us to correct an inaccurate account detail or clarify how a policy clause applies. Send the request through account support with your registered phone number; we may verify ownership before changing a record or discussing its history.

Terms & Conditions Questions Before Access

These Terms & Conditions questions focus on the account decisions you may face before entering the lobby. We explain the practical steps for access, wallet records and policy requests, including what to prepare if a clause affects your account. Where eligibility is relevant, access depends on local law and the account prompts shown to you.

You can open the Terms & Conditions from the policy area before completing your account path. Read the sections on account details, phone verification, wallet matching, permitted use and changes. If a clause is unclear, contact account support before submitting a DANA, OVO, GoPay or QRIS request.

Yes. The terms explain that payment records must match your account details and may need a reference check. We can ask for a receipt or account step when wallet status is unclear, but you should never send a wallet password, PIN or private security code.

You need to provide accurate account details and complete the phone verification shown during access. We may pause a request when the number does not match the account record. Whether you can access the lobby depends on local law and the eligibility wording displayed for your region.

Yes. Send a correction request through account support with your registered phone number and a clear description of the inaccurate detail. We may verify that you control the account before making a change, especially when the request concerns wallet matching or phone verification.

Cookies and session records may keep your browser connected during login and lobby access. Your browser settings can remove that session, which may require another login or phone check. The policy wording explains this browser behaviour without asking you to install a separate application.

We publish revised wording through the site and identify the updated policy area. The new text applies according to its stated effective point, subject to local law. If the change affects your account, wallet status or access, use support and quote the clause you want explained.

Use the account support path and include your registered phone number, the relevant policy heading and any DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We review the request against the account record and explain the next Terms & Conditions step.