Privacy Policy for your 11q1 account
Live Baccarat, Roulette, Andar Bahar and sportsbook account tools at 11q1 sit under one Privacy Policy, so you can see how we collect, use and protect your data...
How our Privacy Policy applies
This Privacy Policy covers the data we process when you create an 11q1 account, enter the lobby, contact support, use security checks or connect payment context through JazzCash, Easypaisa, SadaPay or Raast. We collect only what we need for account access, identity checks, transaction tracing, fraud prevention, service messages and legal requests that apply in supported regions. We may receive confirmation data
from payment partners, device signals from your browser and messages you send to our support team. We do not sell your personal data. When we share data with service providers, we limit the purpose, require confidentiality and keep access tied to the task. You can ask us to access, correct or delete eligible data, subject to record-keeping duties where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about privacy choices
Privacy requests need a clear route, not guesswork. Use the contact path that matches your issue, and we will ask for only the details needed to match the request with your 11q1 account and protect it from unauthorised changes.
Privacy email
Email our support desk when you want access, correction or deletion help. Include your account mobile number and the payment rail involved, such as JazzCash or Easypaisa, so we can trace the privacy request safely.
Live chat privacy queue
Use chat when you need a privacy status update while signed in. Our team may ask short security questions before discussing account data, withdrawal records or saved device activity.
Security escalation
If you think your account data or mobile number was used without permission, contact us at once. We can lock sensitive changes while our team checks login history and payment references.
How we keep this policy accurate
We maintain this Privacy Policy as an operating document for 11q1, not as a form page. Our legal, support and payments teams check wording against real account flows, including login checks, payment...
Named policy owner
A designated 11q1 privacy contact keeps ownership of this page. That role coordinates edits with support, security and payment operations before policy wording is changed for your account flow.
Local payment context
We check privacy wording against JazzCash, Easypaisa, SadaPay and Raast journeys used in Pakistan. The policy separates account data from payment confirmation records wherever our systems allow.
Access controls
Support staff see only the account fields needed for their task. Sensitive records, including identity checks and withdrawal references, require role-based access inside our internal tools.
Retention checks
We keep data for account operation, dispute handling, fraud prevention and legal duties. When a record is no longer needed, our teams place it into deletion or archival routines.
Change tracking
Material policy edits are logged with the reason for the change. If an update affects how we process your data, we aim to make the wording clear on this page.
Plain English
We write this Privacy Policy in clear Pakistani English. You should be able to understand what data we collect, why we use it and how to contact us.
Aligned privacy pages across 11q1
Your privacy terms should not change just because you move between lobby, support or account pages. We keep related policy sections aligned so the same core data rules...
| Same data categories | Account, device, payment context, security and support data are described using the same categories across our legal pages. That helps you compare privacy wording without decoding different labels. |
|---|---|
| Shared contact route | Where a privacy request is mentioned on another 11q1 page, it points back to the same support channels. We avoid sending you through unrelated forms. |
| Aligned payment wording | References to JazzCash, Easypaisa, SadaPay and Raast follow the same privacy meaning across account and cashout pages. We describe confirmation data separately from your personal account profile. |
| Security language | Login checks, device signals and access controls are described in matching terms across security and privacy pages. That keeps the account protection message consistent. |
| Cookie references | Cookie and browser storage wording connects back to this Privacy Policy when the data may identify your account. Short session tools are separated from longer analytics records. |
| Retention phrasing | Retention wording stays consistent across privacy, support and account closure content. We explain why records may remain for disputes, fraud checks or legal duties. |
| Change handling | When policy wording changes, related pages are checked for matching language. This reduces conflict between the privacy page and the account tools you use. |
Visible privacy cues on this page
This page is laid out so you can scan the Privacy Policy before opening an account. We place collection, use, sharing, retention and contact points in...
Date marker
A visible date marker helps you spot whether you have read the current Privacy Policy. If wording changes in a material way, the marker is updated with the page.
Rights summary
Your access, correction and deletion choices are grouped together so you can act without searching the whole page. Each request still needs account matching for security.
Data map
Collection points are mapped to account creation, lobby access, support chats and payment confirmation. This helps you understand which 11q1 action creates which type of record.
Security cues
Security references are kept close to the data they protect. Login checks, device records and role-based support access are shown as part of the same privacy flow.
Contact block
The contact area explains what to include in a privacy request. We ask for account identifiers only when they are needed to verify and resolve your request.
Local wording
Pakistan-specific references are written in clear local English. JazzCash, Easypaisa, SadaPay and Raast appear only where payment context affects privacy handling.