LEGAL REFERENCE

Every Rule We Set Out In One Clear Place

We hold our account terms, privacy commitments and withdrawal conditions in a single legal area, written in plain English rather than dense legal language. You can read how...

Legal hubAccount termsWithdrawal conditionsPrivacy commitments
lucky pak Every Rule We Set Out In One Clear Place

How Our Terms Apply Where You Live

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

POLICY DESK

Reaching Us About A Policy Question

Policy questions deserve a real person, not a copy-paste answer, so we keep three direct routes open. Our team reads every message...

Policy Desk Chat Our in-account chat is open daily from nine...
Email Our Legal Team Write to the address on our contact page...
Written Policy Requests If you need a clause explained in writing...
WRITTEN BY US

Who Writes And Maintains These Documents

These pages are written and maintained by the same team that runs the lobby, the payment rails and the support queue, which means a clause is only published once the people operating...

Operator Authorship

Every clause here is drafted by staff who work on the lobby, payments and support desks, so requirements reflect platform behaviour on the day you read them rather than theory copied from elsewhere.

Plain English Drafting

We write Pakistani English without legalese, keeping sentences short and defining terms the first time they appear, because a rule you cannot parse is a rule you cannot rely on.

Payment Rails Verified

Processing times are checked against real JazzCash, Easypaisa, SadaPay and Raast traffic instead of estimated, and we correct these numbers when a rail changes how it clears.

Revision Dates Shown

Each document carries the date it was last revised, so you can tell whether what you are reading is current and request an earlier version if you need one for your own records.

Support Behind Rules

The team answering your policy questions sits beside the people who wrote the clauses and can escalate a genuine gap, which is how corrections reach the page instead of stalling in a queue.

No Invented Claims

We publish only what we can evidence: payment rails we accept, support hours we staff and security steps we run. Where something falls outside supported regions, we say so instead of implying otherwise.

Keeping Our Policy Pages Consistent

Our legal pages share one vocabulary, so a term defined on one document carries the same meaning on the next. When you move between our account terms and...

Matched DefinitionsTerms such as account, withdrawal and verified are defined once and reuse that exact wording across every document, so meanings do not shift as you move between pages.
Same Revision DatesRelated documents are revised together, and the dates match, so you can tell which set of clauses stood at a given moment without comparing pages line by line.
Consistent TimeframesEscalation windows, reply promises and review periods are stated the same way throughout, which means two pages never promise different timelines for one request.
One Set Of TermsMobile, desktop and app all read from the same rule set, so what you accept on one screen holds unchanged on the next and nothing is quietly reworded per device.
No ContradictionsWhen a clause changes in one place, we update every document that references it in the same pass, so you are not left comparing two versions that disagree with each other.
Shared Contact PathsEvery page points to the same policy desk, so a question raised from any document reaches the same team rather than a different queue depending on where you started.
Aligned Payment WordingReferences to JazzCash, Easypaisa, SadaPay and Raast use identical spellings across all pages, keeping withdrawal rules readable regardless of which document you happen to open first.
POLICY HUB

What You Will Find In This Area

The legal area is built to be read rather than skimmed past. Everything sits in one library that you can reach from the footer on any screen, so...

One Policy Library Account terms, privacy commitments, payout conditions and our complaints process...
Summary At The Top Each document opens with a short set of plain sentences...
Region Availability A short statement on each page sets out where access...
Step-By-Step Timelines Withdrawal reviews, verification checks and dispute escalation are laid out...
Security Practices We set out how sign-in verification works, how you secure...
Document History A revision list records what changed and when, so returning...

Legal Questions We Are Asked Most

Each document shows the date it was last revised at the top. When a change is material, we post a short notice inside your account so you meet it the next time you sign in rather than discovering it later.

Availability depends on where you are when you open the account. Where local law permits we serve you in full, and elsewhere we close or limit access rather than invite you into something we cannot stand behind there.

We hold what we need to run your account, verify your identity and process withdrawals through JazzCash, Easypaisa, SadaPay or Raast. Our privacy commitments list each category, why we keep it and how long we retain it.

Yes. You can close your account from inside your settings or by asking the policy desk in writing. We settle any pending withdrawal first, then confirm closure once the funds have cleared through your chosen rail.

We tell you what happened and why, in writing, where the law allows us to explain. You then have a stated period to appeal or send documents, and our compliance desk reviews that submission before anything becomes final.

Start with the policy desk, since most disputes are timing or document questions we can settle quickly. If you are still unsatisfied, our complaints process sets out the next escalation step and how long each review stage takes.

Ask our team and we send a copy by email, or you can read every document from the footer on any screen. Archived versions are available on request if you need to see what stood at an earlier date.