Reference

dhx4 Terms & Conditions Before Account Access

dhx4 Terms & Conditions explain how your account, wallet activity and access to the lobby work in Indonesia.

Account stepWallet checksLocal-law accessPolicy contact
Browse Our Lobby Read FAQ
dhx4 dhx4 Terms & Conditions Before Account Access
POLICY HELP

Where Account Terms Need Clarifying

A clear support route matters when a clause affects your account or wallet status. We keep policy questions separate from game choices so you can ask about the exact condition that applies to your situation. Include your account identifier, the relevant screen and any payment reference, while keeping your password and one-time codes private. In Makassar and across Indonesia, use the support path shown beside the account or cashier area; we can direct questions about access, verification, payment status or a request to change stored details.

Team online

Account access

If phone verification or a login condition stops account access, contact us through the account support path. Tell us which step you reached and whether you are on mobile or desktop, so we can check the policy route without asking for your password.

Wallet status

For DANA, OVO, GoPay, QRIS or bank transfer questions, send the payment reference and displayed status through the cashier support path. We use those details to locate the transaction record and explain which Terms & Conditions step applies.

Policy request

When you want a clause explained or a stored account detail changed, identify the section and describe the requested action. We will confirm the available route, any verification needed and whether local-law restrictions affect the request.

ACCOUNT SAFEGUARDS

How We Apply dhx4 Policy Rules

We apply these Terms & Conditions through practical account controls rather than hidden steps. Phone verification connects an account request to the details you submit, while payment records help us match DANA…

Data handling

We use the details you submit to operate your account, check phone verification and respond to policy requests. Payment references help us match a cashier event, but you should never send a password, wallet PIN or one-time code in a support message.

Cookie controls

Cookies can keep a session connected to the device path you selected, such as mobile browser or desktop browser. If you clear them, you may need to sign in again and repeat an account step before reaching the lobby.

Login security

Your account remains your responsibility under these Terms & Conditions. Use a private device, keep credentials separate from wallet details and contact us if access looks unfamiliar. We may pause an account check while ownership is confirmed.

Payment records

For DANA, OVO, GoPay and QRIS activity, the displayed reference and status are important policy evidence. Keep your receipt until the account record is settled, and avoid repeating a payment while the first request is still being checked.

Record retention

We retain account and policy records for the period needed to operate the service, investigate account security and handle requests. If you ask what information is held or want a correction, we may verify ownership before responding.

Change requests

To request a correction, access detail or policy clarification, use the support path and name the account step involved. We will explain the evidence required, the available action and any restriction that applies where local law permits.

Answers About dhx4 Terms & Conditions

These Terms & Conditions answers cover the questions we hear before account access. They explain who controls an account, how local payment references are treated, when verification may be requested and where to ask for a correction. If your situation is not listed, send the relevant screen or receipt through the account support route, without sharing private login or wallet credentials.

They cover account creation, phone verification, login security, payment references, access to lobby areas, cookies, stored records and policy requests. The same conditions apply when you use DANA, OVO, GoPay, QRIS, virtual account or bank transfer routes shown in your account.

Yes. Account and lobby eligibility depends on local law. Where local law permits, you can complete the stated account steps and view available areas. We may restrict access when a legal or account condition is not met, and support can explain the displayed reason.

Phone verification helps connect the account request with the contact detail you provided and supports account-security checks. Complete the prompt before entering the lobby. If the code does not arrive or the step fails, use account support and describe the device path.

Payment activity should use a wallet or bank route that belongs to you or is authorised for your use under the account conditions. If a transfer needs checking, keep the receipt and reference available. We may request verification before resolving the account record.

Use the policy support path and name the detail you want corrected, such as a phone number or account record. We may verify ownership before making a change. Do not include your password, wallet PIN or one-time code in the request.

Cookies may support your session, device path and policy preferences. Clearing them can sign you out and require another login or phone-verification step. Your browser settings control many cookie choices, while necessary session functions may still be needed for account access.

Open the account or cashier support path and identify the clause, screen or payment reference involved. We can explain the relevant condition, tell you what verification is needed and direct a correction request. Keep private credentials and wallet security codes out of every message.

Related Pages

dhx4 Indonesia About Us Football Score Chase FAQ Account information