Reference

kpsjitu Privacy Policy for Your Account

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

Account dataWallet detailsDevice signalsCookie choices
kpsjitu kpsjitu Privacy Policy for Your Account
POLICY HELP PATH

Get Privacy Answers Near Account Support

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or check why a wallet reference is being…

Policy questions Use the account support route when you need a plain explanation of the Privacy…
Correction requests Tell us which account field needs changing and provide the sign-in detail that helps…
Wallet status checks For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than wallet…
HANDLING YOUR DETAILS

What Our Privacy Process Covers

We keep the Privacy Policy connected to practical account handling rather than abstract promises.

Account data

We may handle your name, contact detail, phone verification result and account activity needed to open and maintain access. These fields help us match your requests without relying on a wallet number alone.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a rail name, reference and status record. We use those fields to reconcile the account step, not to request your wallet password.

Cookies and devices

Cookies and mobile-browser signals can remember a session, support sign-in protection and show the right account state after you return. You can manage cookie permissions through your browser settings, though some account functions may then need another sign-in.

Account protection

Phone verification and sign-in checks help us identify the account holder before access or a data request is handled. Never share your password, one-time code or complete wallet credentials through a support message.

Retention choices

We keep relevant records for the period needed to operate the account, resolve a payment status question, address misuse or meet a legal requirement. When the purpose ends, records may be deleted, anonymised or restricted.

Your requests

You can ask for a copy, correction, restriction or deletion where the request is allowed by applicable law. Send the request through account support with enough detail for us to verify ownership before we respond.

Privacy Policy Questions for kpsjitu

These Privacy Policy answers cover the account questions you may have before opening access or using an Indonesian wallet rail. We explain the practical path for data requests, device records and payment references. If your situation is not covered, use account support and include only the details needed to locate your request.

The kpsjitu Privacy Policy covers account details, phone verification, sign-in activity, device and cookie records, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests.

Phone verification helps us connect an account request to the person trying to sign in. It also supports account protection when you ask for a data copy, correction, deletion or wallet status check through account support.

Yes. The Privacy Policy covers the rail name, reference and status needed to match a DANA or QRIS account transaction. We do not need your wallet password, one-time code or complete wallet credentials for that purpose.

You can send a data-copy request through the account support route. We first verify that you control the account, then explain which records can be provided and which limits may apply under local law.

Use account support and identify the field that is wrong, such as a contact detail or account name. Include the sign-in detail used for verification, but do not send a password or wallet credentials.

We retain records while they serve account operation, sign-in protection, payment matching, dispute handling, safety checks or a legal need. After that purpose ends, records may be removed, anonymised or restricted.

Yes. Account access and eligibility depend on local law. We may limit a request or ask for additional verification when required, and account support can explain the available path without asking for unnecessary private details.