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.
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...
Where local law permits, we are the party that decides how your account data is handled, and each collection is limited to what running your account genuinely needs. Your name, contact number and device signals enter our systems when you register. Wallet references from JazzCash, Easypaisa, SadaPay and Raast reach us through the payment gateway rather than from your handset. We keep
records while your account stays open, plus the retention window Pakistani financial rules demand, after which they are deleted or aggregated so they no longer point at you. You may ask to see, correct or erase what we hold, and we answer inside a stated window. Rights vary by province and by regulator, so the reach of an erasure request depends on
where you live and on duties we cannot set aside.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
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.
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.
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.
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.
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...
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.
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.
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.
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.
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.
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.
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...
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.
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.
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.
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.
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.
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.
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.
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...