Reference

Privacy Policy for Your ayoo788 Account

We keep your account, wallet and device data tied to clear uses: login checks, payment records, fraud prevention and service messages.

Account dataDANA recordsOVO recordsGoPay checksQRIS logs
ayoo788 Privacy Policy for Your ayoo788 Account
CONTACT ROUTES

Three Ways to Ask Privacy Questions

Privacy requests should reach the right team without slowing your account flow. Use live chat for urgent login or wallet-data concerns, email for written data requests, and the account message centre when you are already signed in. We check identity before changing stored details.

Team online

Live chat

Our chat team is available 10:00-24:00 WIB for privacy questions linked to login alerts, unusual device prompts or wallet status. We may ask you to confirm your phone number before discussing account data.

Email request

Send privacy requests from the email connected to your account when you need a written copy, correction or deletion check. Include your username only, not your DANA, OVO, GoPay or QRIS app PIN.

Account message

When you are signed in, use the message centre for privacy questions about cookies, device history or payment references. This path helps us match your request to the correct profile before action is taken.

DATA CONTROLS

Six Controls Behind This Policy

We write this policy around the way your account actually works: login, wallet, game access and service contact.

Account setup

We collect the phone number, username and password you enter when you open an account. These details let us protect access, send account notices and confirm you are the person asking for changes.

Wallet records

For DANA, OVO, GoPay and QRIS, we keep payment status, reference codes and timing. This helps us trace a missing deposit or withdrawal request without storing your payment app password or PIN.

Device checks

Mobile browser, Android version, IP region and cookie signals help us spot unusual access. If your device changes suddenly, we may ask for another confirmation before showing wallet or profile data.

Cookie use

Cookies keep your session active, remember basic preferences and measure page errors. You can clear them in your browser settings, but doing so may require a fresh login on your next visit.

Retention period

We keep records only as long as needed for account service, dispute checks, security logs and legal duties. When data is no longer needed, we remove it or separate it from your profile.

Change requests

You can ask us to correct account data, check stored records or review retention. We verify the request first, then reply through the channel connected to your account for safety.

Privacy Questions Before You Join

These answers focus on the privacy choices you may check before opening an account or adding a wallet method. They cover data collection, payment records, cookies, account changes and how to reach us when your request needs a human reply.

We collect the details you enter, such as username, phone number, password and contact channel. We also record login time, device signals and account actions so we can secure access and answer your requests.

No. We store transaction references, status updates and timing needed to match wallet activity to your account. Your payment app PIN stays inside your own payment app and should never be shared with us.

Cookies help keep your session active, remember basic account preferences and detect page errors. You can clear them in your browser settings, but you may need to log in again after clearing them.

Yes. Contact us through live chat, email or the account message centre and tell us what needs correction. We verify your identity before changing phone numbers, email records or other profile details.

A new phone may trigger device checks, cookie refresh and extra confirmation before wallet details appear. This protects your profile if someone tries to access your account from a device we do not recognise.

Only the team handling account service, security or compliance tasks can view request details. We limit access by role, record actions where needed and reply through your connected account channel.

Yes. Access and eligibility depend on local law and are available only where local law permits. If a location check affects your account, contact us so we can explain what data was used.