What We Hold, And What We Do Not
This page explains, in plain English, what spinit casino collects when you open an account, sign in from Pakistan, or move money through JazzCash, Easypaisa, SadaPay or Raast...
Where These Privacy Rules Apply
spinit casino applies this policy to every account opened from a supported region, so the wording here takes effect wherever local law permits us to serve you. Pakistan is our home market and the defaults are written for Pakistani account holders: your name, mobile number, date of birth and CNIC details stay encrypted, while JazzCash, Easypaisa, SadaPay and Raast references are stored
as tokens rather than full numbers. Sign in from outside a supported region and parts of this policy may be handled differently, because local rules override ours. Session logs, device fingerprints and login timestamps are kept only as long as a payment partner or regulator requires, then deleted or anonymised. You can ask what we hold at any point and we answer
in writing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How To Reach Our Data Team
Questions about your data never land in a general queue. Write to our privacy desk from the email address registered on your account and a named handler replies, usually inside one working day, in English or Urdu. Live chat routes your request into that same queue, and every case carries a reference number you can quote later.
Privacy email desk
Send data questions from your registered address and our handlers confirm receipt within one working day, then answer in full once your identity and account ownership are verified.
Live chat routing
Chat agents file your request into the same privacy queue, so you keep one reference number and one thread instead of repeating the details to a second team.
Written responses
Every decision about access, correction or deletion reaches you as a written reply you can keep, with the reasoning stated plainly and the date the change took effect.
Who Writes And Checks This Policy
This policy is maintained by our compliance and engineering staff together, not written once and shelved. The people who build the account system draft the sections on storage...
Named data officer
One accountable person owns the text, answers regulator questions and approves each revision, so you always know which role is...
Change log
Each wording change carries a date and a short reason, kept in a public record, so you can compare the...
Plain-language drafting
Our writers avoid legal padding and explain each data practice in ordinary sentences, so a reader in Lahore or Karachi...
Engineering sign-off
Anything we claim about encryption, storage or deletion is tested against the live systems before publication, so the wording matches...
Payment partner checks
We confirm with JazzCash, Easypaisa, SadaPay and Raast what data each rail shares, then state it here rather than guessing...
Support team feedback
Real queries from Pakistani account holders shape each rewrite, so the sections people ask about most get reworded first instead...
One Standard Across Every Page
The wording you read here matches what appears on our terms page, our account-opening screens and the help articles you reach from chat. We use the same vocabulary...
| Cookie policy | The cookie page names every tag we load, separates essential scripts from analytics, and points back here for the rules that govern how long a record survives on your device. |
|---|---|
| Terms of use | Account rules sit on the terms page, while the data handling behind them sits here; the two documents share the same definitions so nothing is redefined quietly between them. |
| Payment pages | Our JazzCash, Easypaisa, SadaPay and Raast payment pages describe each settlement step, and this policy explains which identifiers from those steps we retain afterwards and for how long. |
| Help articles | Answers in chat and on the help pages use the same terms as this document, so you are never left guessing whether two phrases mean the same practice. |
| Account security page | Login checks, device recognition and password resets are described in detail there, while this policy covers what we store about each of those actions and why we hold it. |
| Careers and partners | Teams and partner studios receive a shortened data-handling schedule that mirrors this document, so the same limits apply to anyone who touches your account records on our behalf. |
| Complaints route | If a response disappoints you, the complaints page escalates the matter to the same data officer who signs off on every revision of this policy and replies in writing. |
How This Policy Page Is Laid Out
We designed this document to be read on a phone during a commute, so the parts that matter most appear before any long clause. A summary strip sits...