Consistent Retention Dates
The same storage windows appear here and on our account terms page, so you are not left comparing numbers when you want to know how long a record stays.
Our privacy policy sets out what we collect when you open an account, pay in through JazzCash, Easypaisa, SadaPay or Raast, and move around the lobby — and...
Your data is handled by betpro bet under the rules that apply where you are located, and lobby access is offered in supported regions only, where local law permits. If a clause here conflicts with a mandatory local requirement, that requirement wins for your account. We process account, device and transaction records because we need them to run your account, confirm who
you are, and settle JazzCash, Easypaisa, SadaPay and Raast activity. We keep those records only as long as operations, dispute handling and legal duties require, then delete or anonymise them. You can ask what we hold, request a copy, correct anything wrong, or close the account and withdraw your consent to uses beyond the service you asked for.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
When you want a copy of your account records, a correction or a deletion, write to our privacy desk and we will confirm receipt, tell you what we need to verify you, and give you a realistic timeline for the reply. We answer in English.
Signed-in messages reach our privacy desk fastest because your account is already verified, so we can act on a data request without asking you to prove who you are again.
Write to our published privacy address if you cannot sign in, and include your registered number so we can match the request to your account before we release anything.
Our chat window handles quick questions about what we store, how long we keep it, and which JazzCash or Easypaisa records sit on your account history right now.
This policy is maintained by the team that runs account security, payments and customer support at betpro bet. It is rechecked whenever we change a payment rail, add a sign-in method, or...
The engineers who build our sign-in checks and device logs write the clauses covering login history, so the retention periods you read here match what the system really stores.
Colleagues who reconcile JazzCash, Easypaisa, SadaPay and Raast settlements agree the wording on transaction records, so you can see exactly which details we keep and for how long.
Our support leads describe how a data request travels from your first message to a final reply, including the checks we run and who signs off on the answer.
We rewrite legal wording into clear Pakistani English before publishing, then re-read it against how the platform behaves, so nothing on this page depends on you decoding jargon.
Every edit to this page carries a date and an owner, and we record what moved, so you can tell whether a clause changed because of a new payment rail or a routine tidy-up.
Our team tracks data-handling duties across the regions we support and flags any clause needing different treatment, so this policy stays honest about where local law permits access.
Each betpro bet policy page covers one job, and they are written to agree with each other. If you read this page beside our account terms or payout page, the retention windows...
The same storage windows appear here and on our account terms page, so you are not left comparing numbers when you want to know how long a record stays.
Support links, the privacy desk address and chat entry points are identical across our policy pages, so a route you find here still works when you open the next document.
Terms such as account data, device record and transaction history carry the same meaning on every policy page, which stops a phrase shifting definition as you move between documents.
Identity checks for withdrawals are described the same way wherever they appear, so the process you read about here is the process you meet when you request a payout.
When we change how your details are used, the update note lands on every affected page at once, so you never have to guess if you are reading a newer or older version.
JazzCash, Easypaisa, SadaPay and Raast handling is documented in the same order on each page, which keeps the sequence of collection, verification and settlement easy for you to follow.
If two policy pages ever disagree, the stricter data protection rule applies to your account until we fix the text, and we let you know inside your account once the correction is live.
Everything here sits in plain sections you can scan on a phone between errands. A short hero states the point, chip rows name the rails we...
Four short badges sit under the headline so you can see at a glance what the page covers before you commit to reading the longer clauses underneath them.
The chip row names JazzCash, Easypaisa, SadaPay and Raast, so you can confirm we work with the rails you already use before you read the section on transaction records.
Each block carries a number in the side margin on desktop, which makes it easy to point our support team at the exact clause you want explained in a chat message.
Paragraphs stay short and sentences rarely run past two lines on a phone, which matters when you are checking a detail during a break rather than settling in to read.
The support cards repeat at the foot of the page with working links, so you can raise a question about your records without scrolling back through the clauses to find an address.
A dated line near the header tells you when this text last moved, and the same note appears on our other policy pages so you can compare versions in seconds.