Reference

fa66 Privacy Policy for Your Account

The fa66 Privacy Policy shows what account, device and wallet details we collect when you open access, check Blackjack or Mahjong Ways, and use DANA or QRIS.

Account clarityWallet recordsCookie choicesLocal-law access

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

fa66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies when you create an account, complete phone verification, sign in from a mobile browser, or contact us about a payment record. We may handle contact details, login activity, device signals, cookie choices, transaction references and support messages so we can connect your

1
account with the correct status. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use the details needed to match a receipt or resolve a pending status; we do not ask for unrelated wallet credentials. Opening Blackjack, Rocket Crash or Fish Hunter can
2
also create session and preference records. We retain records only for operational, dispute and legal needs, and access depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH YOUR RECORDS

Get Privacy Policy Support Near Wallet Help

A clear contact path matters when a receipt, phone check or account detail looks wrong. Use the support link inside your account and include your registered phone number, the affected wallet rail…

Account detail request Ask us to confirm the personal details connected to your account. After we match your phone verification step, we can explain which records are held and why they appear.

Wallet status query For DANA, OVO, GoPay or QRIS questions, send the receipt reference through account support. We compare the status record with your account activity and reply through the same support path.

Correction request If your phone number, contact detail or account record needs correction, state the exact change and its reason. We may request account checks before changing information linked to access.

HOW WE HANDLE DETAILS

Your Privacy Policy Choices In Practice

We keep this policy practical by tying each data use to an account action you can recognise.

Account data

We use your registration and contact details to create the account record, connect phone verification, and answer a request about your Privacy Policy rights or stored account activity.

Cookie controls

Cookies can remember sign-in preferences and device choices. You can adjust cookie settings in your browser, although turning them off may require another sign-in or remove saved page preferences.

Access protection

Phone verification and sign-in checks help us distinguish your request from an unauthorised attempt. Do not send a password or wallet PIN when asking about a Privacy Policy matter.

Retention approach

We keep account, receipt and support records for as long as needed for account operation, dispute handling and applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Requesting changes

You can ask for access, correction or clarification through the support link in your account. Include the requested change and registered phone detail so we can verify the correct account.

Third-party rails

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear in a payment reference. We use the reference needed for matching and status checks, not your private wallet password.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear most often before account creation. They cover account records, cookies, wallet references, phone verification and requests made through fa66 support. If your question is not listed, use the account contact path and describe the specific record you want us to check.

The fa66 Privacy Policy covers registration details, phone verification results, sign-in activity, device signals, cookie choices, support messages and payment references connected with DANA, OVO, GoPay or QRIS.

We use phone verification before account access to match a request with the correct account and reduce unauthorised changes. It also helps us respond accurately when you ask about stored data.

Yes. The Privacy Policy covers the receipt reference and status details needed to match QRIS, DANA, OVO or GoPay activity. We do not ask you to provide a wallet password or PIN.

Open the support link inside your account, describe the exact correction, and include your registered phone detail. We may complete an account check before changing information connected with access.

Cookies can retain sign-in preferences and device choices during your mobile browser path. You can change browser cookie settings, though doing so may remove saved preferences or require another sign-in.

We retain account, payment-reference and support records while they are needed for account operation, disputes or applicable legal duties. Records no longer needed are removed or de-identified through our process.

Use the account support link and state whether you want access, correction or clarification. Include the relevant record type, such as phone verification or a bank transfer reference, without sending passwords.

fa66 Privacy Policy for Your Account

Get Privacy Policy Support Near Wallet Help

Your Privacy Policy Choices In Practice

Account data

Cookie controls

Access protection

Retention approach

Requesting changes

Third-party rails

Privacy Policy Answers Before Account Access

01 What does the fa66 Privacy Policy collect?

02 Why does fa66 need phone verification?

03 Does the Privacy Policy cover QRIS and wallet records?

04 How can I request a correction under this Privacy Policy?

05 How does fa66 use cookies on my device?

06 How long does fa66 keep personal data?

07 Where can I ask about my Privacy Policy rights?

Related Pages