LEGAL REFERENCE

Privacy Policy For Your 188bets Account

This Privacy Policy explains how 188bets handles personal data when you open, access or close an account from Pakistan. We describe the information we collect, why we need...

Clear data purposesPakistan account contextSecurity-led handlingContact choices
188bets Privacy Policy For Your 188bets Account

How We Handle Personal Data

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

PRIVACY CONTACTS

Reach Us About Your Personal Data

Our privacy contact paths are designed to keep requests focused and traceable. Tell us which account or record your request concerns, use the email linked to your account where possible, and avoid sending wallet PINs or complete payment credentials. We may ask for reasonable proof of identity before changing or disclosing account data.

Team online

Privacy desk

Send a data request through the privacy contact route shown on 188bets. Include your account email, request type and Pakistan region so we can direct the matter correctly.

Account assistance

For access problems, contact our account support channel first. We can help separate a login issue from a data request without asking you to reveal a JazzCash or Easypaisa PIN.

Request tracking

We record the date, subject and action taken for privacy enquiries. If a request needs clarification, we will explain what is missing before proceeding with a change or disclosure.

SECURITY CONTROLS

Practical Signals Behind This Policy

Privacy commitments matter when they match the way an account actually works. Our controls cover sign-in activity, payment references, support conversations, device access and account changes. We limit...

Access records

We may log sign-in time, device type, IP address and security events to identify suspicious access. These records help us...

Wallet references

When you use JazzCash, Easypaisa, SadaPay or Raast, our records can show a transaction reference, amount and status. Wallet authentication...

Support history

Messages sent to our support team may be retained so we can resolve repeated access or account matters consistently. We...

Device signals

Browser settings, operating system details and device identifiers can help recognise a returning session or detect automated misuse. You can...

Limited access

Personal data is made available internally only where a work task requires it, such as account security, customer care, technical...

Policy changes

If our data practices change materially, we will update this page and show the revised date where appropriate. Please check...

What This Policy Covers Clearly

This page is written to work alongside our account terms and other legal pages without replacing them. Its subject is personal data: what enters our systems, why it...

CollectionWe identify the account, technical, payment-reference and communication data that may reach 188bets during registration, sign-in, support contact or account activity.
PurposeEach listed data category is connected to a practical reason, such as account security, transaction handling, customer care, service operation or legal recordkeeping.
SharingWe explain when data may be disclosed to service providers, payment partners, technical operators, advisers or authorities where a lawful reason applies.
RetentionWe keep records for operational, security or legal needs and remove or anonymise them when continued storage is no longer required for those purposes.
Your choicesYou can ask about access, correction or deletion, although identity checks and lawful retention requirements may affect how a request is completed.
Regional accessAccount availability and data handling can depend on Pakistan rules and supported regions, so access conditions may differ according to your location.
Policy updatesThe current wording on this page governs privacy handling for the relevant period, while a visible update can explain material changes to our practices.
PAGE STRUCTURE

Privacy Details At A Glance

We have arranged this policy so you can move from the short promise to practical detail without searching through unrelated platform copy. The layout separates collection, security, contact...

Plain-language opening The opening block states the policy subject directly, so you...
Data handling detail The legal section connects account information, technical records and payment...
Direct contact paths Contact cards show how to raise a privacy request, handle...
Security signals The security section focuses on sign-in records, wallet references, device...
Consistent scope The comparison block keeps this policy distinct from account rules...
Question-led reading The final section answers common data questions in compact language...

Privacy Questions You May Have

We may collect your contact and account details, login records, device and browser signals, support messages, transaction references and security events. The exact data depends on how you access and use the account.

We use account data to create and secure your profile, respond to support requests, process authorised account actions, detect unusual access, maintain reliable records and meet duties that apply where local law permits.

You should never send a wallet PIN or passcode to us. Payment records may contain a reference, amount and status, while authentication details remain with JazzCash, Easypaisa, SadaPay or Raast.

Yes. Contact our privacy route with the account email, the record you believe is incorrect and the requested correction. We may confirm your identity before changing personal data linked to your profile.

You may ask us to delete eligible personal data. Some records can remain where security, dispute handling, accounting or legal duties require retention. We will explain any limitation that applies to your request.

We use access controls, session and security logs, protective measures for data in transit and monitoring for unusual activity. You also help protect access by keeping passwords and device access private.

Yes. Access and processing can depend on Pakistan requirements and supported regions. Where local law permits, we apply this policy to the relevant account activity and explain limits when a regional rule affects your request.