Reference

Open jajantogel Privacy Policy with clarity

Our Privacy Policy shows what jajantogel collects when you open an account, verify your phone, use the lobby, or select DANA, OVO, GoPay and QRIS.

Account data explainedWallet details handled carefullyMobile access choices
jajantogel Open jajantogel Privacy Policy with clarity
ASK OUR TEAM

Contact support about Privacy Policy

A clear support route matters when you want to understand a record rather than guess why it appears. Use our account support chat for questions about the Privacy Policy, phone verification, device sessions or wallet status attached to your account. Include your account phone number and a short description, but never send a password or wallet PIN. We use the account step to locate the right record without requesting unnecessary details.

Team online

Policy questions

Ask through account support chat if you need a plain explanation of a data field, a cookie notice, phone verification record or payment reference connected with your Privacy Policy request.

Correction requests

Tell us which account detail needs changing and why. We may ask you to complete phone verification before updating information, so a request is linked to the correct account.

Wallet records

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and status shown in your account. We use that reference to check the record without asking for wallet credentials.

DATA HANDLING

Explore the safeguards behind this policy

We keep the Privacy Policy practical by tying each explanation to an account action you can recognise.

Account collection

We collect details you enter during account opening and phone verification, plus records created when you sign in or request account help. We use these details for the stated account and security purposes.

Cookie choices

Essential cookies support session continuity and security checks on your phone or desktop browser. Browser controls let you clear or restrict cookies, but a later login may require fresh verification.

Device records

A mobile browser may send device type, browser version and session events. These details help us spot unusual access and explain why a phone verification step appears before account entry.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status to your account. We do not ask for your wallet PIN or banking password.

Retention choices

We keep records for account operation, security checks, disputes and legal duties for the period needed for those purposes. When no longer needed, records are removed or made less identifying.

Change requests

You can ask support to correct account details or explain stored records. Include the relevant field, use your registered contact path, and complete phone verification if ownership needs confirmation.

Browse Privacy Policy answers for your account

These Privacy Policy answers address the account steps people ask about before opening an account or returning from a mobile device. We keep the wording tied to jajantogel records, local wallet references and access where local law permits. If your case is not covered, account support chat can check the relevant record after phone verification.

It covers account details, phone verification, device and session records, cookies, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and identify the account, complete phone verification and help support connect a request to the correct record without asking for a wallet PIN.

Yes. The policy explains how we use payment status and reference details from DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity to match your account.

Contact account support chat from your registered account path, name the field that needs correction and complete phone verification if requested. Do not send passwords, wallet PINs or banking credentials.

We may record device type, browser version, language setting, session time and security events. These records help explain mobile login checks and identify unusual account access.

We retain records while needed for account operation, security, disputes and legal duties. After that, we remove them or reduce identifying details under our records process.

Access depends on local law. This Privacy Policy applies where local law permits, and support can explain how a local access or account question affects your stored records.