Privacy Policy for your dz22 account
dz22 links your live casino, slot and sportsbook account to one privacy record, so the data we collect, keep and share is stated before you open an account...
How this Privacy Policy applies
Our Privacy Policy is written for dz22 account activity in supported regions of Pakistan and applies when you browse the lobby, create an account, verify access, contact us, or use payment rails shown on our pages. We collect only the details needed to run your account, confirm your instructions, keep sessions stable and answer privacy requests. Some records come from your device,
such as browser type, IP signals and security logs; other records come from what you submit, including contact details and payment reference numbers. Where local law permits access, we share limited data with service partners who process checks, hosting, payment routing, fraud screening and support tooling under confidentiality duties. We do not sell your personal data. You can ask us to correct
or erase eligible records, and we will explain any record we must retain for account security or legal handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep privacy wording reliable
We write this Privacy Policy from the systems dz22 operates: account access, security logs, support tools and Pakistan payment references. The signals below show how we keep the page tied to real...
Named policy owner
Our data handling is assigned to an internal dz22 owner who checks wording, retention periods and partner changes. This gives your request a clear route beyond general support queues.
Local payment context
We describe JazzCash, Easypaisa, SadaPay and Raast references as account records, not banking advice. Wallet receipt numbers stay separate from identity details so each record type has purpose.
Security logging
Login attempts, device changes and unusual session patterns are logged to protect your account. The Privacy Policy explains why these logs may remain when optional data is erased.
Plain language
We write the policy in Pakistani English and avoid hidden legal wording where plain terms work. Definitions sit near verification, support contact and withdrawal checks for context clarity.
Change control
When we change this Privacy Policy, we update the page date and adjust affected sections. Material changes are placed where you can see them before continuing account activity.
Limited sharing
Partner access is restricted to tasks they perform for dz22, such as hosting, payment routing, security screening and care tools. Contracts require protected handling for assigned work only.
Privacy alignment across dz22 pages
Your privacy rights should not change from one dz22 page to another. This comparison explains how related policy pages use the same data categories, contact routes and retention...
| Terms alignment | Account rules use the same personal data categories named here, including identity checks and transaction records. This keeps legal promises aligned when you move between policy pages inside. |
|---|---|
| Cookie page match | Cookie disclosures use the same device data categories named here, including browser signals, session IDs and preference tools. Consent choices therefore match this Privacy Policy rather than separate meanings. |
| Identity check wording | Identity check wording matches this Privacy Policy, so submitted documents, selfie checks and contact details are treated as personal data with retention reasons, not unlabelled account material there. |
| Security page sync | Security wording uses the same session log examples named here, including IP signals and device changes. That helps you understand why some records remain after closure requests apply. |
| Support page route | Support contact text points back to this Privacy Policy for data access, correction and deletion requests. Agents can help route the matter without rewriting your privacy rights separately. |
| Reward page boundary | Promotional pages may refer to account rewards, but they do not change how dz22 collects or keeps personal data. Privacy requests still follow this policy page each time. |
| Mobile access consistency | Mobile access text uses the same privacy terms for device permissions, notifications and crash logs. If an app prompt asks for access, this policy explains the reason clearly. |
Visible Privacy Page Elements
This page is shaped so you can scan privacy duties before reading every clause. The visible elements separate data collection, sharing, retention and request actions. Each element exists...