Terms of Use
Core definitions, such as what counts as an account holder and what a closed account means, are set once in our terms and reused here word for word.
One page covers every detail of how gets bet collects, stores and uses the details you share when you open an account from Pakistan. Read it before your...
gets bet keeps one privacy policy for everyone who opens an account, and it applies wherever we serve you in Pakistan and other supported regions. It explains the personal details we ask for, including your name, date of birth, contact number, email and the identity documents we check before a withdrawal, plus how we record transactions made through JazzCash, Easypaisa, SadaPay, NayaPay
and Raast. We also set out how long records stay on file, who can view them, and which partners help run parts of the process. Where local law permits, you can ask for a copy of what we hold, request a correction, or close your account. Some duties differ by market, so the wording here reflects the rules that apply where you
signed up from.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your records are handled by the same support team that runs the live chat window inside your account. Write in from the email address linked to your profile so we can match you quickly, and mention the market you signed up from. Urdu or English both work; replies usually land the same day.
Open the chat panel from your dashboard and ask for the privacy team by name. We verify you with two account details, then walk you through what we hold.
Send your request to our support inbox from the address on your profile. Include your account number and the records you want to see. We reply within a few working days.
Our helpline runs daily during Pakistan hours for account holders who prefer talking things through. Quote your reference number and the agent opens your policy summary while you wait.
Every claim on this page maps to something you can see inside your own account, from the payment records we store to the verification steps we run. Our legal writers date each...
Every update to this policy carries a date and a short change log, so you can tell exactly what shifted between the version you read at sign-up and today.
We write in everyday English rather than legal shorthand, and Pakistani readers get the same text as everyone else in supported regions. If a clause confuses you, ask and we explain it.
Before anything goes live, our compliance staff read the whole document against the payment flows we actually run, including JazzCash, Easypaisa, SadaPay, NayaPay and Raast. A second editor signs off.
You always know where a request goes: one support inbox, one chat channel, one helpline. No anonymous forms, no third-party counters collecting your questions. Everything routes through accounts you already hold with us.
We list the fields we deliberately skip, such as card numbers for rails that never touch our servers, so you can tell what is on file and what is not.
When you ask what we hold, we answer with the actual fields rather than a summary. You get the same list our staff see on screen, with no waiting queue attached.
Our terms, cookie notice and account rules sit alongside this privacy policy and share the same definitions. Where two documents touch the same topic, whether that is verification, transaction records or closing...
Core definitions, such as what counts as an account holder and what a closed account means, are set once in our terms and reused here word for word.
Tracking preferences described in our cookie notice follow the same categories you read here, so switching a preference off once applies everywhere on the site. One setting, one result.
Verification steps and payment recording rules use identical phrasing across both documents, which matters when you are tracing a JazzCash transfer or checking where an Easypaisa receipt appears.
English is the reference text for every policy page we publish. Regional translations follow it closely, and if a phrase reads differently, the English wording is the one we stand behind.
We revise all four documents together rather than one at a time. Dates stay aligned, so a change to how we store transaction data appears everywhere on the same day.
One team answers questions on every page, so you never get bounced between departments. Whoever replies can see the full set of documents linked to your account. Ask once, get one answer.
Big edits reach you by email before they take effect where local law permits, and every older version stays available if you need to compare what you agreed to.
Nothing on this page is buried in a PDF you have to download. Key points sit in short blocks with plain labels, the chips show which rails feed...