Reference

fangwin Privacy Policy for Your Account Choices

fangwin Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the casino or Sportsbook pages.

Account clarityWallet detailsCookie choicesContact path
fangwin fangwin Privacy Policy for Your Account Choices
CONTACT WHEN NEEDED

Privacy Help Beside Your Account Path

A clear contact route matters when you want to ask about personal data rather than a wallet status. Our support paths let you identify your account, describe the request and receive a response without placing sensitive details in a public message.

Team online

Support chat

Use the support chat for questions about data collected during phone verification, device access or a cookie choice. Share your account identifier, not your wallet PIN or full payment password.

Account contact

Send a privacy request through the account contact path when you need a copy, correction or removal assessment. We may verify account ownership before changing records tied to your login.

Payment reference

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the transaction reference and date. This helps us locate the relevant record while keeping unrelated account data out of the request.

OUR HANDLING PRACTICE

What We Do With Your Fangwin Data

We separate the data needed for account access from the records used to resolve a payment or security question.

Account data

We use your account details and verified phone record to recognise your login, protect account access and respond to requests. We do not need unrelated details to answer a normal privacy question.

Wallet records

When a DANA, OVO, GoPay or QRIS transaction reaches the cashier path, we retain the reference, status and account link needed for reconciliation and support. Wallet credentials remain outside our requested account fields.

Cookies

Cookies and similar device markers can keep a session open, remember selected settings and help us detect unusual access. You can adjust browser controls, although some account functions may then need another login.

Security checks

We may compare login, browser and device signals when access looks unusual. If a check pauses your account, support can ask for details that confirm ownership without requesting your wallet PIN.

Retention period

We keep account, payment and support records only for as long as needed for the stated service, dispute handling, security checks or legal duties. When a record is no longer needed, we remove or restrict it.

Your changes

You can ask us to correct account data, explain a processing purpose or assess deletion through support chat or the account contact path. We may request phone or account verification before acting.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening access. We keep each response tied to a real fangwin step, from phone verification and mobile cookies to payment references and requests sent through support.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect you to the correct account and reduce unauthorised access. We use the verified contact record for account security and support checks, not as a request for your wallet PIN.

Yes. When you open fangwin from a mobile browser, we may process device, browser and connection details for session access, security checks and cookie functions. The same policy applies on desktop.

We may receive a payment reference, amount status, timing and account link for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN for reconciliation.

You can contact support chat or use the account contact path to request access, correction or a deletion assessment. We may verify your account first so changes reach the correct record.

Retention depends on why the record exists, such as account access, payment reconciliation, security, dispute handling or legal duties. We remove or restrict records when the relevant need ends, where local law permits.

Start with support chat or the account contact path and include your account identifier plus a clear request. For payment records, add the transaction reference and date, while leaving wallet credentials out.