Terms of use
The terms page sets out what you agree to when you open an account, while this privacy policy covers only how personal details are gathered, stored and removed. Read them side by side and nothing should surprise you.
We collect only what is needed to verify your account, clear JazzCash, Easypaisa, SadaPay and Raast payments, and keep your login secure. Below you will find what we...
Where local law permits, casino slots handles your account data under the rules that apply in your own region, and this page is written so you can see where each practice sits. We act as the controller of what you give us at registration: your name, contact details, and the payment references that let us match a JazzCash, Easypaisa, SadaPay or Raast
transfer to your account. Identity and age checks run before withdrawals are released, and records are kept only as long as the rules in supported regions require. Because requirements differ across Pakistan and elsewhere, some clauses below are marked as jurisdiction-dependent. Where a province or country asks for something different, we state that plainly rather than burying it. Write to our privacy
desk and we will tell you which clause applies to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write this policy ourselves and revisit it whenever a payment rail, studio integration or law changes. Each revision is dated at the top so you can see what moved, and older...
The page is drafted by the people who run the account platform, so each clause describes a step you can trace, from what registration asks for to how a JazzCash reference is matched.
Every change carries a date and a short line saying what moved. Request an earlier version and we send it, so you can compare what applied when your data was collected.
Requirements differ between Pakistan and other markets, so clauses that depend on where you live are labelled rather than hidden. That keeps the page honest for anyone reading from a supported region.
We ask for the smallest set of details that lets identity checks pass and transfers clear. Nothing is collected because a field was easy to add to the form, and every field carries a stated reason.
You can ask to see the details we hold, fix anything wrong, or have account records removed where the rules allow, from the message centre or by email to the privacy desk.
Each revision is read by a colleague outside the drafting team before it goes live, checking that the wording matches how the platform actually behaves rather than an older description of it.
Parts of this site share one framework, so the wording you read here should line up with the terms, cookies and payments pages you can reach from the footer. Where a sibling...
The terms page sets out what you agree to when you open an account, while this privacy policy covers only how personal details are gathered, stored and removed. Read them side by side and nothing should surprise you.
The cookies page lists the small files that keep you signed in and measure page speed, while this page explains the choices you have over them and how to clear them from your browser.
Payment wording covers settlement times and limits. Here we cover the references those transfers create, how long we keep them, and which team can look at them when checking a JazzCash or Easypaisa reference.
Security wording deals with passwords and login checks, while this policy explains what login records we store, how long they stay with us, and how you can ask for a copy of them.
Promotion terms explain what a campaign asks of you. The privacy policy explains why the entry data behind it is stored, who can see it, and when it is deleted once the campaign closes.
Sportsbook wording covers markets and settlement. This page is the one to read for how sportsbook activity, device details and location checks are kept, and for how long.
The contact page lists our channels and opening hours. For anything touching personal data, use the privacy desk details in the section above so your request lands with the team that handles it.
The page itself is short on decoration and heavy on specifics: a dated change line, plain headings, and links that jump straight to the clause you need. Markers...