Reference

capcusjp Privacy Policy For Your Account

capcusjp Privacy Policy explains how we handle the details you provide when you open an account, verify your phone, enter the lobby or use DANA and QRIS.

Account clarityWallet recordsDevice accessPrivacy requests
capcusjp capcusjp Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Questions Through Your Account Route

A clear support route helps you act on the Privacy Policy without sending personal details through an unverified channel.

Account privacy request Open your account support route and state whether you want access, correction or removal of personal details. We may ask you to confirm the account phone number before discussing records, so a private request reaches the right account.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date and visible reference through account support. Do not include a wallet password or full security code; we use the reference to trace the relevant record.
Login access help When a device session or phone verification blocks your request, tell us which step stopped and whether you used mobile or desktop access. We can explain the privacy process after account checks, while access depends on local law.
DATA HANDLING DETAILS

What We Do With Your Account Details

We keep Privacy Policy decisions tied to practical account events rather than broad platform activity.

Account details

We may handle your name, phone number, sign-in details and verification result to create and protect your account. The phone check happens before account access, and we use those details to connect the correct person with the correct account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave reference data in our records. We use those references to reconcile an account action, check a status and respond when a wallet step stalls.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, protect a page and help us understand whether a request belongs to your active account. Your mobile browser may create a new session after cleared cookies or device changes.

Account security

We use phone verification, session checks and limited access controls to reduce unauthorised account activity. Never share a password or security code through support. If a device looks unfamiliar, sign out and raise the matter through your account contact route.

Retention decisions

We retain account, security and payment references only as long as needed for the stated service, dispute handling, fraud checks or a legal requirement. When a valid retention reason ends, we remove, anonymise or restrict the relevant record.

Your requests

You can ask for access to your personal data, correction of an inaccurate detail or clarification of our handling. Send the request through account support; we may verify your phone first and explain any reason a record cannot be changed immediately.

Privacy Policy Answers For capcusjp

These Privacy Policy answers cover the questions we expect you to ask before opening an account or checking a wallet status. Each answer points to a practical account step, device path or contact route. If your situation is not listed, contact us from the signed-in account area where possible. Access depends on local law.

The capcusjp Privacy Policy covers details connected with your account, phone verification, device sessions, cookies, payment references and support requests. It explains why we use those details for access, security, reconciliation and legal needs, and how you can ask about a specific record.

We may collect your account identifiers, phone number, verification result, sign-in activity, device session details and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps can create records needed to match a transaction with your account.

Our Privacy Policy covers cookies and session tools used to keep an account page connected to your sign-in and protect requests. If you clear mobile browser cookies or change devices, you may need to sign in and complete phone verification again.

Yes. Send an access request through the signed-in account support route and describe the records you need. We may confirm your phone number before responding. We will explain the scope, timing and any record that must remain for security or legal reasons.

Use account support to identify the inaccurate detail and provide the corrected value. We may verify the account phone before changing it. Payment references are usually matched to the original wallet or bank record, so some transaction fields may not be editable.

We keep account, security and payment references for the period needed to operate the account, resolve disputes, check suspicious activity or meet a valid legal requirement. After that purpose ends, we remove, anonymise or restrict the relevant records.

Yes, access and some privacy choices depend on local law. We apply the Privacy Policy to supported Indonesia account activity and explain any regional restriction when you contact us. Where local law permits, we process valid access, correction or deletion requests.