Account terms link
Our account terms explain account rules, while this Privacy Policy explains data handling. Where both pages mention verification, this page focuses on what data is checked and why.
LEGAL REFERENCE
Privacy Policy for your 88df account
88df sets out how your account data, device signals, support messages and payment records are handled before you open an account in supported regions. This Privacy Policy explains...
Account data usePayment record careSupport message privacyPakistan access wording
How we handle your personal data
This Privacy Policy applies when you use 88df through our site, account area, lobby access, support channels or payment flows where local law permits. We collect the data needed to create and protect your account, process payment checks, answer your requests, prevent misuse and keep a clear record of activity tied to your profile. That can include your name, mobile number, email
address, device details, login events, IP address, payment reference IDs and messages you send to us. We do not sell your personal data. We share data only with service providers who help us run account security, payment processing, hosting, analytics, fraud controls and customer care under limited instructions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED COPY
How we keep policy wording accurate
We write this Privacy Policy from the systems we operate: account creation, login monitoring, payment reconciliation, customer care and security checks. Each update is checked against how data actually moves through 88df...
System mapping
We map each data category to the part of 88df that uses it, such as account access, support records, fraud screening, payment matching or security alerts, before policy wording is updated.
Local wording
Our privacy text uses Pakistani English and local payment names so you can connect the policy to your real wallet flow, including JazzCash, Easypaisa, SadaPay and Raast records.
Security checks
We describe login data, device checks and access controls because those signals help us protect your account. The policy explains why we collect them and how long they may stay useful.
Support evidence
Support chats, emails and form messages may be kept with your account history. This helps us answer privacy requests, investigate access issues and keep a clear timeline of our replies.
Provider limits
When we use hosting, analytics or payment service providers, we limit their role to the task assigned. The policy avoids broad permission wording and explains why sharing may happen.
Change control
When our privacy wording changes, we update the policy page rather than hiding changes inside account screens. You can return here to see the current wording before continuing with 88df.
POLICY MATCH
How this policy stays consistent
Your privacy rights should not change depending on which legal page you open. We align this Privacy Policy with account terms, cookie wording, promotion terms and support rules, while keeping each page...
Cookie wording link
Cookie wording covers browser storage and tracking choices. This Privacy Policy connects those signals to account security, site performance and records that may sit beside your profile.
Payment wording link
Payment pages explain transaction steps. This policy explains the related personal data, such as wallet references, bank routing details, payment status, reconciliation logs and support evidence.
Promotion wording link
Promotion terms may mention eligibility checks. This Privacy Policy explains the account data used for those checks, including region, account status, device signals and transaction history.
Support wording link
Support pages explain how to reach us. This policy explains how we store your support messages, verify your identity and use previous replies to handle privacy requests.
Security wording link
Security pages may describe account protection steps. This policy gives the privacy angle, including login records, device fingerprints, suspicious activity checks and access restriction records.
Update wording link
If 88df changes a process that affects personal data, this page is updated to match. We keep related legal pages aligned so your account expectations stay clear.
PAGE MARKERS
Privacy cues you can see
This page is designed to help you spot the privacy points that matter before you share data with 88df. The layout separates collection, use, sharing, security, retention and...
Plain headings
Each heading names a privacy action, such as collecting, using...
Local examples
Where examples help, we name Pakistan payment rails and support...
Short badges
The badges near the hero show the main privacy areas...
Contact prompts
Privacy contact points are separated from general help prompts. That...
Data categories
We group personal data by practical category, such as account...
Change signals
When wording changes, the page structure keeps those changes visible...
Privacy questions before you join
We collect account details, contact data, login records, device signals, payment references and support messages. We use these records to run your account, answer requests, protect access and meet operational duties.
Payment references from JazzCash, Easypaisa, SadaPay or Raast help us match a transaction to your 88df account. We do not ask for wallet PINs, passwords or full private banking access.
Yes. Contact us through your account channel and explain what needs correction. We may verify your identity first, then update eligible records or explain why a record must remain unchanged.
We keep personal data for as long as needed for account operation, security, dispute handling, legal duties and audit records. When data is no longer needed, we delete or anonymise it.
We share data with service providers only when needed for hosting, payment checks, security tools, analytics or customer care. They receive limited data for assigned work, not open permission.
We use login records, device checks and security alerts to detect unusual access. If a privacy request looks risky, we may ask for extra proof before releasing account data.
This policy applies to 88df access in supported regions where local law permits. Availability, verification steps and data duties may vary by location, payment rail and account status.