Reference

awan4d Privacy Policy For Your Account

awan4d Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesCookie controls
awan4d awan4d Privacy Policy For Your Account
REQUEST SUPPORT

Get Clear Help With Privacy Requests

A privacy question should not be mixed into a wallet-status issue, so we keep the request path clear. Start from your signed-in account area and use the support route shown there, including the account details needed to identify your request. When a DANA, OVO, GoPay or QRIS receipt is relevant, attach its reference rather than sending an entire wallet history.

Team online

Account access

Use the support path inside your account when you need a copy of personal data, a correction to your phone details, or help confirming which account record belongs to you.

Wallet reference

For a privacy question involving DANA, OVO, GoPay or QRIS, provide the transaction reference and date. We use those details to locate the relevant record without requesting unnecessary wallet content.

Request status

Keep the reply connected to the same support thread so we can verify the request, explain any identity check, and tell you when the requested account change or data response is ready.

DATA PRACTICES

Protect Account Data Across Mobile Devices

We handle privacy as an account process, not as a statement hidden away from your sign-in flow.

Collection purpose

We collect account, phone verification, device and payment-reference details for stated operational purposes. DANA and QRIS references help us match a status inquiry, while device data helps identify a sign-in session.

Cookie choices

Cookies can support sign-in continuity, page settings and security checks. Your browser controls can limit or remove them, although changing those settings may affect the way account access and policy preferences are remembered.

Mobile behaviour

When you move from a mobile browser into Live Casino, Rocket Crash or Bingo, we may process session and device details linked to that visit. We do not treat a phone model as permission to collect unrelated content.

Account security

Phone verification and sign-in checks help us distinguish an account request from an unverified attempt. Never place a password or one-time access code in a privacy message or wallet receipt.

Retention period

We retain records only for the period needed for the purpose described, account administration, dispute handling or legal duties. When a record is no longer needed, our process removes or securely restricts it.

Your changes

You can ask us to access, correct or clarify personal data through the account support route. We may ask for account verification before changing phone, wallet-reference or sign-in details.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account, device and payment questions you may have before opening an awan4d account. Each response points to a practical step, from checking cookie settings to sending a verified data request.

It covers account details, phone verification, device and browser data, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us confirm that an account request comes from the account holder. We use it for access checks and related support requests, not as permission to collect unrelated phone content.

Yes. The Privacy Policy applies when you use a mobile browser or desktop browser. Session, device and cookie details may differ by device, while your account choices remain connected to your sign-in.

We may retain payment references, selected rail and status details needed to match an account request. We do not need your full wallet history to investigate one DANA or QRIS reference.

Sign in, open the support route shown in your account area, and describe the data you want to access. We may verify your account before preparing or sending the response.

Yes. Send the correction through the account support path and identify the field concerned, such as a phone detail or account record. We may request verification before applying the change.

The Privacy Policy is available for your account questions, but access or eligibility depends on local law. Where local law permits, we process requests using the steps described on this page.