LEGAL REFERENCE

How 2je bat handles your data

2je bat connects your casino, sportsbook and payment activity to one account record, so this Privacy Policy explains what we collect, why we use it and how you...

Pakistan account privacyJazzCash contextEasypaisa contextSadaPay and Raast
Explore the lobby Read FAQ
2je bat How 2je bat handles your data

Privacy posture for Pakistan accounts

This Privacy Policy applies when you access 2je bat from supported regions where local law permits and use our account, lobby, support or payment flows. We collect details you provide, such as your name, contact route and account credentials, plus technical signals like device type, login time, IP range, session activity and security checks. We also process transaction references shared during JazzCash,

Easypaisa, SadaPay or Raast handling so your balance record can match the payment trail. We use this data to run your account, secure access, respond to support, detect misuse, meet legal duties and keep policy records accurate. We do not sell your personal data. We keep data only for operational, legal, security or dispute needs, then reduce or remove it when those

needs end.

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

PRIVACY HELP

Contact paths for privacy requests

If you need to ask about your data, correction, access, retention or account privacy, start with our support routes inside the 2je...

In-account help desk Use the help desk after login for privacy...
Email privacy request Send email when you need a written record...
Live chat handoff Chat can receive urgent privacy concerns, then move...
POLICY CARE

How we keep this policy current

We write this Privacy Policy from the way our service actually works, not from a copied template. Product, support, payments and security staff provide changes when account flows...

Payment mapping

We map each Pakistani payment rail to the account data it creates. JazzCash, Easypaisa, SadaPay and Raast references are described...

Security input

Our security team contributes wording on login signals, device checks and suspicious activity handling. That keeps this policy close to...

Support feedback

Support patterns show which privacy questions need clearer wording. When you ask about access, correction or retention, those themes help...

Legal alignment

We frame access with supported regions and where local law permits. We avoid claiming permissions that depend on local rules...

Change tracking

When we adjust privacy wording, we keep an internal change record covering the reason, affected account flow and team owner...

Plain language

We aim to explain data handling in clear Pakistani English. If a privacy term feels unclear, contact us and we...

How this page fits our policies

This page is limited to privacy: collection, use, sharing, retention and your choices. Other policy pages may cover account rules, cookies, promotions or service terms. We keep the...

Terms page
Our terms page explains account use and service rules. This Privacy Policy explains the data behind those account actions, including login records, verification checks and support conversations.
Cookie page
Cookie wording covers browser storage and similar tags. This Privacy Policy connects those signals to wider account privacy, such as session safety, fraud checks and preference handling.
Promotion rules
Promotion rules may explain eligibility and reward mechanics. This page explains how related account data is processed, such as participation records, support checks and fraud prevention signals.
Payment terms
Payment terms deal with transaction steps and timing. This page deals with privacy around payment references, wallet names, verification records and retention linked to disputes or legal duties.
Security page
Security wording may describe account protection features. This Privacy Policy explains which data supports those controls, including device signals, login patterns and alerts from unusual activity.
Support standards
Support standards explain response routes and escalation. This page explains the privacy side, including identity checks before private account or payment data is discussed.
Regional wording
Regional wording explains access where local law permits. This page explains how privacy handling applies when you use 2je bat from supported regions in Pakistan.
PAGE MARKERS

Visible privacy cues across the site

We place privacy cues near the account areas where data is collected, so you can read the relevant point before sending details. These cues are short, practical and...

Account form cues Account forms show why each required field is requested. We...
Login safety labels Login screens may mention device checks and session controls. These...
Wallet privacy text Wallet screens use short privacy text near JazzCash, Easypaisa, SadaPay...
Support prompts Support forms remind you not to share wallet PINs or...
Verification notices Verification screens explain why extra checks may be needed before...
Policy footer link The footer keeps this Privacy Policy within reach from main...

Questions about your privacy

We collect account details you provide, login and device signals, support messages, verification records and payment references linked to JazzCash, Easypaisa, SadaPay or Raast activity on your account.

Payment references help us match wallet activity to your 2je bat balance record, respond to support questions, check disputed transactions and meet record-keeping duties where local law permits.

No. We do not sell your personal data. We share data only with service providers, payment partners, security tools or authorities when needed for account operation, safety or legal duties.

We keep data for as long as needed for account operation, legal duties, dispute handling, fraud prevention and support records. When the need ends, we reduce or remove data where possible.

Yes. Contact support with the detail you want corrected. We may verify your identity first, especially when the change affects login access, payment records or private account history.

We use login monitoring, device signals, verification steps and restricted staff access to protect private records. These controls help prevent unauthorised access and limit who can view account data.