Reference

Privacy Policy for Your aws66 Account

Our Privacy Policy shows how aws66 handles the details connected with your account, phone verification, wallet activity and browser visit.

Account dataWallet recordsCookie choicesContact rights
aws66 Privacy Policy for Your aws66 Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path matters when you want to know what we hold or why a record appears. Use the support route connected with your account, include the email or phone detail used during registration, and describe the request in plain English. If access is being checked where local law permits, we may ask for account details before discussing private records.

Team online

Account help

Open FAQ Account Help from your account area when your request concerns phone verification, a sign-in record or a correction to your personal details. Adding the registered phone number helps us locate the correct account without asking you to send wallet credentials.

Wallet questions

For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate date through the cashier support path. We use those details to trace status without requesting your wallet password, full PIN or other secret access code.

Privacy request

Ask us to access, correct or remove eligible personal data through the available support contact. State the action you want and the account email or phone number. We may verify ownership first, then explain the next step and any lawful reason a record must remain.

DATA CONTROLS

Six Data Handling Checks We Apply

We treat this policy as an operating process, not a page kept apart from account activity. Our checks connect registration, wallet references, browser behaviour and support requests so we can explain what…

Account records

When you open an account, we may keep your submitted contact details, registration time and phone verification result. These records help us distinguish your account from another account and respond when you ask for access, correction or account closure under the Privacy Policy.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be linked with an account record so a payment question reaches the correct case. Bank transfer and virtual account references may serve the same purpose. We do not need your wallet password to match a receipt.

Cookie choices

Our browser pages may use cookies or similar storage for session continuity, security checks and remembered preferences. You can manage browser storage through Android or iOS settings. Removing cookies can sign you out or reset choices, but it does not erase account records by itself.

Account security

We use phone verification, session controls and checks around unusual account activity to reduce unauthorised access. Never send us a password, wallet PIN or one-time code. If a sign-in concern involves Live Blackjack Diamond, tell support the account detail and approximate time.

Retention periods

We keep personal data only for the period needed for the purpose described, account administration, dispute handling, security, or a legal requirement. Retention can differ by record type, such as a support message, phone verification event or QRIS transaction reference.

Change requests

You can ask us to correct inaccurate details, explain a data use, provide eligible account data or remove data that no longer needs to remain. Send the request through account support with your registered contact detail; we verify ownership before making a change.

Privacy Policy Questions About aws66

These answers address the questions we expect you to ask before opening an account or checking a wallet record. They cover the Privacy Policy, browser access, payment references, account requests and local eligibility. If your situation is different, use the support route and include enough detail for us to find the relevant record.

The aws66 Privacy Policy covers account registration, phone verification, browser cookies, device and session details, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security checks and the choices available to you.

We use the phone verification result to connect account access with the contact detail you provided and to help detect unusual sign-in activity. If you ask about a record or request a change, the registered phone detail may help us confirm that the account is yours.

Yes. The Privacy Policy includes payment references needed to match DANA, OVO, GoPay or QRIS activity with the correct account. It can also cover bank transfer and virtual account references. We ask for a receipt or reference when tracing a status, not your wallet PIN.

Send a request through the account support route and state whether you want access, correction or removal of eligible data. Include your registered email or phone number and a clear description. We may verify ownership before responding, and some records may need to remain for legal reasons.

Cookies or similar browser storage can keep a session active, support security checks and remember selected settings. You can manage them through Android or iOS browser controls. Clearing them may sign you out or remove preferences, but it does not automatically delete your account data.

The retention period depends on the data type and its purpose. A phone verification event, support message, payment reference and security record may follow different periods. We keep records only as needed for account administration, dispute handling, security or a legal requirement, then remove or restrict them where appropriate.

You can read this Privacy Policy and send a data request from an Indonesian browser, including on Android or iOS. Account access or eligibility depends on local law. For a request involving your account, use the registered contact detail so we can complete the required ownership check.