Privacy Policy For Your 1xx Account
Live Baccarat, Aviator, slots and cricket markets all connect to one 1xx account, so this Privacy Policy explains what we collect, why we use it, and how you...
How We Handle Privacy Requests
This Privacy Policy explains how 1xx handles data linked to your account, device, location checks, lobby activity, security events, and Pakistan payment records in supported regions. We collect only what we need to create and protect your account, process requests, keep service logs, meet legal duties, and answer your privacy questions. We may use service partners for hosting, fraud checks, payment routing,
support tools, and analytics, but we require them to handle data only for our stated purposes. If local law gives you access, correction, deletion, or objection rights, you can contact us and we will respond through the route you used or another verified channel.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Where Privacy Questions Reach Us
Your privacy request should reach the right desk without being mixed with gameplay chat. We separate account help, data rights queries, and security alerts so our team can verify you, check the relevant records, and answer with fewer delays. Use the same account details each time so we can match your request safely.
Privacy mailbox
Email us from the address linked to your 1xx account and include the request type. We may ask for extra checks before sharing account data or changing stored details.
Live support handoff
If you raise a privacy question inside support chat, our agents move it to the privacy queue. Chat staff can confirm receipt but will not expose sensitive records there.
Security alert path
Tell us quickly if you think another person accessed your account. We check login records, device signals, and recent account changes before replying with next steps.
How We Keep The Policy Current
We write this Privacy Policy from the way 1xx actually runs account access, support, payments, and lobby security for Pakistan. The wording is checked when we adjust cookies...
Operator wording
We describe the same account fields our team sees during support checks, rather than vague data labels. That keeps the...
Service partner checks
Before adding a hosting, analytics, fraud, or support vendor, we check what data is needed and record the purpose. The...
Payment record clarity
JazzCash, Easypaisa, SadaPay and Raast records may show reference codes, timestamps, status, and account matching details. We explain those records...
Access control
Internal access is restricted by work role, with sensitive actions checked through account tools. The policy reflects that separation so...
Change tracking
When we adjust the Privacy Policy, we update the page date and keep the language direct. Important changes may also...
Plain English
We use clear Pakistani English and avoid legal padding where possible. If a term affects your data rights, we explain...
How This Policy Matches Our Pages
Our legal pages should not contradict each other. The Privacy Policy explains data handling, while account rules explain service use and cookie text explains browser storage. When one...
Privacy Layout You Can Scan
This page is built so you can find the data point you came for quickly. We use short headings, local context chips, request routes, and FAQ...
Short section labels
Each section starts with a plain label so you can see whether it covers collection, sharing, storage, rights, cookies, or contact routes before reading the longer paragraph.
Local context chips
The chip row uses Pakistan references such as JazzCash, Easypaisa, SadaPay and Raast only where they help explain stored transaction records and support matching.
Request-first wording
We place contact routes near the policy details because privacy questions often need verification. You see where to write before reading the deeper legal wording.
Visible update cues
Policy changes are shown through page wording and date cues. If a change affects how we use account data, we aim to make that change easy to spot.
Separate FAQ block
Common questions sit at the end so the main policy can stay structured. Answers use direct examples from account setup, cookies, support, and payments.
Mobile readable copy
Privacy text is broken into compact blocks for phone screens. You can check a data point during account setup without scrolling through unrelated lobby material.