Reference

jingga4d Privacy Policy for Your Account Data

Clear account, wallet and device handling starts with our Privacy Policy. At jingga4d, we explain what we collect when you open an account, sign in from a mobile…

Account clarityWallet contextCookie choicesLocal-law access
jingga4d jingga4d Privacy Policy for Your Account Data
CONTACT THE POLICY DESK

Check Privacy Questions Through Account Support

A clear contact path matters when you want to ask about a record, cookie or account detail.

Account data request Ask us to locate the account details linked to your registered phone or email. We may request an account step before discussing private records, so another person cannot receive your information.
Wallet receipt check For a DANA, OVO, GoPay or QRIS receipt question, send the reference shown in your cashier record. We use that reference to check payment status without requesting your wallet password.
Cookie assistance If a mobile browser keeps a stale session or blocks a policy preference, tell us your device path and browser setting. We can explain which local cookie action may resolve the issue.
HOW WE HANDLE DATA

Browse jingga4d Privacy Controls With Confidence

We keep our privacy work practical: collect what an account step needs, protect records against unauthorised access, and keep data only for a clear operational or legal reason.

Account records

We handle registration details, sign-in activity and verification results to maintain account access. A clear account path helps us separate your request from another person using the same device.

Payment references

DANA, OVO, GoPay and QRIS details are treated as payment references and status data. We do not need your wallet password to match a receipt or investigate a cashier record.

Device signals

Browser type, device identifiers and session events can help us detect unusual sign-ins. These signals support account protection and are not treated as a substitute for your identity details.

Cookie settings

Cookies can remember a session, preserve a selected setting and help the policy page load correctly. You can adjust cookie controls in your browser, although some account steps may then need repeating.

Data retention

We retain records for the period needed to operate the account, resolve a payment status question or meet a legal requirement. When that purpose ends, handling follows our deletion process.

Change requests

Contact us through account support to request correction, access or clarification about your personal details. Include the registered contact path, and we will verify the request before making a change.

Explore Answers About This Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. Each response connects the written policy with a practical account, device or wallet situation.

It covers account details, sign-in activity, device signals, cookies, payment references and support requests. It also explains retention, security checks and how you can ask about or change your records.

We may collect the contact details you submit, account verification results, login events and device information linked to the session. We collect payment references when you use DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy explains that we use payment references and status details to match a QRIS or DANA receipt with your account. We do not require your wallet password for that check.

Cookies can keep your session active, remember a policy preference and support the path from login to the lobby. Browser controls let you remove or restrict them, but some account steps may repeat.

You can contact account support and request access, correction or clarification. Use the registered phone or email path, and we will verify your identity before discussing private records or applying changes.

We keep personal data while it serves account operation, payment-status checks, support handling or a legal requirement. After the relevant purpose ends, the record follows our deletion and retention process.

Yes. Account access and available functions depend on local law. Where local law permits, we apply the handling described here and will explain any request or access restriction through support.