LEGAL REFERENCE

How hc88 handles your data

hc88 gives you one Privacy Policy for your account, casino lobby and sportsbook activity in supported Pakistan regions, so you can see what data we collect before you...

Account data explainedPakistan access contextJazzCash record clarityPrivacy choices listed
Explore Lobby Read FAQ
hc88 How hc88 handles your data

Our privacy position for Pakistan

This Privacy Policy explains how hc88 collects, uses, stores and shares personal data connected with your account, device, login activity, support messages and transaction records. We process only the data needed to run your account, protect access, check payment status and answer privacy requests where local law permits. Your name, contact details, payment reference, device signals and session records may be used

to confirm that the account belongs to you and to reduce misuse. We do not sell your personal data. When service partners help with hosting, fraud checks, payment routing or support tools, they receive limited data for that task only. Records may be kept for legal, security and account-history reasons, then removed or anonymised when retention is no longer needed.

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

PRIVACY HELP

Contact paths for privacy requests

If you want to ask about your privacy record, correction rights or account data trail, contact us through the route that matches...

Live chat privacy queue Use chat when you need a quick privacy...
Email data requests Email works for correction requests, account data questions...
Payment record queries For JazzCash, Easypaisa, SadaPay or Raast record questions...
POLICY CHECKS

How we keep this policy reliable

We maintain this Privacy Policy as an operator statement, not as third-party commentary. Each section is checked against the way our account tools, support desk and payment records actually work, so you...

Account flow mapping

We map policy wording to the data requested during account opening, login checks and profile updates. If a field is collected, the policy explains the purpose in clear language.

Payment trail wording

Our payment language reflects JazzCash, Easypaisa, SadaPay and Raast records used for status checks. We describe references, receipts and matching without asking you to expose wallet passwords.

Security access checks

The policy covers device signals, login timestamps and session alerts because those records help us protect your account. We state these uses plainly before you rely on the service.

Support script alignment

Privacy answers from chat and email are aligned with this page. That helps our team avoid giving mixed responses when you ask about correction, access or retention.

Retention discipline

We explain why records may be kept for account history, legal duties and security checks. When a reason no longer applies, we aim to delete or anonymise the record.

Regional wording

Pakistan access is described with supported-region wording and local-law context. We avoid invented claims and keep privacy terms tied to the service you actually use.

How this matches related policies

Your privacy rights sit beside other hc88 legal pages, but this page stays focused on personal data. We keep wording consistent across account, transaction and support policies so...

Account terms link
Account terms explain eligibility and use of the service; this page explains personal data connected with that account. The two pages work together without mixing privacy rules with service rules.
Cookie wording match
Cookie wording covers browser storage and similar tools, while this policy explains broader personal data handling. Both pages use the same device-language style to reduce confusion.
Payment policy boundary
Payment rules cover transaction processing and status outcomes. This Privacy Policy covers the data behind those checks, including references, receipts and identity matching where needed.
Security page alignment
Security language explains account protection features. This policy adds the privacy reason for collecting login records, session signals and alerts related to unusual access attempts.
Support policy boundary
Support terms explain how we answer service questions. Privacy wording explains how chat transcripts, email requests and verification details are stored and used during those conversations.
Promo message choices
Where account messages are sent, this policy explains how contact details are used and how preferences may be adjusted. Service notices may still be sent when account safety requires them.
Retention wording
Related legal pages mention records for disputes or account history. This policy explains retention from a data angle, including deletion, anonymisation and legal hold reasons.
POLICY LAYOUT

Privacy elements visible on this page

This page is arranged so you can find data points before creating or managing your hc88 account. The layout highlights what we collect, why we collect it, how...

Plain purpose labels Each privacy section names the purpose before adding detail. That...
Local context chips Short chips point to Pakistan-relevant records such as JazzCash, Easypaisa...
Data category cards Card blocks separate account details, device records, transaction references and...
Request routes Support cards show where to send access, correction or deletion...
Retention cues Retention wording appears near data-use explanations, so storage reasons are...
Choice reminders Where choices are available, the page points to account settings...

Common privacy questions at hc88

We collect account details you provide, login and device records, support messages, and transaction references linked to JazzCash, Easypaisa, SadaPay or Raast. The data is used for account operation, security checks and request handling.

Payment references help us match a transfer to your hc88 account and investigate status questions. We do not need wallet passwords or full private wallet access, and you should never share those details with support.

Yes. Send a request through chat or email, and we will explain the verification steps before releasing account-related data. We may need your registered mobile number or recent reference to confirm ownership.

Contact support with the detail that needs correction and the account identifier we request. We may ask for evidence where the change affects identity, payment matching or account access, then update the record where appropriate.

Retention depends on the record type and reason for storage. Account history, transaction references and security logs may be kept for legal, operational or dispute reasons, then deleted or anonymised when no longer needed.

We share limited data with service partners that help run hosting, payment routing, account safety checks and support tools. They receive only what is needed for their task and must handle it under privacy duties.

We use your contact details for account notices, security alerts, transaction updates and selected service messages. Where preference controls apply, you can adjust them, while essential account or safety messages may still continue.