Privacy Policy for your 8h88 account
We set out how 8h88 collects, uses, stores and shares your account data before you open an account or return to the lobby. Read this page to see...
How we treat your account data
This Privacy Policy explains our handling of personal data linked to your 8h88 account, including registration fields, login events, device signals, payment references and messages you send to our team. We use this data to run account access, verify transactions, answer privacy requests, prevent misuse and meet record duties where local law permits. We do not sell your personal data. Some processing
may involve service partners that help with hosting, fraud screening, analytics, payment routing or customer care, and those partners receive only the data needed for their assigned task. If you use JazzCash, Easypaisa, SadaPay or Raast, we may keep transaction references, timing, account match checks and status records so your balance history remains traceable.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to reach our privacy team
Send us a clear privacy request and we will route it to the team that handles account data. Include the email or phone linked to your account, but do not send card images or unrelated documents unless we ask. We may need to confirm your identity before changing, releasing or deleting records.
Privacy email
Use [email protected] when your request concerns account data, payment checks, device records or correction of profile fields. Add the email used on your account so we can locate the right record.
Live chat handoff
If you start in live chat, ask for a privacy request handoff. Our agent can tag the matter, confirm the account reference and tell you what identity check may be needed next.
Account message
You may contact us from inside your account when access is available. This helps us match your request with login history, payment references and prior support messages without extra back-and-forth.
How we keep this policy checked
Our privacy text is written against the way 8h88 actually handles accounts. We check it when forms, payment routing, security tools or support workflows change. The aim is simple: you should understand...
Operational match
We compare the policy with live account flows, including registration, login checks, withdrawal verification and support forms, so the wording reflects actual data handling rather than generic legal phrasing.
Payment trace care
JazzCash, Easypaisa, SadaPay and Raast references are kept with purpose in mind: balance matching, security checks, dispute handling and account history. We avoid collecting unrelated wallet details.
Access controls
Staff access to account data is role-based. Support can see what it needs for your case, while sensitive verification records are restricted to trained teams handling security or payment checks.
Device data use
We use device and browser signals to protect sessions, detect duplicate risk and keep logins stable. These records are linked to security purposes, not sold to outside advertisers.
Retention checks
We keep records for business, legal and security reasons, then reduce or remove them when they are no longer needed. Retention periods depend on record type and account activity.
Plain language
We write policy text in clear Pakistani English so you can read it before joining. If a clause affects your choices, we aim to say it without legal fog.
How our policies stay consistent
This Privacy Policy sits beside our terms, cookie text and account rules. Each page has its own purpose, yet the data handling language should not conflict. When a...
| Terms connection | Our terms explain account rules, while this page explains data handling behind those rules. If verification is mentioned in both places, the privacy wording covers what records are used. |
|---|---|
| Cookie connection | Cookie text covers browser storage and tracking choices. This Privacy Policy explains how those signals may link with login security, fraud screening and site performance data. |
| Payment records | Payment pages describe transaction steps. This policy explains how references from JazzCash, Easypaisa, SadaPay and Raast may be stored, matched and used for account security. |
| Support records | Support pages tell you how to contact us. This policy explains how chat logs, email threads and account messages are kept when you ask for help. |
| Security wording | Security rules may ask for identity checks. This policy explains the privacy side, including why checks occur, who can access records and how requests are handled. |
| Regional access | Access wording across the site uses supported regions and where local law permits. This policy applies that same approach when describing account data handling in Pakistan. |
| Change notices | When policy text changes, we update the page date or wording where needed. Major data handling changes may also be flagged through account or support channels. |
Privacy page layout cues
We structure this page so the important privacy points are easy to scan before you create or use an account. Headings separate collection, use, sharing, storage...
Short badges
Badges near the opening show the main privacy themes quickly: account data, payment context, device checks and support records. They are labels only, not limits on the policy.
Local context
Pakistan references appear where location affects account access, language, payment names or legal wording. We use supported regions phrasing when access may depend on local rules.
Direct contact path
Privacy contact routes are placed before deeper policy detail so you can reach us without searching. We separate email, chat handoff and account message paths.
Specific examples
Examples such as JazzCash references, login events and device signals show what data categories mean. We avoid vague labels when a practical example makes the policy clearer.
Clear rights wording
Where you can ask to access, correct or delete data, we explain the request path and possible identity check. Some records may remain where law or security requires.
Update placement
Policy changes are kept on this page so you can return and compare wording. We avoid hiding privacy changes inside unrelated account messages or sales copy.