Reference

cuan100 Privacy Policy For Your Account

The cuan100 Privacy Policy explains what account, device, contact and wallet details we use when you open an account or access the lobby from Indonesia.

Account dataWallet detailsDevice accessYour requests
cuan100 cuan100 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact path helps when you want to ask about the Privacy Policy, check a stored detail, or question a wallet record. Tell us the account email or phone number linked to your request, but do not send a password, one-time code or full wallet credential. Our team may ask for limited account checks before discussing personal data. If you are in Jakarta, you can use the same account support route as any other Indonesian customer; the request is handled against the account record rather than the city.

Team online

Account questions

Use our account support channel for Privacy Policy questions about your name, phone verification, sign-in record or contact details. Include the subject of your request and the account identifier you can safely share, so we can locate the correct record without asking for your password.

Wallet records

For a privacy question involving DANA, OVO, GoPay or QRIS, include the transaction reference and date when available. We can explain which account data is connected to a payment status, while sensitive wallet credentials remain outside the details we ask you to send.

Correction requests

Ask us to correct an inaccurate account detail through the same support route. We first compare the request with phone verification and account records, then explain any step needed before a change can be made. Where local law permits, we also explain available deletion or access options.

DATA PRACTICES

What We Do With Your Account Data

We apply the Privacy Policy to the practical data trail created by your account, device and payment activity.

Account security

Phone verification helps connect an account request to the person controlling the registered contact detail. We may record sign-in, session and security events to detect unusual access. Never share your password or one-time code with support; our Privacy Policy does not require those secrets in a contact request.

Mobile and desktop

The service can be opened from a mobile browser or desktop browser, and each path can create device, browser and session signals. We use those signals for access continuity, fraud checks and technical operation. They do not replace the account details needed for phone verification or a privacy request.

Cookies

Cookies can preserve essential login or page settings and help us identify a current session. Our Privacy Policy distinguishes necessary operation from optional measurement where that choice is available. Clearing cookies may sign you out or remove saved settings, but it does not by itself close your account.

Payment matching

Payment references help us match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with the right account. We use status and reference data for reconciliation and account support, not as a reason to request your wallet password, card secret or one-time verification code.

Record retention

We retain account, support, device and payment records for the period needed to operate the service, investigate security events, resolve disputes or meet legal duties. When a retention reason ends, our handling follows the deletion, anonymisation or restriction process available under the Privacy Policy and local requirements.

Your requests

You can contact us to ask what personal data is held, request a correction, question its use or ask about deletion where available. We may verify that the request comes from the account holder before responding. Our answer can include limits required by law, payment reconciliation or security investigations.

Privacy Policy Questions For cuan100

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. They explain the practical data created by phone verification, mobile sessions, wallet status and support contact. If your situation is not covered, send a specific request through the account support route and include only the details needed to identify your account.

The cuan100 Privacy Policy covers account, phone verification, device, session, cookie, support and payment-reference data. It explains why we use each category, how long operational records may be retained, and how you can ask about access, correction, restriction or deletion where local law permits.

Our Privacy Policy does not require you to send a DANA, OVO, GoPay or QRIS password or one-time code to us. We may handle a transaction reference, account link and payment status so support can identify a request, while your private wallet credentials should remain with the wallet provider.

Phone verification helps us connect account access and privacy requests to the registered contact detail. It also supports checks when a sign-in or account change looks unusual. We may record the verification result and related security event, but you should not disclose the one-time code in a support message.

Yes. Send a correction request through our account support route and identify the account detail that appears wrong. We may compare your request with the registered phone or email before changing it. The Privacy Policy explains when a correction can be limited by payment, security or legal records.

When you use a mobile browser to sign in, we may receive browser, device and session signals needed for access continuity, technical diagnosis and unusual-login checks. The same principles apply on desktop. These signals support account security and do not replace the personal details used for verification.

We keep records for as long as they are needed for service operation, payment matching, security investigation, dispute handling or legal duties. The exact period can depend on the record type and applicable requirement. You can ask support how a particular record is handled under the Privacy Policy.

Use our account support channel and state whether you want access, correction, deletion information or an explanation of data use. Include your registered account identifier and a payment reference only when relevant. Do not include passwords or one-time codes. Access and eligibility depends on local law.