Privacy Policy For Your Account
allyspin casino keeps this Privacy Policy close to your account flow, so you can see what personal data we collect before you open your profile in supported regions...
How We Handle Your Data
This Privacy Policy explains how we collect, use, store and share personal data when you access allyspin casino where local law permits. We collect details you give us, such as name, mobile number, email and account credentials, along with technical records from your device, session and security checks. When you use Pakistan payment rails, we keep transaction references, status updates and verification
outcomes so we can match funds, handle queries and meet record duties. We do not sell your personal data. We share only what is needed with payment processors, security vendors, support tools and legal or tax authorities when required. We keep records for as long as needed for account service, fraud checks, dispute handling and lawful duties, then we delete or anonymise
them under our retention process.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How To Reach Our Privacy Desk
If you want to ask about this Privacy Policy, send a correction request, or check how a specific account record is used, we give you direct contact paths. Use the same mobile number or email linked to your allyspin casino account so we can verify you without exposing data to another person.
Live chat
Use live chat after you open your account, choose Privacy Policy, and send the email or mobile number linked to your profile. We mask sensitive fields before any reply is prepared.
Email desk
Email privacy requests with your account ID, registered mobile number and the specific record you want checked. Our team separates privacy mail from general service queries to reduce accidental disclosure.
Payment query route
For JazzCash, Easypaisa, SadaPay or Raast record questions, include the transaction reference only. Do not send full wallet PINs, card data or screenshots showing private codes.
How We Keep Policy Text Current
We write this Privacy Policy from our own operating flow, not as a copied legal page. Each change is checked against account opening, verification, payment matching, live chat handling and security logging...
Named policy owner
A privacy owner inside our team keeps the page aligned with account forms, identity checks and payment logs. That person confirms whether each wording change matches the data fields we collect.
Local payment context
We map policy wording to JazzCash, Easypaisa, SadaPay and Raast flows, including wallet reference numbers, status messages and reversal traces. The page explains those records without asking for private wallet credentials.
Security log scope
We describe device, IP, session and failed login records because they help secure your account. These logs are handled with restricted access and are not used for unrelated public profiling.
Plain language checks
Before we publish, we read the Privacy Policy as a Pakistan account holder would read it. If a clause feels vague, we rewrite it around the exact data action involved.
Retention alignment
Our retention wording is tied to account service, payment disputes, fraud checks and lawful record duties. We do not keep every record forever, and deletion timing depends on the record type.
Change tracking
When this Privacy Policy changes, we keep an internal change trail showing what moved and why. That helps support answer your questions with the same version you saw.
How Our Policy Pages Stay Aligned
This Privacy Policy works beside our other legal pages, but it has a narrow purpose: personal data. We keep related pages consistent so your account rights, cookie choices...
| Terms page link | Our Terms page explains account rules, while this Privacy Policy explains personal data processing. When a rule needs identity checks, both pages use matching language around verification and record handling. |
|---|---|
| Cookie page link | Cookie choices sit beside this Privacy Policy because device identifiers can be personal data. We keep cookie categories, analytics wording and consent controls aligned across both pages. |
| Security page link | Security wording covers passwords, login checks and account protection. This Privacy Policy adds why related logs are collected, who may see them and how long they may remain. |
| KYC wording link | Identity checks may require documents, mobile verification or payment references. We keep KYC wording aligned with this page so you know which records support account safety and withdrawals. |
| Promo terms link | If a promotion needs eligibility checks, the promo page states the rule and this Privacy Policy explains the related data use. We avoid collecting extra records beyond that purpose. |
| Support policy link | Support pages explain service channels, while this Privacy Policy explains how chat transcripts, emails and call-back details are stored, accessed and protected after you contact us. |
| Payment records link | Payment help pages explain status messages and processing paths. This Privacy Policy explains the personal data behind those records, including wallet references and dispute evidence. |
Visible Privacy Signals On This Page
We built the policy layout so you can scan what matters before sharing personal data. The page separates account records, payment references, cookies, support transcripts and legal duties...