One definition set
Terms used in the account agreement keep the same meaning on every policy page, including the payment and privacy wording, so you never check which version applies to you.
LEGAL REFERENCE
Everything That Governs Your Account, In One Place
Every clause that governs your 666 gmae account sits on this page: how we handle your details, what you accept when you open an account, how JazzCash, Easypaisa...
Terms of usePrivacy commitmentsRail-specific clausesDispute steps
How Our Terms Apply Across Pakistan
Our terms are drafted to travel across supported regions, which means a few clauses change depending on where you are when you sign in. Payment sections name the rails we work with — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — because transfer rules, naming requirements and cut-off times differ between them. Where you see supported regions, read it as places where local
law permits the activity our lobby offers and where our partners can settle in Pakistani rupees. If a clause conflicts with a rule that applies in your province, the local rule wins and we adjust the terms we show you. We version every change and flag anything that affects a withdrawal you have already requested.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
REACHING THE DESK
Who Answers Your Policy Questions
Policy questions are not the same as gameplay questions, so we route them to the team that drafts the wording. Write in with your account number and the section you are reading, and you get a written answer you can keep. Live hours are listed below.
Team online
Policy desk email
Send your clause question to the policy desk and quote the section you are reading. We reply within one working day and keep the answer attached to your account record.
In-account message thread
Signed-in questions about terms, data handling or a disputed withdrawal belong in the message thread, where the whole exchange stays attached to your own profile for later reference.
Live chat during policy hours
For a quick read of a single clause, open live chat between 9am and 1am Pakistan time any day. Wording changes are passed to the policy desk and answered in writing.
HOW WE DRAFT
How These Pages Earn Your Confidence
You should be able to see who wrote a policy and how it was checked before it went live. Each page names the internal team responsible, shows the revision date, and links...
Named owner
Every policy page names the internal team that owns the wording, so you know who to ask when a clause needs explaining instead of working it out alone.
Effective dates
Each version carries the date it took effect and the date it was last touched, so you can tell whether the clause you accepted at sign-up is still the one in force.
Change summaries
When wording is rewritten we publish a short summary of what moved and why, written by the same people who drafted the original clause, before the change goes live.
Plain sentences
We avoid legal padding where a plain sentence does the job, and any defined term is spelled out the first time it appears so you are not chasing footnotes for meaning.
Rail-aware checks
Payment and data clauses are checked against what our Pakistani rails do at the time of writing, covering JazzCash, Easypaisa, SadaPay, NayaPay and Raast settlement practice.
Escalation route
If a written answer does not settle your question, the same page lists the second contact point and the timescale we work to for a policy response on that matter.
CONSISTENCY CHECK
One Set Of Rules Across Every Page
Our terms, privacy and payment pages are written together, so a definition you read here means the same thing when you open a clause elsewhere. Where a rule only affects one area...
Shared revision dates
When one page changes, the pages that lean on it are re-dated in the same release, so the set does not drift out of step with itself for long.
Linked rail clauses
Chips point to the rail your question is about, whether that is JazzCash, Easypaisa, SadaPay, NayaPay or Raast, instead of one clause covering every transfer type.
Same contact routes
Every page lists the same policy desk address and in-account thread, so you do not have to work out which team owns the clause you are asking about.
One access line
Where access depends on local rules, every page uses the same supported regions wording, so the limit you read on one page matches the next word for word.
Matching data promises
What the privacy page says about holding your documents matches what the account terms let us request, including the identification a Pakistani withdrawal may need at settlement.
No buried conflicts
If two clauses pull in different directions we rewrite one of them, rather than lean on a precedence line buried somewhere at the bottom of a page.
LAYOUT AND LANGUAGE
What You See On Our Policy Pages
Policies are dense by nature, so the layout carries some of the weight. Each page opens with the clause that matters most, keeps related rules in the same...
Clause summary box
Each page opens with a short summary of the clause...
Rail chip row
JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear as chips wherever...
Last-changed stamp
Each block shows when it last changed, which tells you...
Boundary markers
Sections that apply only in some places are marked clearly...
Paragraph anchors
Long clauses carry clickable anchors, which means you can send...
Repeated definitions
Where a term is defined in the account agreement, the...
Questions We Get Asked Most Often
The agreement is read under the rules that apply where you are, and only where local law permits the activity we offer. Anything conflicting with a local requirement gives way to it.
Yes, and we tell you when they do. A material change is published with a date and a short summary, and we give notice before it affects a withdrawal already in progress.
Our policy desk drafts and owns the wording, and each page names the team responsible. Nothing here is handed to a party who would answer for how your account is run.
Raise it through the in-account message thread first, so the full history stays attached to your profile. If the written reply does not settle it, the page lists the second contact point.
It can, in small ways. Transfer naming, cut-off timing and settlement days differ between JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so rail detail sits in chips instead of one blanket clause.
The local rule applies, and we adjust the terms we show you rather than asking you to follow something that cannot be met in your area. Where access is limited, we say so.