Reference

Privacy Policy For Your jaybola1 Account

Our Privacy Policy explains how we collect, use, protect and retain information connected with your jaybola1 account.

Account dataWallet recordsCookie choicesSecurity requests
jaybola1 Privacy Policy For Your jaybola1 Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A direct privacy request helps us locate the right account record and respond with less back-and-forth. Tell us which account step, device path or payment reference concerns you, and avoid sending a password or full wallet credentials. We can then assess access, correction or deletion requests under the Privacy Policy and applicable local law. If a wallet status stalls during a DANA or QRIS transaction, include the date and reference so the privacy and account teams can separate payment evidence from identity details.

Team online

Account request

Ask us to confirm the personal data linked with your account. Include the account contact and the specific record you want checked, such as phone verification or a DANA deposit reference. We use that detail to avoid exposing information belonging to another account.

Correction path

If your name, contact detail or account record needs correction, describe the exact field and why it is inaccurate. We may request an account step to confirm your identity before changing the record, while keeping the request focused on Privacy Policy rights.

Security concern

Tell us promptly if you see an unfamiliar login or payment record connected with your account. Do not share your password in the request. We can review the account trail, protect access and explain which data was used for the security check.

DATA CONTROL POINTS

What Our Privacy Process Covers

We keep the Privacy Policy practical by connecting each data rule with an account action you can recognise.

Account details

We use the details you submit to create and maintain your account, confirm requested changes and connect your account with the correct access path. Before account access, phone verification may be required. We do not need your password in a privacy request.

Payment evidence

A DANA, OVO, GoPay or QRIS reference can be used to identify a transaction status and answer a support question. Bank transfer and virtual account records may also be retained for matching and dispute handling, subject to the Privacy Policy.

Cookies

Cookies and similar browser storage can keep a session active, remember a selected setting and help us understand whether an account page loads correctly. You can manage browser controls, although removing necessary cookies may interrupt login or the mobile lobby path.

Account security

We use account activity, device signals and verification events to identify unusual access and reduce exposure of your data. If you switch from a mobile browser to desktop, the security check may treat that as a new access context.

Retention period

We retain information for the period needed to operate the account, resolve payment or security questions, and meet applicable legal duties. When a record no longer serves one of those purposes, we assess it for removal or further restriction.

Your request

You can ask about access, correction, restriction or deletion of data connected with your account. Explain the request clearly and identify the relevant record. We may verify ownership first, then respond according to the Privacy Policy and local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to ask before using jaybola1. They explain what we collect, why a verification step may appear, how browser storage works and how to request a change. For access or eligibility, the applicable position depends on local law, so your location can affect the answer.

The Privacy Policy covers account details, phone verification, browser cookies, device and security signals, payment references and support requests. It explains how we use, protect and retain those records when you access the site through a mobile or desktop browser where local law permits.

Phone verification helps us connect an account request with the person seeking access and can reduce mistaken or unauthorised account use. We record the verification event for security and account administration, then handle it under the Privacy Policy and applicable local law.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use those references to match status, answer account questions and investigate a discrepancy without requesting your full wallet credentials.

Send a clear request identifying your account contact and the data category you want to access, such as phone verification, cookies or a payment reference. We may confirm account ownership first, then assess the request under the Privacy Policy and local law.

You can ask us to correct an inaccurate account detail by naming the field and supplying the updated value. We may require an account verification step before making the change. Our response follows the Privacy Policy, security needs and the law applicable to your location.

On a mobile browser, cookies may preserve your session, remember a setting and help identify loading faults between login and the lobby. Browser controls can remove or block them, but necessary cookies may be required for account access where local law permits.

We retain account, payment and security records only while they support operation, dispute handling, protection against misuse or a legal duty. The exact period can depend on the record and applicable law. You can ask us to explain retention for a specified data category.