Your Account Data, Kept In Plain English
Here we set out, in plain Pakistani English, which details 888bets keeps when you open an account and what we do with them. There are no hidden clauses...
How We Apply This Policy
888bets handles personal data according to the rules that apply where you access the platform, so this policy works alongside local requirements rather than replacing them. Where local law permits online account opening, we collect only the details needed to verify you, secure the account and process the payment route you choose. In supported regions, transfers typically arrive through JazzCash, Easypaisa, SadaPay,
NayaPay or Raast, and each route leaves its own transaction record. We keep those records only as long as accounting or fraud-prevention needs require. If a local rule asks for something different from what you read here, the local rule wins, and we will say so clearly. Nothing on this page overrides a requirement that protects you more strongly than we do.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching Our Privacy Desk
Questions about your data should not sit unanswered for a week. Our privacy desk reads every message and replies in straightforward language, so you never have to decode legal phrasing to understand the answer. Tell us what you need — a copy, a correction or a deletion — and we will confirm in writing what we can action under the rules that apply where you live.
In-app messaging
Open your account area and send a data request through the messaging panel. It arrives with your reference attached, so nobody proves identity twice before the desk begins.
Email follow-up
For anything complex the desk continues by email, so you keep one written thread. Send the JazzCash, Easypaisa, SadaPay or Raast reference and we trace the payment record.
Profile settings
Some edits need no help at all. Inside your profile you can update your contact number, adjust notification preferences and switch off non-essential messages; every change is logged.
How We Keep Records Secure
Security work sits behind every page you use, even the quiet ones like this. Account sessions are encrypted, staff access to customer records is limited to named roles...
Limited staff access
Only people in operations and finance roles can open a customer record, and each role sees the minimum its job...
Encrypted sessions
Traffic between your device and 888bets travels over an encrypted connection, including screens where you check a balance or start...
Internal audit trails
Every internal lookup against a customer record is stamped with who opened it and when. Those stamps let a colleague...
Retention windows
We do not keep everything forever. Records tied to payments carry a longer window than marketing preferences, which are dropped...
Local rule first
Where a Pakistani requirement differs from a general clause, we follow the stricter of the two and mark the difference...
Plain wording
We rewrite this page whenever a process changes, so wording stays level with the platform you use. If a line...
How This Page Lines Up Elsewhere
A privacy promise only holds up if the rest of the site agrees with it. So we keep the wording here consistent with the terms you accept at...
| Account terms | Registration terms state which details are required to open and keep an account, while this page explains the handling behind those requirements. Side by side, both describe the same collection points. |
|---|---|
| Cookie notice | The cookie notice covers what sits on your device; this policy covers what sits in our systems. Together they show the full picture of tracking, storage and the switches you can turn off. |
| Transfer screens | Every transfer screen lists the rail you picked and the reference we will see. That naming matches the chips here, so a JazzCash, Easypaisa, SadaPay, NayaPay or Raast entry points to one record. |
| Verification steps | Identity checks at sign-up follow the rules described here: what we ask for, why we ask and how long paperwork stays on file. No request appears at withdrawal time that this page leaves unexplained. |
| Market rules | Market rules explain how a wager settles, while this page explains what we record about it. Both describe one timestamped history, so a settled market and a stored transaction line up. |
| Table rules | Live table and slot rules set out how a round plays, while this page sets out what is kept afterwards. Round identifiers and stake amounts are the only fields stored, nothing more personal. |
| Help pages | Contact routes listed in our help area point to the same desk described on this page. Whether you write from the messaging panel or by email, one team owns the request. |
What You Will Spot On This Page
We designed this page to be read in a couple of minutes rather than skimmed and abandoned. Everything sits in the order you would ask it...
Summary badges
Four short badges sit under the headline so you see the whole scope before scrolling. They cover collection, use, your rights and contact routes, which is this policy in one glance.
Covered rails row
The chip row names the Pakistani rails this policy speaks to, so you can confirm whether your usual route is included. JazzCash, Easypaisa, NayaPay, SadaPay and Raast records are all covered.
Dated revisions
Whenever a clause shifts, the revision stamp changes with it. That line tells you whether anything moved since your last visit, and we list what changed so you need not re-read.
Jump anchors
Section links run down the side so you can move between collection, retention and contact without scrolling. On a phone they collapse into a short menu that stays reachable.
Request form
A short form sits near the page end for data requests, asking only what the desk needs to find your record. Fill in the account reference and send it, and confirmation follows.
Language note
Wording here is written for a Pakistani audience first, so payment names, currency references and support hours match what you already use. Tell the desk if a phrase reads oddly.