Terms of Service
Account rules and privacy rules share the same defined terms, so the age you must be and the details you must give match on both pages without contradiction.
lengo bet keeps one plain privacy policy for every Pakistani account, and this is it — what we record when you join, how your JazzCash, Easypaisa, SadaPay and...
When you open an account we store the details you type in yourself: name, date of birth, mobile number, email address and city. Your funding history arrives as a reference from JazzCash, Easypaisa, SadaPay or Raast, and we keep that reference so any settlement can be traced if you query it. Device data such as IP address, browser type and login times
helps us block anyone reaching for an account that is not theirs. We use all of it to run your account, confirm your age and identity, settle withdrawals, answer your messages and meet the record-keeping duties that bind us where local law permits. We do not sell your personal data. We share it only with payment partners, identity-check providers and hosting suppliers
completing a job you started. Marketing messages are optional, and you can switch them off in your account settings. In supported regions of Pakistan you may ask to see, correct or erase what we hold.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions should not sit in a general queue, so we route them to one desk. Whatever you send, quote your registered mobile number so we can match it to the right account without asking you to repeat a long form twice. We aim to acknowledge every data request within two working days.
Open your profile, choose privacy, and you can download a copy of your stored details, adjust marketing switches or begin an account closure without contacting anyone.
Write to our privacy desk with your registered mobile number and the request in your own words; we reply from a monitored inbox and keep the thread open until it closes.
Chat handles quick questions, and the agent can pass your case to the privacy desk with the transcript attached, so you never retype the whole story.
This page is written and updated by the team that operates lengo bet, not by an outside agency. The person who signs off each revision also owns data handling for Pakistani accounts...
The people who run your account wrote this page, so what it says about retention, sharing and account closure matches what happens behind the login screen.
Each update is stamped with a date at the top, and the archive keeps earlier drafts, so you can see which clause changed and when it changed.
We skip legal padding. Where a rule comes from a regulator or a payment partner, we say so inside the sentence rather than burying it in a footnote.
One privacy contact owns incoming requests from Pakistan, so escalation does not bounce between departments while a response deadline quietly runs down.
Before we publish anything about JazzCash, Easypaisa, SadaPay or Raast handling, we check the wording against what those partners actually return to us.
If a revision affects your rights, we flag it in your account messages before it takes effect, so nothing important arrives as a silent edit.
Read this page beside our other policy pages and the definitions should line up. We use one set of words for account data, one meaning for retention and one process for requests...
Account rules and privacy rules share the same defined terms, so the age you must be and the details you must give match on both pages without contradiction.
The cookie categories listed there are the same categories described here for analytics and login sessions, including how you withdraw consent from your browser.
What we ask for during verification is worded the same way here, covering which documents we copy and how long those copies stay on file.
Payout timing depends on the rail, so that page covers processing windows while this one covers the transaction record we retain for tracing.
Login alerts, device history and password resets are described there with the same retention periods you will find in the data section here.
If you raise a privacy complaint, the escalation steps and response targets are the same ones set out there for other account disputes.
Where an offer asks for extra details, the promotion page names what is collected and this page explains how long we keep it afterwards.
Policy pages fail when nothing on them can be used, so this one is built from working parts. A short summary sits above the detail, every...
The short version sits at the top: what we collect, why we hold it, how long it stays and who receives it, with links down to the fuller clause.
Marketing and optional analytics run on separate toggles, so you can keep account messages flowing while turning off everything that is not essential.
A dated strip shows how long each category stays with us, from login logs through to transaction records, instead of leaving you to guess.
A simple table pairs each type of detail with the reason we hold it, so you can find your own case without reading the whole page twice.
The page reads in clear English for accounts in Pakistan, and the clauses stay identical if we add another language later, so meaning never drifts.
One button produces a clean copy of the whole policy with the revision date attached, which helps when you want a record outside your browser.