What Our Privacy Policy Covers
One page, plain wording: what 888et records about your account, how long we hold it, and which teams can see it, all readable before you open an account...
The Rules Behind This File
We wrote this policy for anyone using 888et from supported regions, and it covers the account, wallet and lobby activity tied to that account. Where local law permits, we collect only what a payment, verification or support step actually needs; if a requirement does not apply in your region, we skip it. Local rails such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast
sit behind bank-grade encryption, so we never see your full wallet credentials and your PIN never reaches our servers. Records are kept for the period a regulator, processor or dispute may require, then removed on a set schedule. You can write to us to ask what we hold, ask for a correction, or ask us to close the file where the law
allows it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The Team Behind These Words
This policy is drafted by the same operations team that runs 888et day to day, then checked by our legal editors before it goes live. We date every change, keep older versions...
Named writers
Every revision lists the team that prepared it. You can see whether the change came from operations, payments or legal, telling you how close that clause sits to your account.
Change dates
Each version carries the date it went live plus a short summary of what shifted. Older copies stay archived so you can compare what applied when you joined.
Plain wording
We avoid dense legal phrasing where a normal sentence works. Sections stay short, headings describe the point, and anything affecting your data sits above the small print for your file.
Second check
A second pair of eyes reads every draft before publication and again whenever a payment partner changes its rules. That catches stale wording on retention and deletion windows.
en-PK language
The page is written for Pakistani readers in clear English, using the same terms our chat agents use. If a phrase confuses you here, it confuses you in chat.
Correction window
Spotted something wrong or out of date? Message the data desk and we log it as a policy correction, then publish the fix with the next dated revision.
Same Promise On Every Page
You will find matching language on our terms page, our cookie page and the account rules page that sits beside this one. Where those pages overlap with privacy...
| Account rules | The account rules page sets out how you sign in, what we verify and when access can be paused. Privacy covers the data layer behind it for your file. |
|---|---|
| Cookie page | Our cookie page lists each script we load and what it does. This policy explains why we collect the data behind those scripts and how long it stays. |
| Terms of use | Terms of use covers conduct and account closure. Where a line there touches your data, this policy explains the record-keeping side and the same contact channel. |
| Wallet terms | Wallet terms explain how JazzCash, Easypaisa, SadaPay, NayaPay and Raast settlements clear. This policy handles what we log about those transactions and who can see it inside our tools. |
| Chat transcripts | Chat transcripts are stored under the same retention window described here, so a support conversation follows these privacy rules rather than a separate silo run by another team. |
| Version history | Version history shows which clause changed and on what date. It is the quickest way to check whether a data practice you agreed to has been updated afterwards. |
| Contact page | Our contact page carries the working channels and hours. Use it when a privacy question needs a written reply you can keep for your own records at home. |
Layout Choices That Keep It Clear
When you open this page on a phone, the summary chips and section headings load before the long clauses, so you can find your answer without scrolling the...