Reference

ave189 Privacy Policy Explained Clearly

The ave189 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Browse Our Lobby Read FAQ
ave189 ave189 Privacy Policy Explained Clearly
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A clear contact route helps when a Privacy Policy question concerns your own account rather than a general page.

Account access request Use the account help route when you need to ask which personal details are connected to your ave189 account. We may ask you to complete phone verification before discussing account-specific data, helping us avoid sending private details to the wrong person.
Wallet record question For a Privacy Policy question about DANA, OVO, GoPay or QRIS records, share the payment reference rather than a wallet password. We use the reference to trace the receipt or status check while keeping sensitive wallet credentials out of the support conversation.
Correction request If your contact detail or account record needs correction, tell us what appears wrong and what should replace it. We may request a matching account step before changing data, then use the same support path to confirm that the request has been handled.
DATA HANDLING

How We Apply This Privacy Policy

We apply this Privacy Policy to the account actions you take, not to unrelated subjects.

Account details

We use the details you enter during account creation to establish your account path and support phone verification before access. Keeping those details accurate helps us match a support request to the right account without asking you to repeat unrelated private material.

Payment references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount status and timing record. Bank transfer and virtual account activity may also require a matching reference. We use these details to check the requested payment state, not to request your wallet password.

Cookies and devices

Cookies can remember a session choice and help keep the account path working when you move from the mobile login to the lobby. Device and browser signals may support security checks. You can manage cookies through your browser, although some account functions may then need another sign-in.

Account security

We use sign-in records, phone verification and related technical signals to identify unusual access and protect account details. If a security check interrupts access, contact support through the account route. Never place a verification code, wallet password or full payment credential in a message.

Retention choices

We retain account, support and payment references for as long as needed for the purpose described in this Privacy Policy, account security and applicable legal duties. When a record is no longer needed, we remove it or handle it in a form that no longer identifies your account where appropriate.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion where available, or question a particular use. Send the request through account support with your registered contact detail. We may verify your identity before sharing or changing any account-linked record.

Privacy Policy Questions About ave189

These Privacy Policy answers address the account and wallet questions we expect from Indonesian customers before they open an account. Each answer stays focused on personal data, access, cookies, payment references and contact steps. If your situation is not covered, use the account help route and describe the specific record or action you want us to check.

The ave189 Privacy Policy covers details you submit during account creation, phone verification records, sign-in activity, support messages and technical data needed to operate account access. We use these details for the stated account, support and security purposes, with availability depending on local law.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account references. We use those records to check a receipt or payment state, and we do not ask for your wallet password.

We use phone verification before account access to help match the person requesting access with the account record. A verification event can be retained as a security record. If you cannot complete the step, contact account support without sharing the code in your message.

You can contact us through the account help route to ask what personal data is linked to your account or to request a correction. Explain the record involved and provide your registered contact detail. We may verify your identity before releasing or changing information.

Cookies can keep a requested session active when you move from mobile login to the lobby and may remember selected settings. Your browser controls cookie removal and blocking. If you block required cookies, you may need to sign in again or lose part of the account path.

We keep account, support, security and payment-reference records for as long as their stated purpose requires, including account protection and applicable legal duties. When retention is no longer needed, we remove the record or use a form that no longer identifies your account where appropriate.

Use the account support route and describe the concern, such as a correction, access request, cookie question or DANA receipt reference. Do not send passwords or verification codes. We may ask for matching account details before discussing private information or changing a record.

Related Pages

ave189 Indonesia Access guide Live In-Play Football About Us FAQ