Reference

Open aifa66 Privacy Policy for Your Account

Your aifa66 Privacy Policy explains what happens to your account details, phone verification, device signals and wallet records before you open the lobby.

Clear data purposesWallet record contextRequest access pathIndonesia account use

Explore Our Lobby Read FAQ

Explore How We Handle Account Data

aifa66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the details needed to create and protect your account, such as your phone number, verification result, login events, device details and messages sent to support. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we keep transaction references and status

1
details so we can match a wallet action to your account without storing a wallet password. We use this data to provide account access, check unusual activity, answer requests and maintain required records. Cookies and similar browser storage help remember session choices and measure page function;
2
you can manage them through your browser settings, although some account steps may then need repeating. Our Privacy Policy applies to aifa66 services where local law permits, and any eligibility or access question depends on local law. We may update the policy when our data practices
3
change and will show the current version on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST SUPPORT

Browse Privacy Help From Your Account

A clear request path helps when you need a copy, correction or explanation of personal data connected with your account.

Access request Ask for the personal data connected with your aifa66 account through the account support path. Include your verified phone number so we can check identity before preparing a response.

Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date and status shown in your account. We can investigate the record without requesting your wallet PIN.

Correction request Tell us which account detail needs changing and why. We may ask for phone verification before updating the record, helping prevent another person from altering your profile.

DATA PRACTICES

Switch Through aifa66 Privacy Controls

Our privacy work follows the account actions you can actually take: create an account, verify a phone, sign in, use a wallet rail or ask for help.

Purpose-based collection

We request account, device and transaction details for defined needs such as access, security, payment matching and support. We do not need a wallet PIN to identify a DANA or QRIS reference.

Cookie choices

Browser cookies can keep a session active and remember selected settings. If you clear or block them on your phone, login or account steps may ask you to confirm choices again.

Account security

Phone verification helps us distinguish your account from an unauthorised access attempt. Keep your login details private and contact support if a device or session appears unfamiliar.

Payment separation

For DANA, OVO, GoPay, QRIS and bank transfers, we retain reference numbers and statuses needed for reconciliation. Wallet passwords and PINs remain outside the data we request.

Retention approach

We keep personal data only for the period needed for account service, security checks, support history or legal duties. When a record is no longer needed, we delete or anonymise it.

Change or deletion request

Send a request through the account support route with your verified phone number and the exact change you want. We explain any limit when another legal or security duty requires retention.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the account, device and wallet questions we expect from Indonesian customers before they proceed. If your situation is not listed, use the support path after login and describe the record or request clearly.

It covers personal data used for account creation, phone verification, login security, device sessions, wallet references, cookies, support requests, retention and requests to access or correct your records.

Phone verification helps confirm that an account change or access request comes from you. We use the result for account protection and do not ask for your DANA, OVO or GoPay PIN.

Yes. The Privacy Policy covers transaction references and status details connected with QRIS, bank transfer and virtual account steps. These records help us match activity without storing your external wallet credentials.

After login, open the support route shown near account help and request a copy of your data. Include your verified phone number, relevant dates and the specific record you want us to locate.

Yes. Send a correction request through account support, identify the inaccurate field and explain the requested change. We may repeat phone verification before changing details linked to your profile.

Cookies can remember your session and selected settings on a mobile browser. Blocking or clearing them may require another login or consent choice, while the Privacy Policy still explains how related data is handled.

We retain records for account service, security, support or legal duties, then delete or anonymise them when those needs end. If a duty requires longer retention, we explain that limit when relevant.

Open aifa66 Privacy Policy for Your Account

Browse Privacy Help From Your Account

Switch Through aifa66 Privacy Controls

Purpose-based collection

Cookie choices

Account security

Payment separation

Retention approach

Change or deletion request

Check Privacy Policy Answers Before Opening

01 What does the aifa66 Privacy Policy cover?

02 Why does aifa66 ask for phone verification?

03 Does the Privacy Policy cover QRIS and bank transfers?

04 How can I request my aifa66 account data?

05 Can I ask aifa66 to correct my personal data?

06 How do cookies affect Privacy Policy choices on mobile?

07 How long does aifa66 keep account and wallet records?

Related Pages