LEGAL REFERENCE

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...

Registered detailsWallet referencesDevice signalsSupport history
88pkr How We Handle Your Account Data

The Rules Behind Every Record We Hold

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

REACH OUR DESK

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.

Team online

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.

WHO IS ACCOUNTABLE

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...

Account Terms
Covers what you agree to when you register, including one-account and age rules. Where those terms name a data purpose, this page explains how that purpose works in practice.
Cookie Handling
Describes the small files your browser stores so the lobby remembers your language and session. It repeats the same consent rule you find in the posture block above.
Payment Routes
Show how long each JazzCash, Easypaisa, SadaPay and Raast transfer takes. The reference numbers displayed there are treated as transaction records here and kept on the same schedule.
Security Pages
Explain sign-in alerts and device checks. Every log described there is held under the retention periods set out here, not under the wording on that page at all.
Support Routes
List channels and hours. The three contact paths above lead to the same desk, so a request raised in either place is logged once and answered once.
Sportsbook Rules
Cover market settlement and wager records. Settlement data follows the same storage and retention wording as casino activity, so nothing changes depending on which product you are using.
Priority Rule
If two pages ever disagree on anything concerning personal data, this policy takes priority, the other page is corrected in the next release and we log the change.

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.

Questions We Get About Your Data

Your name, date of birth, contact details, country and the reference your payment rail returns. We also log the device and network behind each sign-in to spot access that is not yours.

We keep the reference your wallet sends back, plus the amount, date and status of each movement. Wallet credentials stay with the provider, out of reach of our systems.

Records tied to money movement are held for the period our auditors expect under Pakistani rules, then removed on a set schedule. Support chats are kept for a shorter window.

Where local law permits, yes. Write from your registered email and we erase what we are not required to keep, then tell you in writing which records stayed and why.

Only teams with a reason: support to answer you, the payments desk for a disputed transaction and the security group for access logs. Every look-up is recorded against a staff account.

Limited data goes to payment providers, identity-check suppliers and hosting partners under written contracts. We do not sell personal data or hand it to advertising networks at any point.