The Rules Behind Your Account
Everything governing your account sits on this page: the terms you accept at registration, how we treat your personal data, the fair-play standards applied at every table, and...
How Our Terms Apply In Pakistan
Our terms are written to work inside supported regions and apply only where local law permits. Opening an account from Pakistan means you confirm you meet the age and eligibility rules in your province, that the funds you use are your own, and that you will keep one account in your own name. We ask for identity documents once, then hold them
on file so withdrawals clear without repeated checks. Tax on winnings stays your responsibility under local rules. Where a term cannot be enforced in your area the rest of the agreement still stands. Payment context matters too: the chips below name the rails referenced across these policies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching A Person About Policy
There is always a route to a person when a clause needs explaining. Our policy desk answers by email, live chat runs through the hours most people in Pakistan are online, and anything unresolved moves up to a named handler. Keep your account email handy so we can match your question to the right record, and you will not have to hunt through menus to find someone.
Policy Helpdesk
Write to the policy desk from the email on your account and a person replies, usually inside one working day. Quote your ticket number and we pull the exact clause you asked about.
Live Chat Window
Chat runs daily from morning until late evening Pakistan time. Bring a screenshot of the clause you are reading and the agent can talk you through that section line by line.
Escalation Queue
If the first reply does not settle matters, ask for escalation. A senior handler opens the file, checks the clause against your account record and responds in writing within five working days.
Who Writes And Checks These Pages
Every policy page here is dated, versioned and written by the team that runs the account systems. When a clause changes we say what moved and when it starts. No claim about...
Clause Ownership
Every clause names the internal team responsible for it, so a payouts question reaches finance while a table dispute reaches operations. No anonymous copy sits on this page.
Version History
Older versions of each policy stay reachable after an update lands, so you can compare what applied yesterday with what applies today without emailing us for a copy.
Plain Language Pass
Draft clauses go through a plain-language check before publishing, which strips padding that carries no legal weight. Any sentence still needing a lawyer to decode gets rewritten before you read it.
Evidenced Details
We name payment rails, support hours and document requirements because we can point to the systems behind them. Licence numbers or user totals we cannot evidence never appear here.
Change Alerts
Material updates trigger an email to the address on your account with a one-line summary of what moved. Small typo fixes are logged quietly in the version list instead.
Data Handling
Identity documents and account records sit behind access controls limited to the teams that need them, and you can ask for a copy of everything we hold about you.
How This Fits Our Other Policies
Our sibling policy pages, covering privacy, payments, fair play and account security, share one structure so you can move between them without relearning the layout. Defined terms carry...
| Shared Definitions | Words such as account, supported region and verification carry one meaning across every policy page, so a clause read here cannot quietly mean something different elsewhere on this site. |
|---|---|
| Matching Rail Wording | Any mention of JazzCash, Easypaisa, SadaPay, NayaPay or Raast here uses the same labels and sequence as our payment pages, keeping transfer rules consistent for you from start to finish. |
| Privacy Alignment | Data clauses mirror the privacy page wherever the two overlap, so retention periods, access requests and deletion steps are described once and repeated identically wherever they appear. |
| Fair Play Linkage | Table conduct, market voiding and anti-abuse rules are cross-linked rather than restated, which keeps the fair play page as the single home for game-specific policy. |
| Security Scope Split | Login, device and session rules belong to the account security page, while this page covers the obligations attached to holding that account. The same paragraph will not appear in both. |
| Dispute Continuity | Complaint routes set out in our terms match the escalation steps described here, including the five working day window for a written position from a senior handler. |
| Revision Rhythm | All policies are dated in one format and revised on one cycle, so you can tell at a glance which pages changed in a given month and which held steady. |
How This Policy Page Is Laid Out
How this page is built shows what we treat as material. Scope statements come first, then the obligations you accept, then the route a disagreement takes...
Scope First
Each section opens by naming the part of your account it governs, from registration and identity checks through to table conduct, so you never guess whether a rule reaches you.
Ordered Reading
Sections follow the life of an account rather than the alphabet: joining, verifying, transacting, playing, disputing. Reading downward, the sequence maps onto what happens after you register.
Tracked Tickets
Every dispute path closes in a ticket with a reference number you can quote in email or chat, so a conversation never restarts from scratch with a new agent.
Local Context Chips
Chips here name the rails our clauses reference, covering JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so you can see which systems the wording actually touches.
Defined Terms
Terms with a fixed meaning appear in bold the first time they are used and are repeated exactly afterwards, which removes the ambiguity that turns a simple rule into an argument.
Change Markers
Updated clauses carry a visible date and a short marker, so returning readers can spot what moved since their last visit without working through the whole page again.