LEGAL REFERENCE

Privacy Policy for Your bf88 Account

Open your bf88 account with a clear view of how your data is collected, used, stored and shared where local law permits. This Privacy Policy covers account details...

Account dataDevice signalsJazzCash contextEasypaisa contextSupport records
Explore Lobby Read FAQ
bf88 Privacy Policy for Your bf88 Account

How This Policy Applies

This Privacy Policy explains how we handle data when you create or access a bf88 account, move through the lobby, contact us, or use local payment rails where local law permits. We collect only the account, device, location, payment and support records needed to run the service, detect misuse, answer privacy requests and keep your access consistent. Payment-related records may include transaction

references, wallet names, time stamps and status updates from supported providers, but we do not ask you to share wallet passwords or app PINs. We may share limited data with processors that help with hosting, security, analytics, verification and customer support. Those processors are expected to handle data under written controls and only for the task assigned to them.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Contact Paths for Privacy Requests

If you need help with data access, correction, deletion, or account-security concerns, use the privacy contact path that matches your issue. We...

Privacy email Write to [email protected] with your account ID, contact...
Account chat Use live chat from inside your account when...
Payment record help For JazzCash, Easypaisa, SadaPay, NayaPay or Raast records...
POLICY CARE

How We Keep Privacy Wording Current

Our Privacy Policy is written from the way bf88 actually handles account records, not from a generic legal template. We check the wording when payment flows, support tools...

Operational input

Privacy wording is checked against real account flows, including login, password reset, wallet reference handling and support tickets. This keeps...

Local payment context

We name Pakistani rails only where they affect data handling. JazzCash, Easypaisa, SadaPay, NayaPay and Raast references help explain what...

Security alignment

Access logs, device signals and session checks are described because they protect your account and help us detect unusual activity...

Support traceability

When you contact us, chat and email records may be kept with timestamps and agent actions. This helps us answer...

Change tracking

When we adjust this Privacy Policy, we update the wording to match current handling. Material changes are presented clearly, so...

Access boundaries

Internal access to personal data is limited by role. Support, risk and technical teams receive only the parts needed for...

How Privacy Fits Other Policy Pages

This page focuses on personal data only. Other policy pages may explain account terms, promotions, cookies or site rules, but the Privacy Policy is where we describe collection...

Account termsTerms describe how your account may be used, while this Privacy Policy explains the records created during that use. The two pages connect, but each answers a different legal question.
Cookie pageCookie wording deals with browser storage, tags and similar tools. This Privacy Policy connects those signals to account security, analytics and your choices where settings are available.
Promotion rulesPromotion terms explain offer conditions. This Privacy Policy explains any data needed to show eligibility, prevent misuse, record acceptance, or answer questions about account-linked promotion records.
Security wordingSecurity pages may describe safe account habits. This policy explains how login records, device checks, alerts and verification details are handled inside bf88 systems.
Payment termsPayment terms explain transaction handling. This Privacy Policy explains related data, such as wallet type, reference number, status time and account matching for Pakistani payment rails.
Support policySupport wording explains how to reach us. This Privacy Policy explains what happens to chat logs, email messages, identity checks and case history after you contact us.
Regional accessAccess pages may mention supported regions. This Privacy Policy explains how location signals are used to manage availability, fraud checks and legal requests where local law permits.
VISIBLE CONTROLS

Visible Privacy Controls Across bf88

We place privacy cues where they matter: account screens, login steps, support forms and payment reference areas. These visible elements help you understand what data is being requested...

Account fields Account forms ask for details needed to identify you and...
Password prompts Password fields are kept separate from support requests. If our...
Wallet references Payment reference boxes are designed for transaction IDs, wallet names...
Session alerts Login alerts and device checks can reveal unusual access patterns...
Preference choices Where account settings allow message choices, we use them to...
Request history Privacy requests may be logged with dates, actions and response...

Questions About the Privacy Policy

We collect account details, contact data, login records, device signals and security checks needed to create and protect your account. We may also keep support messages and payment references linked to your activity.

No. For JazzCash, Easypaisa, SadaPay, NayaPay or Raast, we may record transaction references, wallet type, amount status and timing, but we do not ask for wallet passwords, PINs or one-time codes.

Email [email protected] or open an account chat and request data access. We may ask you to confirm account ownership before sending or changing records, especially when payment or security details are involved.

Yes, if the detail is eligible for correction and we can confirm the request belongs to you. Some records, such as transaction logs or security events, may need to remain unchanged for audit reasons.

We keep data for as long as needed for account operation, legal handling, security checks, dispute handling and support history. When records are no longer needed, we remove or reduce them where practical.

The policy applies to bf88 handling of your data, with access and processing subject to supported regions and where local law permits. Some features or request outcomes may depend on local requirements.

Access is limited by role. Support, risk, technical and account teams may see only the data needed for their task, such as resolving a ticket, checking account access, or handling a privacy request.