LEGAL REFERENCE

The Legal Terms Behind Your city 777 Account

This page holds the legal terms behind your city 777 account: how we describe the service, what you accept at sign-up, how your data and transfers are handled...

Account termsSign-up agreementData handlingDispute stepsRevision dates
Explore The Lobby Read FAQ
city 777 The Legal Terms Behind Your city 777 Account

How These Terms Apply Where You Live

Legal wording has to travel. Open an account from Lahore, Karachi or Islamabad and the clauses you accept are the ones written for Pakistan, not a copied set from another market. Our terms name the rails you actually use — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — because deposit and withdrawal rules shift with the channel. Where local law permits, we operate

in supported regions and describe access that way rather than promising worldwide availability. If a clause cannot apply in your province, we say so plainly and set out what replaces it. Currency handling, verification and closure each get their own paragraph, so nothing sits buried in a footnote. Section headings follow the order of the account journey, from registration through to deactivation.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

LEGAL SUPPORT

Where to Take a Legal Question

Questions about a clause should not sit unanswered. Our support desk handles terms-related queries and routes anything it cannot resolve to the team that maintains this page. Write in with the section heading you are reading and we will reply with the clause and the reason behind it for your account. Chat runs all hours; email usually lands within one working day.

Team online

Compliance inbox

Email the team that maintains this page when a clause needs explaining. Send the section heading with your question so the reply quotes the exact wording you asked about.

Live chat

Chat is staffed through the day and overnight, which suits evening sessions after work. A payment dispute goes to a specialist queue and you keep the same thread until it closes.

Account records

Ask for a copy of the clauses you accepted at registration. We return that version with its date stamp, so you can compare it against any later change.

POLICY ACCOUNTABILITY

How We Keep These Terms Answerable

A legal page is only worth the team standing behind it. Ours is maintained by the same people who build the platform, so a change in how withdrawals...

Named authors

Every revision lists who wrote it, so you can tell whether a payments change came from our finance desk or...

Dated versions

Each revision carries the day it took effect and the day the previous wording stopped applying. Ask for the older...

Change markers

Altered paragraphs are marked rather than quietly swapped. Open the page after an update and you can see which clauses...

Plain wording

We avoid clauses only a lawyer can untangle. Where a rule must be technical, the paragraph opens with a one-line...

Evidence on request

Ask for the record behind any statement and we send it: the ledger entry for a transfer, the session log...

Correction route

Spot a clause that contradicts what happens in the lobby or on the transaction screen? Send it in with the...

How This Page Lines Up With Our Others

Terms only hold together when the pages around them agree. Our privacy notice, payments page, security wording and this legal page share one set of definitions, so a...

Terms of use
The wording you accept when you register. Definitions here feed every other policy page, so changes are made centrally and reflected in the notices that depend on them.
Privacy notice
Covers what we record about your account and why. Section order matches this page, so you can move between the two without losing your place mid-check.
Payments clauses
Explain how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers are handled, including the references we store. Deposit and withdrawal rules here point across rather than repeating.
Withdrawal wording
Sets out verification before a payout leaves. Timescales quoted there and here stay identical, so a change to processing windows updates both pages in the same release.
Security clauses
Describe how sessions are protected, how you reset access, and what we log. Cross-references run both ways, so a reader arriving from either page lands on the same paragraph.
Cookies wording
Lists the storage your browser keeps when you sign in and how long each item lasts. Framework sentences are shared with this page, so the two read as one document.
Complaints path
Describes how a dispute is raised, the evidence we ask for, and the response times you can expect. Escalation wording mirrors the support block on this page word for word.
ON THIS PAGE

What You'll Find Laid Out Here

A legal page is only as good as its layout. We split this one into short labelled blocks, so you can jump to the clause you need. Definitions...

Labelled blocks Each heading covers one idea: acceptance, transfers, data, closure. You...
Named rails JazzCash, Easypaisa, SadaPay, NayaPay and Raast are written into the...
Region flags Clauses that apply only in certain places carry a region...
Version stamps Every block shows when it last changed. Two dates appear...
Linked clauses Where one rule depends on another, the paragraph links across...
Contact strip The support block sits at the end of the page...

Legal Questions We Get Asked

The Pakistan set applies, in the wording dated at your registration. Clauses flagged for other regions do not bind you, and anything dependent on local law is marked that way.

Yes, and we date every revision. Material changes to transfer or account rules are published before they take effect, and older wording stays retrievable on request so you can check what applied at sign-up.

Transfers through JazzCash and Easypaisa follow the payments clause, which names the reference we store and the verification step before a payout. SadaPay, NayaPay and Raast sit under the same rule set.

Treat it as a drafting error. Send both headings to our support block and we reconcile the texts, then republish each page with a fresh date so no mismatch sits between versions.

No. The account agreement you accepted at registration continues to cover new rails, including Raast and NayaPay. You are asked to confirm again only if a clause tied to that channel changes materially.

Closure is covered in the account block: request it from the settings screen or by email, we confirm the balance and any pending withdrawal, then deactivate access inside the stated window.