LEGAL REFERENCE

How zp888 Handles Your Account Data

Open a zp888 account and this page sets out, in plain English, what we collect, why we need it and how long we keep it. We wrote it...

Plain-English wordingPakistan account focusContact routes listedCorrections on request
zp888 How zp888 Handles Your Account Data

Where This Policy Applies And What It Governs

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

REACHING OUR DESK

How To Reach Us About Your Data

Questions about your data should not sit unanswered, so we keep a person on the other end of every channel. Tell us what you need changed, removed or explained, and include your account email so we can match the request to the right profile.

Team online

Policy Email

Email our desk with the subject line Data Request and the email on your account. We confirm receipt the same day, then reply with what changes and when.

Live Chat

Signed-in accounts reach an agent by chat between 9am and 9pm Pakistan time. Chat suits quick checks, such as the phone number on file or a JazzCash reference.

Account Settings

Most updates you handle yourself. Open your profile to change a password, check active sessions, or download the summary of stored details. Edits apply at once on every signed-in device.

HOW WE WRITE IT

Who Writes And Checks These Pages

Our policy text is written by the same team that runs account operations, then checked against how sign-up, cashier and support tools actually behave. When a payment rail changes the reference it...

Written In-House

Our wording comes from the team that runs accounts, cashier and support, never an outside agency. We describe only tools we can open ourselves, sentence by sentence in front of you.

Checked Against Live Tools

Before a claim goes live we test it in a real account: sign up, fund a small JazzCash amount, request the summary, close the session, then fix whatever the platform contradicts.

Change History

Each edit carries a date and one short line saying what moved. Older versions stay on file, so if you read different wording last month we can name the change date.

Plain Language

We skip legal filler and write in the everyday English we use with you across Pakistan. Where a term must be technical, we explain it in the same paragraph rather than a glossary.

Region Aware

Access rules differ by area, so we mark which clauses apply where local law permits and which follow the payment rail instead. You read the rule for your own account.

Feedback Route

If a paragraph does not match what you see in your account, send our desk the page name and a screenshot. We log it as a defect and confirm the fix.

How This Page Matches Our Other Policies

The wording here follows the same structure as our terms, cookie and account pages, so a change in one place is mirrored in the others. Same definitions, same...

Shared Definitions
Account, session, reference and region carry the same meaning here as on our terms and cookie pages. One vocabulary across three documents keeps nothing shifting underneath you when you switch pages.
Same Region Wording
Where access depends on local rules, we say supported regions on every sibling page. Our position stays identical whether you are reading about cookies, accounts or data handling.
One Contact Route
Every policy page sends you to the same support desk, with the same hours and the same subject line. You never have to work out which inbox owns your question.
Matching Update Dates
When one policy changes we check whether the others are affected and update them the same week. Dates stay close so you can see one build behind the whole set.
Linked Between Pages
Our footer links each policy to the others so you can read them in any order. Nothing essential sits on one page, so starting anywhere is fine and you lose nothing.
Same Retention Language
How long we keep records is described the same way on every page: the period, the reason and who requires it. A longer partner period is spelled out where it applies.
No Conflicting Rules
If two pages ever disagreed, the stricter rule would govern your account until we corrected the wording. We publish every change instead of hiding it, and you can ask us to check.

What You See On This Data Page

This policy page is built to be read quickly. A chip row names the Pakistan rails we work with, each clause opens with a short summary...

Chip Row

Along the side of the policy you will see the payment names we support for Pakistan — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — used as context for where data travels.

Plain-English Summary

Each clause opens with a short summary line in everyday English, then the detail underneath. Read the summary if you are in a hurry; expand for the exact wording.

Jump Links

A fixed row of links sits above the first clause so you can move straight to the section you need, whether that is retention, corrections or account access.

Version Date

One dated line sits under the heading and moves only when the wording moves. Compare it with our terms page and you can tell if you are reading the current set.

Contact Card

A contact card repeats at the foot of the policy with our desk email, chat hours in Pakistan time, and the subject line that reaches the right queue.

Region Labels

Small labels mark clauses that depend on your region, so you can see at a glance which parts are universal and which follow the rules of the area you sign in from.

Questions We Get About Your Data

Your email, mobile number, country and device details, plus sign-in history and the references returned when you pay in through JazzCash, Easypaisa, SadaPay or Raast. We keep no wallet PIN or bank password.

We store the transaction reference and the status message the rail sends back, which lets us trace a credit if you query it later. Your PIN, bank password and full wallet credentials never reach our systems.

Retention depends on the record. Account and login history stays while your account is open, and payment references are held for the period our partners in supported regions require, after which they are removed.

Yes. Send the request from your registered email with the subject line Data Request and we compile the stored details into one file, usually within a few working days, then confirm everything we sent.

Update the address or phone number in your profile and it takes effect immediately. If a payment reference looks incorrect, message our desk and we will reconcile it with the rail's own record.

Only staff whose job needs it: support answering your query, and specialists checking payment references. Access is logged, and anyone outside those groups sees account numbers rather than personal details.