Reference

duta jitu Privacy Policy, Clearly Explained

Our Privacy Policy explains what duta jitu collects when you open an account, verify your phone, use a mobile browser or select DANA and QRIS.

Account dataWallet recordsCookie choicesAccess requests
duta jitu duta jitu Privacy Policy, Clearly Explained
CONTACT ROUTES

Contact Paths For Privacy Questions

A clear contact route helps you ask what we hold, why we use it or how to request a correction.

Account support route Ask about phone verification, sign-in records or an account detail through the support path connected to your account. Share only the details needed to identify your request.
Wallet status check For DANA, OVO, GoPay or QRIS questions, provide the payment reference and selected rail. We can check the recorded status without asking for your wallet password or private access code.
Privacy request Request access, correction or removal by clearly naming the account detail involved. We may ask for an account step that confirms ownership before changing or disclosing personal data.
DATA CONTROLS

Six Controls Behind Your Account Data

Our handling process follows the same practical path you see during account access: collect what the step needs, use it for that stated purpose and restrict internal access.

Account collection

We collect your phone number and account details when you open access or complete verification. These fields help match your sign-in activity with the account record you asked us to maintain.

Cookie choices

Cookies can remember a session and support essential page functions. Your browser can block or clear them, although removing necessary cookies may require you to verify your account again.

Device signals

A mobile browser may provide device and session signals used to recognise unusual sign-in behaviour. We use these signals for access protection, not as a substitute for your phone verification.

Wallet records

DANA, OVO, GoPay and QRIS references help us trace a payment status or receipt. We do not need your wallet password to match a recorded transaction with your account.

Retention period

We keep account, support and transaction records for the time needed to operate access, resolve disputes or meet legal duties. After that purpose ends, records are removed or anonymised.

Change requests

You can ask us to correct account data or explain its use through the privacy request route. We may verify ownership first so a private account record is not changed by another person.

Privacy Policy Questions You May Search

These answers focus on the questions you may have before opening an account or connecting a local wallet. Each answer points back to a concrete Privacy Policy step, from mobile cookies and phone verification to DANA records and requests to change your data.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number to create and verify account access, connect sign-in activity to the correct record and help investigate an access question. We do not need your wallet password.

Yes. The policy covers mobile browser sessions, essential cookies and device signals used to keep access working and identify unusual sign-in behaviour. Clearing cookies may require another account check.

We record the payment rail, reference and status needed to reconcile a request or receipt. DANA and QRIS data is used for that operational check, not to request your private wallet password.

Yes. Send a privacy request through the account support route and name the detail that needs correction. We may confirm account ownership before changing a phone, profile or contact record.

We retain account, support and transaction records while they serve access, dispute or legal needs. When the relevant purpose ends, we remove or anonymise the record where applicable.

Yes. Account access and related data handling depend on local law and apply where local law permits. If you need clarification, use the privacy request route before opening or using an account.