Reference

kangjitu Privacy Policy For Your Account Data

kangjitu Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account detailsWallet activityDevice controlsPolicy requests
kangjitu kangjitu Privacy Policy For Your Account Data
CONTACT ROUTES

How To Ask About Your Privacy

A direct request helps us locate the right account record without guesswork.

Account support path Open the signed-in support route and identify the account detail you want checked.
Wallet status request For DANA, OVO, GoPay, QRIS or bank transfer questions, include the payment reference and…
Access concern If a new phone cannot reach your account, tell us the device path and…
DATA PRACTICE

How We Handle Six Privacy Areas

We keep this policy practical: each data category has a reason connected to account operation, security or your request.

Account records

We use the contact and verification details you submit to create an account, confirm account access and connect your requests…

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can identify payment status.

Cookies and sessions

Cookies and similar session records help keep a signed-in page connected to your account.

Account security

We examine sign-in time, device markers and verification events when account access looks unusual.

Retention approach

We retain records only for the period needed for account operation, security checks, payment reconciliation or a legal requirement.

Change requests

You may ask us to correct account details, explain a data use or check whether a record can be removed.

Privacy Policy Questions About kangjitu

These Privacy Policy answers focus on the searches we hear most often before an account is opened. They explain the account step, local wallet references, device records and the route for requesting help, so you can decide what to share before using the site.

It explains how we handle account, device, support and payment-status records connected with your access. It applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account references.

The policy covers details you submit, verification events, sign-in times, device markers, cookies, support messages and payment references. We use each category for a stated account, security, reconciliation or legal purpose.

Your Privacy Policy handling does not require us to ask for a DANA, OVO, GoPay or QRIS wallet password. Send a payment reference instead, and never include a password in a support request.

Yes. Use the signed-in support path, identify the record to correct and provide your registered contact detail. We may confirm account ownership before changing or disclosing personal account data.

A phone browser can create session and device records that help connect sign-in activity with your account. Clearing cookies may remove the session and require you to complete account access again.

We keep records for the period needed for account operation, security checks, payment reconciliation or a legal requirement. The applicable retention process determines when records are removed or otherwise handled.

Sign in and use the support route connected with your account. Include the subject, registered contact detail and any payment reference; access or eligibility depends on local law.