Account terms
The Privacy Policy and account terms use the same meaning for account data, verification data and wallet records, so each page points to the same handling approach.
1xb keeps live casino, slots and sportsbook account data under one Privacy Policy, so you can see why we ask for details before you open your account. We...
Our Privacy Policy covers the data we need to run your 1xb account, confirm access, process wallet activity and respond to privacy requests. This can include your name, contact details, login records, device signals, transaction references and support messages. When JazzCash, Easypaisa, SadaPay or Raast appears in your account flow, we keep only the relevant context needed for verification, reconciliation and record
keeping. We do not sell your personal data. We share limited data with service providers only when they help us operate the account, secure the platform, resolve disputes or meet lawful duties in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions should reach the team that can read account records, verify identity and respond without exposing your details. We keep privacy contact routes separate from general lobby help where possible. Use the route that matches your request, and include only the data needed to identify your account safely.
Send privacy questions from the email linked to your 1xb account. We may ask for extra account checks before sharing, correcting or limiting access to personal data.
If you start through chat, our agent can route the matter to privacy support after basic identity checks. Chat is useful for status queries, not for sending sensitive documents.
For suspected account access issues, contact us with time, device and location details. We use those signals to inspect login records while keeping private data restricted.
A Privacy Policy should match how the account flow actually works. Our internal checks look at registration fields, payment references, login security, live table session data and support transcripts. When the product...
We compare the Privacy Policy against the details requested during account creation, identity checks and profile edits, so the policy reflects data you actually provide to 1xb.
JazzCash, Easypaisa, SadaPay and Raast references are checked against our wallet flow. The policy explains why transaction context may be kept for verification and disputes.
Internal access to personal data is limited by role. Support, payment and security staff see only the account details needed for their task and logged action.
We describe device, browser and session signals in plain language because they help us secure account access, detect unusual activity and protect your balance records.
We keep records only for operational, security, dispute and lawful needs. The policy explains retention in practical terms rather than hiding it in broad legal phrasing.
Privacy requests are logged, checked and answered through controlled channels. We confirm account ownership first so another person cannot obtain your private 1xb data.
Your privacy rights should not change from one legal page to another. We keep this page aligned with our account terms, cookie wording and security explanations. The goal is simple: when you...
The Privacy Policy and account terms use the same meaning for account data, verification data and wallet records, so each page points to the same handling approach.
Cookie wording connects to this Privacy Policy where browser identifiers, session data and preference storage are involved, helping you understand data use across pages.
Security explanations match this policy when they mention login checks, device signals, suspicious access and actions taken to protect your 1xb account.
Wallet wording is kept consistent with the Privacy Policy whenever JazzCash, Easypaisa, SadaPay or Raast transaction context is referenced for checks or disputes.
Support messages can contain personal data, so our support wording connects back to this policy and explains how request history may be stored.
Where local law permits access, we use matching wording across legal pages so Pakistan-related privacy statements do not conflict with account availability terms.
When privacy wording changes in a material way, related policy pages are checked for the same language so your account expectations remain clear.
This page is designed to help you scan privacy duties before creating or using an account. We use plain headings, short badges and direct wording so you can...