Reference

audy88 Privacy Policy for Your Account

Our Privacy Policy explains how audy88 handles the details connected with your account, from phone verification before access to wallet status linked with DANA, OVO, GoPay and QRIS.

Account dataPhone verificationWallet recordsCookie choices
audy88 audy88 Privacy Policy for Your Account
HELP ROUTES

Where Privacy Policy Requests Are Handled

A clear contact path matters when a data request meets an account or wallet issue.

Account access If your phone verification does not open the account, use the account-help route beside…
Wallet status For DANA, OVO, GoPay or QRIS records, send the payment reference and the affected…
Data request To ask for a copy, correction or removal assessment, state the exact data category…
SIX CONTROL POINTS

Six Controls Behind Our Privacy Policy

We apply the Privacy Policy through practical controls rather than a single notice at the bottom of a page.

Phone verification

Before account access, we use the phone verification step to reduce mistaken identity and help connect a request with the…

Mobile sessions

When you use the mobile browser, we may record a session token, browser type and security events needed to keep…

Cookie choices

Cookies and similar browser storage help remember session settings and policy choices.

Wallet matching

A DANA, OVO, GoPay or QRIS receipt is used to match a wallet event with the account and status being…

Retention periods

We retain each category only while it supports the stated account, security, payment or legal purpose.

Change requests

You can ask us to correct account data, provide a copy or assess removal through the support route.

Privacy Policy Answers for audy88 Accounts

These Privacy Policy answers address the practical searches we expect from someone deciding whether to open an audy88 account in Indonesia. They cover the data collected at phone verification, wallet receipts, cookies, mobile access, retention and requests for changes. If your case involves a specific receipt or session, include that reference when contacting us.

It covers account details, phone verification, browser and device session records, cookie choices, wallet references and support requests. It also explains why we use each category, how long it may remain and how you can ask for access, correction or a removal assessment.

Phone verification helps connect account access and data requests with the correct account holder. It can also reduce mistaken access when you switch from a mobile browser to desktop. We use the check for account security and do not treat it as permission to collect unrelated details.

Yes. The policy covers payment references used to match a DANA, OVO, GoPay or QRIS event with your account and its status. Bank transfer and virtual account references are handled for the same stated purpose when a receipt needs checking.

On mobile, cookies or similar browser storage can retain a session setting and your policy choice. You can manage them through the browser or device settings. Clearing necessary storage may end the session and require a fresh login or phone verification.

You can ask for a copy or correction by using the account-help route and naming the data category concerned. We confirm that the request relates to your account before responding. If a record must remain for an operational or legal reason, we explain that reason.

Retention depends on the purpose and any applicable legal duty. Account, security and wallet records remain only for the period needed to operate, check or resolve the stated matter. After that period, we remove, anonymise or isolate the record from routine access.

Yes. Account access and eligibility depend on local law, and our Privacy Policy is applied where local law permits. If a local rule affects a request or account path, contact support with your account identifier so we can explain the relevant handling step.