Reference

Open aksis66 Privacy Policy With Clarity

aksis66 Privacy Policy shows what account, device and payment details we collect, why we use them, and how you can request changes.

Account data explainedWallet details addressedYour request path
aksis66 Open aksis66 Privacy Policy With Clarity
REQUEST SUPPORT

Ask About Privacy Beside Your Account

Privacy questions should have a clear route, especially when a wallet status or sign-in record needs checking.

Account help Use the account help path when you want to ask about a stored phone…
Wallet status If a DANA, OVO, GoPay or QRIS record looks incorrect, send the payment reference…
Access concern When a device session or phone verification blocks account access, describe the device path…
DATA PRACTICE

Explore The Privacy Controls We Use

We handle privacy as part of the account flow, not as a separate promise. Phone verification helps connect access to the right account, while device signals help us…

Data collection

We collect details you submit for an account, including contact data and phone verification results.

Cookies

Cookies can keep your sign-in session active and remember basic page settings on your browser.

Account security

Phone verification is checked before account access, and we may compare device signals with recent sign-ins when activity appears unusual.

Payment records

A transfer reference from BCA, BRI, Mandiri or BNI, or a receipt connected to QRIS, may be kept to match…

Retention choices

We remove or anonymise personal details when the operational, security and legal reason for keeping them ends.

Change requests

To request a correction, deletion or copy of account data, contact us through account help and name the specific record.

Browse Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what happens during account access, how payment references are handled, and where to send a request. If your situation involves a particular device, wallet or sign-in, include that detail when you contact account support.

The aksis66 Privacy Policy covers account details, phone verification, device and connection signals, cookies, payment references and support requests. It also explains why we use each category, how long records may remain, and how you can request a correction or ask about a specific data use.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS. We use those details to reconcile a transaction, check its status or resolve an account question. We do not ask you to send a wallet PIN or full payment credential through support.

Phone verification helps us connect account access to the person who opened the account and helps protect against an unfamiliar sign-in. We may retain the verification result as an account security record. If your phone number changes, ask account support how to update the linked detail.

The Privacy Policy describes limited device and connection signals, such as details needed to keep a session working or identify unusual sign-in activity. These signals help us protect your account. You can ask account support which category relates to your concern without sharing a password.

Use the account help path and state whether you want a copy, correction or deletion request. Name the account detail or payment reference involved. We verify account ownership first, then explain what we can provide, change or remove under the Privacy Policy.

We keep personal data while it supports account operation, security, dispute handling or a legal need. When that reason ends, we remove or anonymise the record. A transaction reference from a bank transfer or QRIS may remain while reconciliation or a related question is open.

The Privacy Policy applies to the account and data handled for Indonesia access where local law permits. If access or eligibility is discussed, it depends on local law. For a location-specific question, tell account support your concern without sending sensitive wallet credentials.