LEGAL REFERENCE

Privacy Policy for Your 88com Account

Live Baccarat, slot rooms and sportsbook access create account, device and payment data, so our Privacy Policy tells you exactly how 88com handles it in supported regions of...

Account data explainedPakistan access contextPayment privacy cuesContact routes included
Explore the lobby Read FAQ
88com Privacy Policy for Your 88com Account

How We Handle Your Data

This Privacy Policy explains how we collect details when you create an 88com account, pass security checks, enter the lobby, contact us or use Pakistan payment rails where local law permits. We keep account records, device signals, login history, transaction references and support messages only for service, safety, fraud control, legal handling and account operation. We do not sell your personal data.

When JazzCash, Easypaisa, SadaPay or Raast is involved, we process only the details needed to match your account, confirm payment status and respond to your request. We also explain retention, correction requests and how to reach us if something looks wrong.

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

HELP ROUTES

Privacy Help When You Need It

If you have a privacy question, we want the route to feel clear before you share anything sensitive. Our support team can...

Live chat privacy desk Use chat for quick privacy questions about account...
Email request path Send privacy requests by email when you need...
Security concern route If you think your account or personal data...
POLICY CHECKS

How We Keep This Policy Accurate

We write this Privacy Policy from the way 88com actually runs account access, payments, support and security checks. The text is checked against our live workflows, so you can see why each...

Workflow checked wording

Privacy wording is matched against account creation, login checks, wallet matching and support handling. If a workflow changes, we update the relevant policy wording rather than leaving vague legal phrasing.

Local payment mapping

We separate payment reference data from gameplay records where practical. JazzCash, Easypaisa, SadaPay and Raast details are treated as payment context, not as content for lobby personalisation.

Access control language

The policy states who may view personal data inside our operation. Access is limited by role, logged where practical and used for account support, safety checks and payment matching.

Retention checks

We describe why records may be kept after an account action, including payment disputes, fraud screening and legal handling. When retention is no longer needed, we aim to remove or anonymise data.

Plain English edits

We keep the policy readable for Pakistan customers using clear local English. Legal terms are explained beside practical examples, so you can connect the wording to your account journey.

Change tracking

When the Privacy Policy changes, we update the visible date and adjust affected sections. Material changes may also be signalled through account messages or page banners.

One Privacy Standard Across Pages

Our Privacy Policy connects with other 88com legal pages, but it has its own job: explaining personal data handling. We keep definitions, request routes and security language consistent...

Cookie page alignment
The cookie page explains browser storage, while this policy explains the personal data link. We keep consent wording aligned so tracking choices and account privacy are not described differently.
Terms page link
The terms page covers account rules; this policy covers data used to run those rules. Identity checks, session records and payment references are described here from a privacy angle.
Security page match
Security wording mirrors this policy when it describes login alerts, session checks and account access controls. That helps you understand both protection steps and the data behind them.
Payment wording match
Payment pages may name JazzCash, Easypaisa, SadaPay and Raast for account funding. This policy explains the privacy role of references, timestamps and verification signals.
Support page connection
Support pages explain how to reach us; this policy explains what happens to messages you send. We cover chat logs, email trails and identity checks in one privacy context.
Promotion page boundary
When offer pages require account eligibility checks, this policy explains the data side. We describe matching, fraud screening and communication choices without turning privacy wording into sales copy.
Regional wording
Where access is limited to supported regions, the same phrasing is used across pages. This policy explains how location signals may be used for availability and account checks.
READING CUES

Policy Layout You Can Read Quickly

This page is arranged so you can scan privacy points without losing the legal meaning. Headings show the data stage, cards explain practical handling and short labels point...

Clear section anchors Each section focuses on one privacy stage, such as collection...
Plain data labels We use labels like account data, device data and payment...
Visible date area The policy date area tells you when wording was last...
Request prompts Privacy request prompts point you toward correction, access or deletion...
Contact strip The contact strip gathers privacy help routes in one place...
Regional markers Regional markers explain when Pakistan availability, supported regions or local...

Privacy Questions Before You Join

We collect account details, login signals, device data, payment references and support messages. The exact data depends on how you use 88com and which checks apply in your supported region.

Payment references help us match your 88com account with JazzCash, Easypaisa, SadaPay or Raast activity. We use them to confirm status, handle disputes and respond to account questions.

No. We do not sell your personal data. We share data only where needed for account operation, payment processing, security checks, legal handling or support services connected to 88com.

Yes. Contact us if your account details are wrong or outdated. We may verify your identity first, then update eligible records or explain why a record must stay unchanged.

Support messages are treated as account records because they may contain identity checks, payment questions or security concerns. We keep them for service quality, dispute handling and account safety.

Retention depends on the record type and reason. Some data is kept for account operation, fraud checks, payment disputes or legal handling, then removed or anonymised when no longer needed.

We update the policy date when wording changes. If a change materially affects privacy handling, we may also use account messages or page banners to draw your attention.