Reference

fw66 Privacy Policy for Indonesia Accounts

fw66 Privacy Policy explains how we handle the details you provide when opening an account, checking DANA or QRIS status, and entering the lobby where local law permits.

Account dataWallet recordsCookie choicesPolicy access
fw66 fw66 Privacy Policy for Indonesia Accounts
CONTACT PATHS

Privacy Help Beside Your Account

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

Policy request Ask about the Privacy Policy from your signed-in account path.
Wallet question For DANA, OVO, GoPay or QRIS questions, include the receipt reference and payment date.
Access concern If a login or verification step stalls, contact support through the account area and…
HANDLING PRACTICES

How fw66 Handles Personal Data

We treat privacy as an account operation rather than a footer link. The records connected to login, wallet status and support are handled for specific service and security purposes, with access shaped…

Data use

We use contact, verification and sign-in records to create your account, confirm account actions and respond to support requests. We do not ask you to place passwords or one-time codes inside a privacy request.

Cookie controls

Cookies and similar device markers can remember session preferences, protect login continuity and help identify unusual access. You can adjust browser cookie settings, although some account functions may then require another sign-in.

Account security

Before discussing private records, we may compare your signed-in account contact with the request. A verification prompt can appear when a new device or unfamiliar login pattern needs checking.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile a cashier event. We retain the reference needed for checking status, rather than requesting your wallet credentials.

Retention period

We retain account, security and transaction records only for the period needed for the stated service, dispute handling and legal duties. When a record is no longer needed, our handling process removes or anonymises it.

Change requests

You can ask us to correct inaccurate contact data or explain a stored record through support. Include the account email or phone path and the specific field, so we can assess the request safely.

Privacy Policy Questions Before Account Access

These answers focus on the questions we expect you to ask before opening an account or sending a payment receipt. They cover access, stored records, cookies and contact steps, including what may be needed when you use a mobile device in Indonesia.

The fw66 Privacy Policy explains the account, device, cookie, support and payment-reference data we handle, why we use it, how retention works and how you can request correction or clarification.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records used to match a cashier event to your account.

You can contact support from your account path and ask what eligible records are held about you. Include your account contact and request scope; we may verify your identity before responding.

We may use session and security signals from your phone or browser to keep login continuity and identify unusual access. These signals support account protection and are handled under the Privacy Policy.

Yes. Send a correction request through the support route beside your account area, name the inaccurate field and provide the correct value. We may ask for an account verification step first.

Yes. Account access and related data handling depend on local law. We apply the Privacy Policy to supported Indonesia access where local law permits and may limit a request when legal duties require it.

You can ask support which cookie purpose relates to your session, login or security check. Browser settings also let you manage cookies, though disabling them may require repeated sign-in.