Reference

batangtoto Privacy Policy for Your Account

batangtoto Privacy Policy explains how we handle the details connected with your account, including phone verification and DANA, OVO, GoPay or QRIS activity.

Clear data purposesWallet record contextCookie choicesAccount contact path
batangtoto batangtoto Privacy Policy for Your Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you ask about data without explaining your concern repeatedly. Use the support path connected to your account when you need a copy request, a correction, a question about cookies or clarification about a wallet reference. Include the phone number linked to your account and the relevant date, but do not send a password or full payment credentials. We can then match the request to the right account record.

Team online

Account privacy request

Send your request through the account support path and identify the phone number on file. We use that step to confirm which account record your question concerns before replying.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, include the payment date and reference shown in your cashier history. Keep sensitive wallet credentials out of the message.

Login or device concern

If a phone or browser no longer feels familiar, contact support from the account path and describe the sign-in event. We can direct the request toward access checks and account protection.

DATA HANDLING

Six Practical Privacy Controls

Our privacy process follows the actual steps you take: account creation, phone verification, sign-in, wallet activity and support contact.

Account details

We use the details you submit during account creation and phone verification to identify your account, support sign-in checks and connect requests with the correct account record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave reference data. We use those references to reconcile status without requesting your wallet password.

Cookies and browser data

Cookies can remember session settings and help us understand whether a sign-in request belongs to the same browser. You can manage cookies through your browser controls.

Account security

Phone verification, sign-in records and device signals help us notice unusual access. Never share your password, and sign out when using a shared phone or computer.

Retention approach

We keep account, support and payment references only for as long as needed for the stated service, security and record-keeping purposes, or as local law requires.

Changes and access

You can ask what personal data we hold, request a correction or raise a deletion question through support. We may first verify account ownership before making a change.

Privacy Policy Questions From Indonesia

These answers focus on the questions we expect you to ask before opening an account or checking a wallet record. They cover the Privacy Policy, account access, browser behaviour and requests sent through our support path. If your situation is not listed, contact us with the account phone number and a short description of the issue.

It explains the account, device, cookie, support and payment-reference data we may handle, why we use it, how long records may remain and how you can request access or correction.

We use the phone number submitted during account creation and verification to identify your account, support sign-in checks and connect a privacy request with the correct account record.

Yes. DANA, QRIS, OVO and GoPay can create payment-status references, while bank transfer and virtual account records help match a cashier event to your account.

You can send an access request through the account support path. Include the phone number on file and enough context to locate the request, but never include a password.

Contact support from the account route, describe the field that appears incorrect and provide the relevant account detail. We may verify ownership before updating or explaining the record.

Cookies may retain a session setting and help identify the browser during sign-in. Your browser settings can clear or restrict them, although some account functions may then need another sign-in.

Yes. Use the account support path, mention the device or sign-in time you do not recognise and avoid sharing credentials. We can direct the concern to access and security checks where local law permits.