Reference

Privacy Policy For Your awan4d Account

Our Privacy Policy explains what awan4d collects, why we use it, and how you can ask about your account records before opening access.

Clear data purposesWallet record contextAccount access choicesCookie controls
awan4d Privacy Policy For Your awan4d Account
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A direct privacy request gives you a clearer next step when a record looks unfamiliar or your account access needs checking.

Account contact route Use the support contact shown after account access to ask what personal details we…
Payment privacy check If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference needs clarification…
Access request Ask us to locate, correct or explain a privacy record through the same account…
DATA CONTROL POINTS

What We Do With Your Account Data

Privacy is handled through practical account steps rather than broad promises. We separate access checks from payment references, limit internal visibility where possible, and use device signals to…

Account details

We use the details you enter for account creation and phone verification to identify your account, respond to privacy requests…

Payment references

A wallet or bank reference can show that a transaction belongs to the right account and status.

Cookies and devices

Cookies and device signals help preserve your session and remember security checks between pages.

Account security

We use phone verification and session details to reduce unauthorised access.

Record retention

We keep account, payment and support records only for the period needed for service operation, security checks, dispute handling or…

Change requests

You can ask us to correct an inaccurate detail, explain a stored record or clarify its use through the account…

Privacy Policy Answers For awan4d

These Privacy Policy answers cover the searches we expect when you are deciding whether to open an account or ask about an existing record. Each answer points back to a practical step, from phone verification to a payment reference or browser setting. Where a request depends on legal requirements, we will explain that position through the account contact route.

The Privacy Policy covers account details, phone verification, device and cookie data, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security steps and ways to request clarification or correction.

We use your phone number to create and verify the account, help protect access and match a privacy request to the correct record. If you contact us about account data, we may ask for a verification step before discussing details linked to that number.

Yes. The Privacy Policy covers payment references used to check a DANA or QRIS status, as well as OVO, GoPay, bank transfer and virtual account records. Send only the relevant reference through the account contact route, never a password or full wallet credential.

We may use device, browser, connection and session signals to keep account access secure and detect an unusual sign-in. A phone-to-desktop change can trigger another check. These signals support security and service operation rather than replacing the account details you provide.

You can request a correction through the support contact shown in your account. Tell us which detail is inaccurate and provide only what we need to locate it. We may confirm your registered phone before changing a record, and the available action depends on local law.

We retain account, payment and support records for as long as they are needed for access, security, dispute handling or legal duties. After that need ends, a record may be removed or restricted under our retention process. Ask through support for a record-specific explanation.

Use the support contact route available after account access and state that your request concerns the Privacy Policy. You can ask about collection, cookies, payment references, retention or correction. For wallet matters, include the payment reference only through the cashier support path.