LEGAL REFERENCE

Privacy Policy for Your Account

8888pk keeps your account, casino, sportsbook, JazzCash, Easypaisa, SadaPay and Raast data under one clear Privacy Policy, so you know what we collect before you open an account...

Account data usePakistan payment contextPrivacy request routesSecurity handling
8888pk Privacy Policy for Your Account

How We Handle Personal Data

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

CONTACT ROUTES

Ask Us About Privacy

Use the privacy contact paths when you want to access, correct, export or erase account data. We may ask you to prove account ownership before acting, because privacy requests can expose sensitive records. Keep your request clear and use the same phone or email tied to your 8888pk account.

Team online

Privacy email

Email us from the address on your account, include your 8888pk ID, and tell us which privacy request you want handled, such as access, correction, deletion, or consent change.

Live chat handoff

Start with chat when you need routing help. Our agent records your request type, confirms account ownership steps, and moves privacy matters to the team that handles data records.

Account centre

Inside your account area, you can check contact details, active sessions and verification status. Keeping these fields current helps us answer privacy requests without avoidable delays.

DATA CHECKS

Policy Checks Behind the Page

We keep this Privacy Policy tied to the systems we actually run. When a data flow changes, we check the wording against account creation, payment reconciliation, live chat records, security logs and...

Account creation

We explain which details are requested at account opening, why they are needed, and how they support login access, verification, fraud checks and account recovery requests.

Payment references

For JazzCash, Easypaisa, SadaPay and Raast flows, we describe references we may store, including transaction status, timestamps and sender identifiers needed for reconciliation.

Session security

We cover device data, IP records and session tokens because they help us detect unusual access, protect your account and investigate login disputes.

Support records

We keep support chats and email messages for service history, complaint handling and proof of your requests, with access limited to staff who need them.

Consent controls

We explain how marketing consent works, how you can change it, and why essential account messages may still be sent after opt-out choices.

Update process

When we change this Privacy Policy, we update the page date and keep the new wording aligned with how account data is processed.

POLICY LINKS

How This Policy Fits

Privacy wording should not clash with other legal pages. We align this page with our terms, cookie wording, account rules and promotional message settings so you can follow one clear privacy thread...

01

Terms page

Our terms set account rules, while this Privacy Policy explains the personal data connected to those rules, including verification, security logging and communication records.

02

Cookie wording

Cookie wording deals with browser storage and tracking choices. This page explains how those signals may connect with sessions, preferences and account protection.

03

Promotional consent

Marketing choices are treated as privacy settings. We explain how opt-ins, opt-outs and essential service messages are recorded against your account.

04

Payment handling

Payment pages may describe transaction steps. This Privacy Policy explains which references from JazzCash, Easypaisa, SadaPay and Raast we keep and why.

05

Security wording

Security pages describe account protection. This page adds the privacy angle, including login records, device signals and access controls around personal data.

06

Support records

Help pages show how to contact us. This Privacy Policy explains why we keep chat, email and request records after a privacy matter closes.

07

Change notices

When a related policy changes, we check whether privacy wording also needs updates, especially around collection purpose, sharing partners and retention periods.

Privacy Page Markers You Can Use

This page is built to help you scan privacy points without losing legal meaning. We use short labels, local context and clear request routes so the...

Plain section labels

Each section is named around a privacy task, such as data use, sharing, retention or contact routes, so you can move through the policy quickly.

Local context chips

We name JazzCash, Easypaisa, SadaPay and Raast where payment data is discussed, because local transaction references affect privacy handling in Pakistan.

Request language

The policy uses action words like access, correct, export and erase, helping you frame a privacy request without needing legal phrasing.

Sharing boundaries

We separate internal use from partner sharing, so you can see when data stays with us and when limited records may reach service providers.

Retention cues

We explain why certain records are kept after account activity, including transaction references, support history, legal requests and security investigation material.

Update date area

The policy date helps you see when wording changed. If a privacy change is material, we aim to make it visible on this page.

Privacy Policy Questions

We collect account details, login records, device signals, verification data, payment references, support messages and activity records needed to run your account, protect access and answer requests.

No. For JazzCash, Easypaisa, SadaPay and Raast, we handle transaction references, status updates and reconciliation details. We do not need your wallet password.

Login and device records help us recognise account access, detect unusual behaviour, investigate disputes and reduce fraud risk. Access to these records is limited internally.

Yes. Contact us from your registered email or phone and explain what needs correction. We may request proof before changing details linked with identity or payment records.

We share limited data with payment processors, verification partners, hosting providers and advisers when needed for account services, security checks, dispute handling or lawful requests.

Retention depends on the record type. We keep transaction, security, support and legal records as needed for operations, dispute handling and lawful obligations.