Reference

ciu123 Privacy Policy And Your Account

Our Privacy Policy explains how ciu123 handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Clear data purposesCookie choicesAccount access requestsSecurity checks
ciu123 ciu123 Privacy Policy And Your Account
CONTACT PATHS

Where Privacy Questions Reach Our Team

A direct support route helps you ask about the Privacy Policy without guessing which account menu to use.

Account access request Ask us to confirm whether ciu123 holds data connected to your account. We may ask you to verify the phone or email used at account creation before discussing records, so private details are not released to another person.
Correction request If your contact detail or account record is inaccurate, send the specific field and the corrected value through the account support path. We compare the request with your account step before changing information that affects sign-in.
Privacy clarification For questions about cookies, device records or wallet references, describe the screen and action involved. Our support team can explain how the Privacy Policy applies without asking you to share a password, PIN or one-time code.
DATA CONTROL

Inside ciu123 Privacy Handling

We apply the Privacy Policy at the points where account activity creates a record, rather than treating privacy as a page you read once.

Account details

We use the phone or email you submit during account creation to support sign-in, verification and account messages. Keep those details current, because a correction request may require confirmation through the contact method already attached to your account.

Device records

A mobile browser session may create device and access records linked to security checks. These records help us notice unusual sign-in behaviour around the lobby, but they do not give us permission to read unrelated files on your phone.

Cookie choices

Cookies can keep a session active, remember a selected setting or help us understand which policy page was opened. Your browser controls how some cookies are stored. Turning them off may require you to repeat an account step.

Account security

We may request a phone verification step before account access or before discussing sensitive records. Never provide an OTP Login Guide code, password or wallet PIN to another person, including someone claiming to speak for support.

Retention handling

We keep records only for the account, security, support or legal purpose that requires them. Payment references from DANA or QRIS may remain for reconciliation, then access is restricted or the record is removed when the applicable period ends.

Policy changes

If we change how personal data is handled, we place the revised Privacy Policy where you can read it before continuing with relevant account activity. Check the page when you sign in, especially after a cookie or security notice appears.

Privacy Policy Questions For ciu123

These Privacy Policy answers address the account questions we expect you to ask before opening or using ciu123 from Indonesia. They explain the usual request path without replacing the full policy text. If your situation involves a legal request, an account dispute or access outside the supported region, contact us with the account detail you can safely share. Eligibility depends on local law.

It covers account details, sign-in and device records, cookies, support messages, payment references and how we retain or secure them. The Privacy Policy also explains your access and correction request paths, including when we need to verify the phone or email linked to your account.

We may use your phone number for account creation, sign-in checks, verification and account-related messages. Before discussing sensitive records, we can ask you to confirm that number. A one-time code should stay private and must not be sent to support or another person.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may be retained to match a wallet action with the correct account and resolve status questions. We may also keep bank transfer or virtual account references for reconciliation and security.

Use the account support path and state that you want an access request under the Privacy Policy. Include the contact detail connected to your account, but never include a password, wallet PIN or one-time code. We may verify your identity before confirming or supplying records.

You can request a correction when a contact detail or other account record is inaccurate. Tell us which field is wrong and what it should say through support. We compare the request with your account information before changing data used for sign-in or verification.

Cookies can support a mobile session, remember a setting or show whether a policy page was opened. Your browser provides controls for some cookie storage. If you disable required cookies, you may need to repeat login or phone verification before reaching the lobby.

You may ask us to remove or restrict personal data where local law permits, but some records can require retention for security, payment reconciliation, account administration or legal duties. We assess the request under the Privacy Policy and explain any limit that applies.