Reference

Legal clarity before you open an account

Our legal page sets out how your account, wallet records, access rights and contact choices work before you create a profile.

Account termsIndonesia accessDANA recordsQRIS logs
roqtoto Legal clarity before you open an account
CONTACT ROUTES

3 ways to ask legal questions

Legal questions need a clear trail, so we route them through account-based contact paths rather than public comments.

Logged-in message Use the account menu, then open Help and choose Legal request so we can attach your question to your profile, device session and wallet records without asking for the same details again.
Email document request Send legal document questions from the email linked to your account. Include your username, payment rail such as DANA or QRIS, and the transaction time shown in the wallet page.
Live chat escalation Chat is open 09:00-23:00 WIB for legal routing. Ask the agent to mark the case as account terms, data record, payment record or access eligibility so it reaches the right desk.
RECORD CARE

6 account records we handle carefully

Your legal record is more than a registration form. It includes login events, wallet references, cookie choices, security checks, support messages and changes you ask us to make.

Account identity

We keep the registration details you submit so your wallet, login history and support cases connect to one profile. If your name or contact detail changes, ask us to update it through a logged-in request.

Payment evidence

DANA, OVO, GoPay and QRIS activity is stored with time, rail name and reference code. These records help us answer wallet disputes and confirm which account initiated a transaction.

Cookie choices

Cookies help keep your session active and remember security checks on the same device. You can clear them in your browser settings, then log in again to refresh the account session.

Security sessions

We log device type, browser and access time to spot unusual account activity. On mobile, check Account, Security, Sessions and contact us if you see a device you do not recognise.

Retention requests

You may ask how long we keep account, wallet and message records. Some records must remain available while payment checks, account disputes or legal duties are still open.

Change requests

If you need a correction, send the request from your linked email or logged-in message centre. We compare it with account history before changing names, contacts or payment references.

Questions about your legal rights

Legal answers should be short enough to act on and specific enough for your account. These questions explain how we treat your eligibility, data, cookies, payment references and requests for correction. For any case tied to Blackjack, Fortune Mouse, Basketball Betting or wallet activity, include the account time and device used so we can find the right record.

Access depends on local law and is available only where local law permits. Before opening or using an account, you should check whether your location allows access and keep your account details accurate.

We keep registration details, login events, wallet references, support messages and security actions. These records help us respond to disputes, verify account ownership and track requests you send through logged-in channels.

Payment references are used to match wallet activity with your account. We may check rail name, time, amount shown in the wallet and reference code when you ask about a transaction.

Yes. Send the request from your linked email or logged-in message centre, then state what should change. We may ask for account confirmation before updating contact details or identity fields.

Cookies can connect your browser session with your login, security checks and language setting. Clearing cookies may sign you out, but it does not remove wallet records or past support messages.

Use Help from your account menu or email from your linked address. Our team is available 09:00-23:00 WIB, and chat can route the case to the legal handling queue.

You can ask what account records we hold by sending a logged-in request. We check ownership first, then explain which profile, wallet, cookie and support records can be shared.