Reference

pragmatic8 Terms & Conditions For Your Indonesia Account

Dragon Tiger, Dragon Hatch and Fish Hunter sit behind one account path, while these pragmatic8 Terms & Conditions explain how access, wallet checks and policy changes work.

Account access rulesWallet verification termsPolicy contact pathMobile and desktop use
pragmatic8.xyz page image
POLICY HELP

Where To Ask About Account Terms

A clear contact path helps when a Terms & Conditions question affects login, phone verification or wallet status. Open the support route from your account and include the email or phone detail attached to your profile, the relevant payment rail and a short description of the clause you are asking about. We use those details to route the request without asking you to repeat the same account history.

Team online

Account desk

Ask about account creation, phone verification, login access or closure by using the support route attached to your pragmatic8 account. Include your registered contact detail so we can locate the correct policy record.

Wallet status

For a DANA, OVO, GoPay or QRIS question, attach the payment reference and state whether the issue concerns a pending check, a rejected detail or a request to correct account ownership.

Policy requests

Request clarification, a copy of account data or a change to eligible details through the policy contact path. We may ask for verification before changing records linked to your account.

DATA AND ACCESS

How Dragon Tiger Account Rules Work

Our policy handling connects account security with practical steps you can check yourself. We record the details needed for access, payment matching and support, protect login activity through account controls, and retain…

Account data

We use your submitted contact and verification details to create the account, confirm ownership and respond to Terms & Conditions requests. Keep your phone and email current so policy notices reach you.

Cookie choices

Cookies and similar browser storage can keep your session and policy preferences working across pages. You can review browser controls, though changing them may interrupt login or saved account settings.

Login security

You are responsible for protecting your password, phone access and active sessions. If another person may have used your account, contact us through the account path before making a wallet request.

Payment matching

When a DANA, OVO, GoPay, QRIS or bank record needs checking, we compare the submitted reference with the account details provided. A mismatch can pause the related request until ownership is clear.

Record retention

We retain account, security and payment-support records for the period needed to operate the service, resolve disputes or meet applicable obligations. Requests about retained records can be sent through policy support.

Change requests

To correct a name, phone detail or other eligible record, submit the request from your account and explain the change. We may verify the request before replacing information tied to payment access.

Terms & Conditions Questions For pragmatic8

The answers below address the policy questions most likely to affect your account before access or payment activity. If your situation is not covered, use the policy contact route with your registered detail and the relevant transaction reference.

You can read the current Terms & Conditions on this page before opening or using an account. Check the page again after a policy notice, because wording may change when local requirements or account processes change.

Yes. Account access and eligibility depends on local law. Where local law permits, you may continue through the stated account steps, while a restriction may apply if access is not permitted in your location.

The terms require payment details to match the account information used for a request. For DANA or QRIS checks, keep the payment reference available and respond if we ask you to confirm ownership.

You can request a correction through the policy contact path in your account. We may verify the request before changing a phone, email or other detail connected with login or wallet matching.

We use account, verification and support data for access, payment matching, security and policy requests. We retain records for operational, dispute or applicable legal needs, as described in the current terms.

A mismatch can place the related request on hold while ownership is checked. Submit the payment reference through support, avoid sending duplicate requests, and use the same account details for follow-up.

Send an account closure request through the policy contact route and include your registered contact detail. We may complete identity checks first, then handle remaining account records according to the current terms.