Account pages
Account screens ask only for data tied to access, verification, contact and payments, and this Privacy Policy explains those purposes in one place.
LEGAL REFERENCE
How d22 handles your data
d22 gives you casino, slots and sportsbook access in supported regions, and this Privacy Policy explains what account data we collect before you join. Read it before you...
Account data useCookie choicesPayment record carePakistan support path
Our privacy position for Pakistan
This Privacy Policy applies when you access d22.vin, open an account, use our lobby where local law permits, contact us, or make transactions through supported Pakistan rails. We collect the data needed to run your account, confirm access, protect balances, process requests and keep records required for platform operation. That may include your name, phone number, device data, login activity, payment references
and messages you send to our team. We do not sell your personal data. We share limited records only with service partners that help us operate payments, security, hosting, analytics or customer care. We keep data for as long as needed for account handling, legal duties, dispute checks and fraud prevention, then reduce or remove it when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY HELP
Contact paths for data requests
If you want to ask about your Privacy Policy rights, use the same contact route shown inside your d22 account. We may ask for proof that the request is really yours before changing or sharing account records. That check protects your balance, payment history and private messages.
Team online
Account inbox
Send privacy requests from the account inbox when you can still log in. It links your message to your account without exposing extra personal data in open channels.
Live chat handoff
Use live chat for simple privacy questions, then our team can move sensitive requests into a safer account channel before any data is discussed.
Email confirmation
If account access is blocked, email support with your registered phone number and a short privacy request. We check identity before sending or changing records.
DATA CARE
Signals behind this policy
We write this Privacy Policy from the way d22 actually operates: account access, payment checks, cookie settings, device security and support handling. The policy is checked when we...
Account data map
We map the data collected at account opening, login, lobby entry and support contact, then align this policy with those...
Payment record separation
JazzCash, Easypaisa, SadaPay and Raast references are kept apart from chat content where possible, reducing unnecessary access across support and...
Device security checks
Login records, browser type and device signals help us spot unusual access attempts, protect account sessions and explain why some...
Cookie wording match
Cookie descriptions are linked to the categories we use, including session stability, fraud prevention, preference memory and service measurement on...
Retention tracking
We track why records are kept, such as account support, payment disputes, risk controls or required business records, then remove...
Team access rules
Only staff roles that need account records for support, security or payment checks can access them, with internal permissions shaped...
POLICY CONSISTENCY
How this policy stays aligned
Your privacy notice should not feel different from one d22 page to another. We keep wording aligned across account, cookie, support and transaction screens, so each page points back to the same...
Cookie panel
Cookie choices use the same category names as this policy, so you can connect a setting with its purpose before accepting or changing it.
Support scripts
Support replies follow this policy when asking for identity checks, avoiding extra documents unless a privacy or account security task needs them.
Payment pages
Transaction screens show only the fields needed for JazzCash, Easypaisa, SadaPay or Raast processing, while privacy wording explains related record use.
Security prompts
When we ask for a code, device check or login confirmation, the reason fits the security purpose described in this Privacy Policy.
Message storage
Chat and inbox records are handled as account support data, with access limited to teams helping with your request or related checks.
Regional wording
Access wording refers to supported regions and where local law permits, keeping the Privacy Policy clear without making broad availability claims.
PAGE ELEMENTS
Policy layout inside your account
This section explains the privacy-facing parts you see around d22, not a separate product pitch. We place policy links, cookie controls and contact routes near the actions that...
Footer policy link
The Privacy Policy link sits in the site footer so...
Cookie control area
Cookie choices appear through a clear panel that separates essential...
Account settings route
Your account area gives you a practical route for privacy...
Security prompt labels
Security prompts are written to show why a code, device...
Transaction context chips
Where payment records are involved, labels mention JazzCash, Easypaisa, SadaPay...
Policy date marker
We show a policy date so you can tell when...
Common Privacy Policy questions
We collect data needed for account access, identity checks, payments, security and support, such as your name, phone number, login records, device data and messages.
We use payment references to process requests, match account activity, answer disputes and meet record duties. We avoid mixing those records with unrelated support content.
No. We do not sell personal data. Limited sharing happens only with service partners needed for payments, hosting, security, analytics, support or required record handling.
Yes. Contact us from your account inbox where possible and describe the correction needed. We may verify your identity before changing account or payment records.
Cookies keep sessions working, remember preferences, help detect unusual access and measure site performance. You can manage available choices through the cookie control area.
We keep records while they are needed for account service, payment handling, security checks, disputes or legal duties, then reduce or remove them when suitable.