LEGAL REFERENCE

Privacy Choices For Your dream11 Account

dream11 keeps your account profile, casino lobby activity and sportsbook records under one Privacy Policy, with clear choices before you open an account where local law permits.

Pakistan account dataJazzCash contextEasypaisa contextRaast references
Explore Lobby Read FAQ
dream11 Privacy Choices For Your dream11 Account

How We Handle Account Data

This Privacy Policy explains what we collect when you create or use a dream11 account in supported regions of Pakistan. We collect account details you give us, device and session data, security logs, transaction references, support messages and records linked to casino, live casino and sportsbook activity. When you use JazzCash, Easypaisa, SadaPay or Raast, we keep the reference, status, amount and

time needed to match the transaction; we do not ask for your wallet PIN. We use this data to run your account, verify withdrawals, protect access, answer privacy requests and meet legal duties where local law permits. We keep records only for as long as we need them for account operation, dispute handling, security checks or lawful reporting, then remove or anonymise

them when retention is no longer required.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Contact Us About Privacy

If you want to ask about access, correction, deletion or a privacy concern, contact us from the same account you use on...

Privacy mailbox Email our privacy team with the account email...
Account chat Use in-account chat when you can access your...
Security escalation If you think your account data was seen...
POLICY CHECKS

How We Keep Policy Text Reliable

We write this Privacy Policy from the way dream11 actually handles accounts, payments, live sessions and support records. Our legal, product and security teams check the wording so...

Operational wording

We describe account data by the records our systems create, such as login events, device signals, table session IDs, sportsbook...

Pakistan context

The policy refers to Pakistan payment rails only where they affect privacy records. JazzCash, Easypaisa, SadaPay and Raast entries are...

Security alignment

Our policy wording is checked against account controls like password reset, device recognition and withdrawal verification, so the text reflects...

Support traceability

Privacy requests are logged with time, channel and outcome. That record helps us answer follow-up questions, confirm what was requested...

Retention mapping

We connect each data category to a retention reason, such as account operation, payment matching, dispute handling or legal duty...

Change control

When we update privacy wording, we check the affected screens and support scripts first. If a material change affects your...

Consistent Privacy Across Our Pages

Our legal pages should not tell different stories about the same account. This section explains how the Privacy Policy lines up with related dream11 pages, so your data...

Terms page
Our Terms explain account rules, while this Privacy Policy explains the data behind those rules. If a security check happens, the Terms cover the action and this page covers the records used.
Cookie page
Cookie settings deal with browser storage and tracking choices. This Privacy Policy connects those signals to broader account records, including sessions, device data and preference choices linked to your profile.
Promotions page
Where a promotion has eligibility checks, this policy explains what account data may be used to confirm those checks. We avoid using promotion wording to expand data use beyond what is stated here.
Withdrawal page
Withdrawal instructions explain the action flow. This Privacy Policy explains why we may keep identity checks, transaction references, support messages and status logs connected to a withdrawal request.
Security page
Security content describes protection tools. This policy explains the personal records those tools may create, such as login alerts, failed attempts, device fingerprints and contact changes.
Support page
Support pages show how to reach us. This policy explains how we store chat, email and ticket records, and how those records help us answer privacy requests securely.
Account page
Your account area shows profile fields and activity records. This policy explains why those details are collected, how they are used and when you can ask us to change them.

Policy Layout Elements You Can Check

We design the Privacy Policy page so key choices are visible without making you search through unrelated copy. Each block points to a privacy action, record...

Clear data categories

The page separates profile details, device data, session records, transaction references and support messages. That structure helps you understand which records come from you and which are created by our systems.

Local transaction context

Where payment rails are mentioned, the wording stays narrow. We describe stored references, status checks and receipt matching, not wallet passwords or unrelated financial details.

Choice language

We explain how you can ask for access, correction or deletion where available. The wording also notes when we may need to keep records for security, disputes or legal duties.

Account safety cues

Security sections call out login records, device signals and withdrawal checks. These cues show why certain data is collected before sensitive account actions are allowed to continue.

Contact placement

Privacy contact paths sit close to the policy text they relate to. That makes it easier to raise a request without leaving the page or sending details through the wrong channel.

Update signals

When policy wording changes, the page can show what shifted and why. We aim to make changes understandable, especially if they affect data use or your available choices.

Privacy Policy Questions Answered

We collect the details needed to run your account, such as profile fields, contact data, login records, device signals, session activity, transaction references and support messages connected to your requests.

No. For JazzCash, Easypaisa, SadaPay and Raast, we store only the reference details needed to match a transaction, such as amount, time, status and receipt or transfer ID.

Withdrawal verification records help confirm that the request comes from the account holder and matches payment history. We may keep identity checks, status logs and support messages for security and dispute handling.

Yes, you can contact us to correct account details where the change is allowed and verified. We may ask for account confirmation before editing records that affect access or payments.

We keep records only while they are needed for account operation, security, payment matching, support, disputes or legal duties. When retention is no longer needed, we remove or anonymise records where possible.

Only trained dream11 staff who need the request for their role should access it. We log the request, check identity and limit shared details to what is needed for a proper response.