Privacy Policy for Your betting slots Account
This page sets out how betting slots collects, uses and protects the details tied to your account. You will find what we record when you register, what happens...
What This Privacy Policy Covers
Our position follows one rule: we collect what your account needs and nothing more. When you register from Pakistan, we record your name, contact details, date of birth and the payment identifiers linked to JazzCash, Easypaisa, SadaPay or Raast. Identity checks may require a copy of your ID document before a withdrawal leaves the platform, because we cannot release funds to the
wrong person. Records sit on encrypted servers and stay only while your account remains open or while the law sets a longer retention window. Where local law permits access, we process your details under the rules that apply in your supported region, and if those rules move, this page moves with them. You can ask us to correct, export or close your
records at any time by writing to our data team.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Where Privacy Requests Reach Us
A question about your own data should never sit unanswered. Our desk runs seven days a week between 9am and 1am Pakistan time, and privacy requests get their own queue so they are not mixed in with gameplay tickets. Write to the data team for copies, corrections or closure; use chat when you simply want to know what a field means. Every request gets a ticket number you can follow.
Email Our Data Team
Send your request to our data team and we log it the same day, then reply within a few working days with either the file you asked for or a clear explanation of what we cannot share.
Live Chat for Quick Questions
Our chat window is open from 9am to 1am Pakistan time. Use it when you want to know what a field on your account means or how long a record stays visible to you.
Change Settings Yourself
Inside your account you can switch off optional updates, edit your contact number and see which devices have signed in. Anything you cannot change there, our team handles on request.
How This Policy Earns Your Confidence
We keep this page honest by describing only practices we actually run. The team that handles your records writes these paragraphs, checks them against what our systems really store, and updates the...
Named Policy Owner
One internal team owns this page and revises it whenever our data practices shift, so you never read text written by someone who does not handle account records day to day.
Plain Language Wording
Every clause is written so a reader in Lahore or Karachi can follow it without legal training, and the structure stays steady so you can find a paragraph again later.
Local Payment Context
JazzCash, Easypaisa, SadaPay and Raast each pass different reference details to us, so we spell out in plain terms what we keep from every channel you use on this page.
Version History Kept
Each update to this page gets a dated version stored internally, so if a clause changed between your first sign-in and today, our team can show you exactly what moved.
Security Practices Explained
We describe how transfers are encrypted, how sign-in checks behave on a new device, and when a withdrawal triggers an extra identity step rather than leaving you to guess.
Requests Handled by Humans
No automated reply closes your request. A named person checks the account history, verifies what you asked for, and writes back once the change is saved in our records.
How This Policy Sits With Others
This page does not stand alone. It sits beside our terms, cookie page, identity checks and payment help pages, and the wording stays consistent between them. Where one...
What You See on This Policy
Legal text is easier to follow when it is simple to scan. We build this page around short headings, plain sentences and named payment rails, so...
Plain Section Headings
Each block carries a short heading so you can jump straight to the part you need: what we collect, who sees it, or how to ask for a change.
Short Summary Blocks
Long clauses sit under short openers, because most readers want the answer first. The detail then follows underneath for anyone who needs the full wording.
Local Payment Chips
Where a rule touches money, the text names the rail directly, whether that is JazzCash, Easypaisa, SadaPay or Raast, instead of a vague phrase about processors.
Contact Block at the Base
The page closes with the same contact channels used across our legal pages, so you never hunt through the lobby to find where a privacy request goes.
No Hidden Switches
There is no concealed toggle and no box you must untick before reaching a setting. Choices described here are actionable from your account dashboard without a ticket.
Reading on Any Device
The page renders cleanly on a phone, so a quick check on the train works as well as reading it on a desktop before you open your account.