LEGAL REFERENCE

Privacy Policy for Your bettor app Account

This page sets out how bettor app collects, uses and stores the details you share when you open an account, so you always know what happens to your...

Identity dataPayment recordsDevice signalsSupport tickets

Explore The Lobby Read FAQ

What We Collect and Why

When you open an account with us, we ask for your name, date of birth, contact number and a copy of your identity document so we can confirm you are eligible to hold an account where local law permits. Transfers you make through JazzCash, Easypaisa, SadaPay, NayaPay or Raast are handled by those providers, and we keep only the reference number needed

to match a payment to your file. We also log device and connection signals such as IP address and browser type so unusual sign-in attempts stand out. Your activity is recorded so balances, pending withdrawals and later queries can be checked. Records are kept for the period local rules set in supported regions, then deleted or anonymised, and you can ask us

to correct anything inaccurate.

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

ASK OUR DESK

Contacting Us About Your Data

If you want to see, correct or remove the data linked to your account, our desk handles those requests directly. We reply...

HOW WE CHECK

Who Checks This Policy Text

The wording on this page is written and checked by the team that runs our account systems, and we revisit it whenever a payment rail, a supplier or...

Operating team

The people who build our sign-in, payment and withdrawal flows write these paragraphs, so each sentence reflects how the systems...

Data stewards

A small group keeps the record of what we hold, how long we hold it and which supplier can see...

Payment partners

JazzCash, Easypaisa, SadaPay, NayaPay and Raast each publish their own handling terms, and we point you to those so you...

Security checks

Sign-in monitoring, encrypted connections and restricted staff access are checked on a regular schedule, and anything that fails the test...

Plain-English edits

We rewrite a block when readers tell us a sentence is confusing, and we date each revision so you can...

Region awareness

Rules differ between provinces and between supported regions, so we flag where a practice depends on local law rather than...

How This Policy Sits With Our Other Pages

Our account terms, payment pages and this policy are meant to be read together. Where one page covers a topic in more depth, we say so plainly instead...

Account terms

The account terms explain eligibility and what we expect from you, while this policy explains what we hold about you, so the two pages rarely repeat each other.

Payment handling

Payment pages describe how a JazzCash, Easypaisa, SadaPay or Raast transfer moves, and this policy adds the narrower point of which transaction records we keep.

Cookie notice

Cookies and similar storage are listed on their own page, and this policy only describes why we set them, not the full list of names and lifetimes.

Withdrawal rules

Withdrawal rules cover timing and verification steps, while the data section here covers the identity documents we keep on file to support those checks afterwards.

Security practices

Our security page talks about protected connections and staff access, and this policy explains which of those measures create a data record tied to your account.

Complaints route

If a dispute moves beyond support, the complaints route sets the timeline, and any data you send during that process is kept under the same rules described here.

Language and region

We publish in English for Pakistan, and where a data practice depends on supported regions or local law, both pages use the same wording so nothing contradicts the other.

How We Lay Out This Policy

We keep the structure steady so you can find a topic without reading the whole page. Headings follow the order of an account journey, each block...

Summary badges

The short labels at the top of each block give you the subject at a glance, so you can decide whether a section needs a full read before you scroll.

Plain paragraphs

We avoid dense legal formatting where a normal sentence will do, and we keep each block to a handful of lines so a phone screen is never overloaded.

Named suppliers

Where a third party handles data, we name the category of work they do rather than hiding it behind a vague phrase, so you can see the role each one plays.

Date stamps

Each revision carries a date, which tells you whether the wording you are reading is the version that applies to your current account activity or an older copy.

Cross links

Related topics link to the page that covers them in more depth, so you can move from a short paragraph to a fuller explanation without searching the site.

Download option

You can save or print the whole page, which is useful if you want a copy of the wording that was live on the day you opened your account.

Questions We Get About Your Data

We ask for your name, date of birth, contact number and an identity document, because we have to confirm you can hold an account where local law permits.

No. Those providers handle the transaction themselves, and we keep only a reference number so a transfer can be matched to your account during a balance check.

Retention follows the periods local rules set in supported regions, after which we delete or anonymise the file. You can ask for a copy of what we hold at any time.

You can close your account from settings or by asking our desk. We remove what we no longer need, and keep only the minimum that a rule still requires.

Access is limited to staff who need it for verification, payments or support, and every view is logged so we can trace who opened a record and when.

Some suppliers run systems from other countries, and when that happens we use contractual terms that keep your data under the same protections described on this page.

Send it to our privacy inbox or raise it in live chat. We confirm receipt, look into the point and reply with what we found and what we changed.