Reference

Open jajabet Privacy Policy Clearly

jajabet Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
jajabet Open jajabet Privacy Policy Clearly
CONTACT ROUTES

Ask About Privacy Through Support

A clear contact route helps when you want to understand a record or request a correction. We handle privacy questions through the support channel shown after account access, with help available every day from 09:00 to 22:00 Western Indonesia Time. Tell us whether your question concerns login activity, a wallet reference, a cookie choice or an account detail. We may ask for an account step, such as phone verification, before discussing personal records. Do not place a password, one-time code or complete bank detail in a support message.

Team online

Account questions

Use the support route beside the account area when you need to check registration data, phone verification records or a sign-in event. We first confirm enough account context to avoid disclosing personal details to the wrong person, then explain the relevant Privacy Policy section and the next step for a correction request.

Wallet references

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the date, amount range and visible status without sharing a full wallet number. We use the transaction reference to investigate the record, while keeping sensitive payment credentials out of ordinary support messages and retaining only what the account process requires.

Access help

When login or phone verification blocks a privacy request, explain the device path you used, such as Android browser or desktop browser, and the time of the attempt. Our support team can direct you through account recovery and then record your request against the correct account rather than asking you to create a second profile.

DATA PRACTICE

See How We Handle Your Records

Privacy depends on practical handling, not just a page of legal wording. We separate account identity details from ordinary support notes where our process allows, restrict account discussions to verified requests, and…

Account collection

When you open an account, we collect the details needed to create access and complete phone verification. Login events may include time, browser or device signals and an account identifier. These details help us distinguish your session from a mistaken or unauthorised attempt without requiring your password in support conversations.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a payment reference, status and reconciliation record. We use those fields to connect your request with the correct account and investigate a receipt question. We do not need a full wallet credential in a normal privacy request.

Cookie controls

Cookies can preserve a login session, remember a setting or help us diagnose a page error on mobile and desktop browsers. You can adjust cookie storage through your browser controls, although disabling some cookies may affect account access or require you to repeat a sign-in step.

Security checks

We use phone verification and account activity checks when access or a personal-data request needs confirmation. If a message arrives from a new device, we may ask for additional account context. Never send a password or one-time code; those details are not required to process a Privacy Policy request.

Retention review

We retain information while it supports account administration, payment reconciliation, security review, dispute handling or a legal obligation. When those purposes no longer apply, our process reviews whether the record should be removed, restricted or kept for a defined reason. A retention question can be sent through support with your account identifier.

Change requests

To ask for access, correction, restriction or deletion of eligible personal data, contact support from the account path and describe the record precisely. We verify ownership before responding, explain any limit that depends on local law, and may keep a request record so we can show how the matter was handled.

Find Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often from people in Indonesia. They cover account creation, wallet references, device behaviour, cookies, retention and requests for access or correction. If your situation is not listed, use the support route and describe only the minimum detail needed for us to locate the record.

The jajabet Privacy Policy covers account details, phone verification, login activity, device signals, cookies, support messages and payment references. It applies when you access the site or request account help, with availability and certain processing choices handled where local law permits.

Phone verification helps us confirm that an account request belongs to you and helps protect access after a sign-in issue. We may use the verification status when you request personal data or ask us to change account details, but you should never send a one-time code to support.

Yes. The Privacy Policy covers payment references and status records linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account reconciliation. These records help us match a transaction question to your account without asking for complete wallet credentials.

Contact support through the account path between 09:00 and 22:00 Western Indonesia Time. State whether you want access to a record or a correction, include your account identifier, and describe the relevant date or activity. We verify ownership before discussing personal information.

A mobile browser may provide session, device and technical-error signals that help us maintain access and investigate page problems. Cookies can remember a session setting, while browser controls let you change cookie storage. Turning cookies off may require another login or affect some account steps.

We keep personal information while it supports account operation, security checks, payment reconciliation, dispute handling or a legal duty. We then review whether retention remains necessary. If you ask about a specific record, support can explain the purpose and any retention limit that depends on local law.

You can send a deletion or restriction request through support, and we will verify that you control the account before assessing it. Some records may need to remain for security, transaction reconciliation or legal duties. We will explain the reason if a request cannot be completed in full.