Reference

idrtoto Legal: account access starts with clear terms

idrtoto Legal explains how account access, identity checks and local-law eligibility apply before you enter rooms such as Speed Blackjack or Aviator.

Local-law accessPhone verificationPolicy request pathDANA and QRIS context
idrtoto idrtoto Legal: account access starts with clear terms
REQUEST HELP

Reach the right policy contact from your account

A clear contact route helps when a Legal question affects account access, identity checks or a wallet status.

Account access Use the account support path when phone verification blocks access or a Legal condition is unclear. We can match your request to the registered account details without asking for your password.
Wallet status For a DANA, OVO, GoPay or QRIS question linked to policy, include the transaction reference and account phone number. We use those details to separate a status query from a policy request.
Policy changes Ask through the account contact route when your personal details, consent choice or policy preference needs correction. Tell us what should change and why, so the request reaches the proper team.
DATA HANDLING

Your Legal choices stay linked to account security

We handle Legal requests through the account record rather than an open lobby message, which helps us identify the right person and reduce accidental disclosure.

Account records

We connect a policy request with your registered phone number and account details before discussing access or stored data. This reduces the chance of sending private account material to the wrong person.

Cookie choices

Cookies can keep your session active while you move from the account page to the lobby. You can raise a cookie-related Legal question through the same account contact route.

Phone verification

Phone verification happens before account access where the account flow requires it. If the code does not arrive or the number is incorrect, contact support without sharing the code itself.

Stored data

We use account and transaction records for the purposes described in our Legal notice. A request about stored data should name the record or detail you want us to check.

Retention requests

Retention depends on the relevant policy and legal requirement. You may ask us to explain how long a record is held, although some records may need to remain available.

Correction route

If your name, phone detail or account preference is inaccurate, send a correction request from the account contact path. We may verify ownership before applying a change.

What Indonesian account holders ask about Legal

These Legal answers cover the points you should settle before opening an account or asking us to change stored details. We focus on local-law access, identity checks, account records and the contact path used for policy requests.

Legal covers account opening conditions, local-law access, phone verification, data handling, cookies, account security, retention and requests to correct or change your stored details.

Access depends on local law. Check that use is permitted where you are before opening an account, and follow the account flow and phone verification step shown on your device.

Phone verification helps connect account access with the registered account holder and reduces mistaken access. Never share a verification code, password or wallet PIN through a support request.

Use the account contact path, identify the detail that needs correction and provide the registered phone number. We may verify account ownership before changing personal or account data.

Yes, Legal sets conditions around payment-related account use, but each wallet or QRIS action also follows its own status checks. Keep your transaction reference when asking about a payment record.

Retention depends on the applicable policy and legal requirement. Ask through the account contact route for the reason a record is held and whether a particular request can be applied.

Start with the support path inside your account and name the Legal clause or account action in question. Include your registered phone number, but do not include passwords, codes or wallet PINs.