Shared definitions
Terms such as account, session and payout carry the same meaning on every policy page, so you never work out whether two documents describe the same thing differently.
LEGAL REFERENCE
The Terms That Cover Your Account
Every tdd777 account sits under one set of terms, and this page is where we keep that wording readable. You can see how jurisdiction, account conduct and Pakistani...
Jurisdiction wordingPlain-English clausesAccount conduct rulesPakistan support
How We Set Out Policy For Pakistan
We write our terms the way we run the platform: short clauses, clear headings, nothing that needs a lawyer to unpack. Access depends on where you are, so everything here applies where local law permits and in supported regions only, and we say plainly when a clause cannot apply to your region. Playing rules, payout handling and account conduct sit in one
document, so you check a single page instead of five. Where you fund your account, the same clauses cover JazzCash, Easypaisa, SadaPay and Raast transactions, because a term built for one rail would be useless to you. When wording changes we publish the updated version here and date it, so the copy you read matches what you agreed to.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
EDITORIAL STANDARDS
Why Our Policy Copy Reads Clearly
The people who write these pages also work on the platform itself, which is why the wording matches what happens in your account. We avoid copied templates, we...
Written in-house
Every clause here is drafted by the team that runs tdd777 accounts rather than lifted from a shared template. That...
Dated revisions
When a term changes we publish the new version here with the date it took effect. You can compare what...
Named payment rails
Our terms name the rails you actually use, JazzCash, Easypaisa, SadaPay and Raast, so funding clauses read as something you...
English and Urdu
Policy explanations are available in English and Urdu, and our desk answers in the language you write in. You get...
Account security wording
We describe how two-factor sign-in, session logging and password resets protect your account, and what to do if you spot...
Query-led revisions
Support logs shape the terms. When the same question arrives repeatedly, we rewrite the clause so the answer is visible...
CONSISTENCY CHECK
How Our Policy Pages Stay Aligned
This page is one of several policy documents on tdd777, and we keep them aligned: the same definitions, the same regional wording and the same contact routes run across all of them...
Matching regional wording
Where local law permits and in supported regions appears here, the same phrasing appears on our other policies, so the boundary on access reads identically wherever you check.
Same contact routes
The live chat, email and Urdu phone routes on this page are the ones named in our account and payout documents, so you never chase a different desk per question.
One revision cycle
We revise every policy page in one pass rather than piecemeal. When a clause moves, the linked documents change the same day, which keeps dates and wording in step.
Cross-referenced clauses
Where a rule depends on another document, whether privacy, payout handling or account conduct, we name that page instead of restating it badly in two places. That keeps each page short.
Consistent tone
We write in direct second-person English across the policy set. No page switches into impenetrable legalese, because unclear wording means someone has to contact us to decode it.
Single date stamp
Each policy page shows the date it was last revised at the head of the page. A shared date stamp lets you confirm which version of the terms applied on any given day.
INSIDE THIS PAGE
What You See On This Legal Page
The layout here is built for scanning. Headings tell you what a clause covers, chips show which Pakistani rails the terms mention, and the question list at the...
Named clause headings
Headings name the clause instead of numbering it, so you...
Rail chips
A row of chips lists JazzCash, Easypaisa, SadaPay, NayaPay and...
Support cards
Support cards sit mid-page with chat, email and phone routes...
Visible revision date
The revision date sits near the head of the page...
Reader question list
Short questions at the foot of the page cover the...
Linked policy pages
Where another document matters, whether privacy, payout handling or account...
Questions About Our Terms
The terms on this page govern your account, and they apply where local law permits and in supported regions. If a clause cannot apply where you are, we say so.
Yes. Funding and payout clauses name those rails directly, so the wording you agree to matches the options shown in your account. NayaPay and Raast follow the same checks.
Most requests are checked within a few hours and processed the same working day once verification clears. Timing also depends on the rail you chose and your bank's settlement schedule.
We ask for basic identity checks before a first payout so funds reach the right person. You upload the documents once and we reuse them for later requests.
We sometimes revise a clause to match how the platform operates. Updated versions appear here with a revision date, and we flag what changed so you can see it.
Depending on the clause, we may ask you to fix something, pause a feature, or close the account. We explain the reason and the clause involved, and you can reply through support.