Terms connection
Our terms explain account rules, while this policy explains the data behind those rules. If an account status changes, privacy records show how that decision was recorded.
LEGAL REFERENCE
Privacy Policy for zb22 Accounts
zb22 places this Privacy Policy beside your account flow so you can see how data is collected, used and protected before you join. It covers Pakistan access where...
Account data useDevice log handlingPakistan payment contextSupport contact routes
How We Treat Account Data
This Privacy Policy explains how zb22 handles data linked to your account, identity checks, device access, lobby activity, payment references and support messages. We collect only what is needed to run your account, process requests, protect access, meet record duties and respond when you contact us. Payment rails such as JazzCash, Easypaisa, SadaPay and Raast may pass reference data to us, but
your wallet PINs and banking passwords stay outside our systems. We use service partners for hosting, security checks and message handling under controlled access. Access to zb22 is for supported regions where local law permits, and this policy may be updated when our account flow, payment routing or legal duties change.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy Contact Paths You Can Use
If you have a privacy question, we route it through the same care desk that handles account access. Tell us the account ID, contact detail and the privacy request type, not your passwords. We may ask for verification before sharing, correcting or deleting data.
Team online
Email requests
Send privacy questions to our care address with your zb22 account ID and the data issue. We use email for deletion, correction and access requests that need a written trail.
Live chat intake
Use chat for quick privacy routing, such as asking where a request should go. Our agent can create a case, but sensitive answers may move to email after checks.
Account security help
If you think your account access was exposed, contact us quickly. We can check recent logins, secure the profile and explain which privacy records may be affected.
CARE SIGNALS
How We Keep Policy Text Accurate
Our privacy wording is maintained against the systems we actually run: account creation, identity checks, lobby logs, payment references and support cases. When an operational step changes, the policy is checked for...
Operational checks
Policy wording is compared with live account flows, including registration fields, login records and verification screens. If a field is no longer used, the wording is adjusted.
Payment context
We describe JazzCash, Easypaisa, SadaPay and Raast data as reference records, not wallet access. That keeps the policy clear about what reaches zb22.
Access control
Internal access is limited by role, so support agents only see the account data needed for their task. Sensitive privacy cases receive tighter handling.
Retention checks
We keep records for account operation, dispute handling and legal duties, then remove or anonymise them when retention no longer applies. Timelines depend on record type.
Plain wording
The policy avoids vague legal phrasing where a practical explanation works better. You should understand what we collect, why we use it and how to contact us.
Change tracking
When privacy wording changes, we keep an internal change record with date, reason and affected sections. This helps support answer questions about older account events.
PAGE CONSISTENCY
Aligned Terms Across Policy Pages
This page works with our terms, cookie wording and account rules without repeating them. Privacy Policy wording explains data handling only. If another page covers conduct, promos or account use, this page...
Cookie wording
Cookie wording covers browser storage and similar tools. This Privacy Policy explains how those signals may link to account security, session control and analytics.
Promo records
If you check a promo board, related logs may record eligibility, display time and account response. This page explains that data use without restating promo rules.
Payment records
Payment pages describe cash-in and withdrawal steps. This policy focuses on reference numbers, verification status and support messages created during those payment requests.
Support logs
Support pages explain how to contact us. This policy explains how chat transcripts, emails and identity checks may be stored, accessed and used.
Security notices
Security wording may mention login protection. This policy explains related data, such as device type, IP signal, failed access attempts and password reset records.
Regional access
Where access is limited to supported regions, this policy explains location signals we may use for availability checks and account protection under applicable rules.
LAYOUT MARKERS
Privacy Layout Cues You See
The Privacy Policy page is designed to make the important data points easy to find before you open an account. Headings follow the account journey, from data collection...
Account journey order
Sections follow the order your data usually appears: registration, login...
Short chip labels
Chips name Pakistan payment rails only as privacy context. JazzCash...
Clear contact block
The contact area separates access, correction and deletion requests from...
Retention markers
Retention wording is grouped by record type, such as account...
Sharing labels
Partner sharing is described by purpose, including hosting, security, messaging...
Update date area
The policy layout reserves space for the latest change date...
Privacy Policy Questions Before Joining
We collect details needed to create and protect your account, such as contact data, login records and verification signals. We do not ask for your wallet PIN or banking password.
We may receive transaction references, status updates and account matching data from payment processing. Those records help confirm requests, answer payment queries and protect against incorrect account crediting.
Yes. We may process device type, browser signals, IP data and approximate location checks to support login security, regional availability and fraud prevention where local law permits.
Yes. Contact support with your account ID and the detail that needs correction. We may verify identity first, especially where the requested change affects withdrawals or account access.
We can delete or anonymise data when it is no longer needed for account operation, disputes, security checks or legal record duties. Some records must be kept for a set period.
Support messages are visible only to teams that need them for case handling, security checks or privacy requests. Sensitive cases may be restricted to a smaller internal group.