Reference

hw168 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an hw168 account, sign in from a mobile browser, use DANA or QRIS, and move through the lobby.

Account dataWallet recordsBrowser controlsAccess requests
hw168 hw168 Privacy Policy For Your Account
HELP WHEN NEEDED

Privacy Policy Support For Account Questions

A clear support path helps you act on this Privacy Policy instead of searching through old messages. Start with the support request route shown after account access, and include your registered phone number, the subject of your request and any relevant payment reference. For a stalled wallet status, attach the DANA, OVO, GoPay or QRIS receipt details visible to you. We use the supplied details only to locate the right account case and answer the request.

Team online

Account access request

Ask us to explain, correct or remove account details through the support route shown after sign-in. We may first confirm your registered phone number before discussing private account records.

Wallet record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and status screen. We compare those details with the matching account event.

Security concern

If a sign-in or phone verification event looks unfamiliar, report it through account support promptly. We can review the session details and apply the next account protection step.

ACCOUNT SAFETY

Inside hw168 Privacy Handling Practices

We keep this policy practical by linking each data action to an account step you can recognise. Phone verification supports account access, transaction references help us reconcile wallet status, and browser records…

Data collection

We collect account details, verification events, device signals and transaction references when those details are needed for sign-in, wallet matching, security checks or a request you send us.

Cookies and sessions

Browser storage and cookies can keep a session working, remember security settings and help diagnose access problems. You can manage browser controls, though some account steps may then require another sign-in.

Account security

Phone verification comes before account access, while session and device signals help us identify unusual sign-ins. Never share your verification code; contact support if an event is not yours.

Payment matching

A DANA, OVO, GoPay or QRIS reference is used to match the wallet event with your account. Bank transfer and virtual account records serve the same reconciliation purpose.

Retention period

We keep records only while they support account service, security, dispute handling or a legal requirement. When the relevant purpose ends, records are removed or changed so they no longer identify you.

Change requests

To request access, correction or deletion, use account support and describe the exact record involved. We may ask for phone verification before changing or disclosing private account data.

Privacy Policy Answers For hw168 Accounts

These Privacy Policy answers focus on the searches we hear most often from Indonesian account holders. They cover sign-in records, wallet references, cookies, retention and requests for changes, so you can decide what to send us and how we use it.

The hw168 Privacy Policy covers account details, phone verification, browser sessions, wallet references, security events and support requests connected with your account, including activity involving DANA, OVO, GoPay and QRIS.

We use your phone number to create and protect the account access step. Phone verification helps us confirm that a request concerns the right account before we discuss records or apply a change.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity when those records are matched to your account.

You can send an access request through the support route shown after sign-in. Describe the account record you need, and we may use phone verification to confirm your identity before responding.

Use account support and name the detail that needs correction, such as a phone number or account record. Include a clear explanation, then complete any verification step we request before the change.

We retain account, security and payment records while they support service, dispute handling, security or a legal requirement. After that purpose ends, we remove or anonymise them where applicable.

You may request deletion through account support. We assess the request against active account, security, dispute and legal needs, explain any records that must remain, and remove eligible data when permitted.