Account terms
Our account terms explain eligibility, access, and account duties, while this policy explains the data records behind those steps. The two pages are checked for matching definitions.
LEGAL REFERENCE
How We Handle Your Data
Live casino tables, slots and sportsbook access all rely on clear privacy choices at dd77. Before you open an account, this Privacy Policy explains what data we collect...
Account data useSecurity checksPakistan privacy contextClear contact routes
Policy Scope For Your Account
Privacy starts with the account details you give us and the records created when you use dd77 in supported regions. We collect the details needed to create and protect your account, run identity checks required by law, process account requests, maintain session security, investigate misuse, and answer privacy questions. When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive transaction reference
data, status messages, sender name details, and timing records from payment processors. We do not ask for wallet PINs or banking passwords. We keep records only for operational, legal, security, and dispute-handling needs, then restrict or remove them according to our retention rules.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy Help From Our Team
Questions about your data need a route that reaches the right people, not a generic inbox. We separate privacy requests from ordinary account messages so your query can be logged, checked, and answered with the correct context. Include your registered mobile number or email, but never send passwords, wallet PINs, or screenshots that expose private codes.
Team online
Privacy email
Send privacy requests from the email linked to your dd77 account. We use that match to confirm the request source before discussing account records, payment references, or correction requests.
Live chat handoff
If you start in live chat, ask for privacy help and we will move the matter to the correct internal queue. Chat agents may ask limited checks before escalating.
Security mailbox
Report suspected unauthorised access through the security route. We check login records, device changes, and recent account actions before advising what privacy steps may apply.
POLICY CARE
How Our Policy Stays Accurate
We write this policy from the way dd77 actually handles account records, payment references, support cases, and device security. The wording is checked when our account flow, processors, or retention practice changes...
Named ownership
Our internal account, security, and support leads contribute to privacy wording. That gives each clause practical context, from verification records to how support sees account history.
Change checks
When we adjust account screens, identity checks, or payment reference handling, the privacy wording is examined for accuracy. Material changes are reflected on this page with clearer wording.
Retention rules
We define why records are kept, who may access them, and when they should be restricted or removed. Security, legal, and dispute needs shape those timeframes.
Access control
Account records are not open to every staff role. We use permission levels so support, payments, and security teams see only the data needed for their task.
Processor checks
Where service providers help with payments, hosting, analytics, or message delivery, we check whether they need the data and require handling aligned with our privacy standards.
Local wording
We reference Pakistan payment rails and supported regions because that is where many account questions arise. Local examples help you understand what records may be created.
PAGE ALIGNMENT
Consistency Across Our Legal Pages
Privacy wording should not conflict with the rest of our legal pages. We align this page with account terms, cookie wording, promotion rules, and security notices so the same data practice is...
Cookie wording
Cookie details connect to this policy because device identifiers and session tools can create privacy records. We describe their purpose without mixing them with account balance rules.
Security notices
Security notices may mention login alerts, password resets, and device changes. This policy explains how those events are recorded, protected, and used for account safety.
Promotion rules
If a campaign needs identity, location, or account status checks, the campaign text should match this policy. We avoid collecting extra data beyond the stated purpose.
Payment references
Payment pages may show JazzCash, Easypaisa, SadaPay, and Raast options. This policy explains the related reference records, status messages, and verification checks.
Support scripts
Support scripts are written to avoid unnecessary private details. Agents should request only what helps identify your account or understand your privacy request safely.
Update notices
When legal wording changes, update messages should point you to the affected page. Privacy changes are written plainly so you can see what has changed.
Privacy Layout Built For Clarity
This page is arranged so you can scan the privacy points that matter before opening an account or sending a request. The layout separates collection, use...
Plain header
The header states that the page is about privacy, not a general account announcement. That keeps your attention on data use, retention, and privacy contact choices.
Context chips
Short chips reference JazzCash, Easypaisa, SadaPay, and Raast only as privacy context. They show where transaction references may arise without turning the policy into payment copy.
Contact cards
Contact cards separate privacy email, chat handoff, and security reporting. Each card explains what to include and what private codes you should never share.
Data categories
Sections group account details, payment references, device data, cookies, and support records. Grouping helps you see which record type is being discussed in each clause.
Retention cues
Retention wording is placed near the data category it relates to. That makes it easier to understand why a record may be held after an account action ends.
Rights prompts
Where a privacy right may apply, we place the contact route close to the explanation. You can then ask for access, correction, or deletion assessment with context.
Privacy Policy Questions Answered
We collect details needed to create, secure, and manage your account, such as contact data, login records, device signals, verification results, and support history. We avoid asking for wallet PINs or passwords.
Payment references help us match account requests with processor status messages and resolve disputes. We may see sender names, timestamps, and reference numbers, but not private wallet PINs or banking passwords.
Yes, you can contact us if your account details are inaccurate. We may ask for identity checks before making changes, because privacy requests must come from the account holder.
Retention depends on the record type and the reason it exists. Security logs, dispute records, and legal records may be kept longer than ordinary support messages, then restricted or removed.
We may share limited data with processors that help operate hosting, payments, analytics, messages, security, or support tools. Each sharing case must have a service purpose tied to dd77.
Cookies and similar tools may remember sessions, protect logins, and measure page performance. When those tools create personal data, we handle that data under this Privacy Policy.
If we change how we describe data handling, we update this page and may place a notice where appropriate. You should read the latest version before sending privacy requests.