Account terms
Our account terms explain eligibility, access and account conduct, while this Privacy Policy explains the data used to run those checks. The two pages are written to support each other without repeating every clause.
LEGAL REFERENCE
How bf1 handles your privacy
bf1 collects only the account, device, security and transaction data needed to run your access, verify requests and keep your privacy choices clear. Read this policy before you...
Pakistan privacy focusAccount data explainedJazzCash contextEasypaisa context
Our privacy stance for Pakistan
This Privacy Policy explains how bf1 collects, uses, stores and shares data when you access our casino, sportsbook and account pages where local law permits. We use your details to create and secure your account, process identity checks, handle transaction records, respond to support requests and improve page reliability. Payment references such as JazzCash, Easypaisa, SadaPay and Raast appear here only to
explain the types of transaction signals we may process, such as reference numbers, status messages and verification outcomes. We do not sell your personal data. Where a service partner helps us run security checks, hosting, analytics or payment routing, we limit access to the data needed for that task and keep records tied to clear operating reasons.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How we keep the policy accurate
We maintain this Privacy Policy as an operating document, not a decoration. Our account, payment, security and support teams provide input when data flows change. We also check...
Data mapping
We map account details, device signals, payment references and support messages to specific reasons for use. This helps us avoid...
Security input
Our security team checks privacy wording around login alerts, suspicious access flags and session data. Their input keeps the policy...
Payment context
Where JazzCash, Easypaisa, SadaPay or Raast records are involved, we describe reference handling without exposing unnecessary financial detail. The policy...
Support records
Support conversations may include account questions, screenshots or transaction references. We explain how those records help resolve privacy requests while...
Change checks
When we adjust account flows, verification steps or tracking tools, we check whether this Privacy Policy needs fresh wording. We...
Plain English
We write privacy terms in clear Pakistani English so you can understand what bf1 does with your details. Legal wording...
PAGE CONSISTENCY
How this policy aligns across bf1
Your privacy rights should not feel different from one bf1 legal page to another. This section explains how our Privacy Policy connects with related account, cookie, security and transaction terms, while keeping...
Cookie details
Cookie wording covers browser storage, session tools and analytics tags. This Privacy Policy places those tools in a wider data context, including why device signals may support security and page performance.
Transaction records
Payment-related pages may describe processing flow, while this policy describes privacy handling for references, status responses and verification outcomes. We separate operational steps from personal data use.
Security notices
Security pages may explain login checks or account alerts. This Privacy Policy explains what data those checks rely on, such as device markers, IP signals and account history.
Support wording
Support pages explain how to reach us, while this policy explains how support messages are stored and used. The same account-matching principle applies when we answer privacy-related questions.
Promo records
If you interact with an offer area, bf1 may record eligibility checks and account activity linked to that area. This policy explains the privacy side without turning legal text into promotion.
Regional access
Access language across bf1 refers to supported regions and local-law limits. This Privacy Policy uses the same approach when explaining data collection connected with Pakistan account access.
Privacy layout you can scan
We structured this page so you can move from a quick privacy summary into deeper detail without losing context. The visible blocks below show how bf1...
Hero summary
The opening block states what this Privacy Policy covers before you reach the longer legal text. It gives you the core account, device, security and transaction categories in plain language.
Context chips
Short chips call out Pakistan rails such as JazzCash, Easypaisa, SadaPay and Raast as data contexts. They are not sales claims; they show where transaction references may appear.
Contact cards
Support cards separate privacy request routes from general account help. Each card explains what details may be needed so your request can be matched without exposing records to the wrong person.
Record categories
Policy sections group data by account, device, security, transaction and support use. This helps you understand why a detail is collected instead of reading a single mixed paragraph.
Retention cues
Where records may be kept for security, transaction checks or dispute handling, the page explains the reason. We avoid open-ended language that leaves you unsure why bf1 keeps data.
FAQ closure
The question block answers common privacy concerns in direct language. It is placed near the end so you can check key points after reading the main policy sections.
Questions about your privacy at bf1
bf1 may collect account details, contact data, device signals, login history, support messages and transaction references. We use these records to run your account, protect access and respond to privacy requests.
When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive reference numbers, status updates and verification outcomes. These details help match transactions to your account and handle disputes or support questions.
No. bf1 does not sell your personal data. We may share limited records with service partners who help with hosting, security, analytics, support or payment routing, and only for the task they perform.
Contact us through your account inbox or the privacy route shown in your account area. We may ask you to confirm account identifiers before correcting personal records to prevent changes requested by the wrong person.
Retention depends on the record type and the reason it was collected. Security logs, transaction references and support messages may be kept where needed for account protection, dispute handling or legal record duties.
We use access controls, account verification, session monitoring and limited staff permissions to reduce unnecessary exposure. Private records are handled through internal tools, and support staff see only what they need for your request.