How We Handle the Data Behind Your Account
This page sets out, in plain Pakistani English, what betting games collects when you open an account, what we keep, and who we share it with. Your JazzCash...
Where Local Law Permits, This Policy Applies
betting games writes this policy for Pakistan first, then applies it wherever local law permits. We collect only what an account needs: your name, contact details, date of birth confirmation, device data and the payment references tied to JazzCash, Easypaisa, SadaPay, NayaPay and Raast. We use that to verify you, settle withdrawals and keep the lobby secure. Records stay while your account
is open and for the period our regulators ask for afterwards. If a feature is not available in your region we do not switch it on, and nothing about that changes how your data is stored. Ask us what we hold, ask for a copy, or ask us to correct something that is wrong. Requests reach the team listed further down this
page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Maintains and Updates This Page
One internal team owns this page, and it is checked every time we add a payment rail, a game studio or a market. Nothing changes here quietly: when a clause is rewritten...
Written In-House
Every clause here is drafted by the same people who build the account flow and the payment screens. When a feature changes, the wording on this page changes alongside it.
Dated Changes
When a clause is rewritten we record the date and what moved, so you can follow the shape of the policy over time rather than a document that shifts without explanation.
Region Checks
Before we open a market we check what local law permits, including how long records must be held. That check decides which features you see and how your data is treated.
Payment Rail Updates
When a rail such as SadaPay, NayaPay or Raast goes live, we check what reference data arrives and confirm it is stored no differently from the rails we already carry.
Requests Answered
If you ask what we hold, we confirm your identity first, then answer in plain English. There is no charge for the first copy of your account file.
No Data Sales
We do not sell your details to outside buyers, and we do not pass them to advertisers. Sharing happens only where a rail, a studio or a regulator needs it.
How This Page Matches Our Other Policies
Privacy, account terms and payment pages on betting games come from one shared internal source, so the wording should not contradict itself as you move between them. If...
| Account Terms | Our account terms describe what you agree to when you open an account; this page describes what we hold afterwards. Both are written from one shared source. |
|---|---|
| Payment Pages | The pages covering JazzCash, Easypaisa, SadaPay and Raast explain the transaction side. This policy covers the reference data left on your account once that transaction clears. |
| Cookie Handling | Our cookie wording sits alongside this policy and explains the small files stored on your device. Read the two together and you have the full picture of what runs. |
| Live Casino Use | Live tables stream from studio partners, and the session data behind them follows the rules set out here. Nothing extra is captured beyond what keeps the table running. |
| Sportsbook Markets | When you place a sportsbook selection we keep a record of the market, the stake and the outcome. It is held under the same window as your account. |
| Rewards Records | Promotions you take part in leave their own record so we can apply the terms correctly. That record stays with your account and is removed on the same schedule. |
| Withdrawal Records | Withdrawal requests are logged from the moment you submit one until the rail confirms it. Those logs help us settle disputes and are covered by this policy. |
What You Will Spot Inside This Policy
Scroll through and you will find the same headings every time we update: what we collect, why we hold it, how long it stays, who can...
What We Collect
The first heading lists the categories we hold: identity details, contact data, device signals and payment references. It is short, and nothing sits behind a second layer.
Why We Hold It
Each category comes with a reason attached: verifying you, settling withdrawals, keeping the lobby secure or meeting a duty set by a regulator. We name the purpose every time.
How Long It Stays
Retention windows are spelled out rather than left vague. Account records follow one window, payment references another, and both are tied to what regulators require in the markets we serve.
Who Can See It
You will see which teams and partners can view a record, from our support desk to a rail confirming a transaction. Inside our team, access is limited to those who need it.
Getting Your Copy
The request route sits in one paragraph: send it from your dashboard thread, confirm your identity and we release the file. No forms, no waiting on a phone line.
Raising A Concern
If you believe we have handled something badly, the last heading explains where to send it. We log every concern and reply with what we found.