Reference

Privacy Policy For Your ayu89 Account

ayu89 Privacy Policy explains what we collect when you open an account, sign in from a phone, or check wallet status through DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsDevice choicesCookie controls
Explore Our Lobby Read FAQ
ayu89 Privacy Policy For Your ayu89 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A clear contact path matters when a Privacy Policy question affects your account or wallet record.

Account data request Ask us to explain the personal data connected with your ayu89 account. Include your registered phone detail and the request you want handled, such as access, correction or removal. We may first verify account ownership before discussing records tied to your profile.
Wallet record question For a DANA, OVO, GoPay or QRIS query, send the payment reference and approximate date through the account support route. We check the wallet status against your account record, then explain what we can change, retain or share for operational purposes.
Sign-in privacy concern If a phone or browser still shows an old session, tell us the device type and last sign-in you recognise. We can help check account access and explain the related security record. Do not send a password, wallet PIN or one-time verification code.
DATA HANDLING DETAILS

What ayu89 Keeps And Why

We separate the data needed to run your account from optional device preferences. Account records help us complete phone verification and protect sign-in; payment references help us reconcile a DANA, OVO, GoPay…

Account details

We use your account details to create access, complete phone verification and connect activity with the correct profile. The same account reference helps us answer a data request without exposing another person's records. We do not need your wallet password to identify a payment entry.

Payment references

A wallet or bank record can include a reference, amount status and time needed for reconciliation. For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, BNI or a virtual account, we use the reference to check whether the account entry matches the payment event.

Device and sign-in

When you move from a phone to a desktop browser, device and sign-in signals help us identify unusual account access. These signals can include session timing and browser details. They support account protection and are not a reason for us to request your private device password.

Cookies and choices

Cookies can keep a selected language, session state or page preference available while you move through the account area. Your browser settings can restrict cookies, although some account functions may then require another sign-in. Our Privacy Policy explains why each cookie category is used.

Retention and removal

We retain records for the period needed to operate access, resolve payment questions, protect the account and meet duties that apply to the service. You can ask whether a record remains and request removal where allowed. Some transaction or security records may need to stay for a defined purpose.

Policy change requests

If a name, phone detail or other account field is wrong, use the account support route and describe the correction clearly. We may ask for an ownership check before changing it. Questions about this Privacy Policy can follow the same path, including requests about how a record is used.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account, payment and device questions you may have before opening access. We keep the route practical: check the relevant record, use the account support path and provide only the details needed for us to verify your request. Payment names below refer to the local rails available in the Indonesia setup.

The ayu89 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, payment references and support requests. It explains why we use each category, how retention works and how you can ask about access or correction. Eligibility and access depend on local law.

We use transaction references and status details to match a payment with your account; we do not need your wallet password or PIN for that check. If a receipt is unclear, send the reference through account support. Never include a password or one-time verification code in your request.

Use the account support route and ask for an account data request. Include the phone detail linked to your profile and describe the records you want, such as sign-in or payment references. We may verify ownership first, then explain what can be provided under the Privacy Policy.

Yes. Send the incorrect field and the replacement detail through account support, using the phone or email connected with your account. We may request an ownership check before making the change. For a bank transfer or QRIS record, include the reference so we correct the right entry.

Cookies may remember a session, selected setting or page preference when you use a phone browser. Your browser controls can restrict them, but account access may then ask you to sign in again. The Privacy Policy explains the cookie purpose and the effect of changing your browser choice.

We keep payment and security records only for the period needed to operate account access, reconcile DANA, OVO, GoPay, QRIS or bank entries, resolve questions and meet applicable duties. You can ask whether a record remains. Some records cannot be removed immediately when a lawful retention purpose still applies.

Use the account support route and state that your request concerns the Privacy Policy. Add your registered phone detail, the relevant device or payment reference and the action you seek. We will explain the next ownership check or correction step without asking for your password or wallet PIN.

Related Pages

ayu89 Indonesia Adu Q Table VIP Baccarat Circle About Us Account information