Shared Definitions
Words like account, region and supported access are defined once and reused, so nothing on this page quietly means something different when you open our privacy or payments wording.
Every rule that touches your wee999 account lives on this page: how you register from Pakistan, what fair use means inside the lobby, and how withdrawals settle through...
Access to wee999 depends on the law where you live, so our policy pages name supported regions instead of assuming one global rule. When you register from Pakistan, you accept the account terms tied to that region, and those terms follow you if you move. Payment clauses sit alongside the general wording: JazzCash, Easypaisa, SadaPay and Raast transfers each settle on their
own schedule, and the clause sets out what happens when a transfer fails or is sent back. We update these pages whenever a rail, a tax treatment or a regional rule changes, and the version live here is the one that governs your account from the moment you use it onwards. Anything older stops applying the day a new version goes live.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Terms questions rarely arrive at a convenient hour, so our desk keeps Pakistan Standard Time and answers through live chat inside your account, email, and WhatsApp. If your query touches a JazzCash or Easypaisa transfer, keep the reference handy and we can usually close it in one exchange. Anything about wording or jurisdiction goes to a second check by our policy team the same working day.
Open your account and the chat window sits one tap away, staffed through Pakistan Standard Time for terms questions, failed transfers and stuck verifications, with a reference number issued for every conversation so nothing gets lost between shifts.
Anything a first reply cannot settle moves to email, where our policy team answers jurisdiction and wording queries with a written position you can keep, usually within one working day of the chat closing.
Chats started on our WhatsApp line link straight into the same queue, so you never repeat yourself, and screenshots of a JazzCash, Easypaisa, SadaPay or Raast receipt can be attached on the spot.
Our policy pages are drafted by the compliance staff who run the account systems day to day, not by a copywriter working from a template. Before anything goes live, a second pair...
We write policy in the same English we use in support chats, so a clause about a failed Easypaisa transfer reads the way our staff would explain it to you on the phone.
Every edit to a legal page carries a date and a one-line summary, so you can see whether a rule about your account shifted after you registered or stayed exactly as it was.
Drafts pass through the staff member who owns the process and a second colleague who tests the wording against live account behaviour before the page is published at all.
We describe only what we operate: named payment rails, support hours in Pakistan Standard Time, and account rules you can verify the moment you sign in and use the lobby.
Terms are written for readers in Pakistan rather than translated from elsewhere, with JazzCash, Easypaisa, SadaPay and Raast named as the rails the clauses actually refer to in practice.
If a clause reads badly or misses a case you have hit, tell the support desk and it goes back to the policy team for a rewrite rather than sitting unnoticed for months.
Our legal pages share one voice and one set of definitions, so a term you read here carries the same meaning on our account, privacy and payments pages. Each page links to...
Words like account, region and supported access are defined once and reused, so nothing on this page quietly means something different when you open our privacy or payments wording.
The table showing where access is available appears in identical form on each legal page, so you never find one page permitting something another page quietly rules out.
Every clause that depends on another page carries a link to it, so you can move from an account rule straight to the payments wording without hunting through menus.
When a rail such as Raast changes its settlement window, we update the payments clause and the account clause together, then publish both with the same effective date.
Policy pages follow the same plain register as our support replies, which keeps the jump from a chat message to a formal clause smaller than you might expect from a platform this size.
Where two clauses could be read against each other, the more specific one governs and the general wording carries a pointer, so disputes do not turn on which page you happened to open.
Every legal page prints cleanly to a single document with the revision date shown first, because some readers still want a paper copy of the terms attached to their account.
Our legal pages are built to be read on a phone between other things, so the structure stays deliberately shallow. A revision stamp shows when the wording last...