Cookie Policy
The Cookie Policy explains browser storage, while this Privacy Policy explains the personal data linked to those signals. The two pages use the same wording for device, session and consent handling.
LEGAL REFERENCE
Privacy Policy for Your d66 Account
d66 keeps Casino Online & Sportsbook account data in one privacy flow for Pakistan, so your profile, device access and payout checks are handled under this policy. Read...
Pakistan privacy scopeAccount data clarityJazzCash contextSecurity request path
How We Handle Your Privacy
Our Privacy Policy explains what we collect when you open, use or close a d66 account where local law permits. We collect details you give us, device signals, session records, payment references and support messages so we can run access checks, protect your balance, process payout requests and answer privacy queries. We do not sell your personal data. We share data only
with service providers that help with security, hosting, verification, payment routing or legal duties in supported regions. Your JazzCash, Easypaisa, SadaPay and Raast references are used as context for account checks, not as public profile details. If we change this policy, we place the updated wording on this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HELP DESK
Privacy Questions Reach Our Team
You can contact us about this Privacy Policy without searching through the lobby. We keep privacy paths separate from general account help, so your request can be checked by the team that handles access, correction and deletion questions.
Team online
Email privacy desk
Send us your account email, the privacy request you want handled and any relevant payment reference. We use those details only to verify the request and reply through the contact channel on record.
Chat escalation
If you start in live chat, ask for a privacy request escalation. Our chat team records your question, confirms your account basics and moves the case to the privacy desk for a written response.
Account request form
When the account area shows a privacy form, use it for access, correction or deletion requests. The form keeps your request tied to your d66 profile and avoids repeated identity checks.
POLICY CARE
How This Policy Stays Current
We treat the Privacy Policy as an operating document, not a static legal page. The wording is checked against account flows, payment references, support scripts and security tools...
Plain language check
We test policy wording against the actual account screens you see. If a privacy term feels unclear, we replace it...
Security alignment
Our security team checks whether login alerts, device records and verification steps match this policy. That keeps privacy wording tied...
Payment context audit
Payment references for JazzCash, Easypaisa, SadaPay and Raast are checked against the policy language. We describe why the reference is...
Support script match
Privacy answers used by support are compared with this page. That reduces mixed messages when you ask about account access...
Device access checks
Mobile web and app-style access can create device records. We keep the policy aligned with those logs, including browser type...
Change record
When the policy wording changes, we update the page date and keep an internal record of what changed. That helps...
PAGE MATCH
Consistent Privacy Across d66 Pages
Your privacy rights should not change depending on which legal page you open. We keep the Privacy Policy aligned with related d66 pages so account data, cookies, security checks and support requests...
Terms page
Our Terms page covers account rules, while this page covers privacy handling. Where both mention verification, this policy focuses on what data is collected and why it is used.
Security page
Security wording describes protection tools; this policy explains the data behind those tools. Login alerts, device checks and unusual access flags are kept consistent across both pages.
Support page
The Support page tells you how to reach us. This Privacy Policy explains what happens to the messages, attachments and account references you provide during a privacy-related support request.
Promo terms
If a promotion needs account checks, related terms may mention eligibility. This policy explains how the supporting data is handled, stored and limited to the purpose of that check.
Account page
The account area shows profile fields, contact details and verification status. This Privacy Policy explains why those fields exist and how correction or deletion requests are handled.
Payment page
Payment pages show local rails and transaction steps. This policy explains how related references are used for account matching, security checks and payout support in supported regions.
Privacy Cues You Can See
We make privacy signals visible across the d66 legal layout, so you can see what the policy covers before you open an account. The page design...
Updated date
The policy area shows the latest update date near the opening copy. That helps you know whether the wording has changed before you send a privacy request or open your account.
Data category labels
Sections use labels for profile data, device data, payment references and support messages. These labels help you connect each privacy statement to the account action that creates the record.
Request route
Contact paths are placed near the policy text instead of hidden in the footer. You can move from reading about your rights to sending a request without losing the page context.
Local rail chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips where relevant. They remind you that payment references can support verification, but do not become public profile details.
Security markers
Where the policy mentions access protection, the layout uses security markers for login, device and verification records. These cues separate protection data from general profile details.
Plain sections
We avoid dense legal blocks where possible. Short sections explain what data is collected, why it is used and how you can ask us to check, correct or delete it.
Privacy Policy Questions Before Joining
We collect account details you provide, contact data, device records, session activity, support messages and payment references. Each category supports account access, security checks, payout handling or your privacy requests.
Payment references help us match JazzCash, Easypaisa, SadaPay or Raast activity to the correct account. They support verification and payout handling, and they are not shown as public profile details.
Yes. Contact the privacy desk from your account email and state that you want an access request. We may ask for verification before sharing account-related records with you.
Yes. If your contact details or profile fields are wrong, send us the corrected details through the privacy route. We check the request against your account before making changes.
Device data helps us protect your account from unusual access. We may record browser type, session time, IP signals and security flags so login checks can be handled more accurately.
We share data only when needed for hosting, security, verification, payment routing, support handling or legal duties in supported regions. We do not sell your personal data to outside advertisers.