How 888jd Handles Your Account Data
Your 888jd account touches a lot: the email you sign up with, the JazzCash or Easypaisa reference on each transfer, and the device logs that keep it secure...
Scope, Law And Supported Regions
We apply this privacy policy to accounts held in Pakistan, wherever local law permits, and we describe our data practices as they work in supported regions rather than everywhere at once. Identity checks, the JazzCash, Easypaisa, SadaPay or Raast references attached to your transfers, and the way we answer a data request can differ from one province to the next, because provincial
and federal rules are not identical. Where a local rule asks for something different, that rule governs your account. Nothing here claims a licence, certification or regulator we do not hold. We also keep a dated copy of every earlier version, so you can see what the wording said when you opened your account and compare it with what applies today.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Checks This Privacy Page
This page is written by the team that operates your account, so the wording matches how our systems behave. Before a change goes live, a second pair of eyes from our data-handling...
Operator Check
Each paragraph is checked against the live systems your account runs on, so a description of how a transfer reference is stored reflects the current setup, not an old draft.
Two-Person Sign-Off
Two people clear every edit: one from the team running account operations and one from our data-handling group. If either finds a mismatch with practice, the wording waits.
Version Dates
We date the head of this page whenever the text changes, so you can see whether the version you read at sign-up still covers your account. Superseded drafts stay archived.
Region Clauses
Clauses that depend on where you live are labelled so you can skip parts written for other supported regions. Provincial differences in Pakistan appear beside the federal wording.
Plain Wording
Technical descriptions are rewritten into everyday English before publishing, since a policy you cannot follow is not much use. Unavoidable legal terms are explained in the next sentence.
Correction Log
If something here does not match what you see in your account, tell support. We log the difference, investigate and correct the page, and the report stays open until it closes.
How This Page Fits The Others
Privacy sits beside the terms, cookie and account pages that also cover your 888jd sign-up, and all four are edited from one source so the definitions match. Where...
| Terms Of Use | The terms page covers what you accept when you hold an account; this page covers the personal data attached to it. One explains your obligations, the other ours. |
|---|---|
| Cookie Notice | Cookies, local storage and session tokens are set out in the cookie notice, including how to clear them on your device. Here we explain why those records exist. |
| Account Rules | Sign-up, verification and closure steps live on the account pages. Repeated wording is stripped from here so each step has one description, with a cross-reference to the detail. |
| One Editing Source | All four policy pages are drafted in a single workspace, so a data-request phrase means the same thing everywhere. When a definition changes, it changes across every document at once. |
| No Contradictions | If two pages ever read differently, the version with the later date governs until the older text is fixed. Tell support when you spot a clash and we correct both together. |
| Shared Retention | Retention periods are stated once, on this page, and the other documents point here instead of repeating numbers. That leaves one answer for how long a transfer reference is held. |
| Shared Definitions | Words such as account holder, personal data and processor are defined once and used the same way across every policy page, so one label never means two things. |
The Shape Of This Privacy Page
The layout is built so you can find one answer without reading the whole document. A summary of the data we hold sits near the start...
At-A-Glance Summary
A short block near the start lists the categories your account generates: profile details, transaction references, device data and support messages. The longer clauses follow in order.
Revision Dates
Each revision carries a date and a one-line note about what moved, so you can scan the history instead of re-reading the document to work out what affects you.
Sticky Section Menu
On a phone the section menu stays within reach, so you can jump straight to retention, sharing or your request rights without scrolling past clauses you already read.
Plain Headings
Headings read like questions rather than legal titles, which makes the clause you want quicker to find. Each heading repeats word-for-word in the sibling documents, so cross-references still work.
Glossary Block
Uncommon terms are gathered in a short glossary near the bottom with a plain explanation beside each one, so you read clause and definition together instead of opening another page.
Contact Footer
The footer on every policy page repeats the same support routes — live chat, email and a registered-number callback — so a question about your data never depends on which page you opened.