Reference

Privacy Policy for Your cor333 Account

Our Privacy Policy explains how we handle the details connected to your cor333 account, including phone verification, wallet activity and device access.

Account dataWallet recordsCookie choicesSecurity requests
cor333 Privacy Policy for Your cor333 Account
CONTACT PATHS

Get Privacy Help Beside Account Support

A clear contact path helps when you want to ask about the Privacy Policy, check a wallet record or correct an account detail.

Account request Use the account support path when your Privacy Policy question concerns phone verification, sign-in…
Wallet record For a privacy question about DANA, OVO, GoPay or QRIS, send the payment date…
Access concern If a device or sign-in appears unfamiliar, contact us through the account support route…
DATA PRACTICES

What You Can Ask Us To Change

We handle this policy area through practical account controls rather than vague promises.

Data collection

We collect details needed for account access, phone verification, support conversations and payment status checks.

Cookie controls

Cookies can remember a sign-in session, device preference or page choice so you do not repeat the same step on…

Account security

Phone verification and sign-in checks help us separate your account from an unfamiliar device.

Payment records

A bank transfer or virtual account request can create a reference used to match status with your account.

Retention period

We retain account, security and payment records only for as long as needed for the purpose described in this Privacy…

Correction request

If your phone detail, account name or contact record is inaccurate, send a correction request through account support.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you are most likely to ask before opening access. We keep the route practical: identify the relevant record, use the account support path and share only the details needed to investigate. If a request involves eligibility or access, the outcome depends on local law.

The cor333 Privacy Policy covers account creation, phone verification, sign-in devices, cookies, support messages and payment references. It explains how we use those details for account access, security, wallet status checks and legal obligations where local law permits.

Phone verification helps us connect a privacy request to the correct account and reduce mistaken access. We may use it when you ask to correct personal data, investigate an unfamiliar device or discuss a DANA, OVO, GoPay or QRIS record.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use these records to match account activity and answer receipt questions.

Contact us through the account support path and identify the field you want corrected, such as a phone detail or contact record. We may ask you to complete phone verification before changing data that can affect sign-in or account ownership.

You can ask us which account, device, cookie, support or payment categories relate to your profile and why they remain retained. Include your account identifier in the request, but do not send a password, wallet PIN or one-time verification code.

We may use device and session details to investigate access that does not match your usual sign-in path. If you contact support from a mobile browser or desktop browser, describe that route and complete the requested account check before changes are made.

You can send a deletion request through account support, and we will assess it against account administration, security needs and legal retention duties. Where local law permits, we will explain what can be removed, what must remain and the next account step.