Shared definitions
Terms such as account, wallet and session mean the same here as on our terms of use and payment pages. You should never have to guess whether a word changed meaning.
This Privacy Policy sets out what 888y apk collects when you open an account, how we store it, and the choices that stay with you. Read it once...
Where local law permits, 888y apk handles your personal data under the terms written on this page. We collect what you give us at sign-up — name, phone number, email, date of birth and the payment handle you use — plus the session data our systems generate to keep your account secure. Records tied to JazzCash, Easypaisa, SadaPay and Raast are held
for reconciliation and for the audit trail our finance team maintains. Some clauses bind only in supported regions, and a few depend on the jurisdiction you register from; where a local rule gives you stronger rights than this page sets out, that local rule applies. We do not sell personal data, and you can write to our privacy desk at any point
to ask what we hold.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The people who write this page sit next to the teams handling payments, security and account access, so every clause reflects what happens in our systems. We revise the text when a...
Our compliance writers sit with the payments and security teams, so clauses come from live workflow rather than another operator's template. When a desk process changes, the wording follows in the same release cycle.
Every data category on this page carries a retention window beside it, from sign-up records to payment logs. When a window closes we delete or anonymise the file, and you can ask which one covers your account.
Each version of this text carries a date in the header and older versions stay available when you ask. You can compare what applied when you opened the account with what applies today.
We describe encryption in transit, hashed passwords and two-step account entry without hiding behind jargon. If a security practice shifts, this page shifts with it and we spell out what changes for you.
Clauses that bind only in supported regions are marked as such, so you never read a promise that misses your market. Where Pakistani record-keeping rules set a longer hold than ours, local wins.
This page says plainly that we do not sell personal data, and no clause can be read as permission to trade your details. Sharing stays with processors that run payments, fraud checks and hosting.
The terms here line up with the rest of 888y apk — the same definitions, the same payment names and the same contact points you meet on our other legal pages. If...
Terms such as account, wallet and session mean the same here as on our terms of use and payment pages. You should never have to guess whether a word changed meaning.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are spelled the same way on every page we publish, so searching one document leads you to the matching clause elsewhere.
The privacy desk address here matches the one on our account and security pages. Whichever document you arrive from, your message reaches the same team and gets a single reference number.
When we update this Privacy Policy we check the sibling pages the same week, so dates do not drift apart and you never read a stale clause beside a fresh one.
Where two documents could be read as giving different answers, the narrower promise is the one we honour. That rule sits in our drafting standard rather than with whoever edits the page.
Each clause here links to the matching section on our account and cookie pages, so you can move between them in two clicks and see how one promise supports another.
Before anything publishes, a colleague outside the compliance team reads it and flags sentences needing a second pass. If a clause cannot be understood on one reading, we rewrite it rather than add a glossary.
The layout here is built so you can find the clause you need without scrolling through the whole document. A short summary opens the page, the...
The first block you meet sums up what we collect, why we hold it and how long it stays. Use it as a map before reading the longer clauses underneath.
Each heading names one kind of data — sign-up details, session records, payment logs, support messages — so you reach the part that answers your question without reading around it.
We write in ordinary English rather than legal shorthand and define a term the first time it appears. If a sentence still needs decoding, tell the privacy desk and we redraft it.
A dated line sits above the first clause so you know which version you are reading. Older versions can be requested from the privacy desk if you need to check earlier terms.
The desk address, chat link and request form sit together in one block, so you can act on a question the moment you finish reading rather than hunting through menus.
The document reflows cleanly on a handset, with headings that stay put as you scroll. Read one clause on the move and return to the rest later without losing your place.