LEGAL REFERENCE

8ball Privacy Policy for Pakistan

8ball connects your account details, lobby activity and Pakistan payment context to one Privacy Policy you can read before you open an account. We explain what we collect...

Account data handlingDevice and login recordsPakistan payment contextSupport contact routes
8ball 8ball Privacy Policy for Pakistan

How We Handle Your Data

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

CONTACT ROUTES

Privacy Contact Paths We Use

You can contact us about access, correction, deletion, restriction or questions linked to this Privacy Policy. To protect your account, we may need to confirm that the request comes from you before taking action. We aim to answer in clear English for Pakistan, with follow-up steps if more detail is needed.

Team online

Account email

Send privacy requests from the email attached to your 8ball account so we can match your message with the right record before sharing, correcting or restricting account data.

Live chat

Use live chat for urgent access concerns, such as a new device alert or a failed login. We may ask account questions before discussing private data with you.

Policy mailbox

For longer privacy requests, write to our policy mailbox with your account ID, request type and country. We separate account help from privacy actions to avoid confusion.

POLICY CHECKS

Signals Behind This Policy

We write this Privacy Policy from the way we operate 8ball, not from a generic template. The points below show how our team checks language, payment references, access...

Plain language

We avoid legal fog where possible and explain account data in direct words. That helps you understand what we collect...

Local payment context

When JazzCash, Easypaisa, SadaPay or Raast appear in account records, we treat those details as payment context and keep them...

Access control

Internal account tools are limited by role, so support, payments and technical teams see different data sets. This reduces unnecessary...

Session records

We keep login time, device type, IP signals and failed access records because they help detect account misuse and support...

Retention checks

Records are kept for legal, payment, security or support reasons, then removed or anonymised when the reason ends. Some records...

Policy updates

When we change a data practice, we update this page and adjust the effective wording. Material changes are surfaced in...

PAGE CONSISTENCY

How This Policy Fits 8ball

Our legal pages are meant to work together without repeating the same paragraph on every screen. This Privacy Policy focuses only on personal data, account records and your privacy choices. Other pages...

01

Terms page

The Terms page explains account rules and service use, while this page explains the data created through those actions. We keep the two pages linked but separate.

02

Cookie page

Cookie wording deals with browser storage and similar tools. This Privacy Policy explains the wider account record, including identity checks, session logs and support messages.

03

Promotions page

Offer pages may ask you to open an account or meet eligibility steps. This Privacy Policy explains how related account data is recorded and handled.

04

Payments wording

Payment pages describe available rails and processing steps. This page explains how related names, references, wallet context and verification records are protected.

05

Support scripts

Support replies may ask for account details to verify you. This policy sets the privacy boundary for those checks and keeps data requests proportionate.

06

Security alerts

Security messages may relate to device changes, login attempts or password resets. This Privacy Policy explains why those records are created and retained.

07

App wording

If you access 8ball through a mobile screen, the same Privacy Policy applies. Device permissions are handled only where needed for account features.

POLICY LAYOUT

Visible Privacy Elements On 8ball

We place privacy cues close to the actions that create data, instead of hiding them in a single footer link. Account forms, verification screens and support flows point...

Form cues Account forms show why each required field matters, such as...
Verification prompts When verification is needed, the screen explains the purpose before...
Login alerts Device and location signals can trigger account alerts. The policy...
Support transcripts Chat and email conversations may be saved so we can...
Preference controls Where account settings allow contact preferences, we record your choices...
Footer access The Privacy Policy link stays available from the footer so...

Privacy Policy Questions Answered

We collect details you provide, such as contact data, account credentials and verification material when requested. We also create login, device and session records as you use 8ball.

Payment context helps us process account requests, check mismatches and answer support questions. References linked to JazzCash, Easypaisa, SadaPay or Raast are handled as account records.

Yes. Contact us from the email linked to your account and explain what needs correction. We may verify your identity before changing data that affects access or payments.

We use device type, session time, IP signals and failed access records to protect accounts, investigate unusual activity and support password or access questions raised by you.

We share limited data with partners that help run hosting, support, analytics, security checks or payments. They receive only what is needed for their work with 8ball.

Retention depends on the record type and reason. We keep data for account, payment, legal, security or support needs, then remove or anonymise it when no longer required.