Against our terms page
The terms page explains what you may do inside the lobby; this page explains what we record while you do it. Both use the same account holder definition.
LEGAL REFERENCE
How bydy bet Handles Your Account Data
Open your account and you hand us real details: a mobile number, a wallet link, and the device you sign in from. This page sets out what we...
What we collectWhy we keep itWho else sees itHow you change it
Where This Policy Applies and Where It Does Not
Your account sits with us as the operator, and this policy travels with it wherever you sign in, as long as you are in a supported region and where local law permits. We hold registration details, wallet references for JazzCash, Easypaisa, SadaPay and Raast, and the receipt trail those rails return. What we store follows the rules covering the region you register
in, and those rules differ. If a market changes its stance we may pause new accounts there while keeping existing records in the form the law requires. Third parties see only what a rail, a fraud screen or a verification partner needs to clear one action, never more. Where two rule sets collide, the stricter one governs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE OPERATE
The People Behind This Policy
This policy is drafted and kept current by the compliance and payments team at bydy bet, not passed to an outside agency. Every revision is dated on this page, and the wording...
Named team, not a template
The wording here is maintained by the group that runs identity checks, wallet settlement and account recovery, so the text describes real processes rather than a copied template.
Dated revisions
Each revision carries an effective date near the head of the page, and we keep earlier versions on file. Material changes also appear inside your own account area.
Local rails, local rules
We describe data handling in terms of the rails you actually use, because JazzCash, Easypaisa, SadaPay, NayaPay and Raast each return a slightly different set of fields after a transfer clears.
Least-access principle
Support staff see masked account numbers by default. A full wallet reference unlocks only during a live case, and every unlock is logged against the agent who opened it.
Plain English, no traps
We write in the English you use every day, keep clauses short, and hold the section headings steady so the paragraph you found last month sits in the same place today.
Corrections taken seriously
If a statement on this page does not match what you saw on your own account, write to the desk. We fix the process and the wording, and say which one moved.
ACROSS OUR PAGES
How This Page Sits With Our Other Policies
Privacy is one strand of a set. Our terms page covers account conduct, the cookie page covers browser storage, and the verification page covers identity checks. Read together they describe one account...
Against our cookie page
That page lists browser storage and why we set it. Here we cover what happens to the session data those files help create, including sign-in patterns and device checks.
Against our verification page
Identity checks produce uploads and match scores. The verification page shows what you send; this page explains how long we hold those files and which partner handles them.
Against our payments page
Wallet and bank rails return their own receipt fields. That page shows how a transfer is submitted; here we set out how long receipts stay readable and who can open them.
Language and numbering
Every page in the set uses the same numbered headings, so clause 4.2 means the same thing whichever policy you opened. That makes cross-referencing possible without raising a ticket.
One change log
A change to account conduct can affect privacy wording too. Affected pages are revised in the same release and dated together, so you never find two pages describing one step differently.
What each page leaves out
This page does not restate wagering rules, reward mechanics or market listings; those sit on their own pages. Keeping the split clean means one policy reads without wading through the others.
What You Will See While Reading
Policy pages get skipped because they read like a wall. We built this one around short headed blocks, a dated change line near the head of...
Dated change line
A single line near the head of the page shows when the wording last moved and which paragraph changed, giving you a fixed point to compare against an older copy you saved.
Short headed blocks
Each block answers one question: what we collect, why we keep it, who sees it, how you change it. Headings stay stable between revisions so bookmarks and saved copies keep working.
Rail chips
Small chips name the local rails the policy covers, from JazzCash and Easypaisa wallets through SadaPay, NayaPay and Raast, so you can see which of your accounts sits in scope.
Plain summary boxes
Where a clause runs long, a box above it states the practical effect in everyday words. The box helps you read; the full paragraph below still carries the binding wording.
Linked sibling pages
Cross-links jump to our terms, cookie and verification pages whenever a step involves them, so one tap moves you to the matching paragraph rather than a search.
Printable view
The page prints cleanly on phone or desktop if you want a copy for your records. Headings, dates and chips all carry through, so a printout shows which revision you kept.
Privacy Questions We Get Asked
We take your mobile number, full name, date of birth, region and the wallet or bank rail you link first. We also log the device and network you sign in from.
Only the fields a transfer needs. When you top up through JazzCash, Easypaisa, SadaPay or Raast, the rail sees your wallet reference and the amount, not your lobby history.
Transaction and verification records stay for the period the rules covering your region require, usually measured in years. Chat logs and device records are dropped sooner once they stop serving a purpose.
Yes. Write from the mobile number registered on your account and ask for an access copy. We compile the entries tied to your profile and send them as a document within seven working days.
Lobby access ends and your profile leaves the active set straight away. Records tied to payments, identity and dispute handling stay in archive for the required period, then go on the normal deletion cycle.
We use grouped figures to see which parts of the lobby get used, without tying them to your name. Campaigns that need your contact details are opt-in and can be switched off in settings.