Your Privacy Policy, In Plain English
Open an account with hitnspin casino and you hand us a small set of details — your name, your phone number, your city and the payment rail you...
Where Local Law Sets The Rules
hitnspin casino handles personal data under the rules that apply where you live, so how we store and share details depends on your region. Where local law permits, we process your data to run your account, confirm your age, settle payment references from JazzCash, Easypaisa, SadaPay or Raast, and meet record-keeping duties. In supported regions we pass limited details to payment partners
and identity-check providers, and we do not sell your data. Where local law sets a holding period, we keep records for that window and no longer. Access from some areas may be restricted, and we will tell you if that applies to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Page Honest
The wording here is maintained by the same team that runs accounts and payments, not lifted from a template. When we change a holding period, add a payment rail or adjust a...
Written in-house
Our own operations and payments staff draft this page, because they handle the files daily. Nothing is passed to an outside agency, so the wording matches the process you actually go through.
Dated revisions
Every edit carries a revision date at the foot of the page, so you can compare what you read last month with what stands today. Earlier wording stays on file for audits.
Checks you can trace
When you ask for a copy of your file, we say which documents we needed, why, and who signed the request off. That trail keeps identity checks fair rather than automatic.
Retention with reasons
Each record type carries a stated holding window — account data, payment references, chat logs — instead of being kept forever. Once the window closes, the record is deleted or anonymised.
Plain-language drafting
We write in everyday English for Pakistan readers, with short sentences so you can scan for your answer. If a clause still reads awkwardly, tell us and we will rewrite it.
Change alerts
Material changes to how we use your data are announced inside your account before they take effect, so you get a window to read them and question them first.
Matching Our Sibling Policies
This policy sits alongside our terms of use, cookie page, verification steps and withdrawal rules, and the definitions carry across all of them. Where one page sets a...
The Layout Of This Policy
The page follows the order you would ask questions in: what we collect, why we collect it, how long it stays, who can open it, and...
What we collect
Name, date of birth, phone number, city and the payment rail you use, plus basic device and log data from each sign-in. Each field is listed with its reason.
Why we hold it
Running your account, settling transactions, meeting regional record rules and keeping the lobby free of duplicate or underage accounts. Nothing is collected without one of those reasons attached to it.
How long it stays
A holding window sits beside every record type, counted from the day your account closes or the transaction settles, whichever comes later. After that, the record goes.
Who can open it
A small group of staff with a stated reason, plus the payment partners needed to clear a transfer. Access is logged, and that log is checked when a request arrives.
How you change it
Ask inside your account or by email and we correct, export or delete what we can. Where a regional rule requires us to keep something, we say so in the reply.
Security practices
Encrypted connections, two-step sign-in on your account, and staff access granted per task rather than held permanently. Each signed-in device is dropped when you change your password.