LEGAL REFERENCE

Privacy Policy for Your 1x2 Account

1x2 keeps account, payment, device and support data in a clear Privacy Policy so you know what we collect before you open your account. We explain how data...

Account dataPayment checksDevice securitySupport records
Explore lobby Read FAQ
1x2 Privacy Policy for Your 1x2 Account

How 1x2 Handles Your Data

This Privacy Policy explains how 1x2 collects, uses, stores and shares data linked to your account where local law permits. We may process your name, contact details, login records, device signals, gameplay records, payment references and support chats to run your account, verify requests and protect the service. Pakistan payment rails can require matching transaction references with the account profile you provide.

We keep only what is needed for account operation, fraud checks, dispute handling and legal duties. When third parties help us with hosting, analytics, payments or security, they receive only the data needed for that task and must keep it controlled.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Privacy Help From Our Team

If your privacy question relates to account access, payment verification or stored support chats, contact us from the account channel you already use. That helps us match the request to the correct profile without asking for data that is not needed.

Team online

Account chat

Use live chat after login for privacy requests tied to account records. We may ask for a payment reference or recent session detail before sharing or changing stored data.

Email request

Send privacy requests by email when you need a written trail. Include your registered phone or email, but do not send full wallet passwords, card data or extra documents.

Security desk

Contact the security desk if you think your account data was accessed without consent. We check login time, device signals and payment changes before advising the next step.

POLICY CHECKS

How We Keep This Policy Current

We keep the Privacy Policy tied to the way 1x2 actually operates. When account tools, payment flows or support processes change, we check whether the wording still matches your experience and update...

Operational wording

Our policy language is based on account flows we run ourselves: registration fields, login checks, session records, payment references and support transcripts connected to your 1x2 profile.

Payment mapping

We map JazzCash, Easypaisa, SadaPay and Raast references to your account only for verification, reconciliation and dispute checks, not for unrelated profiling outside the service.

Access control

Internal access to privacy data is role based. Support can see what is needed to help you, while payment and security teams work with records relevant to their task.

Change tracking

When the Policy changes, we keep the new wording visible on this page. Material changes are written plainly so you can understand what changed before you continue.

Retention checks

We assess stored account records against fraud, dispute, tax and legal needs. When a record is no longer required, we remove it or separate it from direct account identity.

Regional fit

The Policy is written for Pakistan account use in supported regions. It explains local payment data handling while keeping the same privacy principles across casino and sportsbook access.

One Standard Across Policy Pages

Our Privacy Policy sits beside other legal pages, but it has its own purpose: explaining personal data handling. We keep the same definitions, account references and contact routes...

Privacy Policy
This page focuses on personal data: what we collect, why we use it, how long we keep it, and how you can contact us about your account records.
Terms page
The Terms page covers account rules and service use. When it mentions verification, this Privacy Policy explains the data side of that verification process.
Cookie page
The Cookie page covers browser storage and similar tools. This Privacy Policy links that activity to broader account security, analytics and preference handling.
Payment records
Payment wording across our legal pages stays aligned. JazzCash, Easypaisa, SadaPay and Raast references are described as verification records, not open-ended account profiling.
Support records
Support wording stays consistent across channels. Chat transcripts, email threads and call-back logs are treated as account records when they relate to privacy, security or disputes.
Security wording
Security language uses the same approach everywhere: protect account access, detect suspicious activity, verify sensitive requests and reduce misuse without collecting data that is not needed.
Update handling
When one legal page changes in a way that affects privacy, we check related wording here so account data handling remains clear and consistent.
LAYOUT SIGNALS

Policy Layout You Can Scan

We built this page so you can scan the Privacy Policy before opening an account and return to it later when you have a specific request. The layout...

Plain headings Each heading explains the privacy point before the detail starts...
Local labels Pakistan payment names appear where they matter to privacy handling...
Action paths Contact routes are placed near the privacy topics they relate...
Short clauses Policy clauses are written in compact language. We avoid dense...
Device clarity Device and login records are described separately from payment records...
Update marker We keep policy change wording visible on the page. When...

Privacy Policy Questions, Answered Clearly

We collect the details needed to create and run your account, including contact data, login records, device signals, transaction references, session activity and support messages connected to privacy or account help.

Payment references from JazzCash, Easypaisa, SadaPay and Raast help us verify requests, reconcile account balances and handle disputes. We do not need your wallet password or unrelated wallet history.

Yes. Contact support from your registered channel and explain what needs correction. We may verify your identity first so the change is made to the right account record.

Device data helps protect account access, detect unusual login patterns and keep sessions stable. We use signals such as browser type, device identifier, IP range and time of access.

Yes, if a chat relates to account help, verification, disputes or privacy requests. We keep those records so our team can follow up accurately and maintain an audit trail.

You can ask us to delete eligible account data. Some records may need to stay for legal, payment, fraud prevention or dispute reasons before they can be removed.

It applies when you access 1x2 in supported regions, open or manage an account, contact support, use local payment rails or interact with casino and sportsbook features tied to your profile.