Reference

Terms & Conditions Before Account Access

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

Account rulesWallet checksLocal accessPolicy contact
sweetalert2 Terms & Conditions Before Account Access
CONTACT ROUTES

Terms Questions Through Clear Support Paths

A clear contact route helps you resolve a Terms & Conditions question before it affects your account. We keep policy questions close to the account and cashier paths, so you can send the relevant account detail without repeating the whole issue. Include your registered phone number, payment reference or the clause you are asking about. Where local law permits, support can explain how a rule applies without changing the written terms.

Team online

Account desk

Send a question about phone verification, duplicate account details or access conditions through the account support path. Include your registered phone number and the section of the Terms & Conditions that needs clarification.

Wallet desk

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment reference and status shown in your account. We use those details to match the policy question to the correct transaction path.

Policy desk

Ask about a wording change, data request or access clause through our policy contact route. Quote the relevant paragraph, and we can explain the current Terms & Conditions and the process for requesting a correction.

DATA PRACTICES

What Our Terms Cover In Practice

The policy is practical: it tells you what we collect for account access, how we use payment references, when a sign-in or withdrawal may need a check and how long records are…

Account details

We use the phone number and account details you submit to complete the access steps described in the Terms & Conditions. If a detail is wrong, request a correction through support before using another account path.

Payment records

A DANA, OVO, GoPay or QRIS reference helps us match your wallet event to the account record. Bank transfer and virtual account entries may also require the matching account name described in the policy.

Device sessions

Your browser session can be checked when access changes between mobile and desktop. The Terms & Conditions allow us to ask for a fresh phone verification when a device pattern does not match the account.

Cookies

Cookies can keep the policy page, account session and selected lobby path working on your device. Our terms explain their role and give you a route to ask how cookie data relates to your account.

Record retention

We retain account, support and transaction records for the period required by the applicable process. The policy explains why records may remain after a request to close access and how to ask about retained data.

Policy changes

When Terms & Conditions change, we publish the revised wording through the policy access path. Check the effective date before returning to Fishing War Mobile Play or Badminton Uber Cup Bet where local law permits.

Terms & Conditions Questions Answered

These questions address the clauses you are most likely to check before opening an account or using the lobby. Each answer stays focused on the Terms & Conditions, including account verification, payment records, device access, policy changes and your route to request help. Access remains subject to local law.

Open the Terms & Conditions page from the policy access path before completing your account steps. The current wording covers phone verification, wallet references, device sessions, withdrawals, data handling and policy changes for Indonesia where local law permits.

You need to submit accurate account details and complete phone verification before access is enabled. If your sign-in device changes, we may request another check. Eligibility depends on local law, so the written policy should be read before you use the lobby.

Yes. The policy explains how DANA, OVO, GoPay and QRIS references connect to your account record. Bank transfer and virtual account steps may require a matching account name, and a payment status can be checked through the wallet support route.

We can revise the Terms & Conditions when the operating or legal context changes. We publish the revised wording and its effective date through the policy path. Read the new version before continuing, especially where access depends on local law.

Send the policy desk your registered phone number, the account detail that needs correction and the relevant clause. We use those details to locate the record and explain the next step. Do not create a second account while the request is being checked.

The Terms & Conditions describe account, payment, support and device records, along with cookies and retention. We use the stated account processes to handle them. You can ask what record is involved, why it is retained and which request route applies.

Use the policy contact route and quote the exact clause, with your registered phone number if the issue affects account access. For a wallet matter, add the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so support can trace the question.