Privacy versus account rules
The Terms page covers wagering conditions, account rules and how disputes get handled. This page stays on personal data, what we collect, why we collect it and how long it stays.
LEGAL REFERENCE
Your Privacy Policy, In Plain English
Your privacy matters from the moment you open an account here, so we spell out what we hold, why we hold it, and how you can ask us...
What we holdWhy we hold itYour choicesRegional rights
What We Hold And Why
Think of this page as the agreement behind your account. We collect the minimum needed to open your profile, verify who you are, and settle payments through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, usually your name, contact details, date of birth and transaction history. We do not sell personal data. How long we keep a record, and which rights you can exercise,
depends on where you live: in Pakistan we follow local law, and where local law permits we also honour deletion and access requests from supported regions. You can write to us any time to ask what we hold, correct something that looks wrong, or close your profile. We date any revision at the head of the page and flag the sections that
moved.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
OUR EDITING STANDARD
Why You Can Read This Closely
We treat these pages as operator documentation, not marketing filler. The people who set up your account, wire the payment rails and answer your chat messages are the same people who agree...
Written in house
Every clause here was drafted by the same team that runs sapphire bet day to day, so the wording matches how accounts, payment rails and support queues actually behave.
Plain-English pass
Each policy page gets a second edit to strip out legal padding. If a sentence needs three reads before it makes sense, we rewrite it again before it goes live.
Revision log
When something changes, whether it is a new rail such as Raast or a shift in how we store device data, we date the revision at the head and list affected sections.
Local rails named
We name the rails you actually use, including JazzCash, Easypaisa, SadaPay and Raast, so each clause is tied to something you recognise rather than abstract wording.
Security practice
Account access runs over encrypted connections with one-time codes at sign-in, and staff access is limited and logged. We document those controls so our statements stay accurate.
Corrections welcomed
If a line here does not match what you have experienced on the platform, tell us. We log the complaint, check it with the relevant team, and amend the page when we are wrong.
POLICY CONSISTENCY
How This Page Fits The Rest
This page never travels alone. It sits beside our Terms and cookie pages, and we keep them aligned so definitions and contact routes match. Where a sibling page covers a subject in...
Privacy versus cookie settings
Cookies sit on their own page, because you can switch them off in your browser and change that choice later. Here we explain the data those cookies feed.
Privacy versus transaction steps
The payments page lists rails, timings and settlement steps. This policy explains the trail those transactions leave, who inside our business can see it, and for how long.
One contact route
Whichever policy page you land on, requests arrive in the same queue. One privacy desk, one ticket reference, so nothing is lost between teams or answered twice with different wording.
Separate revision dates
Terms, cookies and privacy wording change at different speeds, so each sibling page carries its own update date. Check the strip at the head rather than assuming they all moved together.
Short cross-references
Where a sibling page covers a subject in detail, we link straight to it instead of repeating paragraphs. That keeps this page readable and stops the wording drifting apart over time.
Shared definitions
Words like account, profile and personal data mean the same thing on every policy page, so a clause you read under our Terms still applies when you come back here.
INSIDE THE LAYOUT
What Sits On This Page
Every policy page on sapphire bet follows one layout, so you always know where to look. Revision date at the head, plain summary next, full clauses underneath, contact...
Revision banner
A dated strip sits at the head of every policy...
Plain summary first
Before the clauses, a short block sets out the practical...
Named rails
Where a clause touches money we name JazzCash, Easypaisa, SadaPay...
Region line
A single line states whether the text applies to your...
Contact strip
Our footer strip repeats support hours, the chat link and...
Change flags
When a revision lands we point to the sections that...
Questions We Get Most
Enough to run your account: your name, date of birth, contact details, device and sign-in data, and a record of the payments that move through JazzCash, Easypaisa, SadaPay or Raast.
No. We share details only with the payment processors, verification and security partners needed to keep your account working, plus authorities where local law requires it. Selling profile data is not part of what we do.
Message our privacy desk from inside your account or by email. We confirm identity first, then send a readable summary, and we will give you a date when we reply.
You can close your account and ask us to delete what is not legally required. Some transaction and identity records must stay for a set period, and we will tell you which.
Retention depends on the record type and where you live. Transaction and identity documents stay for the period local rules set, while marketing preferences and device data clear sooner once you ask.
The core promises hold everywhere, but specifics shift. Where local law permits different handling, we follow the local requirement for supported regions rather than hiding the difference from you.