Account terms
The account terms explain eligibility and account duties, while this policy explains personal data handling. We cross-check both so verification, contact details and record keeping are described without conflict.
LEGAL REFERENCE
Privacy Policy for your dk11 account
dk11 sets out how we collect, use and protect the details linked to your account, device and payment activity in Pakistan. Open your account with clear privacy terms...
Pakistan data handlingAccount access controlsJazzCash contextRaast context
How we handle your data
This Privacy Policy explains the way dk11 handles personal data when you access our brand home, create an account, use account security tools or ask us for help. We collect only what we need to run your account, check access, process support requests, manage risk and keep transaction records tied to supported regions, where local law permits. Some data comes directly from
you, such as your name, contact details and account settings. Other data is created when you use the service, including device signals, login times, IP data, session records and payment references from Pakistani rails. We keep privacy wording practical, so you can see which details are used for verification, service operation, security checks and legal record keeping.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Policy checks behind dk11 privacy
We treat this page as part of the account experience, not a loose legal page. Privacy wording is checked against the data we actually collect across registration, login, support and Pakistani payment...
Operational ownership
Our privacy wording is maintained by the same internal team that maps account flows, payment references and support records. That helps the policy reflect real dk11 activity rather than abstract legal phrasing.
Data map checks
We map fields collected during registration, login, verification and support. If a field is added or removed, the privacy text is checked so your account record stays described accurately.
Local rail awareness
JazzCash, Easypaisa, SadaPay and Raast references can appear in transaction records. We use those references to reconcile account activity, answer support queries and meet record duties in supported regions.
Security practice wording
The policy describes device checks, session records and access controls in plain language. We avoid vague claims and focus on what helps protect your account from unauthorised access.
Support training
Support staff are trained to separate privacy requests from routine account questions. They can collect the request, verify account ownership and move sensitive matters to the correct handling queue.
Change tracking
When the Privacy Policy changes, we keep the wording aligned with current account flows. Material edits are dated internally so our team can explain what changed and why.
PAGE ALIGNMENT
Consistent privacy wording across pages
Your privacy rights should read the same wherever you meet them on dk11. We align this page with account terms, cookie wording, support scripts and transaction help so you do not receive...
Cookie wording
Cookie text focuses on browser storage and device signals. This page connects those signals to privacy handling, including login security, session continuity and basic analytics used to maintain service quality.
Support scripts
Our support replies use the same privacy language you see here. That reduces confusion when you ask for account access records, correction of contact details or help with security concerns.
Transaction help
Payment help pages may mention JazzCash, Easypaisa, SadaPay and Raast references. This policy explains how those references become account records and why they may be retained.
Security prompts
Login alerts and account prompts must match our privacy position. We describe device checks and session records here so security messages do not appear unexplained when you return.
Promo board wording
If you check the promo board, related account activity may be recorded for eligibility and audit. This policy explains that data use without turning promotional content into privacy terms.
Regional access text
Where we mention supported regions, the privacy wording stays consistent. Access, verification and record handling are described with Pakistan context and the phrase where local law permits.
Privacy layout you can scan
This page is built so you can find the privacy point you need without reading in circles. Headings separate collection, use, sharing, retention, rights and contact...
Clear section labels
Each privacy section uses a direct label, such as data we collect or how we use it. That structure helps you move from account data to support records without losing context.
Short privacy badges
The badges near the hero summarise key themes before the full policy begins. They are not substitutes for the terms, but they help you see the main privacy areas quickly.
Rights area
Your request options are grouped together, so access, correction and deletion questions do not sit across scattered text. We also explain why identity checks may be needed first.
Retention cues
Retention wording explains that records are not kept forever by default. Some account, security and transaction data may stay longer when required for dispute handling or legal duties.
Sharing limits
The sharing section names the kinds of service partners that may process data for us. It also explains that we do not sell your personal data as a business practice.
Update marker
Policy changes are handled through visible wording updates and internal change tracking. When you return to this page, you can read the current privacy position before continuing.
Privacy questions for dk11 accounts
We collect account details you provide, such as name, contact data and login credentials, plus service records like device signals, session times, support messages and transaction references linked to Pakistani payment rails.
Device and login data help us protect account access, spot unusual sessions and keep the service working across mobile and web. We use these signals for security, troubleshooting and account continuity.
JazzCash and Easypaisa references may be stored with your account record to reconcile transactions, answer support queries and handle disputes. We treat them as account data, not as public profile content.
Yes. Contact support with the detail you want corrected, and we will verify account ownership before making changes. Some records may need to remain unchanged when required for audit or legal duties.
We share data only when needed for service operation, security, payment processing, support handling or legal requirements. Service partners must handle the data for the stated purpose rather than independent sale.
Retention depends on the record type. Support messages may be kept for service history, while transaction and security records may remain longer for dispute handling, fraud prevention and legal record duties.