Privacy Policy for your ff app account
ff app keeps one privacy path for your Casino & Sportsbook account in Pakistan: account details, device records, payment references and support chats are handled under this policy...
How we handle your personal data
This Privacy Policy explains how ff app collects, uses, stores and shares personal data when you create an account, access the lobby where local law permits, use support, or request account actions. We collect only what we need to run your account, check access, process payment references, protect sessions and answer your privacy requests. Pakistani payment rails may create transaction references that
help us match your account activity without asking for more detail than required. We may work with service providers for hosting, analytics, fraud checks and support tools, but we keep those roles limited to the purpose stated here. If a law, regulator or court requires a response, we handle that request in line with applicable rules and supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy contact paths we maintain
Use these contact paths when you want to ask about data access, correction, account records or privacy choices. We separate privacy requests from regular lobby help so your message reaches the right queue and can be matched to your account securely.
Privacy email
Send us a privacy request from the email linked to your ff app account. Include the account name, your Pakistan region and the data topic, but avoid sharing card images or unrelated screenshots.
In-account chat
Use live chat after signing in when you need help locating privacy settings or account records. Our team checks your session first so we can discuss account data without exposing it elsewhere.
Escalation check
If your request needs deeper checking, we move it to a privacy queue and confirm the next step by account message or email. This keeps identity checks tied to your ff app profile.
Checks behind this Privacy Policy
We write this policy from the way ff app actually operates. The wording matches account creation, device checks, payment reference matching, support handling and service-provider access, so you can see how privacy...
Data map
We map personal data to the account step that creates it, such as signup fields, login events, payment references, support chats or security alerts. That map helps us avoid vague collection language.
Payment matching
JazzCash, Easypaisa, SadaPay and Raast references are used to reconcile account funding and withdrawals. The policy explains that matching role without asking you to share unrelated wallet data.
Device care
We use device and session signals to protect access, spot unusual sign-in patterns and keep account actions connected to you. This policy states why those checks exist and how they support account safety.
Access controls
Internal access to account data is limited by role, work need and system permission. Support can see what is needed for your request, while sensitive account actions need stricter checks.
Pakistan wording
The policy uses Pakistan-specific payment names and access language because your privacy context changes by region. Where access depends on local law, we say so instead of using broad claims.
Change record
When we adjust this policy, we update the page date and keep the language aligned with current account flows. Material changes are written plainly so you can compare what changed.
How this policy fits other pages
Your privacy rights do not sit in isolation. We keep this Privacy Policy aligned with our terms, cookie statement, account rules and support process so the same data...
| Terms page | Our terms describe account obligations, while this Privacy Policy explains the personal data used to apply them. The two pages use matching account language so your rights and duties are not split awkwardly. |
|---|---|
| Cookie statement | The cookie statement focuses on browser storage and tracking preferences. This Privacy Policy connects those tools to login stability, fraud checks and measurement, without turning browser data into a separate account profile. |
| Security page | Security wording explains how access is protected, while this page explains the data behind those protections. We keep the same session, device and verification terms across both pages. |
| Support page | Support content tells you how to contact us, while this page explains how support messages, attachments and identity checks are handled. That alignment helps you send privacy requests through the right route. |
| Account rules | Account rules describe verification steps, and this policy states what personal data is needed for those steps. We avoid asking for extra records unless the account action requires it. |
| Funding page | Funding content names JazzCash, Easypaisa, SadaPay and Raast for account movement. This Privacy Policy explains the privacy role of payment references, reconciliation checks and withdrawal confirmation records. |
| Offer terms | Offer terms may require account eligibility checks, but this page controls how related data is handled. We keep eligibility checks tied to account records rather than unrelated personal details. |
What you see on this page
This Privacy Policy is arranged so you can scan the key privacy points before opening or continuing an account. The layout separates collection, use, sharing, storage...
Plain summary
The opening section states the main privacy promise before the legal detail. You can quickly see that account data, device records, payment references and support chats are covered by the same policy.
Data categories
We group data by account step, including signup, login, payments, support and security checks. That layout helps you understand what is collected at each point without reading scattered clauses.
Purpose labels
Each use of data is tied to a purpose, such as account operation, fraud checks, support response or legal compliance. We avoid unclear wording that makes every purpose sound the same.
Sharing boundaries
The policy separates service providers, payment partners and legal requests so you can see why data may leave ff app systems. We describe roles, not broad permission to share freely.
Retention markers
Where records must be kept, we link retention to account activity, dispute handling, reconciliation and legal duties. When a record is no longer needed, we aim to remove or anonymise it.
Request routes
The contact section gives practical routes for access, correction and deletion questions. We explain why identity checks are needed before account data is discussed or changed.