Account pages
Registration and login screens request details that identify and protect your account. The Privacy Policy explains those fields in plain language rather than leaving the reason inside a form label.
LEGAL REFERENCE
Privacy Policy for your 99bat account
99bat keeps privacy choices, account records, and Pakistan payment context in one clear policy so you know what data we collect before you open an account. Read how...
Pakistan privacy contextJazzCash data handlingEasypaisa account recordsRaast transfer traces
How we handle your account data
Our Privacy Policy explains the personal data we collect when you create or use a 99bat account, including contact details, login activity, device signals, game-session records, payment references, and messages sent to support. We use this data to run your account, verify access, process withdrawals, protect balances, answer privacy requests, and meet record-keeping duties in supported regions. Payment names such as JazzCash,
Easypaisa, SadaPay, and Raast appear only where they help explain how transaction references are stored and checked. We do not sell your account data. When service partners help with hosting, verification, analytics, or payments, they receive only the data needed for that task under access controls and retention rules.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy contact paths at 99bat
If you want to ask about your personal data, start with the privacy contact route that matches your issue. We separate account help from privacy requests so your question reaches the right queue and sensitive documents are handled with tighter access.
Team online
Email privacy desk
Send privacy requests from the email linked to your 99bat account. Include the account ID, request type, and any payment reference only when it directly supports your privacy question.
Live chat handoff
Our chat team can identify privacy-related account issues and move them into the privacy queue. They may ask basic checks before escalating, so your personal data is not shown to the wrong person.
Document channel
When a request needs proof of identity, we use a restricted upload path rather than open chat attachments. This helps keep CNIC images, payment screenshots, and account files within controlled storage.
POLICY CHECKS
How we keep this policy current
We check this Privacy Policy when account flows, payment rails, verification steps, or support tools change. The aim is simple: the policy should match the way 99bat actually handles personal data, not...
Operational read-through
Product, payments, and support teams check the wording against live account journeys. If a screen asks for data, the policy needs to explain why that data is requested.
Payment rail mapping
JazzCash, Easypaisa, SadaPay, and Raast records create different reference fields. We map those fields in our internal privacy records so transaction checks stay connected to a clear purpose.
Access control checks
We limit who can see identity documents, payment proofs, and support transcripts. Access is role-based, logged, and checked when job duties or account-handling processes change.
Retention calendar
Some records are kept for account security, payment disputes, or legal duties. We keep retention periods tied to purpose, then delete or anonymise data when it is no longer needed.
Partner checks
When vendors process hosting, verification, analytics, or payment routing data, we assess the data shared, the task performed, and the controls used before enabling access.
Change record
Material policy changes are logged internally with the reason for the update. This helps our team answer your questions with the same wording shown on the page.
PAGE ALIGNMENT
One privacy approach across pages
99bat keeps privacy wording aligned across account, terms, cookie, and support pages. Each page has its own purpose, but the data categories, contact routes, and retention ideas should not conflict when you...
Cookie page
Cookie wording covers device storage, session continuity, analytics, and security signals. The Privacy Policy connects those signals to wider account handling, including fraud checks and preference records.
Terms page
Terms describe account rules; this page describes personal data handling. We keep the link between the two clear so rule enforcement does not hide the privacy purpose behind it.
Support page
Support channels collect chat content, contact details, screenshots, and case history. The Privacy Policy explains how those records are used to answer you and protect account access.
Payment screens
Payment flows may show JazzCash, Easypaisa, SadaPay, and Raast fields. This policy explains how transaction references are stored, checked, and linked to your account history.
Security prompts
Security prompts may ask for extra checks after unusual login activity. The Privacy Policy states how device signals and access logs help us confirm that the account is yours.
Promo pages
When an offer page needs eligibility checks, we use account status and activity records for that limited purpose. The Privacy Policy keeps that data use separate from unrelated profiling.
Policy layout you can read quickly
This page is built to help you scan privacy points without losing context. Headings follow the account journey: data collected, reasons for use, sharing, storage, choices...
Plain headings
Each heading tells you the privacy issue before the paragraph starts. You can jump straight to identity checks, transaction records, support messages, or account access logs.
Local examples
Pakistan payment rails are named where they affect privacy records. A JazzCash or Raast reference is treated as account data, not as a generic finance label.
Short definitions
Technical terms are kept close to the sentence that uses them. Device signals, session logs, verification files, and anonymised data are explained in practical account language.
Choice markers
Where you can ask for access, correction, deletion, or restriction, the policy marks the route clearly. Some requests may depend on legal or account-security duties.
Storage cues
Retention wording is tied to purpose, such as payment disputes, account protection, or legal record keeping. This helps you see why records may remain after a session ends.
Contact prompts
Contact points are placed near the privacy rights section so you do not need to search across pages. We ask for enough detail to locate the account safely.
Privacy questions before you join
We collect the details needed to run and protect your account, such as contact data, login records, device signals, verification files, game-session records, support messages, and payment references linked to your activity.
Payment references help us match JazzCash, Easypaisa, SadaPay, or Raast activity to the right account, check withdrawal requests, handle disputes, and keep an accurate record where local law permits.
Yes. Contact us from your registered email and describe the data you want to access. We may verify your identity first so account records are not released to another person.
Retention depends on the record type and purpose. Account security logs, payment records, verification files, and support cases may have different timeframes, especially where legal duties or disputes require storage.
Some partners help with hosting, verification, analytics, security, or payment routing. They receive only the data needed for their task, and access is controlled under the privacy terms we apply.
Send a correction request through the privacy contact route or account support. We may ask for proof where the change affects identity, payment matching, or withdrawal checks.