Reference

Privacy Policy for Your jingga888 Account

jingga888 Privacy Policy explains what we collect when you create an account, sign in on mobile, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesRequest access
jingga888 Privacy Policy for Your jingga888 Account
CONTACT PATHS

Privacy Requests Through Your Account Path

A clear contact route helps you ask about personal data without explaining your request repeatedly. We direct privacy questions to the support path shown inside your account, where you can identify the relevant phone number, wallet reference or device session. If you cannot sign in, use the account contact route available on the site and include only the details needed to locate your record.

Team online

Account message

Send a Privacy Policy question from your account area and include the email or phone detail attached to your profile. We use that step to match the request before discussing account data.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, share the payment reference and status shown in your account, not a wallet PIN. This helps us examine the correct record.

Access help

If phone verification or sign-in blocks your request, tell us which device path stopped and when. We may ask for an account detail to confirm that the request is yours.

HANDLING DETAILS

Data Handling Behind Wallet Status

We handle this policy area through practical account controls rather than broad promises. Your data is considered alongside the account step that produced it: registration, phone verification, sign-in, wallet status or a…

Account details

We may collect your chosen account identifiers, contact details and phone verification result. These fields help us connect a privacy request to the correct account without asking you to repeat unrelated personal details.

Device signals

When you sign in from a phone or desktop, we may record device and session signals used to spot unusual access. These signals support account protection and are not treated as wallet PIN data.

Cookies

Cookies can remember a session, support account navigation and help us understand whether a page request completed. Your browser controls can restrict cookies, although some account steps may then need repeating.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave reference and status data. We use those records to match a request, check a receipt and resolve a wallet question.

Retention

We retain account and transaction-related records for as long as needed for account operation, dispute handling, security checks or legal duties. Retention can differ by record type and depends on local law.

Your request

You can ask what personal data we hold, request a correction or ask about deletion through the stated privacy contact path. We may verify your account before changing or disclosing those records.

Your Privacy Questions, Answered Clearly

These Privacy Policy answers address the account and wallet questions you are most likely to have before sharing details with us. Each answer points back to a practical step, from checking a QRIS reference to requesting a change through your account contact path.

The jingga888 Privacy Policy covers account identifiers, phone verification, sign-in and device signals, cookies, wallet references, support requests, retention and your options to ask about or change personal data.

We use payment reference and status details for DANA or OVO activity, but your wallet PIN should remain with the wallet provider. Do not send a PIN when contacting us about Privacy Policy.

GoPay and QRIS records can show a reference, route, amount and status connected with your account request. We use those details to match receipts and investigate status questions, not to request your wallet credential.

Yes. Send a correction request through the account privacy path and identify the record, such as a phone detail or sign-in contact. We may verify ownership before changing the information.

Use the privacy contact route displayed in your account and ask for access to your personal data. Include the account identifier needed for matching, while leaving out wallet PINs and unrelated secrets.

Retention depends on the record and its purpose. Account, security, payment-reference and request records may remain while needed for operations, dispute handling or legal duties, subject to local law.

Use the account contact route available without a successful sign-in and explain the blocked step, such as phone verification or device access. We may request limited details to confirm your identity.