Account page
The account page collects profile fields and verification status; this policy explains why those records exist and how correction requests are handled.
LEGAL REFERENCE
Privacy Policy for Pakistan Accounts
bat77 keeps live casino, slots and sportsbook account records under one Privacy Policy, so you can see what we collect before you open an account. We explain data...
Account dataVerification recordsPakistan payment contextSecurity checks
How We Handle Account Data
This Privacy Policy explains how bat77 collects, uses, stores and shares personal data connected with your account in supported regions of Pakistan. We collect details you provide during account creation, identity checks, payment handling, support chats and security monitoring. Payment references may include JazzCash, Easypaisa, SadaPay and Raast identifiers, but we do not publish your private payment details in the lobby or
promo areas. We use your data to run the account, confirm access, process permitted account actions, detect misuse, answer privacy requests and meet record duties that apply to us. We keep records only as long as needed for those purposes, then delete or de-identify them when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How This Policy Stays Current
We keep this policy aligned with the way bat77 actually operates. Product, security, payment and support teams feed changes into the same policy record before new data uses...
Operational ownership
Our privacy wording is maintained by the teams handling account creation, verification, payments and support, so each clause reflects a...
Pakistan context
We reference Pakistan payment rails, local phone formats and supported region access because those details affect how your account data...
Security mapping
Login logs, device markers and risk alerts are described as privacy data, not hidden system extras, because they can affect...
Retention control
We connect each stored record with a purpose, such as identity checks, payment tracing or account safety, then remove data...
Staff access
Only trained team roles may view sensitive records, and access is limited to tasks such as verification, privacy response or...
Change tracking
When the policy changes, we update the page date and keep internal records showing which account process required the wording...
PAGE ALIGNMENT
Same Privacy Standard Across Pages
Your privacy rights should not change when you move between bat77 pages. We keep account, cashier, support and promo privacy wording consistent, then point detailed questions back to this policy. That reduces...
Cashier page
Cashier screens may show JazzCash, Easypaisa, SadaPay or Raast references; this policy explains how those payment records are protected.
Support page
Support conversations can contain personal data, so this policy explains how chat records are stored, escalated and used for account help.
Security page
Security content mentions login checks and device signals; this policy explains how those signals are treated as privacy-related account records.
Promo page
Promo displays may use account status or region eligibility; this policy explains how we avoid showing private account details publicly.
Game lobby
Lobby activity may create session logs and preference records; this policy explains how those records help account continuity and safety.
Mobile access
Phone and browser sessions create device records; this policy explains how those records support login security and privacy request handling.
Policy Layout You Can Read Fast
We structure this Privacy Policy so you can find the clause that matters without reading every legal phrase at once. Each area separates collection, use, sharing...
Plain labels
Section headings use direct labels like account data, payment records and security logs, making it easier to find the privacy clause you need.
Short examples
We add examples such as wallet references, identity checks and support chats so privacy wording connects with actions you recognise on bat77.
Purpose markers
Each data category is tied to a purpose, helping you see whether we use it for access, payments, security, support or legal record duties.
Rights section
Your access, correction and deletion request routes are kept together, so you know how to contact us about personal data without searching elsewhere.
Sharing limits
We explain when service partners may process data for bat77, and we avoid broad language that could hide how your records move.
Date marker
The policy date tells you when wording last changed, helping you compare the current text with any copy you saved earlier.
Privacy Policy Questions Answered
We collect account details, contact data, verification records, payment references, session logs, device signals and support messages needed to run your bat77 account in supported regions.
Verification documents help us confirm account ownership, reduce misuse and process permitted account actions. We store those files with restricted access and keep them only as needed.
Payment partners receive only the data needed to process or trace a transaction, such as wallet reference, amount, time and status, not your full bat77 profile.
Yes. Send the incorrect field, the corrected value and proof where needed. We verify the request before changing records that affect access or payments.
Retention depends on the record purpose. Account, payment and verification data may be kept while required for service, security, dispute handling or legal record duties.
We use access controls, session monitoring, role limits and secure storage practices. Sensitive records are available only to teams that need them for account-related tasks.