Terms page
The Terms page explains account conduct, while this page explains data handling. Where account checks are mentioned in both places, we use the same meaning and avoid mixed privacy wording.
LEGAL REFERENCE
Privacy Policy for your account
111x game keeps casino, slots and sportsbook account data under one privacy policy, so you can see what we collect before you open your account. We explain payment...
Pakistan data contextJazzCash reference handlingAccount privacy checksSupport record clarity
How our Privacy Policy works
This Privacy Policy explains how 111x game handles data linked to your account, login activity, identity checks, payment references and support chats. We collect only what helps us run access, protect balances, process withdrawals, answer privacy questions and meet platform controls in supported regions. When you use JazzCash, Easypaisa, SadaPay or Raast, we record transaction references, status labels and timing data, not
your full wallet passcodes. Device data such as browser type, IP range and session signals helps us detect unusual access and keep your account flow consistent. We may share limited records with service partners that help with payments, hosting, fraud checks or customer support. We do not sell your personal data. Access is handled where local law permits, and you can contact
us to ask for access, correction or deletion where available.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Signals behind this privacy text
We write this Privacy Policy from the way 111x game actually runs account access, support records and payment references. The wording is checked against our current forms, lobby entry points and payment...
Account flow matching
The policy maps to the fields we ask for during account creation, login checks and verification. We avoid adding data categories here unless they appear in our working account flow.
Payment reference masking
JazzCash, Easypaisa, SadaPay and Raast records are described as reference data. Full wallet passcodes are not requested by 111x game, and our policy language reflects that boundary.
Session log clarity
We explain browser, IP range and device signals because these are common security records. They help us spot unusual account entry without turning the policy into vague legal wording.
Plain language edits
Our privacy wording is written for Pakistani English readers using direct account language. We keep legal terms only where needed and explain what each data category means.
Partner access limits
Where service partners process records for hosting, payments or support, the policy explains the reason. We keep this focused on account operation rather than broad data sharing.
Change control
Policy changes are logged before publication so our support team can answer what changed. If a privacy request refers to older wording, we check the version active at that time.
PAGE ALIGNMENT
How this policy stays aligned
Our legal pages should not contradict each other. This Privacy Policy sets the data handling baseline, while other pages explain account rules, cookies, security and promotions. We align the language so you...
Cookie page
Cookie wording sits close to this policy because browser identifiers affect privacy. The cookie page explains browser storage, while this policy explains how that data relates to your account.
Security page
Security content covers protection steps such as login checks and alerts. This policy explains the personal data behind those steps, including session records and device signals.
Verification page
Verification wording explains why we may ask for documents or account checks. This policy explains how those records are stored, used and limited after the check is complete.
Promotion rules
Promotion pages may mention account eligibility checks. This policy explains the data side of those checks, such as account status and activity records, without adding unrelated offer wording.
Withdrawal terms
Withdrawal wording explains timing and approval steps. This policy explains privacy handling for references, bank or wallet status records and support messages linked to a payout query.
Contact page
The contact page shows how to reach us. This policy explains what data we may ask for when you raise a privacy request, correction request or security concern.
Privacy elements you can spot
We place privacy markers near account actions so the policy is easier to use. Short labels, consent text and security prompts connect back to this page...
Consent banner
The consent banner links browser storage choices to this Privacy Policy. It helps you understand how cookies, device signals and session data connect to account access.
Account field labels
Sign-up fields use short labels for mobile number, email and password creation. These labels match the data categories explained here, so the policy reflects the account form.
Security prompt
When we ask for extra verification, the prompt points back to privacy handling. You can understand why a device check or identity step may be needed.
Support ticket tag
Privacy-related support tickets are tagged by request type. This helps us route access, correction and deletion questions without mixing them with general account service messages.
Change date area
The policy page includes a change area so you can identify updated wording. This matters when privacy requests refer to account activity from an earlier period.
Local context chips
Small Pakistan context chips explain where payment references and access wording apply. They keep JazzCash, Easypaisa, SadaPay and Raast mentions tied to privacy, not sales copy.
Questions about our Privacy Policy
We collect account details, login records, device signals, payment references and support messages needed to run your account. We do not ask for wallet passcodes from JazzCash, Easypaisa, SadaPay or Raast.
Device and session data helps us recognise normal account access and spot unusual activity. This can include browser type, IP range, login timing and security signals linked to your account.
We keep payment references, status labels and timing records so deposits and withdrawals can be traced. These records help support answer payment questions while keeping wallet credentials outside our collection.
Yes, you can contact us to request access to personal data linked to your account. We will verify you first, then respond with the records available under applicable privacy handling.
If account details are wrong, contact support with the correct value and verification material. We will check the request, update eligible fields and keep a record of the correction.
We may share limited data with partners that help with hosting, payments, security checks or support. They receive only what is needed for that task and not broad account access.
We update the privacy page when our data handling changes. The page change area helps you see newer wording, and support can check which wording applied to an older privacy request.