Reference

Open aqua66 Privacy Policy Before Account Access

aqua66 Privacy Policy explains how we handle your account details, wallet records and device access when you use the lobby from Indonesia.

Data use explainedWallet records coveredPhone verification noted
aqua66 Open aqua66 Privacy Policy Before Account Access
CONTACT ROUTES

Reach Support About Privacy Questions

A clear contact route helps when you want to ask about the Privacy Policy, account records or a wallet reference.

Account privacy request Use the support contact shown after account access and state whether you need a copy, correction or deletion request under the Privacy Policy. Include your registered phone number only through the secure account route.
Wallet record question For an OVO, GoPay or QRIS reference, share the transaction date and visible status without sending your wallet PIN. We use those details to locate the record and explain how it is handled.
Device access help If the policy page or account screen behaves differently on mobile, tell us your device path and browser. We can help you reach the correct privacy contact route without asking for secret credentials.
DATA PRACTICES

Protect Your Account Data Step By Step

Privacy depends on practical handling, not a broad promise. We limit account details to the work needed for access, payment matching, security and support, while cookies and similar device signals help keep…

Account details

We use the phone number and other details you submit to create, verify and maintain your account. Phone verification helps us distinguish an account holder from an unknown sign-in attempt before access is granted.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match account actions with payment status. We retain the useful reference rather than treating wallet credentials as ordinary profile content.

Cookies and devices

Cookies and device signals can keep your session connected while you move from login to the lobby on mobile or desktop. You can manage browser cookie settings, although changing them may affect page access.

Security checks

We may review sign-in patterns, verification events and account changes to identify unusual access. Never share your password, wallet PIN or one-time code in a support message or privacy request.

Retention choices

We keep records for the period needed for account operation, security, transaction questions and applicable legal duties. When a retention reason ends, handling follows the deletion or restriction process available under the Privacy Policy.

Your requests

You can ask what personal data we hold, request a correction, question its use or ask about deletion where applicable. Send the request through the account support route so we can verify ownership safely.

Ask About aqua66 Privacy Policy

These Privacy Policy answers address the questions you may have before opening an account or using a wallet-linked session. We keep the wording practical: what we collect, why we retain it, how you can request a change and what happens when access depends on local law. If your question is not listed, use the support route without sharing secret login or wallet credentials.

The aqua66 Privacy Policy covers account details, phone verification, sign-in and device signals, support conversations, cookies, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It explains why we use each category and how you can ask about your records.

Phone verification helps connect an account to the person attempting access and gives us a security event to check when sign-in details change. We use the verification result for account protection and access control, while eligibility still depends on local law.

Yes. The policy includes the reference, status and account link associated with QRIS, DANA, OVO, GoPay, bank transfer or virtual account activity. We use these details to investigate payment questions without requesting your wallet PIN or one-time code.

Contact us through the support route available after account access and identify the request as a Privacy Policy matter. You may ask for a copy, correction or clarification. We may verify account ownership before responding, so do not send passwords or wallet credentials.

Cookies and device signals can preserve a session as you move from login to the lobby on a mobile browser. Your browser settings can restrict cookies, but the change may affect access or require another sign-in. The policy explains their account and security purpose.

We retain account, security and payment references while they support account operation, transaction questions, security checks or applicable legal duties. The retention period can differ by record type. When a reason ends, you can ask support how the relevant record is handled.

Use the account support route for a Privacy Policy question and mention your Indonesian access context, device path or payment reference when relevant. We can explain the next step without asking for secret credentials. Account availability depends on local law and supported access conditions.