How virgin bet Handles Your Data
When you open an account with us you hand over more than a username: your name, your mobile number and the reference from your JazzCash, Easypaisa, SadaPay or...
Where Our Privacy Wording Applies
Privacy law is not identical everywhere, and we write this page to match where you sit. In supported regions of Pakistan we follow local data-handling rules; elsewhere we apply the standards that govern the account you hold. Language works the same way. Where local law permits, the English wording here is the version that applies, and any translation is offered so you
can read it comfortably rather than to change its effect. Money movement sits inside that frame too: the references your bank or wallet returns for JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers stay linked to your account record, which lets us settle a dispute with facts instead of guesswork. If a clause conflicts with a mandatory rule in your province, that rule
takes priority and we reword our text to match it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Accurate
A policy goes stale the moment nobody owns it, so ours sits with named people. Every change is dated and summarised before it goes live, and the earlier wording stays available so...
Dated Change Log
Every amendment carries a date and a short summary of what moved, so you can see what changed since your last visit without reading the whole text again.
Named Data Steward
One senior colleague owns this page. Any clause that needs rewriting is signed off by that person before it appears, keeping accountability with a person, not a department.
Checks By Our Engineers
Our platform team checks the technical claims here, including how account records are encrypted while moving and while stored, and how access to them is logged.
Retention Schedules On Record
A written schedule says how long each category of account data stays with us. We apply it on a fixed cycle rather than leaving old files sitting on a drive.
Partner Data Contracts
Any processor that touches your data signs terms limiting it to our instructions. We check those agreements whenever a provider changes or a new tool is added.
Plain-Language Drafting
We write this page the way we would explain it on chat, then a second colleague reads it for clarity. A clause nobody understands is a clause nobody can rely on.
How This Page Fits Our Other Policies
Privacy does not sit on its own, so the language here matches the rest of our policy set. If a phrase appears in two places it means the...
What Sits On The Policy Page
Before you scroll, it helps to know the shape of what you are reading. This page runs in short sections with headings you can skim, ends...
Plain Summary Up Front
The opening paragraphs say what this policy applies to and who it is for, so you can judge in a few lines whether the rest matters to you.
Numbered Clauses You Can Quote
Each clause carries a number, which makes it easy to point at exactly what you are asking about when you write to our team about your data.
Data Categories Named One By One
We list the kinds of records we hold, from identity documents to transaction references, and match each one to the reason we hold it.
Choice Controls For Cookies
A short block explains the switches available for analytics and preference files, with a direct link to the page where you make those changes.
Change Log You Can Compare
Older versions stay published in a dated list, so you can see which sentence moved and when, rather than being told only that something was updated.
Contact Block On Every Screen
Our privacy desk details sit at the foot of each section, so you never have to scroll back to the start to find the address you need.