Reference

Privacy Built Around Your Account

Your hbtoto account connects Live Dealer Lobby, Plinko, Valorant markets, and wallet activity with one privacy flow, so you can see why we ask for each record before…

Account data explainedDANA OVO GoPay QRISCookie choicesSupport request path

Explore lobby Read FAQ

How This Policy Works in Indonesia

hbtoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Clear privacy terms help you decide whether to join us before you share a phone number, username, device ID, or wallet reference. This policy explains how we handle records connected to registration, login, identity checks, deposits through DANA, OVO, GoPay and QRIS, withdrawals, cookie settings, game

1
session logs, and support chats. We use these records to run your account, match payments, detect unusual access, answer your requests, and keep transaction history accurate. If access rules or eligibility matter, they depend on local law and are available only where local law permits. We
2
do not sell your personal records. When a service provider helps with hosting, payment routing, fraud checks, analytics, or chat support, we limit access to the task needed and keep account records separate from public marketing activity.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Three Ways To Ask Us

Fast privacy contact matters when you need to correct a phone number, ask about a wallet match, or check a device login you do not recognise.

DATA CONTROLS

Six Controls Behind Your Privacy

Practical privacy control starts at account creation and continues through each login, wallet request, and support conversation.

Registration records

When you open an account, we collect the username, phone number, password hash, and basic profile fields needed to create access. We keep the registration timestamp so support can check account ownership during privacy requests.

Payment matching

DANA, OVO, GoPay, and QRIS records are used to match your wallet action with the account balance line. We store transaction references, time, status, and amount shown in the cashier, not your wallet PIN.

Device signals

We may record browser type, IP range, device model, and login time to spot unusual access. On Android Chrome, you can clear site data through Settings, Site settings, then All sites before signing in again.

Cookie handling

Cookies keep your session active, remember language choice, and measure page errors that affect login or cashier steps. If you block all cookies, the lobby may ask you to sign in again after moving pages.

Retention checks

We keep account, payment, and support records only for operational, security, and legal needs. When a record is no longer needed, we remove it from active systems or separate it from details that identify you.

Correction requests

If your phone number, email, or wallet label is wrong, contact us before making another payment request. We may ask for a recent QRIS reference or account login check before changing the stored detail.

Privacy Questions You May Ask

Privacy questions usually come up before registration, after a wallet action, or when a device behaves differently. We answer the common points below in plain terms so you know what we collect, why it is used, and how to contact us. For account-specific requests, use the same phone or email linked to your account so we can confirm ownership before changing records.

We collect the details needed to create and secure your account, such as username, registered phone, password hash, signup time, and device signals. We also keep wallet references when you use DANA, OVO, GoPay, or QRIS.

Payment references help us match your account balance with DANA, OVO, GoPay, or QRIS activity. They also help support trace a delayed cashier step, confirm ownership, and check unusual wallet requests tied to your profile.

Yes. Contact live chat or email support from the channel linked to your account, then share the field that needs correction. We may ask for username, registered phone, and a recent transaction reference before making changes.

Cookies remember your session, language choice, and page stability signals while you browse from mobile. On Android Chrome, open Settings, Site settings, then All sites to clear stored site data before you sign in again.

Only the team handling your request can access chat records needed for account help, privacy checks, or payment tracing. We do not ask for your password, wallet PIN, or one-time codes in support conversations.

We keep records for operational, security, and legal needs, including account access history, payment references, and support logs. When records are no longer needed, we remove them from active systems or separate them from your identity.

Access and eligibility depend on local law and are available only where local law permits. Privacy requests still follow the same contact path: confirm your account, explain the record involved, and wait for support handling.

Privacy Built Around Your Account

Three Ways To Ask Us

Six Controls Behind Your Privacy

Registration records

Payment matching

Device signals

Cookie handling

Retention checks

Correction requests

Privacy Questions You May Ask

01 What personal data does hbtoto collect when I open an account?

02 Why do you keep my payment references?

03 Can I ask for my account data to be corrected?

04 Do cookies affect my privacy on mobile?

05 Who can see my support chat details?

06 How long do you keep account and wallet records?

07 Is access to my account always available in Indonesia?

Related Pages