Reference

Privacy Policy for Your hw168 Account

Our Privacy Policy explains what data we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between Sic Bo, Galactic Gems and Volleyball…

Account dataDANA checksCookie choicesSession records
hw168 Privacy Policy for Your hw168 Account
CONTACT ROUTES

Three Ways to Ask About Privacy

Privacy questions should reach the team that can check account records, not a generic inbox.

Live chat privacy queue Open live chat from the lobby footer and choose Privacy or Account Data. We use that route for quick checks on login alerts, device sessions and payment references during 10:00 to 02:00 WIB.
Email request record Send privacy requests to the address shown inside your account centre. Include your account phone number, request type and last payment method, such as DANA or QRIS, so we can match records safely.
Account message form Use Account > Help > Privacy Request when you are logged in. This path attaches your account ID to the message, which helps us confirm who is asking before any data change.
HANDLING PRACTICE

Six Privacy Controls We Use

We treat privacy as an account operation, not a separate promise hidden from the lobby.

Account data collected

We ask for the details needed to create and protect your account, such as phone number, login name, password hash and contact channel. We do not ask for your password after setup.

Payment record handling

DANA, OVO, GoPay and QRIS actions create wallet records with time, amount, reference code and account ID. Those records help us answer payment disputes without exposing full wallet credentials.

Device and session checks

When you log in, we record device type, browser, IP range and session time. You can check active access from Account > Security > Sessions and close a session you do not recognise.

Cookie use in the lobby

Cookies remember language choice, login state and basic lobby settings. They also help us spot repeated failed access attempts, but they do not give us your DANA, OVO, GoPay or QRIS PIN.

Game activity records

We record game category activity such as Sic Bo, Crash Games, Bingo and Volleyball Betting for account history, dispute checks and security monitoring. These records stay linked to your account ID.

Change and deletion requests

You can ask us to correct account data, export key records or remove data no longer needed. Some payment, fraud-prevention and legal records must stay for the period required by applicable rules.

Privacy Questions You May Ask

The answers below focus on the data we handle around your account, wallet, device and support contact. They are written for practical use: what we collect, why we keep it, how you can ask for changes and what we may need before acting on a request.

We collect the account details needed to create access, such as phone number, login name, password hash and contact route. We also log setup time, device type and IP range for account security checks.

No. We store wallet transaction records such as reference code, amount, time and account ID. Your wallet PIN stays with the payment provider, and our team will never ask you to send it.

Device and browser records help us recognise normal access and spot unusual sessions. You can view active sessions from Account > Security > Sessions and close access that does not look like yours.

Yes. Send a privacy request through live chat, email or Account > Help > Privacy Request. We may ask for account proof before changing phone number, contact route or other personal data.

We keep wallet and game activity records while they are needed for account operation, dispute checks and applicable legal duties. When a record is no longer needed, we remove it or detach it from personal details.

Our cookies support login state, language choice, basic security checks and lobby settings. We do not use them to read your wallet apps or collect DANA, OVO, GoPay or QRIS credentials.

Only support and account-security staff who need the case can access your privacy chat. We keep the message record with your account so follow-up questions can be checked without repeating sensitive details.