Reference

Legal terms for your account

This page sets out how we handle access, account changes, data requests, and cookie choices when local law allows it.

Indonesia accessDANA, OVO, GoPay, QRISLocal law first
laqastoto Legal terms for your account
REQUEST CHANNELS

Where to send policy requests

Policy requests move fastest when you send them from the contact route tied to your account.

WhatsApp Send from the number on file so we can match the request to your…
Email Write from the email on record if you need a copy of stored data…
In-site Chat Use chat when you want a quicker answer about cookies, record retention, or a…
DATA HANDLING

How we handle data and access

Our legal handling follows the same path across desktop and mobile. We keep account edits, cookie choices, and login records linked to the request that created them, so we can confirm who…

Data Scope

We store only the fields needed to run access checks, answer policy requests, and match account actions to your session. That usually means your contact route, device type, and the payment rail you chose for the latest deposit.

Cookie Controls

Non-essential cookies can be turned off in Chrome on Android, Safari on iPhone, and desktop browsers through the browser menu. Essential cookies stay active for login, security checks, and the route that sends your request to us.

Account Security

If a login comes from a new device, we may ask you to confirm the email, phone, or last rail used before we change account details. That keeps the request tied to the real account holder.

Retention Windows

We keep request logs for a limited period so we can settle disputes, correct errors, and meet local record duties. After that period, we remove or mask fields that no longer need to stay linked to you.

Change Requests

To update a contact route or fix a field, send the request from the account email and name the exact change you want. We answer with the next step in the same thread and wait for your confirmation.

Escalation Path

If you disagree with our first answer, ask support to escalate it. We check the account history, payment trail, and prior messages, then send a written reply that explains the result and any further step.

Questions about access and records

These questions cover access, record handling, cookies, and who should send a request. If your case needs a second check, use the channel tied to your account and include your username, the device you used, and the last payment rail on file. We answer in the same thread during 08:00-24:00 WIB, and we keep the next step tied to the same case until it closes.

Access depends on local law and where your account is being used. If a rule changes, we may limit entry, ask for a location check, or pause new account steps until the current rule is clear.

Send a request from the email tied to your account and ask for a data copy. We may confirm your phone number, last login device, or payment rail before we release the record in the same thread.

Yes, when the request matches the account record and the new contact can be verified. We usually ask for the current contact, the new contact, and a short confirmation from the registered channel before we update it.

You can block non-essential cookies in your browser menu. Essential cookies stay active for login, security, and request routing, while analytics cookies can be turned off without stopping the account page from loading.

We keep request and security logs only for the period needed to handle disputes, corrections, and local duties. After that, we delete or mask parts of the record that no longer need to stay linked to you.

Use WhatsApp, email, or in-site chat and include your username, the device you used, and the last payment rail on the account. We check the lock and reply with the next step in the same thread.