Reference

jajabet Terms & Conditions in Plain English

jajabet Terms & Conditions set the rules for opening an account, using the casino and sportsbook areas, and requesting account or payment assistance.

Account access rulesWallet name matchingPolicy contact pathIndonesia eligibility
jajabet jajabet Terms & Conditions in Plain English
POLICY HELP

Get Help With Account Terms

A clear support route matters when a Terms & Conditions question affects your account or wallet status. We ask you to contact us from the same account connected to the issue, describe the exact step, and include the relevant transaction reference without sending your password or full security code. This helps us separate a phone-verification question from a DANA, OVO, GoPay, QRIS or bank-transfer query. If you are in Yogyakarta, the same account path applies from mobile or desktop. We use the details you provide only to assess the request and explain the applicable policy.

Team online

Account access

If phone verification or login access is unclear, contact our support team through the account help route. Include your registered phone number in partial form and explain the screen or step that stopped you. We will use the Terms & Conditions to identify the next account action.

Wallet status

For a wallet question, tell us whether the transaction used DANA, OVO, GoPay or QRIS, then provide its reference and date. Do not send a password or one-time security code. We can compare the account record with the payment detail and explain any policy-based hold.

Policy request

For a wording, access or account-data request, quote the relevant Terms & Conditions section and send the request from your registered account path. We will confirm what can be changed, what must remain on record, and whether local law affects the available response.

ACCOUNT SAFEGUARDS

Browse How We Apply These Terms

The policy is applied through practical account controls rather than vague promises. We check account details during phone verification, compare payment references when a wallet or bank rail is used, and keep…

Data handling

We use account details to provide access, verify the registered phone path, investigate payment references and respond to Terms & Conditions questions. Send only the details needed for your request. We do not ask you to place a password, security code or complete wallet credential in a support message.

Cookies

Cookies can keep your login path and selected settings consistent between pages on the same device. Browser controls let you remove or block them. If you change those settings, you may need to repeat phone verification or confirm account details before a policy-sensitive action.

Account security

Keep your phone, password and verification messages private, and sign out on shared devices. Our Terms & Conditions allow checks when an account action, wallet reference or device pattern needs confirmation. Support will not need your full password to discuss an access problem.

Record retention

We keep account, payment-reference and support records only as needed for security checks, dispute handling and applicable legal duties. A request to remove or amend information is assessed against those duties, so some records may need to remain while other details can be corrected.

Change requests

If your phone number, account name or contact detail is wrong, contact us from the registered account path and identify the field that needs attention. We may ask for a verification step before changing it, because the account record must stay connected to the person who opened it.

Policy contact

Questions about access, cookies, retention, payment checks or wording can be sent through the support route. Quote the section and explain the outcome you are seeking. We will respond with the relevant Terms & Conditions position and state when local law limits the available option.

Check Terms & Conditions Before Opening

These answers address the policy questions we expect you to ask before opening an account. They cover account ownership, local access, payment matching, personal data, cookies and requests for changes. Read the full Terms & Conditions alongside these short answers, especially when an account action involves phone verification or a payment reference. If your situation is unusual, use the support path from the registered account so we can check the exact record.

They cover account opening, phone verification, login security, casino and sportsbook access, payment references, personal data, cookies, support requests and policy changes. They also explain when an account action may need checking and when access depends on local law or is available where local law permits.

Access depends on local law. Before opening an account, check the eligibility wording and provide accurate account details for phone verification. We may restrict an action where local law permits, and support can explain the policy position without asking you to disclose your password.

Matching details help us connect a transaction to the correct account and reduce payment disputes. This applies when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Keep the reference and date available if support needs to check the transaction.

We use personal data for account access, phone verification, payment checks, security review and responses to policy requests. We retain records for security, dispute handling and legal duties. If a detail is inaccurate, contact us through your registered account path and request a correction.

Cookies may keep login continuity and device preferences, but they do not replace the Terms & Conditions. You can manage cookies in your browser. Blocking them may require you to repeat account steps, such as phone verification, before a policy-sensitive request.

Send the request from the account connected to the record and identify the exact field, such as a phone number or contact detail. We may request verification before making a change. Some records must remain for security, dispute handling or legal duties.

Use the support route connected to your account and quote the section or issue clearly. Include a payment reference only when relevant, never a password or security code. We can explain account, wallet, cookie and access wording, including limits that depend on local law.