How zply bet Handles Your Account Data
This is where we set out exactly what we collect when you open an account with us, why we collect it, and where it goes. It explains signup...
What This Policy Covers and Where It Applies
Our privacy commitments apply wherever zply bet operates, and some clauses shift depending on the rules in your supported region. Where local law permits, we hold your records only as long as we need them for account operations, dispute handling and tax reporting. Retention differs for payment logs, chat transcripts and device data, so we list each category separately. If a market
rule demands something different, that rule wins over the general wording here.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Draft and Update This Policy
Every clause here is written by the team that runs account operations, then checked by our legal contact before it goes live. When something changes — a new payment rail, a fresh...
Plain-Language Drafting
We skip the legal filler and write each clause in everyday English, so you can tell what we collect and why without needing a lawyer to translate it for you.
Named Data Roles
Our policy names the roles rather than hiding them: who controls the data, who processes it, and which supplier runs verification checks on our behalf for accounts opened in Pakistan.
Change Dates
Each update carries a date and a short line about what changed, so you can track edits to retention periods, payment partnerships or how long support keeps your chat history.
Local Rule Checks
Before wording goes live we check it against the rules in each supported region, and we flag where a local requirement overrides the general text you are reading.
Supplier List
Suppliers who touch your data are listed by category — payments, verification, hosting and analytics — with the reason we use each one and what they can reach.
Your Right to Ask
You can ask us to explain any paragraph, and we will put the answer in writing, including which legal basis we rely on to keep a particular record.
How This Policy Sits With Our Other Pages
The wording here lines up with the terms you accept at signup, the cookie banner on your first visit, and the payout rules in our help area. If...
| Signup Terms | The consent you give when you tick the box at registration lines up with the collection points described on this page, so there is one version of the story. |
|---|---|
| Cookie Banner | Tracking categories on our cookie banner use the same names as the sections here, covering essential session cookies, performance measurement and the optional analytics you can switch off. |
| Payout Rules | How long we keep withdrawal records, and which JazzCash, Easypaisa, SadaPay or Raast references we store, is described in both places with the same retention window for dispute checks. |
| Help Centre Articles | Support articles about account recovery and identity checks link back to the relevant clause here, so you can jump from a how-to page straight to the legal wording. |
| Promotional Pages | Offers shown in your account area never widen what we collect. If a campaign ever needed extra data, we would ask you separately and explain the purpose in plain words. |
| Version History | Each release keeps a reference number and the date it took effect, which our team uses when you ask what the policy said on the day you registered. |
| Regional Addenda | Where a supported region needs extra wording — different consent ages or shorter retention — we publish a short addendum that sits beside this page and takes priority locally. |
What You Will Find Across These Blocks
Scroll this page and you will meet seven blocks, each answering one thing: what we collect, how long we keep it, who else sees it, how...
Collection Summary
A short table-style block lists every data point we gather — name, date of birth, contact details, device signals — and marks which ones are required to keep your account open.
Retention Windows
Each category shows how long we hold it: identity documents for the statutory period, transaction entries for accounting, and chat logs for a shorter support window before deletion.
Sharing List
We name the categories of recipients — payment processors, verification suppliers, hosting providers, regulators where required — instead of using vague wording about partners.
Security Measures
TLS in transit, encrypted storage at rest, role-based staff access and logged admin actions. We describe each control in the same place so you can see the full picture.
Your Controls
Buttons inside your account area let you edit contact details, change notification channels, request a copy of your file or start account closure without emailing anyone at all.
Defined Terms
Words like controller, processor and legitimate interest are explained in one line each, so the policy reads clearly whether or not you work with data every day already.