Your Data, Handled The pro bet Way
This page sets out how pro bet collects, stores and uses the details behind your account, from the wallet transfers behind your JazzCash or Easypaisa payments to the...
Jurisdiction, Consent And How We Apply This Policy
Privacy rules differ by country, so we apply this policy where local law permits and adapt the parts that need adapting for supported regions. When you open an account from Pakistan, you agree to the handling of the details you give us: your name, contact number, age check, JazzCash, Easypaisa, SadaPay or Raast reference, and the device you sign in from. We
keep that data only as long as we need it for account access, fraud checks and payment reconciliation, then delete or anonymise it. If a rule in your region gives you extra rights, such as a copy of your file, a correction, or a removal request, tell us and we act on it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How To Reach Us About Your Data
When something in your account data looks wrong, you should not have to hunt for a way to fix it. Our support desk takes privacy requests through live chat inside your account and by email, seven days a week, and every request gets a reference number you can follow. Tell us what needs changing and we confirm the outcome on the same ticket.
Live Chat
Open the chat window from your account dashboard and an agent picks up the live thread, normally inside a few minutes, to start or track a data request.
Email Desk
Write to our privacy mailbox with your account number and the change you want; we reply with the next step and keep the chain open until it closes.
Request Tracker
Every privacy ticket gets a reference you can reopen later inside your account, so you always see what we did, when we did it and who handled your case.
The People Who Keep This Policy Current
This page is kept by the compliance and platform teams who run the pro bet account systems day to day, not by a copywriter working from a template. We rewrite it whenever...
Named Owner
A named data owner on our platform team signs off every revision, so any question about the wording lands with a person who can actually change it for your account.
Change Log
We date each update and list what moved in plain English, whether it was a payment route, a login check or a shorter storage window for old account records.
No Borrowed Text
Nothing here is lifted from another operator. The wording describes the systems we actually run for Pakistan accounts, including our own support hours and the checks we apply before any payout.
Plain Language Pass
Before publishing we read the page back with a support agent, who flags anything a normal account holder would not understand on a first read through. Then we rewrite the sentence.
Security Team Input
Our engineers check every storage, encryption and access line before publication, so the policy matches the way sessions, devices and wallet references are protected on our side in practice.
Regional Check
We keep a short record of which regions we serve and confirm the wording suits each one, using local payment names such as JazzCash, Easypaisa and Raast for clarity.
This Policy And Our Other Standing Pages
Our standing pages share one vocabulary, so you never have to guess which version is the newer one. The account terms, the game rules and this privacy page...
| Shared Terms | Account, wallet, lobby and session mean the same thing on every page, so a word you learn here still fits when you open your own account terms. |
|---|---|
| One Update Release | When a rule shifts, the wording on this page and on the terms page changes together, so you are never reading an older version without knowing it at all. |
| Same Contact Paths | Live chat, email and the request tracker work for every policy question, so you do not need a different channel to ask about this page or the account terms. |
| Matching Dates | Each revision carries the same date stamp across the policy pages side by side, which makes it easy to spot whether you are on the version we last published. |
| No Contradictions | Where two pages could overlap, ours points to the clause that governs instead of adding a second rule, so nothing conflicts when you read them back to back. |
| Mobile And Desktop | The policy renders the same on a small screen and on a desktop browser, with the same headings, so you can settle a question from either device you pick. |
| Archive Access | Older versions stay reachable on request, so if you agreed to something under previous wording you can ask us for that copy without a long wait. |
What You Will Find On This Page
The page is laid out so you can reach the answer you need without reading all of it. A short summary sits at the head of...
Summary Box
A short block near the head of the page tells you in a few lines what we collect, why we keep it and how long it stays on our systems.
Contents Rail
A side rail lists every heading on the page, so you can jump straight to the clause on device checks, wallet references or account closure, without scrolling the whole page.
Plain-Language Headings
Headings lead with everyday words and put the legal label in brackets afterwards, so you always know what the paragraph is about before you read it in full.
Definition Strip
Four terms carry the whole page: account, wallet, lobby and session. Each one is defined once near the start and used with the same meaning in every clause below.
Storage Table
A simple table shows how long each record type stays with us, from sign-in logs to wallet references, and what happens when the period ends. We delete or anonymise.
Change Marker
A dated marker at the foot of the page shows the last revision, and new clauses carry a short tag so you spot them quickly on your next visit.