LEGAL REFERENCE

How cz888 Handles Your Data

cz888 keeps your account details behind encrypted access and spells out exactly what we collect, why we collect it and how long we hold it. Open an account...

Encrypted account accessPlain-word clause textYour data, your settingsSupport in Urdu and English
cz888 How cz888 Handles Your Data

Where This Policy Applies

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

REACH OUR TEAM

Talk to Us About Your Data

Questions about your privacy do not wait for office hours, so our support desk stays open around the clock, in English and Urdu. Write from the email address on your account and we can verify you quickly, which keeps your data out of the wrong hands.

Team online

Live chat

Open live chat from your account dashboard and a Pakistan-based agent picks up your privacy question, whether it touches stored records, a settings change or a deletion request.

Privacy email desk

Write from the address registered on your account and we answer within one working day, leaving you a written record of what you asked and exactly how we replied.

Secure message inbox

Your account inbox handles requests that need documents attached, such as a correction or a copy of your records, and every thread stays encrypted behind your own sign-in.

HOW WE WRITE

Why You Can Rely on This Text

We wrote this policy ourselves, in the same language our support team uses when you message them, and we keep it beside the terms page so the two never contradict each other...

Written in plain words

We skip legal shorthand and say what actually happens to your data at each step, from the moment you open an account to the day you ask us to close your file.

Kept current

When our handling of data changes we refresh the date at the head of this page and add a short line saying what moved, so you never reread a stale clause.

One house style

Terms, cookie text and this policy go through the same editors, which is why the wording matches between pages and no clause quietly contradicts another one.

Local context

Our examples name JazzCash, Easypaisa, SadaPay, NayaPay and Raast because those are the routes you use, and policy wording should describe your real account.

Data-minimal asks

We list every field we request, explain why it is needed, and leave out anything an account does not strictly require, which keeps what we hold small.

Accountable answers

If you are unhappy with how a request was handled, tell us and it escalates to the team that owns this page instead of sitting with front-line support alone.

How This Policy Fits Our Other Pages

This text sits alongside our terms, cookie notice, account-security section and complaints route, and the set is written to hang together. Read any of them and you meet...

Terms and conditions
The terms page covers the rules of holding an account while this page covers your data, and each links to the other so nothing important slips between them.
Cookie notice
The cookie text explains which small files your browser stores and why, then points back here for the wider picture of how that data is treated.
Account security page
Sign-in steps, two-step checks and password resets for your account live there, and that wording lines up with the safeguards promised here on the data side.
Funds wording
Money added through JazzCash or Easypaisa creates a transaction record, and the funds section states how long that record is kept, matching the retention clause written here.
Complaints path
If a privacy request is not handled the way you expected, the complaints route names the next step, and both pages point to the same team at the end.
Verification steps
Documents sent for account checks are handled under the same rules described on this page, and both texts explain who may open a file and when it is removed.
Update history
Every page in this set carries its own change date, and when one is rewritten the rest are checked in the same week so no stale clause is left behind.

What You Will Find on This Page

The layout here is built for quick reading rather than a wall of clauses. A dated header, short labelled blocks, expandable answers and a chip row...

Dated header

A line under the headline shows when this text last changed, so you can tell whether the version in front of you is the one you read last month.

Labelled blocks

Every block carries a short heading naming its subject, which lets you skim the list and open only the clause that answers the question in front of you.

Local rail chips

A chip row names JazzCash, Easypaisa, SadaPay, NayaPay and Raast, showing which payment routes the examples refer to before you read a full paragraph.

Expandable answers

The questions further down the page open in place, so you can settle a point about your data without losing your position in the main text above.

Plain-word lead lines

Short lead sentences sit above the technical detail, handing you the gist in one line with the full wording right underneath if you want to go deeper.

Contact block

A fixed block lists the ways to reach the team that owns this page, so the route to ask about your data is never more than a scroll away.

Common Questions About Your Data

We ask for your name, date of birth, contact details and the payment handle you use with JazzCash, Easypaisa, SadaPay, NayaPay or Raast, plus sign-in records that keep the account secure.

Transaction and account records are held for as long as a legal, tax or accounting duty requires, and once that window closes we delete or anonymise whatever is left.

No. Data goes only to the processors running parts of the service, such as verification checks, payment clearing and support tooling, and they act on our written instructions alone.

Yes. Ask from the email address on your account and we send a readable copy of your profile, transaction history and contact settings, normally within a month.

Sign-in traffic is encrypted on the way through, passwords are stored in hashed form, and two-step checks guard sensitive actions so a stolen password alone cannot open your account.

Message our support desk and we close it, keep only the records a regulator or accountant requires, then write to confirm what was removed and what had to stay.