Reference

Open with clear privacy controls

Your account data, DANA, OVO, GoPay and QRIS wallet records, device signals from mobile browser sessions, and game-session logs for Sic Bo, Aviator and Royal Fishing are handled…

Account data controlsDANA OVO GoPay QRIS recordsCookie choicesSupport 09:00-23:00 WIB
bettoto Open with clear privacy controls
CONTACT ROUTES

Reach us about your privacy

Privacy requests need a clear route, so we keep three contact paths tied to your account rather than open social comments. Support is available every day from 09:00 to 23:00 WIB through live chat and email. For safety, we may ask you to confirm the account email, recent QRIS reference, or the device used for the last sign-in before we discuss records.

Team online

Privacy email

Send privacy questions to [email protected] with your account email and the last four characters of the payment reference. We use that match before discussing DANA, OVO, GoPay or QRIS records.

Live chat privacy queue

Use live chat from 09:00 to 23:00 WIB when you need help finding Account > Privacy. Our team can explain cookie controls, contact records and the request status without asking for your password.

Account request form

Open Profile > Support > Privacy Request to ask for correction, export or deletion checks. We reply inside your message center so your request stays linked to the account session you used.

DATA HANDLING

Manage data across account steps

Practical privacy control starts inside your account, not in a hidden document. After login, head to Profile > Privacy to manage communication choices, and Account > Security to see recent sign-in activity.

Account data collected

We collect the details you type during account setup, plus login time, device type and security events. These records help us identify your account when you ask for correction, export or deletion checks.

Payment record handling

DANA, OVO, GoPay and QRIS references are stored with amount, time and channel so wallet questions can be matched. Support can see only the fields needed to answer your privacy request.

Cookie choices

Cookie prompts appear in your browser session. On Chrome for Android, you can also open the lock icon near the address bar to manage site cookies after using Account > Privacy.

Security checks

Account > Security shows recent sign-ins and password changes. If a privacy request comes from a new device, we may ask for extra confirmation before showing account or wallet records.

Record retention

We keep records while they are needed for account access, wallet matching, security checks and legal duties. When a record is no longer needed, we remove it or make it harder to link back to you.

Change requests

You can ask us to correct account details, export eligible records or delete data where local law permits. We track each request inside your message center so you can follow the reply.

Ask common privacy questions

These answers focus on privacy rights and account data on bettoto.one. If a question touches payments, games or device access, we answer only from the data-handling angle: what we collect, why it is kept, who can see it and how you can ask for a change. For account-specific replies, use the support paths above and keep your account email ready.

We collect the details you enter, device and session records, wallet references for DANA, OVO, GoPay or QRIS, and security events. We use them to run your account, verify requests and protect access.

Yes. Open Profile > Support > Privacy Request or email [email protected] from your account email. Tell us what needs correction and attach a matching reference, such as a recent QRIS receipt code.

Payment records are stored with time, channel, amount and reference code. We keep them separate from marketing messages where possible, and we use them mainly to check wallet history and answer privacy questions.

Yes. Cookie choices apply when you use a mobile browser, including Chrome on Android. You can adjust optional cookies in the browser and manage communication choices inside Profile > Privacy after login.

Only trained support, risk and payment staff can access account records for a work reason. We use role-based access, log staff actions, and reduce shared fields when a full record is not needed.

We keep records while they are needed for account access, payment matching, security checks, dispute handling and legal duties. You can ask for deletion checks, and we remove eligible data where local law permits.

Some cookies are needed for login, wallet security and session memory. If you reject optional cookies, the lobby can still load where local law permits, but saved preferences may reset on your next visit.