LEGAL REFERENCE

Our Privacy Policy, Written for You

Our privacy policy sets out what we record when you open an account with zh88 win, why each field is needed and the choices that stay with you...

What we collectWhy we hold itHow long it staysYour requestsVersion dates
zh88 win Our Privacy Policy, Written for You

Where We Stand on Your Data

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

REACH THE DESK

Asking Us About Your Records

Something in this policy reading oddly, or want a record changed? Our support desk is the way in, and it is staffed by people who can see your account rather than a scripted queue. Write in English or Urdu and quote the email address on your account so we match your file on the first reply.

Team online

Email desk

Send your question to our data desk with a short subject line. Most queries about stored addresses, device logs or wallet references are answered the same working day.

Live chat

Chat suits quick checks such as confirming which email we hold for you. The agent verifies your account, then answers or raises a written request so the outcome reaches you.

Data request form

For copies, corrections or erasure, use the form so we capture exactly what you want. It records your account email, the record type and your preferred reply channel.

BEHIND THE CLAUSES

Checks Behind Every Clause Here

Policy text is only worth the checks behind it. Ours is drafted by the team that runs account operations, then read back by colleagues outside it, so a clause about wallet references...

Named owner

Each clause has an owner inside our operations team, so a question about retention reaches the person who can rewrite the wording rather than being passed along to another desk.

Dated versions

Every revision carries a date and the previous wording stays on file, so you can see what applied before a clause about device logs or wallet references changed.

Plain reading

Legal drafts are rewritten into the English used across Pakistan. If a sentence needs a flow chart to make sense, we say the same thing in shorter words.

Field map

We keep a map of where each field travels, from the registration form to the payment gateway, the support tool and the fraud checks, so no record sits unaccounted for.

Access limits

Only staff with a work reason can open personal records, and each look-up is written to an audit trail. Permissions drop away when someone changes role, and the list is checked monthly.

Complaint path

If our first answer does not settle your question, ask for it to be escalated. A senior colleague reads the file again and you receive the outcome in writing.

ACROSS OUR PAGES

How This Page Matches the Others

The rest of our pages share this one's definitions on purpose. Retention windows, the address for data questions and the terms for wallet funding are written once and reused, so you never...

01

Terms of use

The account rules and this policy share one definition of an account holder, so a term you meet in one page means the same on the other.

02

Cookie notice

Our cookie notice covers browser-side signals, while this page explains what happens once those signals reach our servers and become a stored record. Read side by side, they describe one journey.

03

Wallet funding terms

Funding terms set out what happens to a transfer through JazzCash, Easypaisa, SadaPay or Raast. This page covers the reference number that stays with us after it clears.

04

Account rules

Rules for using the lobby and this policy are revised on the same schedule, so a change to how we verify identity lands in both rather than drifting apart.

05

Security page

The security page describes how we protect login access, while this one explains what sits behind it. Neither repeats the other, and both share one contact address for follow-up.

06

Complaints page

A disagreement about a data decision runs through the same route as any other account issue, and the timeline shown on the complaints page applies here as well.

07

Contact page

The contact page lists every channel and data questions use the same desk. Your reference number from a privacy request works across chat, email and the form.

WHAT SITS HERE

What You Will See on This Page

You will meet the same layout on every privacy read: a short summary first, a table showing how long each record type stays with us, a panel listing...

Summary strip A few lines at the start name what we collect...
Retention table A table sets each record type beside the period we...
Rights panel One panel gathers every request you can make, from a...
Language switch The page is written in the English used in Pakistan...
Version stamp A date stamp sits near the heading, so you can...
Save for later You can keep a copy of any version you have...

Data Questions You Send Us Often

The name, contact number and email you register with, your device and login signals, plus references for wallet funding through JazzCash, Easypaisa, SadaPay or Raast.

Payment gateways see the reference for a transfer, and our fraud checks see device signals. We do not sell your file, and suppliers are bound by written agreements.

Login and device signals are held briefly and then dropped. Financial references stay for the period Pakistani rules require, after which they are deleted or aggregated so they stop identifying you.

Yes. Send the request from the email address on your account and we will return a copy or make the correction. If part of it cannot be actioned, we explain why.

Staff with a work reason, such as a support agent handling your query or a colleague checking a payment. Every look-up is logged and permissions go when roles change.

It changes when our systems or the rules around them change. Each version carries a date, and where a change affects what we hold, we tell you by email.