How fd888 handles your data
fd888 puts casino, sportsbook and account tools behind a privacy policy that explains what data we collect before you open your account. You can read how we handle...
Our privacy position for Pakistan
This Privacy Policy explains how we collect, use, store and share data linked to your fd888 account where local law permits. We ask for details needed to create your account, confirm access, process payout checks, respond to support requests and keep account activity secure. Payment references from JazzCash, Easypaisa, SadaPay and Raast may be attached to your account record so we can
match a request with the correct wallet or bank route. We do not write this policy as a game page; it is about your personal data, device signals, contact choices and account history. We also describe when service partners may handle data for hosting, fraud checks, payment routing or customer care, and how you can ask us about your record.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to ask privacy questions
We keep privacy contact routes separate from general lobby help so your request reaches the right team. When you contact us, include the phone or email tied to your account, but avoid sending wallet PINs or full card details. We may ask for limited proof before changing any record.
Privacy email
Write to our privacy contact when you want to ask what data we hold, correct account details, or query a past support exchange. We reply after matching your message with your account record.
Live chat handoff
If you start in live chat, our agent can move a privacy question into the correct queue. The chat transcript may stay attached to your account so the privacy team sees the full request.
Account centre request
Use the account centre for changes to your contact details or password data. We log the request time, the device used and the outcome so your privacy record stays traceable.
How we keep wording current
Our privacy text is checked against the way fd888 actually handles accounts, payment references and support cases. We update wording when a data route changes, such as a new verification step or...
Operational matching
We compare policy wording with real account flows, including login checks, payout verification and support ticket handling. If a process changes, the policy text is updated so your reading matches our practice.
Local context
Pakistan wallet and bank references are named only where they affect data handling. That keeps JazzCash, Easypaisa, SadaPay and Raast records clear without turning this page into a payment page.
Access records
We explain why device signals, IP ranges and login times may be stored. These records help us protect accounts, investigate unusual access and answer your privacy questions with a clear trail.
Support accuracy
Privacy requests often begin with customer care, so our agents follow set wording for data questions. They avoid asking for sensitive wallet secrets and route deeper requests to the privacy contact.
Partner boundaries
Where service partners process data for hosting, verification, analytics or payment routing, we describe the purpose in plain terms. We do not give partners wider access than the task requires.
Change tracking
Policy edits are logged internally with the reason for the change. This helps us answer why wording moved, which account flow it relates to and when you should read it again.
How this policy fits other pages
This Privacy Policy works beside our terms, cookie text and account rules, but it has its own job. Here we focus on personal data: what we collect, why...
| Terms boundary | Our terms explain account rules and service use, while this policy explains the data behind those actions. If both pages mention verification, this one covers the privacy reason for the check. |
|---|---|
| Cookie boundary | Cookie text deals with browser storage and tracking choices. This policy connects those signals with your wider account record, such as login security, preference storage and session management. |
| Payment record boundary | Payment pages may show available rails, but this policy explains the personal data attached to a transaction reference. That includes wallet names, request times and verification status linked to your account. |
| Support boundary | Help pages tell you how to reach us. This policy explains how messages, chat transcripts and case outcomes may be stored, shared internally and used to answer a privacy request. |
| Security boundary | Security text may describe account protection in action. The privacy page adds why we process device signals, login patterns and identity checks when access looks unusual or a payout needs confirmation. |
| Promotion boundary | Offer pages may use your account status to display eligible items. This policy explains the data logic behind personalisation, consent choices and how you can ask us about promotional contact. |
| Update boundary | When another policy page changes, we check whether the privacy wording needs an edit too. That keeps account, cookie and support language aligned without mixing their separate legal roles. |
Privacy cues across the page
We design the privacy page so you can scan the parts that matter before opening or using an account. Headings separate account data, security checks, partner...
Plain section labels
Each section uses direct labels so you can find account data, device records, partner processing and contact rights quickly. We avoid broad language when a specific data purpose can be named.
Named data examples
We use examples such as phone number, email, wallet reference, login time and support transcript. These examples make the privacy policy easier to connect with your actual fd888 account activity.
Pakistan access wording
Where access depends on supported regions, the policy says so without overpromising. This helps you understand that data handling may follow local requirements and account checks linked to your location.
Security purpose markers
When we mention device or login data, we state the security purpose near it. That keeps the policy focused on why the data exists, not only that it is collected.
Partner purpose tags
If a service partner may process your data, we state the task, such as hosting, verification, support tooling or payment routing. The label shows why access is needed for that task.
Contact prompts
Privacy contact prompts appear near the rights wording so you know where to ask about access, correction or account data handling. We keep these prompts separate from general lobby messages.