Account terms alignment
Our account terms describe access rules, while this Privacy Policy explains the personal data behind those rules. We keep both pages aligned so identity checks are not described two different ways.
LEGAL REFERENCE
How dx11 Handles Your Privacy
dx11 keeps account checks, payment records and security logs in one clear Privacy Policy, so you know what we collect before you open your account. It explains why...
Pakistan privacy contextAccount data explainedPayment records coveredSecurity logs included
Our Privacy Position In Pakistan
Our Privacy Policy is written for dx11 account activity where local law permits access. We collect only the details needed to create your account, verify access, process payment records, respond to support requests, secure sessions and meet lawful record duties. When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive transaction references, status marks and timing records, not your full banking
secrets. We keep privacy wording plain so you can decide whether to join, update details, or ask us to correct account data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED CONTROLS
Privacy Checks We Keep Visible
We want you to see practical privacy controls before you share details with dx11. The policy reflects how account access, payment status checks, device sessions and support records work in day-to-day operation...
Account verification
We compare account details with session and payment records when needed to protect access. The check is narrow, and support cannot discuss private records without matching identity signals first.
Payment references
JazzCash, Easypaisa, SadaPay and Raast activity may create transaction IDs, status marks and time stamps. We use those records to reconcile account balance questions and resolve payment disputes.
Session security
We record device type, login timing and risk signals to spot account misuse. These logs help us challenge unusual access without exposing your private account data to unrelated teams.
Support case trail
When you contact us, we keep the message thread, response timing and case topic. That trail helps us answer follow-up privacy questions without asking you to repeat sensitive details.
Data retention
Some records stay while your account remains active or while lawful duties apply. When a record is no longer needed, we reduce, archive or remove it under our internal schedule.
Access requests
You can ask what account data we hold, where practical and lawful. We verify the request first, then share the relevant categories without exposing security controls or another person’s details.
POLICY MATCH
How This Policy Stays Consistent
This page sits beside our other legal pages, but it has one job: explain privacy. We keep wording aligned with account terms, cookie handling and payment rules so you do not face...
Cookie page alignment
Cookie handling may involve device IDs, browser settings and session tags. This policy connects those signals to account security and explains why some technical records matter for privacy.
Payment rule alignment
Payment pages discuss how balances move, while this policy explains the records created around JazzCash, Easypaisa, SadaPay and Raast. The aim is one privacy meaning across each page.
Support script alignment
Support replies follow the same privacy language used here. If your request concerns personal records, the team should confirm identity and avoid sharing data in an open chat thread.
Security wording alignment
Security pages may mention login checks and device signals. This policy explains the privacy side of those controls, including why logs are collected and how they support account protection.
Update timing alignment
When we edit privacy wording, we check connected legal pages for matching phrasing. That helps you understand current handling without reading conflicting versions across the dx11 site.
Pakistan context alignment
Where local law permits access, this policy explains how Pakistan account records are handled. Local payment names and support paths stay consistent across related legal pages.
POLICY LAYOUT
Visible Privacy Page Elements
We structure this Privacy Policy so you can scan it before opening an account and return later when a question comes up. The layout highlights what data is...
Clear data categories
The page separates account details, payment references, device logs and...
Plain purpose labels
Each data category is paired with a reason, such as...
Pakistan context chips
Short chips name JazzCash, Easypaisa, SadaPay and Raast where payment...
Request path prompts
Contact prompts are placed near privacy rights wording, so you...
Retention cues
Retention wording tells you why some records stay longer than...
Change markers
When privacy wording changes, page markers help you notice the...
Privacy Questions About dx11
We collect account details, contact data, login records, device signals, payment references and support messages needed to run your account, secure access, process requests and meet lawful record duties.
For JazzCash, Easypaisa, SadaPay and Raast, we normally handle transaction references, status marks and timing records. We do not need your full wallet secrets to reconcile account activity.
Device and login logs help us detect unusual access, protect your account and investigate security questions. They may include time, browser type, approximate location signal and session behaviour.
Yes, you can ask us to correct account data that is inaccurate. We verify your identity first, then amend records where practical, lawful and consistent with account security needs.
Retention depends on the record type. Account, payment and security records may stay while your account is active or while legal, dispute or fraud-prevention duties still apply.
Only teams handling support, privacy, security or payment reconciliation should access relevant messages. We limit access by work need and avoid sharing private case details across unrelated areas.