Reference

Privacy Policy For Your afa123 Account

afa123 Privacy Policy explains what we collect when you open an account, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice securityCookie choices
afa123 Privacy Policy For Your afa123 Account
CONTACT ROUTES

Ask About Privacy Policy Through Account Help

A clear contact route matters when an account detail or wallet record needs checking.

Account data request Use the account support path to ask what personal details are linked to your…
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, mention the payment…
Policy clarification If a Privacy Policy paragraph is unclear, contact us through the same support route…
DATA CONTROL

Six Practical Privacy Policy Safeguards

We keep this policy tied to actions you can recognise: opening an account, confirming a phone, checking a wallet status or returning to the lobby from a mobile…

Data we receive

We may receive your contact details, account preferences, phone-verification result, payment reference and technical session data.

Cookie operation

Cookies and similar browser storage can remember a session, preserve selected settings and help identify repeated security checks.

Account security

We use phone verification, session controls and device signals to reduce account misuse.

Payment separation

A payment reference is used to reconcile a cashier event, not to collect your wallet password.

Retention choices

We keep account, security and transaction records for as long as needed for the stated service, dispute handling and duties…

Change or correction

If your contact detail is wrong, request a correction through account support and identify the field that needs changing.

Privacy Policy Answers For afa123

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain the practical link between your account, device, payment reference and access request. If your situation is not covered, use the account support route with the smallest amount of personal detail needed to identify your request.

The afa123 Privacy Policy covers account details, phone verification, device and session data, cookie use, payment references and support requests. It explains why we handle each category, how it supports account security, and how you can ask for access, correction or a retention explanation.

We record the payment rail, reference and status needed to match a DANA or QRIS cashier event with the correct account. This helps us investigate a pending or mismatched record. We do not need your wallet password or one-time code to check that status.

Yes. Use the account support path and identify the field that needs correction, such as a phone or contact detail. We may verify account ownership before making a change because an edited detail can affect login checks, wallet matching and access from another device.

The Privacy Policy covers cookies and browser storage used for sessions, selected settings and security checks. You can adjust cookie controls in your browser. If you remove required storage, the next visit may ask you to sign in or complete phone verification again.

We retain payment and account records for the period needed for service operation, security checks, disputes and duties that apply where local law permits. The exact period can depend on the record category. Contact support with a reference if you need a category-specific explanation.

You can ask through account support for the personal data connected with your account. State whether you mean profile details, device records, cookie-related data or payment references. We may first confirm ownership, and the response remains subject to duties that apply where local law permits.

Yes. The Privacy Policy covers data created when you access the service from Indonesia, including mobile browser sessions and local wallet checks. Availability and eligibility depend on local law. If you are unsure about an access request, contact support before sharing additional personal or payment details.