Account terms
Registration terms carry the same definitions used on this page, so eligibility, verification and closure are described once and referenced elsewhere rather than redefined.
Every account you open with us runs on a written set of terms, and this is where you read them before you register. The page sets out how...
Our terms are written to work alongside Pakistani law rather than around it, so the clauses you accept at registration are the ones we apply when you deposit, wager or withdraw. Access is offered where local law permits, and individual features may be limited in particular supported regions. When you move money through JazzCash, Easypaisa, SadaPay or Raast, that provider's rules sit
alongside ours, and the wallet name must match your account name. Verification is completed before a first withdrawal is released, not afterwards. Any change to these terms appears on this page with its effective date, and continuing to use your account means you accept the updated wording. Nothing here removes a right you hold under Pakistani consumer law.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
These pages are maintained by the same team that handles your account day to day, which is why the wording matches what you see in the lobby. Each edit is dated and...
Each set of terms carries the date it took effect, so you can tell which wording governed a decision made months ago. Older versions stay on file.
When you ask why something happened on your account, our reply quotes the numbered clause behind it rather than paraphrasing, so every answer stays checkable against this page.
Long clauses carry a short English summary written for readers in Pakistan, so the meaning lands first. The full clause still governs if the two ever seem to differ.
Wallet and bank rails arrive with their own terms, and we state plainly where your JazzCash, Easypaisa, SadaPay or Raast agreement ends and ours begins.
Nothing is published after one pass. A second reader confirms each change, makes sure payment wording matches what our systems actually do, and flags anything ambiguous.
We describe only what we can show: the rails we support, the languages we answer in and the hours our desk runs. Figures we cannot evidence do not appear here.
This page does not stand alone. It shares its definitions with the sibling policies listed below, and we keep those documents in step whenever a rule changes. Amend a clause in one...
Registration terms carry the same definitions used on this page, so eligibility, verification and closure are described once and referenced elsewhere rather than redefined.
Data handling, retention and access requests are set out there using identical jurisdiction wording, so no second definition of a supported region exists.
Stored browser data, session handling and your choices are written in line with the account terms, including how a session cookie keeps you signed in.
Wallet and bank rails, processing windows and name-matching rules sit here, naming JazzCash, Easypaisa, SadaPay and Raast in the same order used site-wide.
Any offer carries its own qualifying conditions, expiry and wagering wording, and those conditions sit alongside these terms rather than replacing them.
How a dispute is logged, who answers it and when it escalates is written once, matching the escalation path described further up this page.
Identity and address checks, accepted document formats and the point a withdrawal is released follow the same sequence here and in the account terms.
This page is built to be read in pieces. A dated header, numbered clauses and short summaries sit above the full wording, and a change log at the...