Account terms link
Account terms describe how you may use zs99, while this policy explains what data we handle during that use. The two pages are written to avoid conflicting account wording.
LEGAL REFERENCE
Privacy Policy for your zs99 account
Live tables, slots and sportsbook access on zs99 rely on account data, payment records and device signals, so this Privacy Policy explains exactly why we collect them. Open...
Pakistan privacy scopeAccount data handlingJazzCash contextEasypaisa recordsRaast checks
How this policy applies
This Privacy Policy explains how zs99 collects, uses, stores and shares data connected with your account, lobby activity, support chats and payment checks in supported regions. We collect only the data needed to run account access, verify transactions, manage security alerts, answer your questions and meet lawful record duties. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay and Raast may appear in our
systems as transaction status, wallet name, time stamp or reference code, not as a reason to collect extra private data. Where local law permits, you can ask us to correct account details, request a copy of data linked to your account or ask how long specific records are kept.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CARE
How we keep privacy wording current
Our Privacy Policy is written around the way zs99 actually handles account access, payment checks, support history and security events. When we change a form, add a verification...
Account access checks
We connect privacy requests to the signed-in account or another verified route. This helps us avoid sending personal account data...
Local payment context
Our policy covers payment references from Pakistan routes such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast. We describe the record...
Security event logs
Login attempts, device signals and session changes may be recorded to protect your account. The policy explains this security use...
Support history controls
Support chats and email messages may be kept with your account so we can resolve repeat privacy questions. Access is...
Retention checks
We keep different privacy records for different periods, depending on account, payment and legal needs. When a record no longer...
Clear update markers
When policy language changes in a meaningful way, we make the wording visible on this page. You can return here...
POLICY ALIGNMENT
Consistency across legal pages
This Privacy Policy works beside our account terms, cookie wording and any payment rules shown during the account flow. Each page has its own purpose, but the privacy wording stays centred on...
Cookie wording link
Cookie text covers browser storage and session tools. This Privacy Policy explains how those signals may connect with account security, support checks and privacy choices.
Payment rules link
Payment rules may describe transaction steps, while this policy covers privacy records created during those steps. References can include status, time stamp, wallet route and account match.
Security wording link
Security notices explain protection measures; this policy explains the data side of those measures. That includes device signals, unusual login checks and records used to protect account access.
Support wording link
Support pages explain how to reach us, while this page explains how we handle the messages you send. We keep privacy requests separate from routine service questions.
Regional wording link
Where access depends on supported regions, this policy still explains data handling for your account. We avoid using regional wording as a reason to collect extra private details.
Update wording link
If a related page changes, we check whether this Privacy Policy also needs fresh wording. That keeps privacy explanations aligned with the account screens you actually use.
PAGE SIGNALS
Visible privacy elements on this page
We built this page so you can scan the privacy points before opening your account and still return later for detail. The layout separates contact paths, data types...
Plain account language
We use direct wording for account records, login checks and...
Local record examples
Examples mention Pakistan payment routes only where they affect privacy...
Request pathways
The page separates correction, access and retention questions so you...
Security purpose callouts
Device checks, session logs and unusual activity markers are explained...
Storage purpose labels
Each privacy area explains why the record exists, such as...
Change visibility
When wording changes, we keep the page easy to revisit...
Questions about this Privacy Policy
We collect account details, login records, support messages, transaction references and security signals needed to run your account. The exact data depends on how you access zs99 and which account steps you complete.
No. For JazzCash, Easypaisa, SadaPay, NayaPay and Raast, we may store transaction status, reference codes or timing details. We do not need your wallet password to handle privacy records.
Device and login records help us spot unusual access, protect account sessions and answer privacy requests accurately. They also help confirm whether a request is coming from the correct account context.
Yes, you can ask us to correct account details where local law permits and where the requested change matches verification checks. We may need proof that the account belongs to you.
Retention depends on the record type, such as account access, payment matching, support handling or legal duties. When we no longer need a record, we remove it or reduce identifying details.
Support messages are limited to staff who need them to answer your request, resolve a privacy issue or check account history. We do not place your private messages in public areas.
Use the privacy contact route shown inside your account or ask support to escalate the matter. We may verify your account before discussing personal records or transaction references.