Reference

Privacy Policy For Your aqua4d Account

Our Privacy Policy explains how aqua4d handles the account details you provide before access, during wallet activity and when you contact support.

Clear data purposesWallet record contextAccount contact pathMobile access detail
aqua4d Privacy Policy For Your aqua4d Account
PRIVACY HELP PATH

Where To Ask About Your Data

A clear contact route helps when a Privacy Policy question concerns your account rather than the lobby.

Account help Use the account help path for questions about the Privacy Policy, phone verification, login…
Wallet records Ask about a DANA, OVO, GoPay or QRIS reference when a payment receipt or…
Access questions If a mobile browser or desktop session cannot reach account controls, contact us through…
DATA CONTROL POINTS

What We Do With Account Data

Privacy Policy choices affect more than a form: they explain the records behind account access, wallet matching and security checks.

Account details

We use the details you enter to create the account, connect your login with account controls and respond to a privacy request. A clear phone verification step helps us associate access with the correct account before we discuss or change personal details.

Cookie choices

Cookies can keep a mobile or desktop session working and remember choices made during account access. Our Privacy Policy treats these records as session or preference data, not as a reason to collect unrelated details. You can ask what cookie purpose applies to your session.

Wallet matching

Payment references help us match an account action with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use the reference to investigate status and receipt questions, rather than treating wallet details as general browsing data.

Account security

We use login events, device session details and phone verification signals to help protect account access. If a sign-in looks inconsistent with your normal path, we may ask for an account step before releasing details or handling a requested change.

Record retention

We keep account and transaction records for the period needed for operations, security or applicable legal duties. When you ask how long a particular record remains, identify the account event or wallet reference so our response addresses the correct data set.

Change requests

You can ask us to explain, correct or remove eligible account details through the privacy contact path. We first confirm account ownership, then assess the request against operational and legal needs. Access and eligibility depends on local law.

Privacy Policy Questions About aqua4d

These Privacy Policy answers focus on the account situations you are most likely to encounter: phone verification, wallet records, cookies, device sessions, retention and requests for access. They also explain what to include when you contact us, so the response can stay tied to the correct aqua4d account. Where a request concerns access or eligibility, the applicable position depends on local law.

The aqua4d Privacy Policy covers account details, phone verification, login and device session records, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It explains purposes, security handling, retention and available request paths.

Phone verification helps connect account access with the correct account and gives us a security checkpoint before we discuss personal details. It can also help separate a genuine account request from an unfamiliar mobile or desktop session under the Privacy Policy.

Yes. The Privacy Policy covers transaction references associated with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those references to match receipts or status questions with the relevant account event, not as general browsing data.

Use the privacy contact path from your account help area and include your account identifier, the type of record requested and an approximate event date. We may confirm ownership through the account step before explaining which data can be provided or changed.

Retention depends on the purpose of the record and any operational, security or legal duty that applies. Account, session and wallet references may therefore have different periods. Ask about a specific login, phone check or payment reference for a useful Privacy Policy response.

You can ask us to correct eligible account details through the privacy contact route. Include the field that appears wrong and the replacement detail, then complete any ownership check we request. Changes remain subject to account security needs and local legal requirements.

It does. The Privacy Policy covers cookies and session details used when you access the account through a mobile browser or desktop browser. These records can support login continuity and preferences; you can ask which cookie purpose applies to your device path.