Cookie page
The cookie choices you set carry across, and any tracking we switch off is switched off on that page on the same working day.
LEGAL REFERENCE
How We Handle Your Data at online slots
Open an account with online slots and you share a short set of details with us: your name, mobile number, date of birth and payout wallet. This page...
Data held in PakistanWallet references maskedEvery change datedAsk us to delete
How Our Privacy Policy Works Where You Live
Where local law permits, we apply the practices described here in full. Data rules differ between Pakistan and the other supported regions we serve, and some clauses are shaped by the law that applies where your account sits. When a local rule gives you a stronger right than this page sets out, that rule wins; when a rule restricts what we may
store, we shorten our retention to match. If a legal change affects how we handle your details, we update this page and flag it on your dashboard before it takes effect. Write to us any time and we will confirm, in writing, which jurisdiction wording applies to your account. Nothing here replaces the law that protects you where you live.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO WRITES THIS
The People Behind This Policy Page
This page is written and kept current in-house by the people who run online slots, not by an outside agency. Our data protection lead, payments operations manager and support supervisor all sign...
Data protection lead
Owns this policy end to end, from the wording you read here to the retention schedules our engineers follow in the background every working day.
Payments operations
Makes sure your JazzCash, Easypaisa, SadaPay and Raast references stay masked in dashboards and are never printed in full on a support transcript.
Support supervisors
Read every escalation about a data request, and they hold authority to override a standard answer when your situation needs a different outcome.
Security engineers
Run encryption on stored records, watch login patterns for odd behaviour, and document each change so the wording on this page stays accurate.
Regional compliance
Checks each update against the rules of every supported region, and tells us early when wording has to differ by jurisdiction before we publish.
Account records team
Handles corrections, export requests and deletions, then confirms in writing what was changed, when it happened and who authorised the change.
SAME TERMS HERE
How This Page Matches Our Other Policies
Every page we publish about data has to agree with the others. If we change how we handle your details, the same wording appears across our cookie page, account terms and withdrawal...
Account terms
Where account terms touch on your details, they point back to this page instead of inventing a second set of rules you would have to weigh up.
Withdrawal rules
The verification steps in our withdrawal rules use the same retention periods listed here, so a payout check never asks for data we said we would not keep.
Verification checks
Identity checks follow one standard across the platform, and the documents you upload are handled under the storage periods written on this page.
Security page
Login advice, session timings and device handling stay consistent, so a tip you read there will not contradict what this page says about stored records.
Complaints route
If you disagree with a decision about your data, the escalation path on our complaints page mirrors the one described here, with the same response windows.
Language versions
When a translated version and this English text disagree, the English wording is used, and we correct the translation rather than leaving two answers live.
What Stands Out When You Read This Page
You should not need a legal background to follow a privacy page. Ours opens with a short summary, then lists your rights in plain language, then...
Short opening summary
A few lines at the start tell you the shape of the whole page before you scroll, so you know exactly where your own questions get answered.
Rights in one list
Access, correction, deletion and objection are set out as separate entries, each with the exact step you take to use that right on your account.
Change log with dates
Every edit is stamped with a date and a one-line reason, so you can see what moved without reading the whole page again from the start.
Retention table
A table maps each record type to the period we hold it, from wallet references to chat transcripts, and says what happens at the end of that period.
Wallet context chips
JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear as chips, so you can jump straight to the section covering the wallet you actually use.
Download option
You can pull a copy of the current version as a file from your dashboard, which helps when you want to keep it with your own account records.
Privacy Questions We Get Asked
Your name, mobile number, date of birth, wallet reference and the activity on your account. We do not store your JazzCash or Easypaisa PIN, and we never ask for it by chat or phone.
Wallet and transaction references stay for the period our rules require, while chat transcripts and marketing preferences are cleared sooner. The retention table on this page lists each record type beside its period.
Yes. Write to the privacy desk and we close the account and remove what we are permitted to remove. Some transaction records have to stay for a set time under the rules we operate.
We pass only what a payment or verification partner needs to complete a step you asked for. We do not sell your contact details, and we do not hand them to advertisers.
Open your dashboard and edit the field if it is editable, or send the correction to the privacy desk. We confirm the change in writing and record who made it and when.
Every revision is dated and flagged on your dashboard before it takes effect. If a change affects how your wallet data is used, we also message the contact number on your account.