Account Terms
The rules you accept when you open your account: eligibility, the one-account policy, closures and what happens to a balance when you leave. This page states the version that governs.
Every account on lengobet.app runs on one set of written terms, and this page sets them out in plain English. You will find the rules on regional access...
Access to lengobet.app is offered only where local law permits, and the terms you agree to are the ones shown for your supported region when you open an account. Some clauses change by market: the rails listed for Pakistan, the currency a wallet holds, and how a disagreement escalates. Where a rule cannot apply in your region, we remove it from your
agreement and tell you which version is live.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Legal questions rarely fit a chat box, so we run three paths for them. Each lands with a person who can read your account record, check the clause in question and reply in writing. We answer within one working day, and every reply carries a reference you can quote later.
Send a message through your account inbox when you want a clause explained. We read the exact wording you point to and answer in plain English.
Ask us to close your account at any time and we confirm the closure in writing, settle the balance in your wallet and tell you the retention period.
If you disagree with a decision, reply to the thread and ask for a second look. Another team member reads the case and sends the outcome with reasoning.
We write our own terms rather than lifting a template, and the drafting rules hold across every page. Plain sentences, no hidden sub-clauses, one named owner per section. When something changes we...
Every clause carries a version number and a revision date. When we amend one, the earlier wording stays archived so you can see exactly what moved and when it changed.
We cap each clause at a few sentences and avoid cross-references that force you to open five pages. If a rule needs length, we split it rather than bury the point.
Pakistani readers see the clauses that match the rails and rules live here. Where a provision fits only another market, we mark it clearly rather than leave you guessing.
Each policy page lists the team that drafts and signs it off, so you know who to address when a sentence reads badly. We do not hide behind an anonymous desk.
When a clause changes we log the date, the section number and a short reason. You can open that log from any policy page and follow the trail without asking support.
Before publishing, a second editor reads for ambiguity, missing definitions and inconsistent rail names. Nothing goes live until both readings agree and the wording is signed off.
Our policy pages share one vocabulary so a term keeps the same meaning wherever you read it. If account closure means something under the terms, it means the same on the privacy...
The rules you accept when you open your account: eligibility, the one-account policy, closures and what happens to a balance when you leave. This page states the version that governs.
Covers what we store when you register, how long we keep it, and the request channel you use to ask for a copy or a deletion of your record.
Lists the storage our pages set, which ones keep you signed in, and how to clear them from your browser. The naming matches the account terms so nothing reads oddly.
Explains the identity step we run before a first withdrawal clears, the documents we accept from Pakistani account holders, and how long a check usually takes to complete.
Sets out how a disagreement moves from support to a senior reader, what you need to include, and the timeline we hold ourselves to at each stage before a final answer.
Names every rail we support, the currencies a wallet can hold, and when funds clear for use on the site.
Repeats the exit wording: how to close your account, what we settle first, and the record-keeping period, so you can compare them side by side.
The layout is built for skimming. A jump menu sits near the header so you can reach a clause in one tap, each block carries a...
A sticky list of anchors sits beside the copy on desktop and above it on mobile, so you can skip straight to the clause you came for.
Every block shows the date it was last amended. When two pages disagree, the later stamp wins and we point you to the newer wording in our reply.
A single line near the header names the market your agreement belongs to, telling you which rails and clauses are live before you read any further. It saves guesswork.
Each rule has a fixed number that does not shift between versions, so a support reply can cite exactly the clause it means and you can find it fast.
A short plain-English summary opens each section, with the fuller wording underneath. The summary helps you scan; the full text is what applies to your account.
You can download the page as a PDF from the footer and keep it beside your records. We hold the same file for every version we publish.