Cookie page alignment
Cookie wording covers browser storage and tracking choices, while this policy explains broader account data use. The two pages are matched so device records and preference tools are described in the same way.
LEGAL REFERENCE
How 1xbat handles your data
1xbat keeps your privacy choices, account details, verification records and Pakistan payment traces inside one clear policy, so you know what we collect before you open an account...
Pakistan privacy termsJazzCash contextEasypaisa contextRaast context
Privacy posture for Pakistan accounts
This Privacy Policy explains how 1xbat collects, uses, stores and shares data when you access 1xbat.biz from Pakistan or another supported region. We may collect account identifiers, contact details, device signals, login records, verification material, transaction references and service messages. When you add funds through JazzCash, Easypaisa, SadaPay or Raast, we record the references needed to reconcile your account and address payment
queries; we do not ask you to share wallet passwords. We use your data for account access, fraud checks, support replies, security monitoring, legal duties and internal service measurement. We keep records only for as long as they are needed for these purposes, unless law requires a longer period.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CARE
How we keep policy records reliable
Our privacy wording is written around the records we actually handle: account registration, sign-in events, payment references, verification checks and support messages. We avoid asking for data that...
Clear collection points
We identify the places where your data enters our systems, including account forms, login screens, verification steps, payment reconciliation and...
Local payment handling
JazzCash, Easypaisa, SadaPay and Raast references are used to match account balances, investigate failed transfers and answer your payment questions...
Verification records
When verification is needed, we collect the material required to confirm account ownership or meet legal duties. Access is limited...
Security monitoring
Device type, IP signals, session activity and failed login attempts help us spot unusual access. We use these signals to...
Retention controls
Some records must stay available for payment disputes, fraud checks or legal requests. When a record is no longer needed...
Policy change checks
Before we update this page, we compare the wording with current account screens, payment flows and support scripts. That helps...
PAGE ALIGNMENT
Consistency across privacy pages
This Privacy Policy sits beside our cookie, terms and account notices. Each page has a different role, but the privacy wording must stay consistent wherever your data is mentioned. If one page...
Terms page alignment
Account terms explain service rules; this page explains privacy handling behind those rules. We keep both pages consistent when registration data, verification duties or account closure records are mentioned.
Payment notice alignment
Payment notices may explain timing and reconciliation, while this policy explains the personal data attached to those steps. JazzCash, Easypaisa, SadaPay and Raast references are described with matching privacy language.
Security notice alignment
Security notices focus on protecting account access; this policy explains which signals help that protection work. Login activity, device data and alert records are described without expanding collection beyond stated purposes.
Support script alignment
Our support replies are written to avoid asking for unnecessary private data. The same rule appears here, so you know why we request references instead of passwords or full wallet credentials.
Verification wording alignment
Verification pages may request documents or account checks when required. This policy explains the privacy side: why records are needed, who may access them and how long they may be kept.
Regional access alignment
Where access depends on supported regions, this policy uses the same regional wording as other legal pages. That avoids mixed messages about when 1xbat can provide account access.
Privacy details you can spot quickly
We structure this page so your privacy questions are easy to locate before you join or return to your account. The visible layout separates collection, use...
Purpose labels
Each privacy purpose is written in plain language, such as account access, verification, support, security or legal record keeping. These labels help you see why a record is collected before you share it.
Local context chips
Pakistan payment names appear only where they explain data handling, not as a separate promotion. JazzCash, Easypaisa, SadaPay and Raast references show which transaction records may connect to your account.
Retention cues
Retention wording explains why different records may have different timeframes. Payment disputes, security incidents and legal requests can require longer storage than a routine support message.
Sharing boundaries
The policy separates internal staff access from external sharing. Where processors, payment partners or legal authorities are involved, we describe the purpose rather than using vague privacy language.
Control routes
Privacy controls are connected to contact routes, so you know where to ask for access, correction or removal. We may still keep records that are needed for disputes or legal duties.
Update signals
When the policy changes, the page wording should make the change visible through revised sections or dates. We avoid silent changes that would make your privacy choices harder to follow.
Questions about this Privacy Policy
We collect data needed to create and operate your account, such as contact details, login records, device signals, verification material, support messages and payment references connected with JazzCash, Easypaisa, SadaPay or Raast.
Payment references help us match a transfer to your 1xbat account, investigate failed or delayed entries and answer your support request. We do not need your wallet password or full banking credentials.
Yes. Contact us through the account help area or registered email and explain what needs correction. We may ask for identity checks before changing records, because privacy requests can affect account ownership.
We may share limited data with processors, payment partners, security providers or authorities where required for account service, fraud checks, legal duties or dispute handling. We do not share more than the purpose requires.
Retention depends on the record. Some support messages may be kept for a shorter time, while payment, verification or security records may stay longer for disputes, fraud checks or legal requirements.
Use the in-account help area or contact us from your registered email. Include the account identifier and request type, but avoid sending wallet passwords, full card details or unrelated private documents.