Reference

Privacy Policy for Your destoto Account

Your account data, wallet receipts from DANA, OVO, GoPay and QRIS, and device signals are handled under this Privacy Policy before you jump into Dragon Tiger, Aviator or…

Account data useDANA and QRIS recordsCookie controlsDeletion request path
destoto Privacy Policy for Your destoto Account
CONTACT PATHS

Privacy Requests Through Our Team

Fast answers matter when your data is involved. Our privacy contact paths are built for account questions, not generic inbox traffic, so you can ask about profile edits, device sessions, payment records, cookies or deletion requests from one place. Support runs daily from 09:00 to 23:00 WIB by live chat and Help Center message, with email follow-up when a written record is needed.

Team online

Live chat privacy queue

Use live chat from 09:00 to 23:00 WIB when you need a quick check on saved profile details, login alerts, or whether a DANA or QRIS receipt is linked to your account.

Help Center message

Send a Help Center message when your request needs attachments, such as a masked OVO receipt, GoPay reference, or screenshot from Account > Security > Active devices.

Account security check

If you see a device you do not recognise, open Account > Security > Active devices, remove the session, change your password, then contact us for a privacy check.

CONTROL CHECKS

Controls Around Cookies and Wallet Records

Practical privacy controls should be easy to find while you are on mobile in Jakarta or checking the lobby from a computer browser.

Account creation data

When you open an account, we store the details you enter, including contact fields and login credentials in protected form, so we can recognise you on return sessions.

Payment record purpose

DANA, OVO, GoPay and QRIS references are kept to reconcile deposits, check withdrawals, answer wallet questions, and detect duplicate or mismatched payment activity on your account.

Cookie handling

Cookies help keep you signed in, remember language choices, and measure page errors. You can clear them through your browser, though some account checks may run again.

Device session view

Go to Account > Security > Active devices to see recent sessions. This path helps you remove old phones, shared browsers, or unknown logins before contacting us.

Retention checks

We keep account and transaction records only for operational needs, dispute handling, security checks, and legal duties that apply to the service in your location.

Change and deletion requests

Ask us to update, export or delete eligible data through live chat or the Help Center. We verify account control before making any privacy change.

Privacy Policy Questions You May Ask

Your privacy questions should have direct answers before you create or manage an account. These answers explain what we collect, how payment records are handled, how cookies work, and how you can contact us for changes. They also set expectations for requests tied to access, account proof, and local legal requirements in Indonesia.

We collect the details needed to create and protect your account, such as contact fields, login records, device signals, cookie choices, and payment references when you use DANA, OVO, GoPay or QRIS.

We keep payment references to match deposits, check withdrawal requests, answer wallet questions, and investigate mismatched activity. The record usually includes a transaction code, time, amount, and account-related match result.

Yes. Contact live chat or send a Help Center message with the account field you want changed. We may ask you to confirm account control before we update saved profile data.

Open Account > Security > Active devices, choose the session you do not use, and remove it. If the device looks unfamiliar, change your password and ask us for a privacy check.

Cookies may help remember session status and page behaviour, but account logs handle activity records. You can clear cookies in your browser, though sign-in and security checks may repeat.

You can request deletion through live chat or the Help Center. We verify account control first, then remove eligible data while keeping records required for security, disputes or legal duties.

Only team roles that need to resolve the request can view related records. For example, payment staff may see a QRIS reference, while account security staff checks device sessions.