Reference

Open Privacy Policy Before Account Access

aero666 Privacy Policy explains how we collect, use and protect the details connected to your account, device and wallet activity.

Clear data purposesWallet reference handlingAccount access choicesPolicy request path
aero666 Open Privacy Policy Before Account Access
REQUEST SUPPORT

Browse Your Privacy Contact Path

A clear contact path helps when your Privacy Policy request concerns a login record, wallet status or account detail.

Account request Use the account support route to ask how we hold your profile details, phone verification record or login history. We may ask you to confirm the contact detail already attached to the account before discussing private data or making a change.
Wallet record For a DANA, OVO, GoPay or QRIS question, add the payment date, amount reference and account contact detail visible in your receipt. We use those details to locate the status without asking for your wallet password or security code.
Access concern If a device or login record looks unfamiliar, tell us through the account support path and change your account password before sending more detail. We can explain the security review process and the policy choices available where local law permits.
DATA PRACTICE

Switch Through Your Privacy Choices

Our Privacy Policy is practical: it connects each data use to an account, security, payment or service purpose.

Data collection

We collect the details needed for an account path, including contact information, phone verification status and activity linked to your login. Device type, browser data and session timing can also support security checks when you open the lobby from mobile or desktop.

Cookie choices

Cookies can remember a session, language preference or security state on your device. You can manage available browser controls, although blocking necessary cookies may require a fresh login or prevent the account path from working as intended.

Account security

Phone verification is part of account access, and device or login signals may be checked when activity appears unusual. Keep your password and wallet credentials private; our support route does not need your DANA, OVO, GoPay or QRIS security code.

Retention period

We retain account, payment and security records only for the period needed for the stated service, fraud prevention, dispute handling or a legal requirement. When a record is no longer needed, our handling follows the deletion or disposal process available to us.

Access request

You can ask what personal data is connected to your account, request a correction or ask about deletion through the support path. Include the account contact detail and a precise request; we verify ownership before releasing or changing private records.

Policy changes

When our data handling changes, we revise this Privacy Policy and show the updated wording on the policy page. Check the page before using your account again, especially if the change concerns cookies, phone verification, payment references or device security.

Ask Before You Open An Account

These Privacy Policy answers cover the points most often raised before account access. We explain what happens to contact details, device records and payment references, plus how you can contact us about a correction or deletion. The same policy applies when you move between mobile and desktop, and it remains subject to local access conditions.

The aero666 Privacy Policy covers account details, phone verification, login and device records, cookie use, payment references and support requests. It explains why we use each category, how we protect access and how you can ask for access, correction or deletion where local law permits.

Yes. Privacy Policy coverage includes the payment reference, status and receipt details needed to connect DANA, OVO, GoPay or QRIS activity with your account. We do not ask for your wallet password or security code, and the payment provider remains responsible for its own data handling.

Phone verification helps connect the account to the contact detail you provide before access and supports account recovery or security checks. We may retain the verification status and related event record for the period needed to protect the account and meet a valid operational or legal requirement.

You can use the account support path to ask which personal data is connected to your account. State whether you want access, correction or another policy request, and include the account contact detail. We verify ownership first, then explain the response and any limits that depend on local law.

Send a deletion request through the account support route and identify the account with its attached contact detail. We assess the request against active account needs, payment disputes, security records and legal retention duties. We explain which records can be removed and which must remain where local law permits.

The same Privacy Policy applies when you sign in from a phone, tablet or desktop. Device type, browser session and login timing can differ between paths, so those technical records may appear separately in security checks. Cookie settings can also change how a session is remembered on your device.

Contact us through the account support path, change your account password and describe the device, time or location shown in the record. Do not send a wallet password or security code. We can review the account activity and explain the available Privacy Policy and security steps where local law permits.