LEGAL REFERENCE

1xbat - How We Protect Your Privacy

1xbat puts your Pakistan account data, identity checks and JazzCash-linked transaction references under one Privacy Policy before you open your account. Read it to see what we collect...

Pakistan privacy scopeAccount data useSecurity checksRequest paths
1xbat How We Protect Your Privacy

What This Policy Covers

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

CONTACT ROUTES

How To Reach Privacy Support

Questions about this Privacy Policy should go through a channel that lets us verify you before we discuss account data. Use the...

Privacy email Use our privacy email path when you want...
Account chat Start a chat from inside your 1xbat account...
Security alert Tell us quickly if your phone, email or...
POLICY CHECKS

How We Keep Policy Checks Current

We maintain this page as an active 1xbat privacy statement, not a static legal file. The wording is checked against account flows, verification screens, wallet references and support...

Policy ownership

Our internal privacy owner checks this page against live account screens, verification prompts and support scripts. That keeps the wording...

Local context

Pakistan-specific references are checked before publication, including JazzCash, Easypaisa, SadaPay and Raast wording. We avoid naming rails or processes that...

Security alignment

Privacy wording is matched with security controls such as login checks, device signals and account recovery prompts. That helps you...

Data minimisation

We ask teams to justify each data field before it appears in a form or support request. If a field...

Plain wording

We write this policy in clear Pakistani English so you can understand your rights without legal shorthand. Technical terms are...

Change records

Material policy changes are logged internally with the reason, affected account flow and date of approval. That record helps our...

SIBLING PAGES

Consistency Across Our Legal Pages

Our Privacy Policy works beside other 1xbat legal pages, but it has a separate job. This page covers personal data: what we collect, why we process it, how long records may stay...

01

Account terms

The account terms explain how your 1xbat account is used, while this Privacy Policy explains the data behind that account. The two pages should match on verification, access and record keeping.

02

Cookie page

Cookie wording covers browser storage and session tools, while this policy explains how those signals connect with login security, device recognition and fraud checks on your account.

03

Promotions page

If you check a promotion, this policy explains what account data may be used to show eligibility, prevent duplicate claims and record your response within the account system.

04

Security page

Security wording describes protective controls, while this Privacy Policy explains the personal data those controls may process, including login time, device type, IP records and recovery activity.

05

Wallet records

Wallet-related pages may explain transaction steps, but this policy covers the personal data linked to JazzCash, Easypaisa, SadaPay and Raast references inside our account records.

06

Support terms

Support wording tells you how to contact us, while this policy explains what data we may request during a support case and how that case record is handled.

07

Regional access

Pages about access in supported regions should align with this Privacy Policy on location checks, language support and the way legal requests are handled for Pakistan accounts.

Visible Privacy Page Signals

This page is built so your privacy choices are easy to find before you continue with 1xbat. The layout separates collection, use, sharing, retention and contact...

Clear scope block

The opening block states that the page is about privacy only, including account data, identity checks and wallet references. You do not need to search through unrelated product copy.

Short context chips

The chips under the notice show Pakistan-relevant data contexts such as JazzCash, Easypaisa, SadaPay and Raast. They remind you which local records may appear in support or verification files.

Request wording

Rights requests are named in direct language: access, correction and deletion. We describe the channel and the identity check so you know why we cannot change records without verification.

Sharing limits

The policy separates internal use from partner sharing. When service partners help with verification, support or security, the text explains that sharing must stay tied to those narrow tasks.

Retention cues

We explain that some records stay while your account is active or while legal, security or dispute duties apply. The aim is clarity on why deletion may not be instant.

Plain contact path

The contact section sits near the policy details, not hidden at the end. If a privacy concern blocks your account decision, you can ask before you continue.

Privacy Policy Questions Answered

We collect the details needed to create and protect your account, such as name, contact details, login records, device signals and verification material when required for access, security or legal duties.

Wallet references help us match your account activity with funding or withdrawal records, answer support questions and investigate disputes. We treat those references as account data, not as permission for unrelated use.

Yes. Send a privacy request through our email path or verified account chat. We will check your identity first, then explain what account data we can provide and any legal limits.

You can ask us to correct inaccurate account details. For security, we may request proof before changing phone numbers, email addresses, identity records or wallet references connected with your account.

We may share limited data with partners that support verification, security, transaction processing or customer support. The sharing must relate to your account flow and should not expand beyond that purpose.

We keep records for as long as needed for account operation, legal duties, dispute handling and security checks. When a record is no longer needed, we aim to delete or anonymise it.

When we make a material change, we update this page and align the wording with account screens or support prompts. You should check this Privacy Policy before continuing if data use matters to you.