How We Handle Your Account Data
This page sets out how 88pkr collects, stores and uses the details you give us when you open an account. It covers signup data, wallet transaction records, device...
The Rules Behind Every Record We Hold
88pkr processes personal data to run your account, verify who you are before a payout and keep the records our auditors expect in supported regions. We rely on your consent, on the contract between us and on our own interest in keeping the platform secure. Where local law permits, you can see which categories we hold, fix anything wrong and ask us
to erase records we no longer need. Transaction histories stay for the periods regulators require, then go. Data moved outside Pakistan travels under written safeguards in our supplier contracts. None of this narrows a right you hold under Pakistani law, and if a rule in your region differs, that local rule wins.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways To Reach Our Data Desk
Questions about your data do not need a queue. Write from the email on your account, raise a ticket inside your profile, or open live chat during support hours. Tell us which records you mean and what should change, and we confirm receipt, then follow up once the check is done.
Registered Email
Write from the address on your account, because that is how we confirm a request is yours. Tell us the detail you want corrected and we log it the same day.
Live Chat
Chat opens while you are signed in, seven days a week, for quick checks such as which email we hold. Follow with a written request if a formal record is needed.
Help Ticket
Raise a ticket from your profile so it stays with your account and any agent picking it up sees the full history. Attach a screenshot only for a wallet record.
The Checks Behind Each Policy Revision
Each time data flow changes inside 88pkr, we sit with the team that built it: what is captured at signup, what the payments desk can see, what the security group logs, what...
Data Lead
A named person owns this page. They sign off any change to how account data is stored or shared, and they hold the record of when each version was published.
Security Desk
Handles access logs, sign-in alerts and encryption keys. If a device you do not recognise reaches your account, this team traces the route and tells you what they find.
Payments Team
Works with JazzCash, Easypaisa, SadaPay and Raast so every transaction reference stays attached to your account, and nothing beyond that reference is held on our systems at all.
Support Crew
Reads only what is needed to answer you: your account status, your recent tickets and the channel you wrote in from. Full wallet numbers stay out of reach.
Legal Adviser
Checks each revision against Pakistani record-keeping duties and against the rules of every supported region, so the wording here matches what our teams actually do in practice.
Localisation Editor
Keeps this page in en-PK English for Pakistan, so a term such as wallet reference carries the same meaning for you as it does for our staff reading it.
Where The Same Rule Appears Twice
Terms of use, cookie handling and this page are written together so you never meet a different answer in each one. When a detail changes, every route updates...
What This Page Puts In Front Of You
We built this as a readable page rather than a wall of clauses. A short hero names the subject, a posture block explains the legal basis...
Plain Summary
The opening block answers what we collect and why before any clause appears, so you can decide whether to keep reading without opening a separate document first.
Region Wording
Every access rule on this page carries the phrase where local law permits, because the answer can differ between supported regions and we do not pretend otherwise.
Wallet Chips
Small labels beside the posture block name JazzCash, Easypaisa, SadaPay and Raast, so you can see which rails the transaction wording refers to at a glance.
Named Roles
Cards name the function responsible for each promise, from the security desk to the payments team, instead of hiding every duty behind a generic brand statement.
Revision Dates
We date each published version and keep the previous wording on file. Ask the data desk and we will send you what changed and when it changed.
Contact Strip
Three routes sit in one place, each naming the detail it needs, which keeps your request out of a general queue and attached to the record concerned.