Terms Of Use
Explains how you may use your account, what counts as misuse and when access can be paused. It shares the same definitions of account holder, verified number and registered email used here.
LEGAL REFERENCE
How 92bat Handles Your Account Data
This page sets out what 92bat collects when you open an account, deposit through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, and switch between our slots, live tables and...
Account data basicsLocal payment privacyYour control optionsRetention windows
Our Approach To Your Personal Data
92bat is the data controller for the account you open here, and we handle your details only where local law permits. We ask for your name, date of birth, contact number, email and the payment references returned by JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Device data, session logs and approximate location help us flag unusual logins before they cost you. We share
data only with payment processors, identity-check partners and hosting providers working under contract, never with unrelated advertisers. Where local law permits, you can request a copy of your data, correct it, or close the account and have routine records removed. Transaction and identity records stay on file for the period local rules set, and the governing law follows whichever jurisdiction applies to
your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY OWNERSHIP
Who Writes And Maintains This Page
This page is written and maintained by the 92bat team that runs account operations, payments and security day to day. Every change is signed off by our security lead before it goes...
Account Operations
The team handling sign-up, mobile verification and account closure writes the sections on identity data. They know which fields are mandatory and which we only request when a check needs them.
Payments Desk
The people reconciling JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers draft every line about payment references, and revisit it whenever a rail is added to the chip row.
Security Lead
Our security lead signs off before anything is published. They cover session logs, device identifiers and login alerts, and check that nothing here claims protection we do not actually operate.
Support Supervisors
Support supervisors check the contact channels above every quarter, confirming the hours, WhatsApp number and in-app chat routing still match what you see after you sign in.
Regional Editor
A Pakistan-based editor reads the wording against how you actually use the platform, covering mobile-first sessions, longer names in account fields and familiar local payment habits.
Version Notes
Every amendment carries a date and a short summary, so you can see what moved and when. Material changes to how we use your data are flagged in the lobby before they take effect.
POLICY CONSISTENCY
How This Page Lines Up With Our Others
Our other pages cover different ground, so it helps to know which one answers what. This page deals only with your personal data. Terms of use covers account conduct, the cookie notice...
Cookie Notice
Lists the cookies and local storage keys we set, grouped by purpose. Session cookies keep you signed in; analytics cookies are optional and can be switched off without breaking the lobby.
Payment Terms
Covers deposit and withdrawal mechanics for JazzCash, Easypaisa, SadaPay, NayaPay and Raast. The payment references described there are the same ones listed in our data-collection section.
Account Security Rules
Sets out password standards, two-step verification and how we alert you to a new device login. Security logs named on this page follow the same holding period described there.
Sportsbook Rules
Explains market settlement, void bets and how wagers are recorded. Bet history feeds the transaction records we keep, so both pages describe one data set.
Live Dealer Rules
Covers table conduct, chat moderation and recorded streams. Because live tables are filmed, that page explains what appears on camera and how long recordings stay available.
Promotions Terms
Describes how offers are credited and what eligibility means. Where a promotion needs extra details from you, that page says so first and this one explains how we store them.
What You Will Find On This Page
This page is built to be read on a phone in a couple of minutes, then kept for reference. We lead with plain language, list what...
Plain-Language Scope
The opening block tells you which parts of 92bat this page covers: the site, our apps and the account you sign into. Sections that apply only in some regions are labelled.
What We Collect
A running list of every category we hold, from your registered mobile number to device identifiers. Each entry says whether we need it to operate your account or collect it optionally.
Why We Hold It
The reason behind each category sits next to it, covering account operation, payment reconciliation, fraud checks and service messages. Nothing appears on the list without a working reason.
Who Sees Your Data
Named partner types, including payment processors, identity-check providers and hosting suppliers, appear with the role each one plays. We do not sell account details to unrelated advertisers or data brokers.
Retention Windows
Each record type carries a holding period. Routine session logs clear sooner than transaction records, and the page explains why identity documents follow a longer rule in most supported regions.
Your Controls
Copy requests, corrections, closure and removal of routine records are described step by step, along with the channel you use to start each one. Response times are listed per channel.
Questions We Hear About Your Data
Your name, date of birth, mobile number and email, plus payment references returned by JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We also log device type, IP address and session activity for security.
Only what a transfer needs. Those rails receive the identifiers required to move money and confirm it cleared, and nothing about which games or markets you use.
Transaction and identity records follow the holding period local rules set for your jurisdiction. Routine session logs and device identifiers clear much sooner, once they are no longer needed for security.
Yes. Request closure through in-app chat, email or WhatsApp, and we verify you against your registered number. Routine records are removed; transaction and identity records stay for the period local law requires.
The same rules apply. The app collects the device identifiers needed for secure sign-in and push alerts, and stores session tokens differently from a browser. Both are covered by this page.
We watch for unusual logins, alert you to new devices and support two-step verification. If something looks wrong, we can freeze the session and ask you to confirm your identity before access continues.
Send a correction request through any support channel with your registered number. Most name, address and contact details are editable yourself; identity documents are updated by our team after a fresh check.