Reference

Open the axa88 Privacy Policy

The axa88 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet recordsCookie choicesAccess depends on local law
axa88 Open the axa88 Privacy Policy
PRIVACY SUPPORT

Check Your Privacy Request Route

A clear contact route helps you ask about a privacy record without guessing which team to reach. We handle account, device and wallet questions through the support path connected to your axa88 account, and we may ask for verification before discussing personal details. This protects you when a request concerns phone access, a DANA receipt or a sign-in from a new device. If you are in Surabaya or elsewhere in Indonesia, include your account contact and the specific date or record so we can locate the matter accurately.

Team online

Account privacy

Ask our account support team to explain the personal details linked with your axa88 profile. We may confirm your phone verification first, then help you request a correction, access a copy, or clarify why a particular account field is needed for sign-in and service protection.

Wallet records

For a DANA, OVO, GoPay or QRIS record, send the payment reference, date and wallet name through the account support path. We use those details to locate the status without asking you to send a full wallet password, card secret or unrelated account material.

Access concerns

If a privacy page or account screen behaves differently on your phone, tell us the browser, device type and visible message. We can separate a technical access issue from a data request and explain the next step where local law permits.

DATA HANDLING

Browse the Controls Behind This Policy

We handle privacy through account controls and ordinary operational checks rather than vague promises.

Account details

We use details such as your account contact and phone verification status to create access, respond to support requests and protect the correct profile. We do not need your wallet password for a normal privacy question, and you should never place that secret in a support message.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may keep a reference, amount status and related account identifier. These records help us reconcile a cashier event and answer a receipt question without storing every detail held by the payment rail.

Cookies and browser data

Cookies may keep your session available, remember a selected page setting or help us diagnose a loading problem. Your browser provides controls to block or clear them, although removing necessary cookies can affect sign-in and may require you to verify your account again.

Device protection

A mobile browser can send device, browser and session signals when you open the lobby or account area. We use these signals for security checks and troubleshooting, especially when a new phone, changed browser or unusual access pattern needs a closer account check.

Retention choices

We keep personal records only for the period needed for account operation, security checks, payment reconciliation, dispute handling and legal duties. A deletion request may be limited where a record is still required for one of those purposes, and we can explain the reason through support.

Change requests

You can ask us to correct an inaccurate account detail, explain a processing purpose or provide a copy where the request is available under applicable rules. Include the account contact, requested action and supporting context; we may verify ownership before making a change.

Ask About axa88 Privacy Policy

These answers address the privacy questions we expect before an Indonesian customer opens an account. They cover the records created during phone verification, mobile access and wallet status checks, along with the practical route for correcting or requesting account data. Where a rule depends on location or eligibility, access depends on local law and services are available where local law permits.

The axa88 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use those records, how we protect account access, how long records may remain and how you can ask about correction or access.

Phone verification helps us connect an access request with the correct account and reduce mistaken or unauthorised account changes. We may use its status when you sign in from a new mobile browser or ask about wallet activity, while any service access depends on local law.

Yes. The Privacy Policy covers the account-linked reference and status we may receive for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. The relevant payment provider controls its own processing, so you should also check that provider's privacy terms.

We use device, browser and session signals to support sign-in, protect your account and investigate a page that fails on your phone. Cookies can keep a session or basic setting available. You can clear or block cookies in your browser, though account verification may then appear again.

You can contact account support to request an explanation, copy or correction where the request is available under applicable rules. State the account contact and the exact record you mean. We may verify ownership first, and retention duties can limit deletion or immediate removal.

We retain records for the period needed to operate an account, protect access, reconcile payment references, handle disputes and meet legal duties. When a record is no longer needed for those purposes, we remove or de-identify it according to our operational process.

Use the support route connected to your account and include your account contact, request type and relevant date or reference. For a wallet question, add the DANA, OVO, GoPay or QRIS status without sending a password. We respond through the available account support channel.