Reference

asi200 Privacy Policy For Your Account

asi200 Privacy Policy explains how we collect, use, protect and retain details linked to your account, including phone verification, device access and wallet records for DANA, OVO, GoPay…

Clear data purposesWallet record contextCookie choicesAccess depends on local law
asi200 asi200 Privacy Policy For Your Account
HELP WITH REQUESTS

Get Policy Help Beside Account Support

A clear contact route helps when you cannot tell whether a question concerns account access, a wallet record or the Privacy Policy itself.

Data request Ask us to explain, correct or provide the personal details connected with your account.
Privacy question If a cookie, device signal or account record is unclear, contact our support path…
Wallet record check For a payment record question, send the transaction reference and name the rail used…
HOW DATA IS HANDLED

Practical Privacy Controls Inside asi200

Privacy choices work best when each data use has a clear reason and an identifiable account path.

Data collection

We collect details needed for account creation, phone verification, login protection and payment status checks. A DANA or QRIS reference can help us match a transaction, while your wallet PIN remains with the wallet provider and should never be sent to our support team.

Cookie choices

Cookies and similar device storage can remember a session, protect the sign-in path and help us understand whether a page loads correctly on your phone or desktop. You can review browser controls and contact us if a cookie purpose in the Privacy Policy needs clarification.

Account security

Phone verification is used before account access, and login or device signals may be checked when activity looks unusual. Keep your verification code private, sign out on shared devices and contact us promptly if your account opens from a device you do not recognise.

Retention periods

We retain account, support and transaction records only for the period needed for the stated purpose, account administration, dispute handling or a legal requirement that applies to us. When a retention reason ends, the record is deleted or separated from direct account identifiers.

Limited sharing

We may share necessary details with service providers that help operate account access, security or payment status checks. A bank transfer reference, BCA, BRI, Mandiri or BNI detail is used for the relevant transaction purpose, not as a reason to request unrelated profile data.

Changes and access

You can ask for a copy, correction or removal of personal details where local law permits. Send the request through the account support path with your registered contact detail; we may verify ownership before making a change so another person cannot alter your record.

Privacy Policy Answers For asi200

These questions address the points Indonesian account holders commonly check before sharing details or completing phone verification. Each answer relates to our Privacy Policy and gives you a practical next step, whether you are checking cookies on a mobile browser, tracing a QRIS record or asking how to update an account detail. Access and eligibility depend on local law.

It explains the personal data we collect for account access, phone verification, security, support and payment status checks. It also covers cookies, device signals, retention, limited service-provider sharing and the process for requesting a copy, correction or removal of details where local law permits.

We use your phone number to create and identify your account and to complete phone verification before access. It also helps us locate a support request. Keep verification codes private, and contact us if the number on your account is no longer yours.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a payment question to your account, while wallet passwords and PINs should remain with the payment provider.

Use the account support path and state that you are making a data request. Add your registered phone number or email and describe whether you want access, correction or removal. We may verify account ownership before responding, and timing depends on the applicable local law.

Cookies or similar storage may keep a session active, support sign-in protection and help us identify loading problems on a phone or desktop browser. You can manage browser settings, but some account functions may not work as expected when required session cookies are blocked.

We keep those records for the time needed to operate the account, answer a dispute, maintain security or meet a legal requirement. The period can differ by record type. Once the purpose ends, we delete the data or remove direct links to your account.

You can ask us to correct account details through support, including a phone number or contact detail. Provide the registered account information and explain the change. We check ownership first, then update the record where local law permits and the request can be verified.