Reference

Terms & Conditions for bata23

bata23 Terms & Conditions set the rules for opening an account, using our casino and sportsbook sections, and moving funds through DANA, OVO, GoPay or QRIS.

Account accessWallet checksLocal lawPolicy requests
bata23 Terms & Conditions for bata23
HELP WITH TERMS

Where Policy Questions Go

A clear support route helps when a clause affects your account or wallet status. Open the support path from your account area and include the account identifier, the relevant transaction reference and the section of the Terms & Conditions you are asking about. We can then separate a login question from a payment receipt check or an access question tied to local law. Keep screenshots limited to the details needed for the request, and never send your password or one-time verification code.

Team online

Account access

If a login step stalls, use the account support route and describe the exact screen, device path and time of the attempt. We can check whether the issue concerns verification, a policy condition or a temporary access restriction without asking for your password.

Wallet status

For DANA, OVO, GoPay or QRIS questions, attach the payment reference and receipt details through the support path. We use those details to compare the wallet record with the account condition before explaining what action is available.

Policy request

When you disagree with an account decision, identify the clause and give us the facts you want considered. Our team can explain the decision path, request a correction to inaccurate details, or tell you when access depends on local law.

ACCOUNT SAFEGUARDS

How We Apply These Rules

We apply the Terms & Conditions through ordinary account controls rather than hidden steps. Your login details should remain private, wallet records are checked against the account, and policy changes are placed…

Data handling

We use the information tied to your account to operate the conditions, confirm payment ownership, answer support requests and investigate unusual access. We do not need your password in a support message, and you should remove unrelated personal details from any attached receipt.

Cookies and sessions

Cookies can keep a session active between the login screen and lobby, including when you move from mobile access to a desktop browser. Disabling them may interrupt account steps, so check your browser settings before reporting a policy or access problem.

Login security

Your account path may include phone verification before access. Use a private device, keep your password confidential and sign out on shared hardware. If you see an unfamiliar session, contact support with the time and device path so we can review it.

Payment records

A DANA, OVO, GoPay or QRIS receipt helps us match a transaction to the correct account. Bank transfer and virtual account records may need additional checking when the sender name or reference does not match the account details.

Record retention

We retain account, transaction and support records for the period needed to administer these conditions, resolve disputes and meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Changes and requests

You can ask us to correct account details, explain a policy decision or clarify a changed clause through the support route. Include the affected account step and policy wording; we will use that context when assessing the request.

Terms & Conditions Questions

These Terms & Conditions answers address the account decisions Indonesian customers most often need clarified before using bata23. They cover acceptance, wallet ownership, data requests, device access, policy changes and local eligibility. If your situation depends on a transaction or an account restriction, use the support path with the matching reference so we can respond to the actual record rather than a general description.

You must submit accurate account details, complete the account steps shown to you and finish phone verification when requested. You also need to use the service where local law permits. We may pause access when required details are missing, inconsistent or linked to a payment check.

Our conditions require payment activity to match the account holder and the relevant transaction record. A wallet or QRIS payment that cannot be matched may be held for checking. Use your own payment rail and contact support if a receipt contains an incorrect reference.

The same conditions apply whether you use a mobile browser or desktop browser. Cookies and session settings can affect the path from login to the lobby, while phone verification remains an account requirement when shown. Sign out on shared devices and report unfamiliar access promptly.

Yes. Send a correction or access request through the account support route, naming the affected field and explaining the change needed. We may ask for details that confirm account ownership before changing records, especially when the request affects wallet matching or payment history.

Access may be restricted when account details are inaccurate, payment ownership cannot be confirmed, security activity appears unusual, or a feature is not available where local law permits. We may also act when use conflicts with these conditions. Support can explain the applicable policy path.

We place updated wording in the policy area connected with account access. The revised text applies from the stated effective point or from continued use where the notice says so. Check this page before using the lobby after a change, particularly if payment or access clauses were updated.

Open the support path from your account and provide the relevant clause, account identifier, transaction reference and a short explanation. For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account issue, include the receipt details but never include your password or verification code.