Privacy Policy: How real slots Handles Your Data
Every real slots account starts with a handful of details about you: your name, your mobile number, your city. This page sets out what we collect at registration...
Where Local Law Permits, This Is What Applies
real slots runs as one brand for Pakistan, so this policy is written around our own account flow rather than a generic template. We keep a single master version and, where local law permits, apply it as the default across supported regions. Some provinces and payment partners add their own conditions, and there the stricter rule wins. That is why a few
clauses carry a 'where local law permits' note: local rules, not ours, settle the edge cases. Your JazzCash, Easypaisa, SadaPay and Raast records sit inside the same framework, we pass only what a payment partner needs to clear or reverse a transfer. When a regional rule changes, we update this page and stamp the new date in the header.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching the Team Behind This Policy
Questions about what we hold, or a request to see or delete it, reach our support desk first. We answer in English and Urdu and aim to reply within one working day. If your query touches a transfer, keep your JazzCash, Easypaisa or Raast reference handy, it shortens the loop.
Live chat
Open live chat from your dashboard and choose the privacy subject. Our team covers Pakistani hours seven days a week and can pull your data summary while you wait.
Email desk
Write to our privacy mailbox with your registered mobile number and a short line on what you need. We reply with a written summary of the data on your account.
Account request
Raise a data or deletion request straight from account settings. The ticket travels with your profile, so nobody has to re-ask you for a JazzCash or Easypaisa reference.
The People Who Check Every Clause
A small group inside real slots owns this page: someone from payments, someone from support, one editor who reads every legal draft line by line. They meet whenever a new payment rail...
Payments checker
Checks each clause against how JazzCash, Easypaisa, SadaPay and Raast behave, so wording matches the rails you use rather than a template drafted abroad. Vague lines get rewritten.
Support reader
Brings the questions you send us each week. If three people ask the same thing about stored phone numbers, that clause gets smoothed out and dated again on this page.
Security checker
Watches how logins, device sessions and two-step codes are recorded, then confirms the wording here still describes what our systems genuinely store. Nothing is described that we do not keep.
Legal editor
Rewrites clauses in plain Pakistani English so a first-time reader can follow them, keeps definitions aligned with our terms of use, and removes jargon wherever one clear sentence will do.
Regional adviser
Confirms how provincial rules and partner banks affect what we may hold, so the jurisdiction wording here reflects supported regions rather than one blanket promise. The stricter rule is written in.
Version keeper
Keeps the change log, stamps every revision with a date, and archives old versions so you can compare what this policy said when you registered. Nothing is edited without a line beside it.
How This Page Sits With Our Others
Our terms of use, cookie notes, payout rules and this privacy page share one voice and one set of definitions. Where two pages overlap, the stricter wording governs...
| Terms of use | Covers the rules of your account: eligibility, fair use, and what happens if a sign-in is shared. The privacy wording here fills in the data side of each clause. |
|---|---|
| Cookie terms | Explains the small files that keep you signed in and remember your language. The definitions match this page, so a term means the same thing in both places. |
| Payout rules | Set the timing and checks behind JazzCash, Easypaisa, SadaPay and Raast cash-outs. This page says which account records those checks rely on, and both are kept updated together. |
| Account security | Explains two-step codes, device sessions and how we respond to a suspected login. The retention wording here says how long those security logs stay. Both pages are checked on one schedule. |
| Contact page | Lists the channels and hours behind this policy, including the chat and mailbox used for data requests. Every request lands in our own queue, never a third-party form. |
| Complaints path | Describes how to escalate a concern if our first reply misses the mark. The same request log feeds both pages, so reply windows and escalation steps stay consistent. |
| Change log | Keeps every dated revision of this policy in order. If a clause changes after you registered, the log shows the old wording beside the new, so you can see what shifted. |
Landmarks You Will Spot on This Page
This page is built so you can find a clause without scrolling through a wall of text. A dated banner sits in the header, a plain-language...
Dated banner
The revision date sits in the header, so you can tell at a glance whether you are reading the current wording or an older copy saved on your device.
Plain-language summary
A short block of everyday sentences opens the page and covers the five points you ask about most before the numbered clauses begin. It previews them, never replaces them.
Clause anchors
Each numbered clause has its own link, so support can point you to the exact sentence behind a request instead of asking you to search the page.
Rail chips
JazzCash, Easypaisa, SadaPay and Raast appear as chips, so you can see which account records this policy covers without digging through a long schedule. Tap one to jump straight to its clause.
Change log
Older versions stay listed with their dates, letting you compare what applied when you registered against what applies to your account today. Nothing is removed from the record.
Save and print
You can save the page as a PDF or print it, and the layout keeps clause numbers intact so your copy stays usable offline. Handy for your own files.