Reference

How the cuanjp Privacy Policy protects wallet data

Your account details, DANA activity and QRIS records are handled under the cuanjp Privacy Policy, so you can see why we collect data and how it supports account…

Account dataWallet recordsCookie choicesSecurity requests
cuanjp How the cuanjp Privacy Policy protects wallet data
HELP CHANNELS

Where to ask about Privacy Policy

A clear contact route matters when you want to understand a data record or correct an account detail. We keep privacy questions close to the login and cashier paths, so you can explain the issue without sending payment credentials in an open message. Include your registered phone number only through the account support route, and we will use it to locate the relevant request.

Team online

Account support route

Use the support path beside account login when you need a copy of your stored details, a correction to your phone record, or an explanation of a verification request.

Wallet status help

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact us through the cashier support path. We can check the related record without asking you to share a wallet PIN.

Privacy request

For deletion, restriction or consent questions, state the request clearly and identify the account email or phone number. We may ask for an account step to confirm that the request is yours.

CONTROL DETAILS

Six privacy controls behind your account

We apply the Privacy Policy to practical account events rather than treating it as a page you read once.

Data used for access

We use your registered phone, account credentials and verification result to identify your account before showing account or wallet details. This reduces the chance that a device session exposes another person’s records.

Payment references

A DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI reference may remain in transaction records. We use the reference to reconcile status and support a payment question, not to request your wallet PIN.

Cookies and devices

Cookies can remember a session setting, while device signals help us identify repeated sign-in patterns. You can manage browser cookie controls, though changing them may require another login or verification step.

Security monitoring

We record sign-in time, device type and selected account events to detect suspicious access. These records help us investigate a locked session or an unexpected change connected with your account.

Retention periods

We retain records only for the period needed for account operation, payment reconciliation, dispute handling or legal duties. When a record no longer serves one of those purposes, our process removes or anonymises it.

Changing your details

Ask us to correct a name, phone number or contact detail through account support. We verify the request against your account before making a change, and we explain any record that cannot yet be altered.

Privacy Policy answers for cuanjp accounts

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. If your situation is not listed, contact us through the account support path and mention the exact record, device event or payment reference you want us to check.

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

Phone verification helps us confirm that the person requesting account or wallet access controls the registered account. We record the result so we can investigate disputed sign-ins and unusual changes.

We do not ask you to send a DANA, OVO or GoPay wallet PIN through support. The Privacy Policy covers payment references and status checks, while your wallet provider handles its own secret credentials.

Use the account support route and identify your registered phone number or email. We may request an account verification step before releasing records, helping ensure the request comes from you.

Yes. Send a clear correction request through support, naming the field that is wrong, such as your phone number. We check account ownership first and then update the record where permitted.

Retention depends on the purpose of each record, including reconciliation, dispute handling, account security or legal duties. When the purpose ends, we remove or anonymise the relevant record.

Yes. It applies when you sign in from a mobile browser or desktop. Cookies and device signals may differ by browser, and changing cookie settings can trigger another account verification step.