Reference

Terms & Conditions For Your jaguar33 Account

jaguar33 Terms & Conditions explain how you open, use and protect your account before entering the Live Dealer Lobby, Asgardian Rising or Basketball Betting.

Account rulesWallet checksIndonesia accessPolicy changes
jaguar33 Terms & Conditions For Your jaguar33 Account
HELP WITH TERMS

Where To Ask About Account Rules

A clear support route helps when a Terms & Conditions question affects your account or wallet status.

Account access If you cannot sign in or complete phone verification, use the support route shown on the account page. We can explain which Terms & Conditions step is pending and ask for the account details needed to match your request without requesting your password or one-time code.
Wallet status For a DANA, OVO, GoPay or QRIS question, send the transaction reference visible in your cashier history. We use that reference to separate a policy question from a payment-status check and tell you whether further ownership evidence is needed.
Policy request When you need a wording explanation or want to ask for a change to your account information, contact us through the signed-in support path. Include the section you mean and your requested outcome so our team can respond to the right policy issue.
DATA AND SECURITY

How We Apply These Account Terms

We apply these Terms & Conditions alongside practical controls that protect your account records. Registration uses your submitted phone details, and security checks can compare account information with a payment record before…

Account details

We use the information you submit during account creation to identify the account holder, complete phone verification and connect your activity with the correct wallet record. If a name or phone detail is wrong, ask support for the correction path before using another account.

Payment evidence

A wallet or bank transaction may be checked against the account request when the Terms & Conditions require payment ownership confirmation. This can include DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI references. Send only the evidence support requests.

Cookies

Our cookies can retain a sign-in preference and help the account page behave consistently when you move between mobile and desktop. You can manage browser cookie settings, but removing required cookies may interrupt account access or make a verification step appear again.

Security controls

Keep your phone, password and one-time security codes private. We do not ask for a security code through an unverified message. If you suspect someone accessed your account, contact support through the signed-in route and stop further account actions until we respond.

Record retention

We retain account, transaction and support records only as long as needed for service operation, dispute handling, security checks and applicable legal duties. A retention question belongs in the support request, where we can explain which record category your request concerns.

Data changes

You can ask us to correct inaccurate personal details, clarify how a record is used or explain a decision made under these Terms & Conditions. Submit the request from the account support path with enough detail for us to locate your record safely.

Terms & Conditions Questions Answered

These Terms & Conditions questions cover the account decisions you are most likely to face before opening access or using the lobby. We answer them for Indonesian account holders with direct references to phone verification, local wallets, device behaviour and policy contact. If your situation is not listed, use the signed-in support path and quote the relevant part of this page. Access depends on local law, so a support explanation cannot replace the legal requirements that apply where you live.

They cover account creation, phone verification, permitted access, wallet ownership, account security, policy changes, data handling and support requests. They also explain how we handle account actions linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account when local law permits access.

Yes, phone verification is an account step before access is completed. Use a number you control and keep its security code private. If the code does not arrive or the account details do not match, contact support from the available account route rather than opening another account.

Those local wallet rails are available where local law permits and where the cashier displays them for your account. The wallet record should belong to you, and a transaction reference may be requested when we need to confirm payment ownership or resolve a status mismatch.

We may pause access while checking inaccurate registration details, duplicate account activity, phone verification, payment ownership or unusual transaction records. A pause is not a final outcome by itself. Use the support path shown after sign-in, provide the requested reference and wait for the account-specific explanation.

The same wording applies whether you sign in through a mobile browser or desktop browser. Cookies and device security settings can affect the sign-in path, so clearing browser data may require phone verification again. Do not share your device or one-time security code while an account check is open.

Send a data correction or policy question through the signed-in support route, identify the account detail involved and explain the change you want. We may ask for account or transaction evidence before editing a record, and we will not ask you to disclose your password or one-time code.

Access depends on local law and on the eligibility wording shown during account creation. Check the current Terms & Conditions before submitting your details. If the message is unclear, contact support through the available account route and include your location and the exact access message displayed.