Reference

Privacy Policy For Your cuanunited Account

Our Privacy Policy explains what cuanunited collects when you create an account, sign in on mobile or desktop, and check wallet status for DANA, OVO, GoPay or QRIS.

Account clarityWallet record handlingCookie choicesPolicy access

Explore Our Lobby Read FAQ

Know What Your Account Records Cover

cuanunited Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details linked to your account journey, such as your contact details, phone verification status, sign-in activity, device information and records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account checks. We may use this data to keep access consistent, investigate

1
an unusual sign-in, match a payment receipt or answer a request about your account. We do not treat a payment name as permission to collect unrelated details. You can ask us what we hold, why we use it and how long we retain it through our
2
account support route. Access and eligibility depends on local law, and our handling applies where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps you deal with a privacy question without guessing which account screen to use.

HANDLING DETAILS

See How Privacy Works In Practice

Privacy is handled through ordinary account actions rather than a separate process you must learn.

Data we receive

We may receive the contact details you enter, phone verification results, account preferences, sign-in events and device information linked to your access. When you use DANA or QRIS, we keep the reference needed to connect a wallet status or receipt question with the correct account action.

Cookie choices

Cookies and similar browser records can help retain an account session or remember a setting on the device you use. You can review browser controls before signing in. If you clear cookies, we may ask you to complete the account access and phone verification steps again.

Account security

Phone verification gives us an account step to compare when access or a data request appears unusual. We do not need your password in a support message. Keep sign-in details private, and contact us through the account support path if a device entry or access event does not look familiar.

Retention approach

We retain personal and payment-related records for as long as they are needed for the stated account, security, support or legal purpose, subject to local requirements. A request to remove or correct data can be assessed against those duties, and we will explain any record that must remain.

Requesting a change

To request access, correction or deletion, identify the account contact detail and describe the data involved. We may verify ownership before acting. If the request relates to a QRIS, GoPay or bank transfer reference, include only the limited receipt context needed to find it.

Policy contact

Questions about this Privacy Policy can follow the same support route used for account help. Tell us whether you need a copy of your data, a correction, a cookie explanation or clarification about retention; we will direct the request to the relevant policy handling step.

Privacy Policy Questions Before Access

These answers address the privacy searches we expect before an Indonesian account holder opens an account or signs in again. They explain the practical link between the Privacy Policy and account records, device behaviour, phone verification and local wallet references. If your situation is not covered, use the support route and describe the exact data question. Access depends on local law, including where local law permits account use.

It covers personal details connected with account creation, phone verification, sign-in activity, device behaviour, cookies, support requests and payment references. DANA, OVO, GoPay and QRIS records are handled as account-related payment context, so we can investigate a receipt or wallet status question.

Phone verification helps connect an account request to the person who controls the registered contact detail. We may use that step when you open an account, recover access or request a data change. It also helps us review an unusual sign-in without asking you to send a password.

Yes. The Privacy Policy explains that browser cookies or similar records can keep a session or setting available on your device. If you clear them on a mobile browser, you may need to sign in and complete phone verification again before reaching your account area.

Use our account support route and state that you want access to your personal data. Provide the registered contact detail and describe the records you want reviewed, such as device entries or account activity. We may verify ownership first, then explain the available response under local requirements.

You can request a correction or deletion through the same privacy contact path. Tell us which field or record is wrong and why. We assess deletion requests against security, account and legal retention duties, including a payment reference needed to resolve a DANA or QRIS receipt query.

We use limited payment context to connect your account action with a status or receipt check. For OVO, GoPay, DANA, QRIS, bank transfer or virtual account activity, send only the relevant reference details through the support route. Do not send passwords or full payment credentials.

You can read this Privacy Policy from the policy area before completing account access, whether you use a mobile browser or desktop. Review the collection, cookies, security, retention and request sections first. Where local law permits, account eligibility still depends on local law.

Privacy Policy For Your cuanunited Account

Get Clear Answers About Your Data

See How Privacy Works In Practice

Data we receive

Cookie choices

Account security

Retention approach

Requesting a change

Policy contact

Privacy Policy Questions Before Access

01 What does the cuanunited Privacy Policy cover?

02 Why does cuanunited need phone verification?

03 Does the Privacy Policy explain cookie use on mobile?

04 How can I request my cuanunited account data?

05 Can I ask for a correction or deletion?

06 How are payment details handled under this policy?

07 Where can I read the Privacy Policy before opening an account?

Related Pages