Account terms
Account rules may explain eligibility and access, but this policy explains the data behind those checks. We separate behaviour rules from records such as identity fields, phone numbers and login history.
LEGAL REFERENCE
1bat Privacy Policy for Pakistan
Our Privacy Policy explains what account, device, game-session and payment data we handle when you use 1bat where local law permits. Before you open your account, check how...
Account data scopePakistan payment recordsSecurity controlsYour privacy requests
How This Policy Applies
This Privacy Policy applies when you access 1bat from supported regions, create an account, contact us, verify your profile, enter the lobby, or use Pakistani payment rails linked to your account. We collect only the data needed to run account access, security checks, transaction records, fraud screening, service messages and support handling. Some data comes directly from you, such as your name,
phone number, payment reference and identity checks. Some data is created automatically, such as device type, session logs, IP address, browser data and login timing. We use these records to keep your account traceable, process requests, secure sessions and meet legal duties where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Keep Privacy Current
Our privacy wording is maintained around real account flows, not generic templates. When we adjust verification, payment record handling, security logging or support routing, we update the policy...
Account-flow mapping
We map each privacy clause to a real step in your account journey, from registration fields to payment references, so...
Payment record checks
JazzCash, Easypaisa, SadaPay and Raast references are treated as account records. We describe why they are stored, who can access...
Security log purpose
Device, IP and session logs are explained as security records, not hidden profiling. We keep the wording tied to account...
Support handling
Privacy requests can involve support staff, compliance checks and technical teams. Our policy states when internal access is needed and...
Retention wording
We state that some records must remain for legal, accounting or dispute reasons. The policy separates retained transaction logs from...
Change tracking
When policy wording changes, we keep the page focused on the affected data category. That helps you understand whether account...
PAGE ALIGNMENT
Privacy Across Our Legal Pages
Our Privacy Policy works with our related legal pages without repeating unrelated terms. This page explains data handling, while account rules, promotions, cookies and complaints sit in their own places. That separation...
Cookie page
Cookie wording covers browser storage and tracking choices. This Privacy Policy connects those signals to account security, preference handling and session continuity when you return to 1bat.
Payment records
Payment pages describe transaction steps, while this policy explains how references, confirmations and verification outcomes become privacy records linked to your account and request history.
Support records
Support terms explain contact availability; this policy explains how chat transcripts, emails and case numbers are stored, accessed and used to answer your privacy or account query.
Security rules
Security wording may cover account access expectations. Here, we explain the privacy side: device logs, IP checks, unusual activity flags and the data needed to protect your profile.
Promo terms
Offer pages may need account status checks. This policy explains the data used for eligibility, message preferences and audit records without turning privacy wording into promotional copy.
Complaint handling
Complaint pages explain process steps. This policy explains the related data handling, including case records, identity checks, payment references and retention where a dispute must be documented.
Privacy Page Layout Cues
The Privacy Policy page is designed so you can scan sensitive topics quickly before creating or updating an account. We group clauses by data type, purpose...
Plain headings
Each policy area uses direct labels such as account data, device data and payment records. This helps you find the privacy topic you need without reading unrelated platform wording first.
Local context chips
Short chips name Pakistan payment rails only where they matter to privacy records. They show which references may be stored without turning the policy into a transaction page.
Request prompts
Privacy request routes are placed near the clauses they affect. If you need correction, access or deletion handling, the page points you towards verified contact steps.
Purpose labels
Data uses are described beside the related record type. You can see whether a record supports login security, payment verification, support history, legal duties or service messages.
Retention cues
Retention wording is shown near account, payment and support data sections. That makes it easier to see which records may remain after a request and why.
Sharing markers
Where service partners help process records, the policy marks the purpose clearly. We avoid vague wording and describe sharing through support, security, payment and hosting needs.
Questions About Your Data
We collect the details needed to create and secure your profile, such as name, phone number, login credentials, device data and verification records. Payment references are added when you use supported Pakistan rails.
Payment references help us match your account with transaction records, confirm requests and handle disputes. The Privacy Policy treats those references as personal account records and limits internal access to relevant teams.
We may share limited records with service partners that support hosting, payment processing, security checks, verification or customer support. The policy requires a clear purpose before any such sharing takes place.
Send a request through the privacy contact path in your account area or email support with your registered phone number. We verify your identity before releasing, correcting or restricting account records.
Retention depends on the record type and legal need. Some account, payment and security logs may remain for accounting, dispute handling or compliance reasons even after other details are updated.
Yes, you can ask us to correct inaccurate account details. We may request proof before changing identity or payment-linked records, because those changes affect privacy, security and transaction history.
We use session checks, device records and access controls to protect your account. The Privacy Policy explains that these logs support security checks and are handled as privacy-sensitive records.