Reference

hhbowin Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, complete phone verification and move between the lobby and wallet area.

Clear data purposesWallet record detailsAccount request path
Explore Our Lobby Read FAQ
hhbowin hhbowin Privacy Policy For Your Account
REQUEST HELP CLEARLY

Where To Ask About Policy Data

A direct support route helps when you want to ask what data is linked to your account or why a payment record appears. Open the support path shown in your account area and include the phone number connected with your profile. We use those details to locate the correct record without asking you to send a password.

Team online

Account data request

Ask us to confirm the account data held for your phone-verified profile. Include your account phone number and the specific record you want checked, rather than sending login credentials.

Wallet record question

For DANA, OVO, GoPay or QRIS status questions, share the transaction reference and date through the account support path. We can then match the payment record without requesting your wallet PIN.

Correction request

If your account details are inaccurate, tell us which field needs changing and why. We may ask for account verification before updating the record, helping prevent changes requested by someone else.

HANDLING YOUR RECORDS

Phone Checks, Cookies And Account Records

We keep this policy practical by connecting each data use to an account action you can recognise.

Phone verification

Before account access, we use the phone verification result to help distinguish your profile from an unauthorised sign-in. We do not need your password in a support message to investigate a basic access question.

Session cookies

Necessary cookies keep your signed-in session connected while you move from the mobile login screen to the lobby. They can also preserve basic device preferences so the account page loads consistently.

Payment matching

DANA, OVO, GoPay and QRIS activity can create a reference, amount and status record. We use those fields to match a wallet event with your account and investigate an unresolved cashier status.

Account security

We limit account support changes to requests that can be connected with your profile. Never place a password, wallet PIN or phone verification code in a support message or payment reference.

Record retention

Account, support and payment records remain available only as long as needed for service operation, dispute handling or legal obligations. After that point, we remove or anonymise them according to our process.

Policy changes

If our data practices change, we update this Privacy Policy and show the revised wording on the policy page. Check the page before opening an account or changing your account details.

Privacy Policy Questions For Indonesian Access

These Privacy Policy answers focus on the account steps and payment records you are most likely to ask about before opening an account. If your question is not covered, use the support path visible in your account area and describe the exact record or request.

It covers account details, phone verification, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We collect the phone number you provide for account creation and use its verification result to support account access. Send only the number needed to locate your profile when contacting support.

QRIS activity may produce a transaction reference, amount and status. We use those details to match the payment with your account and investigate a missing or unresolved wallet status.

Yes. Use the account support path, identify the field that is incorrect and explain the requested change. We may complete an account check before changing personal details.

We keep account, support and payment records while they are needed for account operation, dispute handling or legal duties. We then remove or anonymise them when retention is no longer needed.

You can send a deletion request through the account support path. We assess it under applicable requirements, because some records may need to remain available for legal or dispute-related reasons.

The policy is written for Indonesian account access, including mobile use in Jakarta. Availability and eligibility depend on local law, and processing may vary where local requirements call for it.

Related Pages

hhbowin Indonesia Access guide FAQ Account information About Us