Reference

Privacy Policy for Your Indonesia Account

Account, wallet and lobby records sit under one Privacy Policy: when you open your account, we explain how DANA, OVO, GoPay and QRIS references, device sessions, and game-category…

DANA reference careQRIS status recordsDevice session logsData request path
totosupe Privacy Policy for Your Indonesia Account
PRIVACY CONTACTS

Privacy Help Through Indonesia Channels

Privacy requests should reach people who can act on the account, not a public comment thread.

Live chat after login Choose Help > Live Chat after login for urgent privacy questions, such as an unfamiliar device or wrong wallet label. We can see the account context and answer during 10:00-02:00 WIB.
Privacy email Send [email protected] your account username, registered mobile number and the privacy request you want handled. Attach a DANA, OVO, GoPay or QRIS receipt only when it helps identify a transaction.
Session report path Open Account > Security > Active Sessions when your concern is device access. Share the session time with us, and we can close the connection while we check related privacy records.
RECORD CARE

How We Protect Account Records

Privacy controls work better when you know where each record comes from. We separate account profile data, payment references, cookie choices, security logs and support messages so a request can be handled…

Account profile data

Your profile record covers username, mobile number, email if added, password hash and account status. We use it for login, identity checks, service messages and privacy requests, not for selling contact lists.

Payment references

For DANA, OVO, GoPay and QRIS, we keep wallet labels, reference numbers, status, time and amount. We do not ask for your e-wallet PIN or store it in our systems.

Cookie choices

Cookies remember language, session state and basic device settings, so you do not repeat the same account step every time. You can clear them in your browser, then log in again.

Security logs

When you sign in, we record IP range, device type, browser and time. In Account > Security > Active Sessions, you can check devices and ask us to close a session.

Retention schedule

Payment and security records are kept for account protection, dispute handling and legal duties. When a record is no longer needed, we delete it or remove details that identify you.

Correction requests

If your mobile number, wallet label or email is wrong, contact us from the logged-in account. We may ask for a receipt reference before changing payment-related records.

Privacy Questions Before You Join

Before you create an account, you may want to know exactly what sits in our Privacy Policy. The answers below cover data collection, e-wallet records, cookies, access requests and account closure. Each answer points to a real account path or support channel, so you can act without guessing where to click. If local law affects access, we apply that rule before any account feature is made available.

We collect the details needed to run your account: username, mobile number, hashed password, session logs, wallet labels and transaction references. We also keep support messages when you contact us about privacy or account access.

No. For DANA, OVO, GoPay and QRIS we keep reference codes, status, timestamps and wallet labels. Your e-wallet app login, PIN and biometric setting stay with that provider, not with us.

Cookies keep your session active, remember language choice and help detect repeated sign-in attempts from the same device. You can clear cookies in Chrome, Safari or your device settings, then log in again.

Yes. Send the request through live chat after login or email [email protected] from the address on your account. We may verify your mobile number before sharing or changing personal data.

You can ask us to close your account and remove data that is no longer needed. Some payment, security or dispute records may be kept for legal duties before deletion is completed.

We share only what is needed with payment processors, security tools, hosting providers and support systems. If local law requires a response from us, we handle the request through the proper channel.

Go to Account > Security > Active Sessions, close the session you do not recognise, then contact live chat. We use that report with IP and device logs to protect your account record.