Reference

jiwa62 Privacy Policy for Your Account

Our Privacy Policy explains what jiwa62 collects when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
jiwa62 jiwa62 Privacy Policy for Your Account
PRIVACY CONTACT PATH

Three Ways to Resolve Data Questions

A clear contact path helps you address a privacy concern without mixing it with a wallet-status query. Start from the account support route, describe the specific record or device issue, and include only the details needed to locate your account. We use the same route for access questions, correction requests and follow-up on a payment receipt.

Team online

Account privacy route

Open the contact path inside your account and state whether you need access, correction or deletion of personal data. We may ask for an account step to confirm the request belongs to you.

Wallet record question

For DANA, OVO, GoPay or QRIS references, identify the payment method and date without sending a wallet password. We use the receipt or status detail to locate the relevant record.

Login data concern

If a phone, browser or login record looks unfamiliar, tell us through the account contact route. We can explain the recorded event and the steps needed to protect account access.

HANDLING YOUR RECORDS

Six Practical Privacy Commitments

Privacy work is part of the account flow, from the first phone verification to a later request to change stored details.

Collected account details

We may hold contact details, verification results and sign-in records supplied during account access. These records help us identify the correct account when you ask about a privacy matter.

Device and cookie signals

A phone or browser can create technical records such as session activity and cookie preferences. You can review cookie controls on your device and contact us about a record you do not recognise.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may be linked to your account for receipt matching. We handle the reference needed for checking, not your wallet password.

Account protection

Phone verification and sign-in checks help us distinguish an account holder from an unfamiliar device. Never send a password in a privacy request; use the account contact path instead.

Retention decisions

We retain records for the period needed to handle account access, payment reconciliation, security checks or a legal request. When a record is no longer needed, our process addresses its removal or restriction.

Changes and objections

You can ask which personal details we hold, request a correction or raise an objection through the privacy contact route. We may verify account ownership before making a change.

Privacy Policy Answers for jiwa62

These Privacy Policy answers address the account, device and payment questions we expect you to ask before opening an account. If your situation is not covered, use the privacy contact route with a short description of the record involved. Access remains subject to local law.

It covers account details, phone verification, device and cookie records, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps us confirm account ownership before access and before responding to a data request. It also helps us investigate an unfamiliar login without exposing account details to another person.

Yes. The policy covers payment references and receipt details used to match DANA or QRIS activity to your account. We do not ask you to send a wallet password through a privacy request.

Use the privacy contact route inside your account, identify the records you want to access, and complete any ownership check we request. We will use the details supplied to locate the relevant account.

You can request a correction through the same privacy route. State which detail is inaccurate and provide the replacement value; we may confirm your account step before updating the record.

We keep records for the period needed for account access, receipt matching, security checks or a legal request. The applicable retention decision can depend on the record and local law.

Use the privacy contact route and mention the device or browser involved, along with the cookie or session concern. You can also adjust available cookie controls directly in your browser.