LEGAL REFERENCE

Privacy Policy for your zj88 account

zj88 treats privacy as part of your account journey: we collect the details needed to create access, protect sessions and check withdrawal requests where local law permits. Before...

Account dataDevice logsWithdrawal checksPakistan support
zj88 Privacy Policy for your zj88 account

How we handle account data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

Ways to ask about privacy

Privacy requests need a careful path, not a rushed chat answer. We give you several contact routes so you can ask for access, correction, deletion assessment or consent changes. Use the route that matches your issue, and keep your account email ready for verification.

Team online

Privacy inbox

Send privacy requests by email when you need a written trail. Include your account email, phone code and the data issue, but never send card numbers or one-time passcodes.

Live chat routing

Use chat for quick routing if a privacy matter affects login, verification or withdrawal checking. Our agent will confirm safe account questions, then move complex data requests to email.

Account centre

Inside your account centre, choose the privacy help path when you want copies, corrections or deletion assessment. We may ask for fresh verification before making changes to protected records.

POLICY PROOF

Checks behind this Privacy Policy

We write this policy from the systems we operate: account creation, login checks, support records and withdrawal verification. The wording is checked against those flows so the page matches what happens inside...

Plain wording

We write privacy text in direct Pakistani English so you can see what we collect, why it is needed and which choices you have before sharing extra account details.

Local rail context

When JazzCash, Easypaisa, SadaPay or Raast appears in a privacy example, we treat it as transaction context only, not a reason to expose your full wallet activity elsewhere.

Session logs

We separate session logs from profile fields where our systems allow it. That helps us check device risk without placing every click beside your name in routine privacy work.

Access controls

Only trained team roles can open sensitive account records, and access is logged. This Privacy Policy reflects those internal checks rather than vague promises about data handling every day.

Change log

When the policy changes, we update the page date and keep the new wording beside your account journey. Material changes are written in plain language for quick reading.

Human support

Privacy questions do not sit only with automated messages. Our support team can route your request, ask for proof, and explain the next step clearly by email or chat.

Same privacy stance across pages

This Privacy Policy is the main privacy source for zj88. Other legal and account pages should point back here instead of creating different promises. That consistency matters when...

Account page consistency
The account area uses the same privacy terms as this page, so profile edits, password changes and verification prompts do not create a separate data promise for you.
Cashier wording
Cashier screens mention JazzCash, Easypaisa, SadaPay and Raast only to identify transaction records. The privacy meaning matches this page, including retention and verification purposes for your account there.
Lobby notices
When the lobby asks for cookies or device checks, the wording connects back to this Privacy Policy. We avoid separate consent language that changes your rights without warning.
App access
Mobile web and installed access use the same data categories. If device permissions differ, the privacy purpose stays tied to security, account access and service messages for you.
Support templates
Support replies follow the same privacy wording, whether you ask by chat or email. We do not invent new retention periods inside a single conversation with you there.
Message choices
Message preference screens connect to this policy, including email, SMS and in-account alerts. You can ask how consent records are stored before changing those settings inside your account.
Legal wording
If a legal page links here, it should not narrow the privacy rights described here. We keep the same contact path for data access requests from your account.
PAGE ELEMENTS

Visible privacy cues on zj88

Rather than hiding privacy details in dense legal text, we place visible cues around the policy page and account flow. These cues show the date, data categories, consent...

Policy date chip A visible date chip helps you confirm when this Privacy...
Data category cards Short cards group account, device, transaction and support records separately...
Consent banner The consent banner links back to this page and separates...
Security prompts Security prompts explain why we request a code, device check...
Retention cues Where a record must be kept for account, transaction or...
Choice links Choice links send you to correction, access or deletion request...

Privacy Policy questions answered

We collect account details, contact fields, verification records, device data, session logs and transaction references. The Privacy Policy explains each category so you can see why it is needed before adding more.

Yes. When JazzCash, Easypaisa, SadaPay or Raast appears in your transaction history, we store only the references needed for account checks, withdrawal handling and dispute records where required.

Yes, you can contact support from your account email and ask for a copy of eligible records. We verify identity first so account data is not released to another person.

We keep records for as long as they are needed for account access, legal duties, security checks, transaction tracing and dispute handling. Some records may be removed sooner when no longer required.

Cookies help us keep sessions active, remember language choices and check device risk. Optional analytics are separated where our tools allow, and the policy explains how those settings affect your account.

Sensitive records are limited to trained roles that need them for support, verification, security or transaction work. Access is logged, and unnecessary sharing outside those purposes is not part of our policy.