Privacy Policy For Your 88ff Account
88ff keeps its Privacy Policy close to the account flow, so you can see how your data is handled before you join or return. We explain what we...
How Our Privacy Policy Applies
This Privacy Policy explains how 88ff handles data when you create an account, enter the lobby, contact support, complete verification, or use Pakistani payment rails where local law permits. We collect account details you submit, device signals that help keep access orderly, transaction references from JazzCash, Easypaisa, SadaPay and Raast, and messages you send to us. We use that data to operate
your account, process requests, check security events, answer privacy questions, and keep records required for service operation. We do not sell your account data. When service partners help with hosting, fraud checks, payment routing or support tools, they receive only the data needed for that task and must handle it under restricted access terms.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach Us About Privacy Requests
If you want to ask about privacy rights, account records, correction of details, or deletion requests, contact us from the same profile area you use for account service. We may ask for account markers before discussing private data, because we need to confirm we are speaking with you. For sensitive requests, keep your message clear and avoid sending extra documents unless we ask.
Privacy inbox
Send a privacy request through the contact form linked inside your 88ff account. Include your account name, registered phone or email, and the exact data question you want us to answer.
Chat handoff
Use live chat for quick routing, then ask the team to pass your privacy matter to account care. Chat agents may confirm basic account markers before escalating your request.
Payment query
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, share only the transaction reference we request. Do not post wallet passwords, one-time codes, or full financial screenshots.
How We Keep This Policy Clear
We write this Privacy Policy from our own operating view, not as a third-party summary. Each update is checked against the account journey you actually use: joining, logging...
Account flow tested
We check privacy wording against the account screens you pass through, including registration fields, login checks and profile edits, so...
Payment data separated
Wallet and bank rail references are described apart from gameplay records. This helps you see which data comes from JazzCash...
Access controls
Internal access is limited by role. Support can see what is needed to answer your case, while deeper technical logs...
Retention checks
We keep account and transaction records only for service, security, dispute handling and legal record needs. When retention is no...
Regional wording
Pakistan context matters, so we mention supported regions, local law, Pakistani contact expectations and the payment names you recognise instead...
Change tracking
When privacy wording changes, we adjust the page date and make material updates easier to spot. You can return here...
Privacy Links Across Related Pages
Our legal pages work together, but this page stays focused on privacy. If another page explains account rules, promotions or access terms, this Privacy Policy explains the data...
| Account terms | Where account terms mention identity checks, this Privacy Policy explains the data used for those checks, including profile fields, login markers and verification records tied to your account. |
|---|---|
| Cookie page | Cookie wording should match this policy on device signals, session IDs and preference storage. If we use cookies for security, the privacy reason is stated here. |
| Promotion rules | If a promotion requires eligibility checks, this policy explains the account data used to assess it. We avoid adding unrelated marketing claims inside privacy wording. |
| Payment terms | Payment pages may explain processing steps, while this policy explains privacy handling for transaction references, account matching, wallet names and support messages linked to a request. |
| Security page | Security wording covers controls; this policy covers the data those controls use. Examples include device checks, login alerts, suspicious access flags and support escalation records. |
| Support page | Support contact paths may collect chat text, email details and case markers. This policy explains how those records are stored, accessed and connected to your account. |
| Policy updates | When another legal page changes a data-related process, we check this Privacy Policy as well. That keeps privacy wording aligned with your real account journey. |
Privacy Layout You Can Scan
This page is arranged so you can find the privacy detail you need without reading unrelated service copy. We place account data, support records, local transaction references, security...