Terms Of Use
Covers the rules you follow while using your account, while this policy handles what we record as you do. The overlap is deliberate and the phrasing matches on both sides.
LEGAL REFERENCE
Your Privacy Policy, Set Out Plainly
One privacy policy covers every account we open, and it is written to be read in a single sitting rather than skimmed. We set out what we collect...
Single Policy, Every AccountPlain English ThroughoutCorrect Or Export On RequestDated Revisions
Where This Policy Applies To You
Where local law permits, this policy governs everything tied to an account we hold for you, from the moment you register to the point your records are deleted. Because we look after accounts opened from several supported regions, a few clauses change depending on where you are signed in from. If you register in Pakistan, Pakistani rules on record keeping shape how
long we keep transaction references tied to JazzCash, Easypaisa, SadaPay, NayaPay or Raast. From elsewhere, the local rules of that supported region apply to the same records. We do not move your data into a market we cannot support, and we do not sell account records to anyone. Any clause that depends on where you are is written so one reading tells
you which version applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW IT STAYS CURRENT
Who Keeps This Policy Current
This policy is not a template we set and forget. A small in-house team drafts the wording, a data-protection lead checks it against how our systems actually behave, and an outside reader...
Drafting Owner
One named writer owns every paragraph on this page. When a clause reads badly, that person rewrites it rather than pasting new legal boilerplate over the wording you already agreed to.
Data Mapping Check
Every place our account flow collects something is listed against the clause that describes it, so nothing you type into a form sits outside the wording you accepted when you joined.
Retention Audits
We test our own deletion schedule twice a year and publish the outcome as a dated line, so you can tell how long each kind of record really stays on file.
Access Logging
Staff access to account records is role-based and written to a log. When those logs are audited, any finding that needs different wording is folded into the next revision.
Plain-Word Pass
Before publication a second reader hunts for jargon and rewrites it. If a sentence needs a lawyer to decode it, it does not reach this page in that form.
Outside Sign-Off
An independent reader from outside our team goes through each full revision before it goes live, and flags any clause that asks for more than the platform actually needs.
ACROSS OUR PAGES
How This Policy Sits With Others
This privacy policy works alongside the other documents you accept when you open an account, and we keep the phrasing consistent between them. Where two pages touch the same record, such as...
Cookie Notice
Deals with the small files stored in your browser. Where one of those touches account data, this privacy policy says so rather than leaving you to join the two pages together.
Account Verification
Explains the documents we may ask you for. Here we state how long those documents are kept and which staff can open them once a check has closed.
Payment Terms
Sets out how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers are handled. This page states what reference data we store from each one and for how long.
Sportsbook Rules
Covers market settlement and how bets are processed. Privacy wording joins it at the point your betting history becomes a record we hold against your account. The retention line is identical.
Security Practices
Describes logins, device checks and session handling. This policy explains which of those events get written to a log and how long each entry lives on our systems.
Complaints Path
Tells you how to raise a dispute. When a complaint involves personal data the same route reaches the privacy desk, so you never need to find a second address.
ON-PAGE ELEMENTS
What You See On This Policy Page
We built this page to be scanned rather than endured. A sticky section menu sits on the left so you can jump straight to the clause you care...
Sticky Section Menu
A fixed list of clauses stays visible as you scroll...
Last-Updated Stamp
Every clause shows the date it last changed, and the...
Plain-Language Summary
A short block above the formal wording says the same...
Downloadable Copy
You can save the whole policy as a file from...
Print-Friendly Layout
Printing keeps the clause numbers and headings intact. Nothing important...
Highlighted Keywords
Payment rail names, retention periods and contact routes are marked...
Privacy Policy Questions We Hear Most
It covers every record tied to your account, from the name you register with to payment references created by JazzCash, Easypaisa, SadaPay, NayaPay or Raast, plus how long each one stays on file.
No. We do not sell account records, and we share them only where a clause on this page says we may, such as with a payment partner completing a transfer you asked for.
Message the privacy desk from inside your account and request a data copy. We assemble everything we hold and send it to your registered contact within two working days.
Where local law permits, yes. Some transaction references must stay for a set period after closure, and the policy says which ones and for how long before anything is erased.
Rarely, and never quietly. Each revision carries a date, we note what moved, and the summary at the top of the page is rewritten at the same time as the full wording.
Your login no longer works once the account is marked closed, but a small set of records stays until the retention period in the policy runs out. After that they are deleted.