Reference

Privacy Policy For Your a5pro Account

Our Privacy Policy explains how a5pro handles the account details you provide before access, including your phone verification, wallet status and payment records.

Account recordsWallet activityCookie choicesAccess requests
a5pro Privacy Policy For Your a5pro Account
DATA HELP ROUTES

Get Privacy Policy Help Near Your Account

A clear support route matters when you want to understand a record or change a detail held against your account.

Account access When phone verification or login records need checking, give us your account identifier and…
Wallet record For a DANA, OVO, GoPay or QRIS status question, mention the payment rail and…
Policy request Ask for a copy, correction or deletion assessment through the support route shown with…
DATA HANDLING PRACTICE

What Our Privacy Policy Covers In Practice

We keep the Privacy Policy connected to the steps you actually take: opening an account, confirming a phone number, signing in from a mobile device and checking a wallet record.

Account data

We may record the phone number and verification result linked to your account, along with sign-in events needed to keep access consistent. The Privacy Policy explains the purpose of each category and how you can ask us to correct an inaccurate detail.

Device signals

A mobile login can create device and session records, such as browser or device context and approximate event timing. We use these signals to investigate access requests and account security concerns, not to replace the account process or your own request.

Cookie choices

Cookies can support account sessions and remember selected settings while you move between pages. Our Privacy Policy explains their role and the choices available through your browser. Clearing cookies may require you to complete phone verification again at the next login.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event can leave a reference, amount status and timing record. We use those details to trace a receipt or stalled cashier step, while wallet credentials remain yours.

Retention period

We retain account, security and payment-related records for the periods described by the Privacy Policy and any applicable local requirement. A deletion request does not automatically remove every record when keeping a narrow audit trail is required.

Change requests

You can ask us to access, correct or assess removal of personal data through the support route. Include the account identifier and record type, and we will verify the request before changing account data or explaining why a limit applies.

Privacy Policy Answers For a5pro Accounts

These Privacy Policy answers focus on the questions you may have before opening an a5pro account or asking us to change an existing record. They cover the data connected with phone verification, mobile access and Indonesian wallet activity, plus the route for requesting access or correction. For any eligibility question, access depends on local law and only applies where local law permits.

The a5pro Privacy Policy covers account details, phone verification, login and device events, cookies, payment references, retention and requests to access or correct data. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may connect to your account.

Phone verification helps connect an access request to the correct account and lets our support desk investigate a login issue. We keep the verification result and related event details under the Privacy Policy, while access and eligibility depends on local law.

Yes. The Privacy Policy covers payment references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. These records can help us trace a receipt or status question, but we do not need your wallet PIN to investigate a payment event.

Use the support route connected with your account and state that you want a copy of your a5pro data. Include your account identifier and the record category, such as phone verification, device access or payment reference, so we can verify and locate the request.

You can ask for a correction through the support desk by naming the account detail that appears inaccurate. We will verify that you control the account, compare the requested change with the relevant record and explain the result under the Privacy Policy.

Cookies can maintain a mobile session and remember selected settings as you move through account pages. The Privacy Policy describes their purpose and your browser choices. If you clear them, the next login may ask you to complete phone verification again.

We assess deletion requests against the Privacy Policy and applicable local requirements. Some account, security or payment records may need to remain for a defined retention period. We will explain which record is affected, what action is possible and why a limit applies.