Reference

Privacy Policy for Your coc55 Account

Our Privacy Policy explains what we collect when you open a coc55 account, sign in from a phone or desktop, and choose DANA, OVO, GoPay or QRIS.

Account detailsWallet recordsCookie choicesData requests
coc55 Privacy Policy for Your coc55 Account
CONTACT DATA DESK

Where to Ask About Your Data

A clear contact path helps when a Privacy Policy question concerns an account record or wallet receipt. Start from the support route beside the cashier area and tell us whether your request concerns phone verification, a DANA receipt, a QRIS reference or another account detail. We may ask for the registered contact detail and a transaction reference, but never ask you to send a password. For access, correction or deletion requests, we check ownership before discussing the record.

Team online

Account questions

Tell us which registered detail needs checking, such as your phone verification status or sign-in record. We compare the request with the account contact detail before sharing or changing personal data.

Wallet receipts

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate date. This lets our support desk match the receipt without asking you to reveal your wallet password.

Privacy requests

Ask for a copy, correction or deletion assessment through the same support path. We explain what can be changed, retained or removed after confirming that you control the coc55 account.

HANDLING YOUR RECORD

How coc55 Handles Account Data

We handle Privacy Policy matters around the actions you take: creating an account, confirming a phone, signing in on a device and matching a payment reference.

Account creation

We collect the contact details needed for your account path and use phone verification before account access. This helps us distinguish your request from an unverified attempt to use the same details.

Device sessions

When you move between a mobile browser and desktop, session data can help keep your account step connected. Sign out on shared devices and avoid saving your password in a public browser.

Cookies

Cookies can remember session state, language or consent choices. You can manage browser cookie settings, though removing required cookies may affect sign-in and the path back to your account.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match a cashier event. We do not need your wallet password to check whether a receipt reached the account.

Account protection

We use phone verification and ownership checks before discussing account records. Never send a password, one-time code or full wallet credentials when asking us about Privacy Policy matters.

Retention requests

We keep records only for the operational, security and legal purposes that apply to them. Ask us about a specific record, and we will explain the available correction or deletion route where local law permits.

Privacy Policy Questions for coc55 Accounts

These Privacy Policy answers cover the questions we hear before an account is opened and when a wallet receipt needs checking. They explain the account step, device behaviour, payment references and request process without asking you to share unnecessary credentials. If your question is not listed, use the support route beside the cashier area and identify the account detail involved.

It covers account details, phone verification, device sessions, cookies and payment references connected with your use of coc55. It also explains how we respond to requests about access, correction or deletion, with eligibility and handling depending on local law.

Phone verification confirms the account step before access and helps us check that a Privacy Policy request comes from the account holder. We use the verification status for account protection and support checks, not as a reason to request your password.

Yes. The policy covers payment status and reference details connected with DANA, OVO, GoPay and QRIS. For bank transfer or virtual account questions, we may also use the relevant BCA, BRI, Mandiri or BNI reference to match the account event.

Our mobile browser path may use cookies for session continuity, consent choices and account navigation. You can adjust cookie settings in your browser, but removing required cookies may interrupt sign-in or return you to the account start step.

Contact support through the route beside the cashier area and identify the registered contact detail on your account. We first confirm ownership, then explain which account or payment records can be provided and the response process where local law permits.

You can ask us to correct an inaccurate account detail or assess deletion of a specific record. Include the relevant account contact detail, but not a password or wallet code. We explain any retention need and available outcome where local law permits.

Retention depends on the purpose of the record, such as matching a QRIS receipt, resolving a DANA status question, protecting an account or meeting an applicable requirement. Ask about a particular reference and we will explain its handling without requesting wallet credentials.