Privacy Policy for your dream11 account
dream11 keeps account data, device checks and Pakistan payment privacy rules in one clear policy, so you know what we collect before you open your account.
How we handle your privacy choices
This Privacy Policy explains how dream11 collects, uses, stores and shares data connected with your account, device, payments and support requests in supported regions where local law permits. We use this data to keep access secure, process account actions, detect misuse, answer your privacy questions and meet lawful duties that apply to our service. We do not ask for more data than
we need for these purposes, and we keep retention periods tied to account, safety and regulatory needs. When you use JazzCash, Easypaisa, SadaPay or Raast, we record only the payment references needed to match your account activity and resolve privacy or account queries.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep privacy wording current
Our Privacy Policy is written for the account flow you actually use on dream11. We check the wording against login screens, payment records, support forms, cookies and security...
Account mapping
We map each policy clause to an account step such as opening access, login checks, phone confirmation or profile edits...
Payment reference check
JazzCash, Easypaisa, SadaPay and Raast references are checked against privacy wording to make clear which payment data we keep, why...
Cookie assessment
We separate cookies needed for login and security from optional measurement cookies, then describe them in plain English so you...
Support training
Support staff follow privacy scripts for identity checks, data copies and correction requests. The scripts reduce unnecessary data sharing and...
Access control
Internal access to personal data is limited by role. Payment teams, security staff and support agents see different fields, and...
Change log
When we change the Privacy Policy, we record the reason, affected clauses and date. This helps you see whether a...
How this policy connects with others
Privacy wording should not sit alone. We align this page with our cookie, terms, support and account-security pages so your rights and our data duties stay consistent. If...
| Terms page | Our Terms page describes account conduct, while this Privacy Policy explains the data used to manage that conduct. Both pages use the same account wording so you can read them together. |
|---|---|
| Cookie page | The Cookie page focuses on browser storage, session tools and measurement choices. This Privacy Policy links that data to account security, device recognition and service improvement in plain language. |
| Security page | Security content explains controls such as login checks and device signals. This Privacy Policy sets out which personal data supports those controls and how long related records may be kept. |
| Support page | Support content tells you how to reach us, while this policy explains how support messages, attachments and identity checks are handled when your request includes personal data. |
| Payment pages | Payment pages mention JazzCash, Easypaisa, SadaPay and Raast for account activity. This policy explains how related references are stored, matched and used for privacy or account queries. |
| Promo board | If a promotion requires account eligibility checks, this policy explains the data categories behind that decision. We avoid adding extra personal data collection just for display purposes. |
| App access | App access content may mention device behaviour and login flow. This policy explains the privacy side, including device identifiers, crash data, session records and account protection signals. |
Visible Privacy Layout Cues
We designed this Privacy Policy page so key privacy details are easy to find before you open or continue using your account. The layout separates data...
Short privacy badges
The badges near the hero summarise the main privacy areas without replacing the full policy. They point you toward account data, payment privacy, security checks and your available request paths.
Local context chips
Chips for JazzCash, Easypaisa, SadaPay and Raast show where payment references may appear in privacy handling, without turning the policy into a payment instruction page.
Plain headings
Each heading names the privacy task being explained, such as collection, sharing or support contact. This keeps the page scannable while still giving enough detail for careful reading.
Rights section
Privacy request routes are grouped in one place so you can ask about access, correction or deletion without searching through unrelated account copy or payment text.
Security markers
Security markers show where privacy data supports login checks, device matching and misuse detection. They help explain why some records must stay linked to your account for a period.
Change signals
Policy change signals explain when wording has been adjusted and why. They help you understand whether an update affects cookies, account data, support records or payment references.