Reference

aba99 Privacy Policy Explained Clearly

Our Privacy Policy shows how aba99 handles the details you provide when opening an account, checking a wallet status or entering the lobby from your phone.

Account clarityWallet record careCookie choicesLocal-law access
aba99 aba99 Privacy Policy Explained Clearly
CONTACT PATHS

Get Help With Privacy Requests

A clear contact route helps you act on this Privacy Policy without searching through the lobby. Use the support path shown inside your account when you need to ask about stored details, a wallet record, a login event or a correction. Include the email or phone detail connected with your account and a short description of the request. We may ask for an account step to confirm that the request belongs to you before sharing or changing information.

Team online

Account request

Send a Privacy Policy question through the account support path and identify the email or phone detail attached to your profile. We use that context to locate the right record and avoid discussing account data with an unverified contact.

Wallet records

If your request concerns DANA, OVO, GoPay or QRIS, include the transaction reference and date shown in your cashier history. We can then separate a payment-status question from a request to correct personal account details.

Access concern

When a login or device event looks unfamiliar, contact us through the same support route before changing account details. We may ask you to complete phone verification so we can protect the account while checking the event.

DATA PRACTICES

How We Handle Your Account Details

Privacy is part of the account flow, from phone verification through a return to the mobile lobby.

Account details

We may store contact details, verification status and account events needed to let you sign in and investigate access problems. We use the information you submit for the account purpose described in this Privacy Policy, including a phone check before protected changes.

Device signals

A phone, tablet or desktop can send device type, browser information and session events when you access the lobby. These signals help us identify unusual sign-in activity and keep a mobile path from login to account pages working as intended.

Cookie settings

Cookies can remember session choices and help pages load with the account state you selected. You can adjust cookie controls in your browser, although switching them off may affect sign-in continuity or parts of the Privacy Policy page.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, amount status and time needed to match your account request. We do not need unrelated wallet content to check a transaction record.

Retention period

We keep account, security and transaction records only for the period needed for the stated service purpose, dispute handling or a legal requirement. When a record is no longer needed, our process is to remove it or separate it from direct account identification.

Change requests

Ask us to access, correct or delete eligible details through the account support path. Include the record you mean, such as a phone number or QRIS reference; we may verify your identity first, and the result depends on local law.

Privacy Policy Questions About aba99

These Privacy Policy answers focus on the account actions you are most likely to take before opening the lobby. They cover device access, local wallets, cookies, correction requests and account closure. If your situation is not listed, send the details through the support path shown in your account so we can identify the relevant record without asking you to post private information publicly.

The aba99 Privacy Policy covers details you submit for an account, such as contact information and phone verification, plus login, device and support events. We use them for account access, security and the stated service purposes, with any restriction depending on local law.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including a transaction status, time and reference used to check your account request. We may also handle matching details for bank transfer or a virtual account.

You can request a correction through the support path inside your account. Tell us which detail is wrong, such as your phone number or contact address, and complete any identity check we request. We handle the outcome according to the Privacy Policy and local law.

When you sign in from a phone, tablet or desktop, we may record device type, browser information and session events. The Privacy Policy allows these signals to help identify unusual access and investigate login problems; they are not a request for unrelated content from your device.

You can manage cookies through your browser controls and ask our account support path about their purpose. Cookies may preserve a session or selected setting. If you block them, sign-in continuity or parts of the aba99 account flow may not work as expected.

We retain account, security and transaction records for the period needed for the stated purpose, dispute handling or a legal requirement. The exact handling can depend on local law. You may ask which record applies to your request through verified account support.

You may ask for deletion of eligible account details through the support route shown after sign-in. Include the record you want removed and complete verification. Some records may need to remain for security, disputes or legal reasons, so the result depends on local law.