Same account language
Across our legal pages, account, wallet and support terms use the same meanings. That helps you connect a privacy statement here with the account action described elsewhere.
LEGAL REFERENCE
Privacy choices for your dream11 account
Your account data, payment rail labels and support records are handled under this dream11 Privacy Policy for Pakistan access where local law permits. Open your account in seconds...
Pakistan privacy termsJazzCash data contextEasypaisa record handlingSadaPay and Raast labels
How we handle account data
This Privacy Policy explains how dream11 collects and uses the data you provide when you open an account, verify access, contact support, receive security alerts or use supported payment rails in Pakistan. We may process your name, phone number, device signals, login records, wallet references, transaction status, game-session markers and communication history so your account can be operated, checked and protected. We
use this data for account administration, fraud prevention, payment reconciliation, legal compliance, customer care and service measurement. We do not sell your personal data. We share limited data with processors only when needed for hosting, verification, payment routing, analytics, security monitoring or lawful requests, and we keep retention periods tied to account, compliance and dispute needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How our privacy text stays current
We maintain this Privacy Policy as a working account document, not a static page. When our account flow, payment routing, verification process or support tooling changes, we check whether the privacy wording...
Operational ownership
The policy is written around the account data we actually handle, including login records, support tickets, wallet references and verification signals. That keeps the wording tied to dream11 processes.
Pakistan context
We name local rails such as JazzCash, Easypaisa, SadaPay and Raast only as privacy context. The policy focuses on records created around those account actions.
Retention checks
Retention periods are assessed against security, account administration, transaction disputes and legal needs. When data is no longer required, we aim to delete or anonymise it safely.
Access controls
Internal access to personal data is limited by role. Support, security and payment operations can only reach records needed for the task they are handling.
Processor control
Where vendors support hosting, analytics, security or payment routing, we share only the data needed for that function. We expect those vendors to apply suitable safeguards.
Change tracking
Policy changes are checked against live account flows before publication. If a material privacy change affects you, we may flag it through the account area or support channel.
PAGE CONSISTENCY
Policy consistency across dream11 pages
This Privacy Policy sits alongside our other legal pages, but it has its own purpose. Terms explain account rules, cookies explain browser storage, and this page explains personal data handling across dream11...
Cookies kept separate
Cookie storage is mentioned only where it affects privacy records, such as device recognition or session security. Detailed browser storage choices belong on the cookie page.
Terms do not replace privacy
Account rules may explain what you can do on dream11, but this page explains what happens to your personal data when those account actions create records.
Payment records framed carefully
Payment rails are referenced for data context only. We explain how transaction references and status labels may be processed, without turning this policy into a banking page.
Security wording aligned
Security statements across dream11 use the same practical approach: access controls, monitoring, verification and fraud checks. This page explains the personal data side of those safeguards.
Support records matched
Support pages describe how you reach us. This policy explains how messages, attachments and response history may be stored, searched and used to resolve privacy requests.
Regional access wording
Where access depends on location, we use supported regions and where local law permits. That same wording is reflected here when privacy handling depends on jurisdiction.
Privacy layout cues you can read
We structure this page so you can spot the privacy areas that matter before opening an account. Short badges, plain headings and separate request routes are...
Plain section labels
Each section title names the privacy issue it covers, such as account data, contact routes or retention. We avoid burying privacy points inside unrelated platform wording.
Local context badges
Badges mention Pakistan and local rails only where they help explain data records. They are not a substitute for the full wording in this Privacy Policy.
Request path cards
Contact cards show how to reach us for access, correction or deletion requests. Each route explains what verification may be needed before we discuss account data.
Short retention cues
Retention wording is placed near the data-use explanation, so you can see why records may be kept and when deletion or anonymisation may be considered.
Processor mentions
Where third-party processors are relevant, we describe the service function rather than naming every vendor. That keeps the privacy point focused on purpose and safeguards.
Account-first wording
We write the policy around your account journey, from sign-in to support requests. That makes the data flow easier to follow without turning the page into technical paperwork.
Privacy Policy questions for Pakistan
We may collect account details, contact data, device signals, login records, payment references, support messages and verification status. The exact data depends on how you use dream11 and which account actions you take.
When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive status labels, references and timestamps. We use those records to reconcile account activity, handle disputes and support security checks.
Yes. Contact us from your linked account channel and state the data you want to access. We may verify your identity before sharing records to protect the account from unauthorised requests.
You can ask us to correct inaccurate personal data linked to your dream11 account. Some records, such as transaction logs or security events, may need to remain unchanged for audit or legal reasons.
We keep records for as long as needed for account operation, security, dispute handling and legal obligations. When records are no longer required, we aim to delete or anonymise them safely.
We may share limited data with vendors that support hosting, security, analytics, verification, communication or payment routing. They receive only what is needed for their function and are expected to protect it.