Reference

FW66 Privacy Policy for Your Account Data

Our Privacy Policy explains how we collect, use and protect the details connected with your FW66 account, including phone verification, wallet records and device access.

Clear data purposesWallet record controlsYour contact rightsDevice access clarity
FW66 FW66 Privacy Policy for Your Account Data
CONTACT PATHS

Reach FW66 About Privacy Requests

A clear support path helps when you need a copy, correction or explanation concerning your personal data. Use the account support route shown near the cashier area and include the phone number linked to your account, the relevant DANA, OVO, GoPay or QRIS reference, and the request you want us to review. We may ask for another account check before disclosing private records.

Team online

Access request

Ask for the personal data linked to your account, including phone verification records, sign-in history and wallet references. We will confirm your account before sending material that could expose private details.

Correction request

Tell us which account detail needs changing and why. Include the affected phone number or payment reference, so our support route can separate your request from another DANA, OVO or QRIS record.

Privacy support

For a deletion, retention or cookie question, contact us through the account help route beside the cashier path. We will explain any local-law reason a record must remain stored.

DATA PRACTICES

Explore How We Handle Privacy

Our privacy work follows the same account steps you see when moving from phone verification to the lobby: we identify the account, record the relevant event and restrict access to the people…

Collected details

We may store your phone number, verification result, sign-in time, device and browser markers, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Use of records

We use account data to confirm access, match a payment status, investigate a stalled wallet update, respond to privacy requests and meet duties that apply where local law permits.

Cookie choices

Cookies can keep a session active and preserve basic page settings. You can manage cookies through your browser, though blocking them may require another sign-in or affect the account access path.

Account security

Phone verification helps us distinguish your account before access or support action. We may compare device and sign-in signals when a request concerns wallet status or a sensitive account change.

Retention approach

We retain each record for the period needed for its stated purpose, dispute handling, security checks or a legal duty. When no valid need remains, we remove or de-identify it.

Change requests

You can request access, correction or deletion through support. State your account phone number, the data involved and the requested action; we may verify ownership before making any change.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account access. We explain what happens to account data, how payment references are used and where to send a request. If your case involves a wallet status, device change or deletion request, include the relevant account detail so we can follow the correct path.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify the account, help distinguish your request from another account, and support access checks when a wallet status or account change needs confirmation.

Yes. The Privacy Policy includes payment references and status details received when you use DANA or QRIS. We use them to match activity, investigate support cases and maintain relevant records.

Use the support route beside the cashier path and state your account phone number, the records you want and your preferred response. We may verify account ownership before sharing private material.

Yes. Send the incorrect detail, the corrected value and any matching account or payment reference. We will check the request, update eligible records and explain if a legal duty requires retention.

Retention depends on the purpose, security needs, dispute handling and duties that apply. We keep records only as long as needed, then remove or de-identify them where local law permits.

Yes. Mobile browser access may create device and cookie records just like desktop access. A change from phone to desktop can trigger another sign-in or verification step to protect your account.