Terms Of Use
Our terms cover what you may do with your account; this page covers what we do with your details. Clauses that touch both are worded to match.
This page sets out exactly what we hold about you, why we hold it, and how to have it changed. You'll find registration data, JazzCash, Easypaisa, SadaPay and...
Where local law permits, we process your details on the basis of your consent and the need to run your account. If you sign in from Pakistan, the rules that govern your data also depend on the region you live in, so some clauses shift slightly for supported regions. We never sell your records to outside advertisers. We share the minimum needed
with payment partners so your JazzCash, Easypaisa, SadaPay or Raast transaction settles and shows on your statement. You can ask us to correct, export or erase what we hold, and we answer inside the timelines the applicable law sets. When a rule changes we update this page and flag the revision date at the top. If a clause reads oddly, write to
our privacy desk.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Every update passes three pairs of eyes: the team that writes it, our data protection lead, and an outside lawyer familiar with Pakistani rules on consumer data. We record what changed and...
Clauses start as the explanation we would give on chat, then a lawyer tightens the wording. If a sentence needs a second read, it goes back for a rewrite.
One person owns this page. They sign off every change, keep the revision log current, and answer internal questions about why a clause reads as it does.
A Pakistani practice reads each version against local consumer data rules. Their feedback lands before publication, never after, so you do not read a clause we already know needs fixing.
Our JazzCash, Easypaisa, SadaPay and Raast connections are checked with the partners themselves, so how we describe shared data matches what happens on a real transaction.
Nothing is edited silently. Each version carries a date, and older drafts stay on file so anyone can compare what the page said last month with today.
Chat and email agents are briefed on every update before it ships, so when you ask why we hold a particular detail, the person answering knows.
Privacy sits beside our terms, cookie notice and payments pages, and they have to agree. Where one page states a retention window, the others use the same number. Where we name a...
Our terms cover what you may do with your account; this page covers what we do with your details. Clauses that touch both are worded to match.
The cookie page lists what loads on your device and why. It uses the same consent switches described here, so opting out in one place applies in the other.
Withdrawal timing and verification steps appear on both pages in identical terms. If payments says a check takes a set number of hours, this page repeats it.
Sign-in, two-step verification and device history live on the security page. This policy only adds why those logs are kept and how long they stay.
Promo terms sit on their own page, but the data they lean on, such as wager history, is described here using the same retention windows.
Verification compares your name against your ID. This page explains which documents we store, for how long, and what happens to copies after your account closes.
Complaints reach the same team that handles privacy requests. Escalation steps and response windows are listed on both pages, so the path is never a mystery.
Scroll this page and you see the same furniture each time we publish a legal update: a revision strip at the top, short clause headings you can scan...