Reference

Privacy Policy for Indonesia Accounts

We keep the privacy terms tied to your account: when you open one, we record the details needed to verify access, keep DANA, OVO, GoPay and QRIS records…

Account detailsDevice logsWallet recordsLocal-law limits

Browse Lobby Read FAQ

What our data policy covers

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

For Indonesian account holders, our policy covers the details you share when you create an account, the device signals we log when you open the lobby, and the payment records created by DANA, OVO, GoPay, or QRIS. We use that data to confirm access, keep wallet

1
histories aligned with the correct account, answer correction requests, and stop duplicate submissions that can confuse the record. If we need extra checks, we may ask you to confirm the name on file or show the latest transaction reference before we update anything. We keep records
2
only as long as needed for service, dispute handling, fraud checks, and legal duties, then remove or mask what we no longer need. When access or eligibility is discussed, it depends on local law and is available only where local law permits.

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

CONTACT ROUTES

How to contact our privacy team

If you want to ask how your data is stored, corrected, or removed, we answer through live chat, email, and the privacy form inside your account.

Live chat Use live chat from 09:00-21:00 WIB if you need a fast answer about a correction, a recent login, or a request to check stored data. We link the chat to your ticket so the next agent sees the same thread.

Email Send [email protected] when you want a copy, an update, or a deletion request. We reply with the exact verification step we need, such as account ID and the last payment rail used on your account.

In-account form Open the privacy form inside your dashboard when you prefer a written request. It lets you ask for contact updates, cookie questions, or retention checks without posting your account details in a public channel.

STORAGE AND ACCESS

How we protect and keep data

We keep the policy practical: only the details needed to run the account, verify a request, and protect login access are stored, while cookie settings help remember your language and session on…

Account setup data

When you open an account, we record only the fields needed to verify identity and keep your profile matched to future requests. We do not ask for extra details that do not serve the privacy policy.

Cookie session data

Cookies remember language, session state, and the last page you opened so the lobby loads faster on phone or desktop. You can clear them in your browser, but some settings will reset.

Device and login logs

We log device type, browser, IP range, and time stamps to detect unusual access and answer your ticket accurately. This helps us separate your session from someone else’s.

Wallet record handling

Wallet records from DANA, OVO, GoPay, or QRIS stay tied to the transaction ID, not public chat. We use them to confirm the source of a request and resolve mismatched entries.

Retention windows

We keep records only while we need them for service, dispute handling, fraud checks, and legal duties. After that, we remove or mask the data so it is no longer used for account operations.

Request changes

To request a copy, correction, or deletion request, send the account ID and the detail you want changed through email or the in-account form. We will reply with the next step and any verification needed.

Privacy questions we hear most

These questions cover the parts you usually need first: what we collect, how long we keep it, how cookies behave, and which channel handles a change request. Each answer stays tied to the account actions you actually take, such as opening on mobile, checking a wallet record, or asking for a copy through email. If local law narrows a request, we will say that plainly before we move ahead.

We collect the name, contact detail, login choice, and basic device signals needed to verify the account and handle your requests. If you use DANA, OVO, GoPay, or QRIS, the related transaction reference stays in the account record.

Device and login logs help us spot a new browser, a failed access attempt, or a session that does not match your usual pattern. That lets us protect the account and answer your support ticket with facts, not guesses.

No. Cookies keep session state, language choice, and the last page you opened; they do not hold your payment details. The DANA, OVO, GoPay, and QRIS records stay in the transaction file, not the browser.

We keep records while they are needed for service, dispute handling, fraud checks, and legal duties. After that period ends, we remove or mask the fields that are no longer needed for account operations.

Send your account ID through live chat, email, or the in-account form and say what you want changed. We may ask for a recent verification step before we share a copy or update the file.

Yes. You can change contact details through the account form or ask support to help you do it, and we will confirm the new detail before it is saved to the profile.

If local law limits a request, we will tell you what can be shared and what must stay on file. Access and eligibility are available only where local law permits.

Privacy Policy for Indonesia Accounts

How to contact our privacy team

How we protect and keep data

Account setup data

Cookie session data

Device and login logs

Wallet record handling

Retention windows

Request changes

Privacy questions we hear most

01 What data do you collect when I open an account?

02 Why do you keep device and login logs?

03 Do cookies store my payment details?

04 How long do you keep my data?

05 How can I ask for a copy or correction?

06 Can I update my contact details later?

07 What happens if local law limits my request?

Related Pages