Terms Of Use
Covers what you accept when you open an account: eligibility, one account per person, how the lobby may be used, and what follows if a clause is broken.
LEGAL REFERENCE
The Legal Terms Behind Your Account
Open an account and one connected set of terms applies — your data, your transfers through JazzCash, Easypaisa, SadaPay and Raast, and how disputes are handled where local...
Terms of usePrivacy termsCookie rulesAccount clausesSupported regions
How Our Policy Pages Work Together
Our policy pages work as one connected set: terms, privacy, cookies and account clauses all point at each other, so you never have to guess which one governs a situation. Access is offered on a jurisdiction-dependent basis, which means we accept sign-ups only where local law permits and our supported regions list allows. Payment clauses follow the same logic, so how a
JazzCash, Easypaisa, SadaPay or Raast transfer is treated depends on the region your account is registered in. Where a clause conflicts with a mandatory local rule, the local rule wins. We revise these pages when rules change, and the version published here governs your account from the day you open it. Clauses carry dates so you can see which version applied when.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
LEGAL DESK CHANNELS
Where To Send Policy Questions
Policy questions go to the same team that runs your account, so nothing gets lost between departments. Quote your account number and the clause heading, and the reply comes back in writing. Response hours for each path sit beside it.
Team online
Policy Email Line
Mail keeps a dated record, which suits written policy replies. Send your account number and the clause heading, and the case is logged the same working day.
Chat Window For Access
Chat handles quick points about account access, verification documents or a page that will not open. The team can see your account while you type, and formal answers move to email.
Escalation Route
If a reply does not settle things, ask for escalation. You get a reference number, a named handler and a stated reply window, plus the route outside our process.
EDITORIAL STANDARDS
How These Pages Stay Accurate
Rules move and these pages move with them. Each one carries a revision date, an editorial role instead of a personal name, and a summary in everyday English...
Clauses Written In-House
These clauses come from the people who run accounts, transfers and live tables daily, not from an outside agency repurposing...
Revision Dates
Every policy page carries the date of its last edit. If you saved the terms months ago, the revision date...
Plain Summary First
Each page opens with a short summary in everyday English, then the full clause. The summary helps you navigate; the...
Region List Checks
We hold a supported regions list and check it when rules shift. If a region leaves the list, affected accounts...
No Invented Claims
You will not find licence numbers, awards or player counts on these pages unless they can be checked. Where a...
Local Rule Priority
Where a mandatory Pakistani rule clashes with a clause written here, the local rule takes priority. You get the same...
PAGE SET CONSISTENCY
Why Sibling Policy Pages Match
Terms, privacy, cookies, account rules and payment clauses are drafted as a single set with shared defined words. A term means the same thing on every page, so you can read them...
Privacy Terms
Explains which data we collect, why, how long we hold it and who can see it. Verification documents and payment references from Easypaisa or Raast sit under this page.
Cookie Rules
Covers the files that keep you logged in, remember your language choice and measure which pages get read. Non-essential cookies can be switched off in your browser without losing access.
Account Rules
One account per person, accurate registration details and no shared logins. We also set out how duplicate accounts are spotted and what happens to balances on closure.
Payment Clauses
How transfers through JazzCash, Easypaisa, SadaPay and Raast are credited, how long withdrawals take, and what we do when a reference does not match an account name.
Complaints Path
Step one is a written request to support. Step two is escalation to a senior handler with a reference number. Step three sits outside our process where local rules allow.
Change Log
Each policy revision is dated and described in a single line, so you can see what moved without comparing two whole documents side by side. Older versions are sent on request.
What You See On Each Legal Page
The layout stays deliberately plain. A summary box opens each page, defined words are gathered at the foot, and every page carries a revision date plus...
Summary Box
Every policy opens with a four-line summary box stating what the page covers and when it changed. It links straight to the clause it describes, so you get the point first.
Defined Terms Panel
Words with a fixed meaning — account, transfer, supported region — are gathered at the foot of each page with links back to where they first appear, so there is no guessing.
Revision Marker
A revision date sits in each page header, with a one-line description of the last edit. You can spot whether a clause you relied on has moved since you last read it.
Contact Block
Each page closes with policy email, chat hours and the escalation route in one block, so you never leave the clause you are reading in order to ask about it.
Section Anchors
Long clauses are split into anchored headings, which lets a support reply point you at an exact paragraph instead of a wall of text. Every anchor carries its own short label.
Change History
The foot of each page lists earlier revision dates with a short description of each edit, so a clause you reopen can be compared against a version you saved.
Questions We Get About Legal Terms
Four pages govern your account: terms of use, privacy terms, cookie rules and account rules, with payment clauses inside the terms. All apply from day one, and each links to the others.
Access follows our supported regions list, which we keep current against local law. Where your area is covered, registration needs a valid ID and a payment account in your own name.
They can, when rules or payment handling shift. Revised pages carry a new revision date and a one-line description of the change, and material edits reach you by email first.
The mandatory local rule wins and the conflicting clause falls away for your account rather than blocking you. A support reply will name the clause and say what applies instead.
Quote the page name and clause heading in a policy email, with your account number. Written questions get written answers, which keeps a record you can revisit later.
Identity documents sit in a restricted store that only the verification team can open, while payment references from JazzCash, Easypaisa, SadaPay or Raast are held against your account record.