How prk888 Looks After Your Account Details
This page sets out what we collect when you open an account with prk888, why we collect it, and how long we keep it. You will see which...
Where Local Law Shapes What We Can Store
Privacy rules differ from country to country, so the way we handle your records depends on where you are when you reach prk888. Where local law permits, we keep a lean data set: your contact details, your account credentials and a log of the transfers you run through JazzCash, Easypaisa, SadaPay or Raast. If a supported region asks us to hold records
longer or delete them sooner, that local rule wins over our default schedule. You can ask which rule applies to your account and we will answer in writing. Every request is actioned inside your region's retention window. Nothing here removes a duty we owe to a court or regulator in your jurisdiction, and we tell you when a lawful demand forces us
to hand something over.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Routing Your Privacy Questions To A Person
Every privacy request lands with a named team rather than a queue that swallows it. Tell us what you need, whether that is a copy of your records, a correction, a deletion, or an explanation of why we hold something. We confirm receipt and follow up on the channel you used. Hours follow Pakistan Standard Time, and even a small question gets an owner and a deadline.
Access And Copies
Ask for a copy of everything tied to your account: registration details, login history and the transaction records we hold for your JazzCash, Easypaisa, SadaPay or Raast activity.
Corrections And Deletions
Tell us if a profile detail is wrong and we will correct it once confirmed. Ask us to remove records we no longer need, and we will name what law keeps.
Response Times
Privacy messages reach us through the contact form inside your account. We acknowledge each one within a working day and give you a reference number to follow the thread.
The Checks Behind Every Policy Change
Wording here changes only after the team that runs your account systems, our data protection lead and an outside adviser have read it and signed it off. We date every revision and...
Data Minimisation
We collect what an account needs: your name, contact number, date of birth and the payment identifiers that link each JazzCash, Easypaisa, SadaPay or Raast transfer to you.
Human Sign-Off
A named person approves each wording change before it goes live, so nothing here is generated and forgotten. That editor answers the questions you send in about it.
Version Dates
Every revision carries a date and a short changelog entry, so you can tell whether the clause you agreed to last month still reads the same way today.
Secure Storage
Account records sit on encrypted systems, and access is limited to staff who need it for support or fraud checks. We log who opens a record and why.
Language Access
This wording is written for Pakistan readers in clear English. Urdu-speaking agents are on chat if a sentence needs unpacking, so you never face legal shorthand alone.
Outside Scrutiny
An independent adviser with a data-protection background reads each version and can ask us to rewrite anything unclear. Their comments are logged and answered in writing before publication.
How This Page Matches Our Other Legal Pages
You may read our terms, our cookies text and this page side by side. Definitions match across all three, because one stray edit would leave a gap a...
| Consistent Definitions | Words such as account, personal data and processor carry the same meaning on our terms page, our cookies page and here. One glossary sits behind all three documents. |
|---|---|
| One Contact Route | Every page sends you to the same privacy inbox, so a request about data never bounces between teams. Quote our reference and your thread stays intact. |
| Matching Retention Rules | Where our terms page states how long an account record survives closure, this page carries the same retention window. You will not find two answers to one question. |
| Shared Rail Wording | JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear with identical descriptions in our transfer terms and here, covering what each processor sees and what stays with us. Consistent naming helps. |
| Same Security Baseline | The login checks, session rules and staff access limits set out on our security page apply here too, because both come from one written standard we test periodically. |
| Aligned Update Dates | When one legal page changes, the other documents are checked in the same sitting, so dates stay close together and no page lingers with stale wording. That habit keeps the set coherent. |
| No Conflicting Clauses | If two pages ever disagreed, we would correct the older text rather than leave you to guess which one wins. On data handling, this page takes precedence. The rest link back. |
What You Will Find As You Scroll
The layout is built for reading on a phone without pinching. A summary strip opens the page, chips name the transfer routes we work with, and each clause...