Reference

aoncash Privacy Policy for Your Account

Our Privacy Policy explains how aoncash collects, uses and protects the details connected with your account, including phone verification, device access and wallet references.

Account dataWallet referencesDevice controlsPolicy requests
aoncash aoncash Privacy Policy for Your Account
REQUEST HELP

Ask About Your Privacy Policy Rights

A clear support path matters when your account details need correcting or you want to understand a wallet record. Contact us through the support route available after login and include the phone number linked to your account, the subject of your request and any relevant receipt reference. We use those details to locate the right record without asking you to send a wallet PIN.

Team online

Data access request

Ask us which account, device and transaction details are associated with your profile. We may first verify the phone number on the account before releasing personal data.

Correction request

If your phone, contact detail or wallet status is wrong, send the corrected value through account support. We will assess the request against account-security checks.

Privacy contact

For deletion, retention or cookie questions, use the same support route and state the specific Privacy Policy concern. Keep DANA, QRIS or bank references limited to what we need.

DATA PRACTICES

Explore How We Handle Your Details

The Privacy Policy follows the account journey rather than treating every detail alike. We separate contact and verification records from wallet references, use device signals to help protect login sessions and explain…

Account collection

We collect details you provide during account creation and phone verification, plus records created when you contact support. These details help us identify your account and respond to a specific request.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can identify a payment status or receipt. We use those references to match account activity, not to request private wallet credentials.

Device signals

Browser, device and session signals help us notice unusual account access and keep the login path safer. If you switch from mobile to desktop, each session can create a separate access record.

Cookie choices

Cookies can retain necessary session settings and help us understand whether an account page loads correctly. You can adjust cookie controls in your browser, although some account functions may then need another login.

Retention approach

We retain personal details only while they support account administration, support follow-up, dispute handling or legal duties. When a record is no longer needed for those purposes, we assess it for removal or restricted storage.

Security requests

You can ask who handles a Privacy Policy request, what data is involved and whether a correction or deletion is possible. We may verify account ownership before changing or disclosing personal details.

Browse Common Privacy Policy Questions

These Privacy Policy answers focus on the questions you may have before opening an account or contacting support. They cover the data connected with phone verification, wallet status, mobile access, cookies, retention and requests for changes. If your situation is not listed, send the support team the narrowest question you can, without sharing a wallet PIN.

It covers account details, phone verification, login and device records, cookie settings, wallet references, support messages, retention and requests to access, correct or delete personal data.

Yes. The Privacy Policy covers references showing DANA or QRIS status, as well as OVO, GoPay, bank transfer and virtual account records needed to match account activity.

Phone verification helps connect account access to the correct contact detail and supports security checks. We may use the verification record when you request data access or an account correction.

Yes. Use the support path after login and ask for a data access request. Include your linked phone number and a clear scope, so we can verify ownership and locate relevant records.

Send a correction request through account support, identify the detail that is wrong and provide the replacement value. We may check your phone verification before applying any account change.

We keep data while it is needed for account administration, support, disputes, security or legal duties. Retention can differ by record type, and you may ask support about a specific record.

Yes. It covers mobile browser sessions, device signals and cookies used when you access the account or lobby from a phone. Cookie controls remain available through your browser settings.