Reference

Privacy Policy for your jingga account

jingga Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and lobby access.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
jingga Privacy Policy for your jingga account
CONTACT PATHS

Get policy help beside account support

A clear contact path matters when you want to ask what we hold about your account or why a wallet record appears.

Account access If you cannot pass phone verification, use the account support route and describe the device path you followed. We may ask for account identifiers needed to confirm ownership before discussing personal data or changing access details.
Wallet status For a DANA, OVO, GoPay or QRIS privacy question, send the transaction reference and date through support. Do not send a wallet PIN or password; we only need enough detail to locate the related account record.
Data request To ask for a copy, correction or removal of personal data, write from the contact route linked to your jingga account. We may verify your identity first, then explain which records can be changed or retained.
DATA HANDLING

What we do with account data

We handle account data for practical reasons: opening access, matching wallet activity, protecting the account and answering your requests.

Account creation

When you open an account, we collect the details needed to create your profile and begin phone verification. We use those details to connect your login with account settings, access checks and requests made from the same account.

Wallet matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record may include a reference, status and account link. We use these fields to identify the relevant action without asking for your wallet PIN.

Cookie controls

Cookies can remember a session, language setting or consent choice on your browser. You can manage or clear them in your browser settings, although removing necessary cookies may require another login or affect account access.

Device signals

We may record practical device signals such as browser type, operating system and connection details. These signals help us spot unusual account access and investigate a login question without reading private content on your device.

Retention requests

We keep personal data only for the operational, security or legal purpose connected with it. If you ask us to remove data, we check the account and explain whether a record can be deleted, anonymised or kept for a stated reason.

Policy contact

Questions about this Privacy Policy should include your account email or phone detail and a clear request, such as access, correction or deletion. We may ask for ownership checks before sharing personal data or changing the record.

Privacy Policy answers for jingga

These Privacy Policy answers cover the searches we expect before you open an account: what data we collect, how wallet records are used, what cookies do and how to request a change. We keep the answers tied to real account steps, including phone verification and mobile access to the lobby. If your situation is not covered, use the support path and tell us which part of the policy you are asking about.

The jingga Privacy Policy covers account details, phone verification, wallet references, device signals, cookies, support messages and records linked to access. It explains why we use each category, how we respond to requests and when local rules affect what we can provide.

We collect the account details you submit, the phone detail used for verification and technical data from the browser or device used to access the account. We collect only what is needed for account access, security, support and the purposes set out in this Privacy Policy.

Yes. The policy covers records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These can include a reference, status, date and account connection. We do not need your wallet PIN to investigate a payment record or answer a data request.

Cookies can keep a session active, remember a setting or record your consent choice. We may also use device signals to identify unusual access. You can clear or manage cookies in your mobile browser, but necessary account steps may then ask you to log in again.

Yes. Send a clear request through the account support route, using the phone or email connected with your profile. We may verify ownership before sharing data, correcting a detail or explaining why a specific record must remain available.

Write to support with your account identifier and state which data you want removed. We review the request against account security and applicable legal or operational needs, then explain whether the data can be deleted, anonymised or retained.

Yes. Access depends on local law, and some requests may have limits where local law permits only certain records to be shared or removed. We will explain the relevant outcome through the support route instead of asking you to bypass an access rule.

Related Pages

jingga Indonesia Football Score Chase About Us Access guide Account information