Reference

warisanjitu Privacy Policy Explained Clearly

Our Privacy Policy shows exactly how warisanjitu handles the account details, wallet references and device data connected with your access.

Account dataWallet referencesDevice choicesPolicy requests
warisanjitu warisanjitu Privacy Policy Explained Clearly
REQUEST PATHS

How To Ask About Your Data

A clear support route helps when a Privacy Policy question concerns your login, phone verification or wallet record.

Account access request Use your account support path to ask which personal details are connected with your login, phone verification and security checks. We may confirm account ownership before sharing any record.
Wallet record question For DANA, OVO, GoPay or QRIS questions, include the relevant payment reference and date. We use that detail to locate the wallet status without requesting your full wallet credentials.
Correction request If your phone, email or account detail needs correction, tell us which field is wrong through the same support route. We check the request before changing the account record.
HANDLING DETAILS

Six Practical Privacy Controls We Use

Our handling approach is built around limited collection, clear account purpose and a practical way to request changes.

Account details

We use your supplied phone or email details to create the account record, support phone verification and respond to account requests. You can ask us to confirm or correct those details.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data. We use the reference, amount status and account link for reconciliation, not your wallet password.

Cookies and sessions

Cookies may keep a signed-in session available and remember selected access settings. Clearing browser cookies can end that session, so you may need to complete account access again.

Device signals

We may record browser, operating system and device signals connected with login events. These details help us examine unusual access and protect your account from unauthorised use.

Retention approach

We retain account, security and payment-reference data only for operational, dispute, legal or security needs that apply to the record. You can ask why a particular record remains stored.

Changes and contact

To request access, correction or deletion where applicable, use the account support path and identify the relevant record. We verify ownership first, then explain the available next step.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions most likely to arise before you open access or use an Indonesian wallet. We keep the wording practical: what we collect, why a payment reference appears, how device data works and how you can request a change. If your situation is not covered, use the support path with the account detail you want us to check.

It covers account details, phone verification, login events, device signals, cookies, payment references and support requests connected with your access. It also explains retention, security handling and requests for changes.

We use your phone number for account creation, phone verification and account access checks. It can also help us locate your record when you ask about a login or correction request.

Yes. The Privacy Policy covers payment references created when you select DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use those references to match status with your account.

We may record browser type, operating system, device signals and login timing. This helps us identify unusual access and protect your account; it does not require your wallet password.

Use the account support path and ask for an access request, including the phone or email attached to your account. We verify ownership before explaining which records can be supplied.

Yes. Send a correction request through account support and identify the incorrect phone, email or account field. After ownership checks, we explain the available correction step under applicable local law.

Retention depends on operational, security, dispute and legal needs linked to the record. You can ask why specific account or payment-reference data remains stored and whether a deletion request applies.