Reference

aon338 Privacy Policy for Clearer Account Control

Our aon338 Privacy Policy explains what account, wallet and device data we use when you open the lobby from Yogyakarta or elsewhere in Indonesia.

Account recordsWallet referencesDevice controlsCookie choices
aon338 aon338 Privacy Policy for Clearer Account Control
HELP WITH DATA

Get Privacy Help Near Your Account Path

If a Privacy Policy question affects your login or wallet status, use our account support route rather than sending sensitive data through an open message. Tell us the account phone number, the relevant date and the payment reference only through the available support channel. We use those details to locate the right record, while access depends on local law and identity checks may be required.

Team online

Account access

Ask us to check phone verification, sign-in history or a device record when your account path stalls. We may request an account detail before discussing any Privacy Policy matter.

Wallet status

For DANA, OVO, GoPay, QRIS or bank transfer questions, share the payment reference through account support. We can check the matching status without asking for your wallet password.

Receipt checks

If a cashier receipt does not match your account, send its reference through the support path. We compare the event with our records and explain what data was used for the check.

CONTROL YOUR RECORDS

What Our Privacy Process Covers

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Account data

We use contact and verification details to create, protect and locate your account. Before discussing a record, we may match the phone number or another account step to the request.

Cookies

Cookies can remember a sign-in state or help us understand whether a page works on your device. You can adjust browser controls, although some account functions may then need another sign-in.

Device signals

We may record browser type, operating system, approximate network details and sign-in time to detect unusual access. This helps us investigate account security without reading private files on your phone.

Payment matching

A wallet or bank reference is used to reconcile the requested transaction with your account. We do not ask for DANA, OVO, GoPay or QRIS passwords through support.

Retention period

We retain account, security and payment records for as long as needed for service checks, disputes or legal duties. After that, we remove or anonymise them where practical.

Change requests

To correct a phone number, ask about stored data or request deletion, contact account support with the relevant account step. We assess the request where local law permits.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear before an account is opened or checked. You can use them to understand wallet references, device records, cookies and contact steps without guessing which details belong in a support request. Where access or a request is discussed, it depends on local law.

It covers account, phone verification, device, cookie and payment-reference data connected with your use of aon338. It also explains retention, security checks, correction requests and how to contact us.

No. Our Privacy Policy concerns the transaction reference and status needed for account reconciliation. We do not ask for your DANA or OVO password through the aon338 support path.

Device type, browser, operating system, approximate network details and sign-in time help us identify unusual account access. The Privacy Policy does not give us access to private files on your device.

Contact account support with your registered phone number and the account step connected to your request. We may verify your identity before responding, and access depends on local law.

Yes. Send a correction request through the account support route and identify the affected account step. We check the request before changing records, where local law permits.

We keep DANA, OVO, GoPay, QRIS, bank transfer and virtual account references as long as needed for reconciliation, disputes, security checks or legal duties, then remove or anonymise them where practical.

Contact us through account support with the device and browser involved. You can also adjust browser cookie controls, though changing them may require another sign-in for account access.