Privacy Policy for Your h88 Account
h88 keeps your account data, device details and payment records under a clear Privacy Policy built for Pakistan. Open your account knowing how we collect, use, store and...
How We Handle Your Data
This Privacy Policy explains how h88 handles personal data when you create an account, access casino or sportsbook areas, contact support, or request account checks where local law permits. We collect only what is needed to run your account flow, confirm payment references, protect access, answer your messages and meet record duties in supported regions. Your data may include name details, contact
points, device signals, login history, payment references and security checks. We do not sell your personal data. We share limited records only with service partners who help with account safety, local payment verification, hosting, analytics or support, and they must handle those records under our instructions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Paths for Privacy Requests
You can ask us about your data without searching through the lobby. We keep privacy contact paths separate from routine account chat so your request reaches the right team and can be logged with the account record it concerns.
Privacy inbox
Write to our privacy team when you want access, correction or deletion checks for account data. Include your account email and a brief request so we can match it without asking for extra details.
Account chat
Use live chat for time-sensitive privacy concerns linked to login, device access or payment reference visibility. We may move the matter to email if identity checks or written records are needed.
Security escalation
If you think your account data has been exposed, tell us quickly through support. We can lock access checks, refresh credentials and trace recent sessions while keeping a record for privacy handling.
How Our Policy Stays Accountable
Our Privacy Policy is written from the way we operate h88, not from vague wording. It links data use to real account actions: login, payment reference checks, support contact, fraud prevention and...
Clear data map
We separate account data, payment references, device signals and support messages so you can see why each category exists. That structure helps us answer privacy requests without mixing unrelated records.
Local payment handling
JazzCash, Easypaisa, SadaPay and Raast references are used to confirm account activity and payout checks. We keep transaction context limited to what support and finance teams need for verification.
Access controls
Only staff with a direct work reason can view privacy-linked account records. Permissions are role-based, and sensitive actions are logged so we can trace access if you raise a concern.
Device security
We use device and session signals to detect unusual logins, repeated failed attempts and account takeover risks. These signals support account safety while staying tied to clear security purposes.
Retention checks
We keep records only for account operation, legal duties, dispute handling and security analysis. When a record is no longer needed, we remove it or reduce it so it no longer identifies you.
Policy updates
When our privacy wording changes, we update the page date and adjust the text around the affected data practice. Important changes may also be flagged inside your account area.
Consistency Across h88 Policy Pages
Our Privacy Policy works beside other h88 legal pages, but it has its own purpose: data handling. When another page explains account rules, cookies or promotions, this page...
Privacy Elements You Can See
The policy page is designed so key privacy points are easy to scan before you open an account. Each visible block answers a practical question about...
Short badges
The hero badges show the privacy areas most relevant to Pakistan: account data, local payment context and access checks. They help you spot policy scope before reading deeper.
Plain sections
Each section explains one privacy duty in direct language. We avoid mixing data handling with lobby promotion so you can judge account privacy on its own terms.
Named rails
When payment context matters, we name JazzCash, Easypaisa, SadaPay and Raast. That keeps the policy linked to the records you may actually see in your account.
Action routes
Privacy contact routes are shown as separate cards so you know where to ask for access, correction or security escalation without sending extra details to the wrong queue.
Retention signals
Retention wording tells you why some records remain after a transaction or support case closes. We tie timing to account duties, disputes, security and legal record needs.
Change markers
The policy can be updated as our account flow changes. Visible revision cues help you see when wording has shifted and which data practice the change concerns.