Reference

jayabola Terms & Conditions for Your Account

Clear Terms & Conditions show how your jayabola account, DANA, OVO, GoPay and QRIS activity is handled before you open the lobby.

Account accessWallet recordsPolicy changesSupport route
jayabola jayabola Terms & Conditions for Your Account
HELP PATHS

Terms Questions Near Your Account Area

A clear contact path helps when a Terms & Conditions question affects your login, phone check or wallet record.

Account access If the Terms & Conditions prevent account access, contact our support desk from the account area and include your phone-verification stage, browser type and the exact message shown.
Wallet status For a policy question about DANA, OVO, GoPay or QRIS records, send the payment reference through the support path beside the cashier area so we can match the account event.
Policy changes When you need clarification on a revised clause, ask through the listed support channel and identify the section title or date displayed on the Terms & Conditions page.
DATA PRACTICE

How We Apply These Account Rules

The Terms & Conditions work alongside practical account controls rather than replacing them.

Data handling

We handle account details, phone-verification records and payment references to apply the Terms & Conditions. A DANA or QRIS reference should be sent only through the account support route.

Cookies

Cookies can support sign-in continuity and remember policy-related choices on your browser. You can manage browser cookie settings, although changing them may affect account access steps.

Account security

Keep your password and phone access private, and sign out on shared devices. Our Terms & Conditions place responsibility for account credentials with the account holder.

Retention

We retain account, verification and transaction records for the period needed to apply the Terms & Conditions, address account questions and meet obligations where local law permits.

Contact ownership

For a question about your personal records or a policy clause, contact us through the support path linked to your account. Include your account phone number without sharing your password.

Change requests

You may ask us to correct account details or explain how a change affects your access. We may request phone verification before changing records connected with DANA, OVO, GoPay or QRIS.

Terms & Conditions Questions Answered

These Terms & Conditions answers focus on the account decisions you are most likely to check before opening access. We cover eligibility, payment records, device changes, data requests and the support route, with practical examples for Indonesian account activity.

Open the Terms & Conditions page from the account or policy link before completing account access. The current wording applies where local law permits, and linked clauses should be read together with the displayed policy.

Yes. The Terms & Conditions cover account-linked activity involving DANA, OVO, GoPay and QRIS, including references used to check wallet status. Send payment questions through support rather than sharing credentials.

Yes. Account eligibility and access depends on local law. You are responsible for checking that you may use the service in your location, while we apply the account checks described in the policy.

You need to provide accurate account details and complete the phone-verification step before account access. If the check stalls, use the support route and mention whether you are on mobile or desktop.

The policy applies to your account on both mobile and desktop browsers. Device or browser changes can trigger another login check, so keep your phone available and follow the displayed account step.

Contact us through the support path connected to your account and state which detail needs correction. We may ask for phone verification before changing records covered by the Terms & Conditions.

Keep the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, then contact support from the cashier or account area. We can use that reference to identify the relevant policy event.