Privacy Policy for Your dd22 Account
dd22 gives you a clear privacy policy before you open an account, so you know how account details, device signals and payment records are handled. Read it before...
How We Handle Your Data
This privacy policy explains what dd22 collects when you create, use or secure your account in supported regions. We collect details you provide, technical logs from your device, session activity, verification outcomes and transaction references linked with Pakistan payment rails. We use this data to run account access, process requests, protect balances, answer support messages and meet duties that apply where local
law permits. We do not write this policy as a generic notice; it is tied to the dd22 account flow, casino lobby, sportsbook records and payment checks. When data is no longer needed for those purposes, we reduce, archive or remove it under our retention process.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Controls We Maintain
Our privacy work sits beside account security rather than after it. We separate routine support details from verification records, limit internal access and log changes that affect account...
Access separation
Team access is separated by task, so support, payment checks and technical maintenance do not receive the same data by...
Session records
We keep session logs such as device type, timing and security events to protect access and investigate account changes. The...
Verification handling
When verification is required, documents and checks are handled for account safety and legal duties. We restrict reuse, keep related...
Payment references
JazzCash, Easypaisa, SadaPay and Raast references may appear in account records as transaction evidence. We use those references to trace...
Language clarity
We write privacy wording in clear Pakistani English so you can understand what is collected and why. Where a term...
Request tracking
Privacy requests are tracked from first contact to closure, including identity checks and outcome dates. This helps us keep a...
Where This Policy Stays Consistent
Privacy rules should not shift depending on which legal page you read. We align this page with account terms, cookie wording and security notices, while keeping each page...
Privacy Layout Cues You Can Use
We designed this privacy page so you can find the parts that affect your account quickly. The layout separates collection, use, sharing, retention and request rights...
Clear headings
Each heading names the privacy issue before the detail begins, so you can move from collection to use, sharing, storage and requests without reading unrelated platform copy.
Short policy blocks
Paragraphs stay focused on one privacy purpose at a time. This makes it easier to understand how account details, device logs or payment references are handled.
Local examples
Pakistan payment names appear only when they explain real privacy context, such as transaction references or verification support. They are not used as filler inside policy wording.
Request prompts
Privacy request prompts tell you which route to use and what details to include. That helps us answer without asking for more private data than needed.
Retention markers
Retention markers show where storage time matters, especially for account access, transaction evidence and support history. They help separate active records from archived material.
Security labels
Security labels mark places where data protects your account, such as login logs and device checks. They explain why certain technical records may remain necessary.