Reference

Terms & Conditions For Your hwg500 Account

hwg500 Terms & Conditions set out how you open, use and maintain an account for the casino, sports and wallet areas.

Account accessWallet checksPolicy contactLocal law
hwg500 Terms & Conditions For Your hwg500 Account
CONTACT ROUTES

Three Ways To Resolve Policy Questions

A clear contact path helps when a Terms & Conditions question affects your account or payment status.

Account access Use the account help path when phone verification, sign-in details or an account step does not match these Terms & Conditions. Share the time of the issue and the device you used; keep passwords and one-time codes private while we check the account record.
Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment name, amount shown in your account and the receipt reference. We can compare the displayed status with the account ledger and explain the next policy step without asking for your wallet password.
Policy change If you need to ask about a correction, deletion or access request, use the same account help route and identify the specific Terms & Conditions section. We may request account verification before changing personal details or releasing policy-related account records.
DATA PRACTICES

How We Apply These Account Rules

Our policy handling is tied to practical account events rather than broad promises. We use the details needed to open an account, confirm a phone number, check payment ownership, maintain security and…

Account details

We use your submitted contact and account details to create the profile, send account notices and match a policy request to the correct record. Keep your phone number current so a verification step or account response reaches you through the path attached to your profile.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record may be compared with your account details and receipt reference. This check helps us identify the correct transaction and may require evidence that the payment route belongs to you.

Device cookies

Cookies and related browser storage can preserve a login session, language choice or security signal. They do not replace your account credentials. You can clear or restrict them in your browser, although doing so may require another sign-in or verification step.

Account security

Do not share your password, phone verification code or payment credentials. We may pause an account action when the details, device pattern or payment ownership require checking. Follow the account help path if you see an action you did not request.

Record retention

We retain account, transaction, device and consent records for the period needed to operate the account, handle disputes, apply these Terms & Conditions and meet applicable obligations. The period can depend on the record type and the law that applies to your location.

Change requests

To request a correction, access copy or removal of eligible personal details, contact us through the account help path and name the record concerned. We may verify your identity first, then explain what can be changed and what must remain for legal or transaction reasons.

Terms & Conditions Questions Answered

The questions below cover account ownership, payment evidence, data requests and access decisions under the hwg500 Terms & Conditions. Read the relevant answer before confirming an account action, especially when a wallet status, device check or local eligibility question is involved. If your situation is different, use the account help path with the details needed to locate your record.

They apply to your account, account access, phone verification, wallet activity, lobby entry, transaction checks, data handling and requests made through the available account path. They also explain when an action may need review against local rules or additional evidence before it can continue.

Access depends on local law and the route displayed for your location. Before opening an account, check the eligibility wording shown on the account page and provide accurate details. If the route is unavailable, contact account help so we can explain the policy position without bypassing a local restriction.

Phone verification links the account to a contact detail you control and helps protect sign-in and account changes. A verification code should remain private. If the code does not arrive or the account step stalls, use account help and describe the device path without sharing the code.

For DANA, OVO, GoPay and QRIS, we may ask for the receipt reference or status shown in the wallet. Bank transfer and virtual account requests may need the bank name, such as BCA, BRI, Mandiri or BNI, plus the matching reference. Do not send wallet passwords.

Use the account help path and name the exact detail that needs correction, access or removal. We may verify your identity before acting. Our response will explain whether the request can be completed and whether a transaction, security or legal record must remain under these Terms & Conditions.

Cookies or similar browser storage may keep a session, preference or security signal available during account use. You can manage them through your device or browser controls. Clearing them may sign you out or trigger another verification step, but it does not erase the account record automatically.

A restriction can relate to verification, payment ownership, device security, account details or local eligibility. Do not create another account to work around it. Contact account help with the displayed message and your location; where local law permits, we will explain the applicable policy step.