How We Handle Your Account Data
We wrote this page so you know exactly what happens to the details you hand over when you open an account. It explains what we collect, how long...
What This Policy Covers For You
This page sets out our stance on personal data while you use scorpion casino in supported regions. Where local law permits, we are the party that decides why your data is held and how long it stays. We collect what running your account needs: your name, contact details, the identity checks we must make, device signals, and the references created when money
moves through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. That record stays while the account is open, then for the period our auditors and payment partners require. You can ask us to correct anything inaccurate, request a copy of what we hold, or ask us to close the account and drop what we need not keep. How far each right stretches depends on
where you are when you ask, so we confirm the position with you first. We do not sell your personal data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Talk To Us About Your Data
Privacy requests move faster when they arrive with detail. Tell us which number or email sits on the account, what you want changed, and roughly when the record was created. Our desk replies in English or Urdu and keeps one case open until it is closed.
Data Request Desk
Send your request from the email address tied to your account so we can match you without extra checks. Include your account reference and the outcome you want, and the ticket is logged on arrival.
Live Chat
The chat window inside your account keeps its own history, so you never repeat the same details twice. Agents can pull your payment references and answer policy questions while you wait with them.
Follow-Up Window
If a request needs a second look, we write back with a plain-language update and a reference number you can quote later. We chase the case internally rather than leaving you to ask again.
Why You Can Rely On These Words
This wording is maintained by our compliance and payments teams rather than an outside writer. The same people who handle account checks and JazzCash settlement queries update it when a process changes...
Named Owner
Every revision carries the team accountable for it, so you know who to question when a clause matters to you. There are no anonymous edits and no wording nobody will stand behind.
Plain Language
We skip legal shorthand where an ordinary sentence does the job. You should be able to read a clause once, understand what it means for your account, and carry on with your day.
Practice Matches Words
Our copy describes the same process our agents follow when money moves. If a JazzCash or Raast reference is retained, this page says so instead of leaving you to guess.
Revision Cycle
We revisit the wording on a fixed cycle, and sooner if a payment partner or regulator changes what we must disclose. Whatever shifts gets written into the next version of the page.
Second Opinion
Ask for your request to be raised to a senior handler and we will do that. You get a named contact and a response window rather than being passed around a queue.
Request Log
We record every privacy request and the answer we gave, so the same question is handled the same way next time. It keeps our replies consistent and something we can audit.
How This Page Sits Beside Our Others
The privacy wording you are reading follows the same rules as our terms and account pages. Definitions line up, the local payment names appear in identical form, and...
| Shared Definitions | Terms such as account data and payment reference mean the same thing here as on our terms page, so you can move between documents without relearning our vocabulary. |
|---|---|
| Consistent Retention | Closing windows are stated once and reused across the site. If a payment record is kept for a set period on this page, no other page claims something different. |
| Same Contact Points | The support address listed here is the one printed on your account pages. One desk, one queue and one reference number, whichever page sent you towards us. |
| Matching Rail Names | JazzCash, Easypaisa, SadaPay, NayaPay and Raast are written the same way across every page, so searching for any of them lands you on wording that fits together. |
| Aligned Security Wording | Session handling, device checks and password rules are described the same way on the account pages and here, which means nothing gets quietly softened on one of them. |
| Single Revision Date | When we update one document we sweep the whole set, so the date shown at the head of this page tells you how fresh the group of pages is. |
| Conflict Rule | Where two pages ever disagree, the privacy wording here takes priority and we correct the older page, which keeps your expectations fixed rather than shifting under you. |
How We Lay Out Your Choices
We built this page to be scanned rather than worked through from start to finish. Sections are short, headings say what the paragraph answers, and a...
Local Rail Chips
The row above names JazzCash, Easypaisa, SadaPay and Raast, and each chip leads to the section explaining how references from those rails are handled and how long they stay.
Short Headings
Each section title states what the paragraph answers, so you can jump straight to retention, sharing or account closure without working through everything that comes before it.
Dated Revisions
A version marker near the start of the page shows when the wording last changed. If that date is recent, something in our process moved and you are reading the current position.
English And Urdu
Headings and key sentences read naturally in Pakistani English, and our support desk will walk you through any clause in Urdu if that is easier for you to follow.
Saveable Copy
You can store or print the current version alongside your own records, which helps if you later want to compare what we said against what we actually did.
Question Block
The short answers further down sit in one place, so the things people email us about most are usually settled before you ever contact the support desk.