Reference

asiacuan Privacy Policy For Your Account

asiacuan Privacy Policy explains how we handle the details connected to your account, including phone verification, DANA and QRIS activity, device access and support requests.

Account dataWallet recordsCookie choicesSecurity requests
asiacuan asiacuan Privacy Policy For Your Account
CONTACT THE DESK

Privacy Help Beside Wallet Checks

A clear contact path helps when you want to ask about the Privacy Policy or a payment record attached to your account. Use the support route shown after login and include the phone number linked to your account, the relevant request type and any payment reference you want checked. We ask for only the details needed to locate the record, and we do not ask you to send a full wallet password or security code. If you are in Makassar, the same account contact path applies.

Team online

Account privacy request

Ask us to explain the personal data connected to your asiacuan account. Include your verified phone number and request category so we can locate the correct account record without asking for your password.

Payment record question

For DANA, OVO, GoPay or QRIS data questions, send the payment reference and approximate date through the signed-in support route. We use those details to check the record while limiting unnecessary account exposure.

Access correction path

If a phone verification detail or device record appears wrong, tell us what needs changing and why. We may ask for an account step that confirms control before updating private account data.

DATA HANDLING

Inside asiacuan Privacy Controls

We treat privacy as an operating task rather than a footer link: account records, wallet references and device events need different handling.

Account data

We use your submitted account details and phone verification status to identify the correct account during sign-in and support contact. A request about asiacuan data should come from the account route where possible, so we can reduce mistaken disclosures.

Wallet references

DANA, OVO, GoPay and QRIS references can appear in records used to match a payment status with your account. We keep the reference for checking and reconciliation, not as a reason to request your wallet PIN or one-time security code.

Cookies and storage

Our mobile and desktop pages may use cookies or browser storage for sign-in continuity, security checks and saved privacy choices. You can manage browser permissions, although changing them may require a fresh login or remove a stored preference.

Account security

Phone verification, sign-in events and device signals help us identify unusual access. Keep your password and verification code private; support will not need the full code to answer a Privacy Policy question or locate a payment reference.

Retention timing

We retain account, support and payment-related records only for operational, security or legal needs described by the applicable Privacy Policy. Retention can differ by record type, and you may ask which category applies to a specific request.

Requesting changes

To request access, correction or clarification, use the signed-in support path and state the account phone number, record category and requested action. Where local law permits, we will assess the request and explain any identity check needed.

Privacy Policy Answers For Indonesia

These answers address the questions we expect you to ask before opening an account or sending a privacy request. They focus on asiacuan records, local wallet references, mobile access and the steps used to protect your account. If your question concerns a specific record, the signed-in support route gives us the context needed to respond accurately.

It covers account details, phone verification, device and sign-in events, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains requests for access, correction, retention details and privacy contact.

Phone verification helps us connect a sign-in or support request to the correct account and reduce mistaken access to private details. We may use its status during account checks, but you should never send your full verification code through a support message.

Yes. The Privacy Policy includes payment references and status details needed to match DANA or QRIS activity with your account. Similar handling applies to OVO, GoPay, bank transfer and virtual account records when those rails are selected for an account transaction.

Use the support route available after signing in and state that you want an account data request. Add your verified phone number and the categories you want checked, such as cookies, payment references or support messages. We may request an account security step.

You can request a correction through the signed-in support path. Describe the incorrect field, the accurate replacement and the reason for the change. We may verify control of the account before editing the record, and the outcome depends on local law.

On a phone or desktop browser, cookies or similar storage may support sign-in continuity, security checks and saved privacy choices. Browser settings can remove or block them, but doing so may clear preferences or require you to complete account access again.

Yes. Send a retention question through the account support route and name the record involved, such as a QRIS reference, phone verification event or support message. We will explain the applicable category and any reason the record must remain available.