How d222 protects your privacy
d222 is built for Pakistan access where local law permits, and our Privacy Policy explains exactly how we handle your account details, device checks, lobby activity and payment...
What this policy covers
This Privacy Policy applies when you access d222 in supported regions, create or manage an account, open the lobby, contact support or use local payment rails. We collect only the details needed to run your account flow, confirm access, keep sessions secure, process payment requests, answer service messages and meet legal or operational duties where local law permits. Your data may include
account profile fields, login records, device identifiers, location signals, payment references, chat content and verification material if requested. We do not sell your personal data. When we use service partners, they receive only the limited data needed for the specific task, such as payment routing, fraud checks, hosting, analytics or support handling. We keep records only for as long as needed for
service, security, dispute handling and lawful record duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to reach our privacy team
If you have a privacy question, we want the route to be simple. Tell us which account, device or payment event your message relates to, and avoid sending full wallet credentials or card-style secrets in chat. We may ask for basic verification before discussing account data, because privacy requests must come from the account holder or an authorised contact.
Live chat privacy request
Use live chat for quick privacy questions about account records, login history or payment references. Our agent may move the matter to email if documents or a longer written answer are needed.
Email data enquiry
Email is better for correction, access or deletion requests because it creates a clear record. Include your account email, approximate date and the privacy issue you want us to check.
Security report
If you think your account data was accessed by someone else, contact us straight away. We can help secure the session, check recent activity and explain the privacy steps that follow.
Privacy controls we use
Our privacy work is tied to real platform operations rather than generic promises. We check how account opening, payment routing, live table access, sportsbook pages and support tools handle data. Each control...
Purpose-based collection
We ask for data when it has a clear account, payment, security or support purpose. If a field is not needed for that purpose, we aim not to collect it.
Limited partner sharing
Payment processors, hosting providers and verification partners receive only the details needed for their task. They are not given open access to your full account history.
Session protection
Login records, device signals and session checks help us spot unusual account access. These checks support privacy by reducing the chance of someone else viewing your account data.
Payment reference handling
JazzCash, Easypaisa, SadaPay and Raast records are used to connect a transaction with your d222 account. We do not ask you to share wallet passwords.
Request verification
Before we release, correct or delete account data, we may confirm that the request is really yours. This prevents another person from using privacy rights against your account.
Retention discipline
We keep records for service, security, disputes and legal duties, then remove or anonymise them when they are no longer needed for those purposes.
How this policy stays aligned
Your privacy rights should not change depending on which legal page you open first. We keep this Privacy Policy aligned with our account terms, cookie wording, support handling...
What you see on this page
We designed this privacy page so you can scan important data points before opening an account. The layout separates collection, use, sharing, retention, rights and contact routes. That...