Account terms
Terms describe how your account may be used; this Privacy Policy describes the personal records connected to that account. We keep those lines separate so data handling remains clear.
LEGAL REFERENCE
Privacy Policy for your account
Our Privacy Policy explains what personal details we collect when you open or use a crypto casino account in supported regions of Pakistan. We set out why each...
Account dataPakistan supportJazzCash contextSecurity checks
How we handle your privacy
This Privacy Policy applies to crypto casino services where local law permits access. We collect details you provide, such as name, phone number, email address, account credentials and support messages. We also record device signals, login times, page activity and transaction references needed to operate your account, resolve disputes and meet lawful requests. Pakistani wallet or bank rail names may appear in
records when you choose them during account checks, but we do not ask for wallet passwords or app PINs. We restrict staff access by role, keep logs of sensitive actions, and use encrypted channels for account and service traffic. If our data handling changes, we update this page so you can read the current Privacy Policy before continuing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY CONTACT
Contact paths for privacy requests
You can reach us about this Privacy Policy without sharing extra private material in the first message. Send only enough detail to identify your account and the request type, then wait for our privacy team to ask for any needed proof through the same secure channel.
Team online
Privacy email
Email us for access, correction or removal requests. Include your account email or phone number, the request you want handled, and any transaction reference only if it relates directly to the privacy concern.
Live chat handoff
Chat can receive a privacy request and pass it to the correct team. For your safety, we do not ask you to paste wallet PINs, card secrets or full identity scans into chat.
Account message
If you can log in, send a message from your account area. That lets us match the request to your profile faster while keeping the reply tied to your existing access controls.
DATA ASSURANCE
Privacy checks behind this page
We maintain this Privacy Policy as an operating document, not a generic legal page. Product, support and security staff check the wording against how data is actually collected during account creation, login...
Collection mapping
We map each form field and account event to a stated purpose in this Privacy Policy, so you can see why a phone number, email address, login signal or receipt reference may be needed.
Role access
Support staff see only the records needed to answer your request. More sensitive account data is limited to trained staff with logged access and separate approval paths for unusual cases.
Security logging
We keep audit logs for password resets, account changes and privacy request handling. These logs help us detect misuse, confirm actions taken and respond if you question a change later.
Retention checks
We keep personal records only for account operation, dispute handling, security and lawful needs. When a record is no longer required, we remove it or detach it from direct account identity.
Local wording
The policy names Pakistan-relevant channels such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast only where they affect account or transaction records, keeping the privacy text grounded in your account flow.
Change control
When we change collection, sharing or retention practices, the Privacy Policy is checked before publication. We avoid hidden edits that would make your account data use unclear.
POLICY CONSISTENCY
How this policy stays aligned
Our privacy wording is checked beside related legal pages so the same account event is not described in conflicting ways. If a term page covers service rules and this page covers data...
Cookie notice
Cookie text covers browser storage and tracking choices. This Privacy Policy links those signals to wider account records, such as device checks, session logs and security monitoring.
KYC checks
Identity checks may require documents or matched account details. This Privacy Policy explains why those records are requested, who can access them and how they are stored.
Wallet records
Wallet and rail references are used to match transactions to your account. We describe these records as privacy data, not as a request for app passwords or secret codes.
Support logs
Support pages explain how to reach us; this Privacy Policy explains how your chat, email and account messages may be saved, searched and linked to your profile.
Security rules
Security pages focus on account safety actions. This policy explains the data behind those actions, such as login timestamps, device checks and account change records.
Update timing
When related legal pages change, we check this Privacy Policy for matching language. That helps avoid conflicting statements about collection, sharing, storage and deletion.
Visible cues in our policy
This page is built to make privacy choices easier to spot. We use short labels, plain headings and Pakistan-specific examples only where they explain data handling...
Plain headings
Each heading tells you the privacy point being covered before you read the paragraph. That helps you move from collection to use, sharing and retention without scanning dense legal wording.
Local examples
Where Pakistan examples are useful, we name rails such as JazzCash, Easypaisa, SadaPay and Raast as record contexts, not as broad service promotion.
Short badges
Badges highlight the data area being discussed, such as account records or security checks. They are visual labels only and do not change the Privacy Policy wording.
Request clarity
The contact section separates privacy requests from general account help. That lets you ask for access, correction or removal without being routed through unrelated service steps.
Scope markers
We state when a paragraph applies to supported regions or where local law permits. Those markers help you understand the legal scope of data collection and account access.
Change signals
When policy wording is updated, we aim to make the changed area easy to find. Clear section labels help you recheck the point that matters to your account.
Common Privacy Policy questions
We collect details you give us, such as name, phone number, email address and account messages. We also record login signals, device data and transaction references needed for account security and support.
We keep rail references only to match transactions, resolve account disputes and meet lawful record needs. We do not ask for JazzCash, Easypaisa, SadaPay, NayaPay or Raast passwords or secret app codes.
Yes. Contact our privacy email or use account messaging if you can log in. We may ask for proof that the request belongs to you before sharing account-linked records.
You can request correction when account details are outdated or inaccurate. Some changes may need checks if they affect identity records, transaction matching or access security for your account.
Retention depends on the record type and the reason it was collected. We keep data for account operation, dispute handling, security and lawful needs, then remove or detach it when no longer required.
Only staff who need to handle the request or secure the account can access it. Sensitive actions are logged, and unusual requests may require an added internal check before completion.