Reference

Privacy Policy for Your cuan25 Account

Our Privacy Policy explains what cuan25 collects when you create an account, verify your phone and use wallet routes such as DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
cuan25 Privacy Policy for Your cuan25 Account
REQUEST HELP

Privacy Questions Around Wallet Status

A clear contact path matters when a Privacy Policy question concerns a pending receipt, a changed phone number or an unfamiliar login.

Account request Ask us to locate, correct or explain account data through the signed-in support route.
Cashier record For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, name the…
Access correction If your phone, name or account detail needs changing, tell us which field is…
HANDLING YOUR DATA

What We Do With Account Details

We keep this policy practical: each data use connects to an account action, a security check, a wallet record or a request from you.

Account details

We use your account name, contact route and phone-verification result to create and protect access. The same details help us connect your session with a cashier record or a request to change data. We do not need your wallet PIN to handle an ordinary policy question.

Cookies and devices

Cookies can remember a session choice, while device signals help us recognise an unusual login from a phone or desktop browser. You can clear browser cookies through your device settings, though doing so may require another login and phone check before account access returns.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be stored with the related account action so we can match status and receipt questions. Bank transfer and virtual account references serve the same narrow purpose when you ask us to trace a cashier record.

Account security

We record login events, phone verification and selected device signals to reduce unauthorised access. If a session looks unusual, we may pause the account step and ask you to verify the phone again. Never share a password, wallet PIN or one-time code with support.

Retention timing

We retain account, support and transaction records only for the period needed for the stated service, dispute handling, security checks or a legal duty. When those reasons end, we assess deletion or removal from active systems, subject to records that law requires us to keep.

Your requests

You can ask what account data we hold, request a correction, question a wallet reference or ask about deletion through the signed-in support route. State the account step involved; we may verify your phone first so a change does not expose your account to another person.

Privacy Policy Questions About cuan25

These answers address the Privacy Policy searches we expect before account creation or a wallet request. We explain the practical path for access, correction, cookies and payment references without asking you to disclose secret credentials. If your question concerns eligibility or access from Indonesia, it depends on local law and the account route available to you.

The cuan25 Privacy Policy covers account creation, phone verification, login events, device signals, cookies, support messages and wallet references. It explains why we use those records, how long we may retain them, and how you can request access or correction through the signed-in support route.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references connected with your account, as well as bank transfer and virtual account records. We use the relevant reference to match cashier status or receipt questions, and we do not need your wallet PIN for that check.

Sign in, open the support route beside the cashier area and ask for an account data access request. Include your account reference and the type of record you mean. We may repeat phone verification before responding, because the request must not expose your details to another person.

You can request a correction when your phone number or another account field is wrong. Use the signed-in support route, identify the field and complete any phone check we ask for. We will assess the request against account security and the local rules that apply to access.

Cookies can retain a session choice, while device signals may help us identify an unusual login. Clearing cookies in your phone or desktop browser can sign you out and trigger another login or phone-verification step. The Privacy Policy explains these uses and the related account request path.

We keep payment references only as long as needed for the stated service, receipt questions, security checks, disputes or a legal duty. This can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference linked to your account activity.

Use the signed-in account support route and describe whether you want access, correction, deletion or an explanation of a specific record. Do not send your password, wallet PIN or one-time code. Requests from Indonesia are handled where local law permits and may require phone verification.