How the 777 gems legal framework works
Every account you open with 777 gems sits inside a written legal framework, and this page gathers it in one place. You will see how our terms apply...
Where our terms apply and how we read them
The legal posture behind 777 gems is simple to state and firm in practice. Everything here operates where local law permits, and access can differ between supported regions, so a clause applying to one country may not apply to the next. In Pakistan our account terms sit alongside the rails we use — JazzCash, Easypaisa, SadaPay and Raast — because money movement
raises most questions. When a transaction is held, the reason is usually verification: the name on your account must match the wallet name. We write in plain English and update the text whenever a partner changes its requirements. Where local law conflicts with our wording, the local rule wins and we adjust to match it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The standards behind our policy wording
Policy text is only useful if you can trace who wrote it and why. Each entry here is maintained by the team that runs the account flow, checked against our live terms...
Named authorship
Every policy entry carries the team responsible for it, so you know whether you are reading account terms, payment rules or regional access wording instead of anonymous text.
Dated revisions
Each revision is stamped with the month it took effect and the previous wording stays available on request, so you can see which version applied to your account.
Plain-English drafting
Clauses are rewritten until a reader without a legal background can follow them, which is why these pages lean on short sentences and examples from real account cases.
Payment-partner accuracy
Rail names and processes are checked against JazzCash, Easypaisa, SadaPay and Raast documentation, and we correct the wording as soon as a partner changes its own requirements.
Region-aware wording
Statements that depend on your location are labelled as such and name the applicable region, so you are never left guessing whether a clause covers you where you live.
No invented claims
We avoid licence numbers and account counts we cannot evidence, and would rather publish a shorter page than decorate it with figures that nobody can verify independently.
How this page lines up with other policies
Our policy pages share one vocabulary, so the same word means the same thing wherever you meet it. A term defined here keeps that meaning on the account...
| Account terms | Account terms set the baseline: who may hold an account, what verification asks of you and which conduct leads to suspension. Every other page extends them rather than contradicting them. |
|---|---|
| Transaction rules | Transaction rules reuse the same definitions, covering how JazzCash, Easypaisa, SadaPay and Raast transfers are matched to your registered name before any release from our side. |
| Regional access | Access wording is written once and reused, so a reader in a supported Pakistan region meets identical language about where our services may and may not be used. |
| Privacy wording | Privacy text reuses our definitions of account data, verification documents and wallet references, which keeps the two documents readable side by side instead of contradicting each other. |
| Dispute handling | Dispute handling repeats the escalation ladder described elsewhere, from live chat to a written decision, so you are never offered two different routes to the same outcome. |
| Revision log | Every revision records the page it touched and the reason behind the change, which keeps separate policy pages from drifting into subtly different versions of one promise. |
| Reader corrections | Corrections you raise are checked against the live terms and pushed to every page carrying the same clause, not only the one you happened to be reading. |
The visible elements behind these legal pages
This page is built so you can find a clause and follow it without asking anyone. Headings name the subject, the body states the position, and...
Named clause headings
Each heading names the exact subject it governs, so you can reach jurisdiction wording, account conduct or verification rules without reading three unrelated paragraphs first.
Region badges
A small badge sits beside any clause that behaves differently between supported regions and names the region concerned, rather than leaving you to infer it from context.
Rail chips
Chips underneath a clause list the Pakistani rails it touches, from JazzCash and Easypaisa through SadaPay and Raast, so the money side of a rule stays visible.
Version line
A short line at the top of each policy page shows when the text last changed, letting you compare today's wording with what applied when you opened your account.
Contact strip
The support strip sits at the foot of every policy page with chat, email and WhatsApp routes, so a question raised mid-read can be answered without navigating away.
Readable length
Sections are kept short enough to finish on one screen, on the reasoning that a clause nobody reads protects nobody, least of all the person it was written for.