Terms of use
The rules you accept at registration sit beside this policy and share its definitions, so the same words carry the same meaning on both pages.
888fd game keeps one privacy policy, and it covers your account, your JazzCash and Easypaisa transaction records, and the data the lobby stores on your device. Read it...
Where local law permits, we collect only what an account needs: your name, contact details, device and login data, and the transaction lines created when you move money through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Rules differ across supported regions, so the same policy can apply differently depending on where you open your account. We keep records for the period local rules
require, restrict internal access to the teams that need it, and delete or anonymise what we no longer have to hold. You can ask for a copy of your data, correct an entry, or close your account at any time, and we answer those requests within the timeframe the law allows.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Every policy line on this page is written and re-checked by the same small team that runs verifications and account security, so the wording matches what our systems actually do. When a...
A named internal owner holds this page. They approve every edit before it goes live and answer escalations when a request is disputed or delayed beyond our stated timeline.
Each update carries the date it took effect, so you can tell whether the terms you accepted at registration still match the wording you are reading now.
We write the clauses we can in everyday English and keep the legal wording beside them, because a policy you cannot read is a policy you cannot use.
We set out how long each record type is held, from login logs to withdrawal files, so you know what disappears automatically and what you must ask us to remove.
Access to personal data is limited, logged and checked, and we contact affected account holders directly if a breach ever touches the details we store about them.
If a reply does not resolve your request, you can escalate it to a senior contact, and we give you the outcome in writing with the reasoning attached.
This policy is not written alone: it shares definitions, retention periods and escalation routes with our other pages, so a rule you read here matches what you find when you open the...
The rules you accept at registration sit beside this policy and share its definitions, so the same words carry the same meaning on both pages.
Our cookie page lists each tag we load and what it does, and anything described there falls under the consent and storage wording you are reading here.
The payments page shows how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers are handled, while this policy explains what we store about those transfers.
Identity checks described on our verification page use the same documents and the same retention periods this policy sets out, so you are never asked twice.
Login protection and device rules on the security page match the access controls promised here, including how we confirm an account request really comes from you.
If a privacy request is refused or delayed, the complaints page shows the same escalation route this policy names, with the same response timelines.
Closing your account follows the deletion schedule set here, and the closure page repeats those steps so nothing about your stored data changes without notice.
The layout is deliberate: summary first, detail after, contact routes at the end, so you can read the short version and still find the clause behind it. Every...