Privacy Policy for your eh77 account
This Privacy Policy explains how we handle your account details, device signals, wallet references and support messages when you use eh77 in supported regions of Pakistan, where local...
Privacy posture for Pakistan account data
We collect only the data needed to create your eh77 account, keep access secure, process wallet requests and respond when you contact us. This Privacy Policy covers personal details you provide, technical records from your device, payment references from JazzCash, Easypaisa, SadaPay and Raast, and messages sent through our help channels. We use this data to confirm account ownership, detect unusual login
activity, reconcile transactions and meet record keeping duties that apply in supported regions. We do not sell your personal data. When a studio, payment rail, identity check partner or hosting provider helps us run the service, we share only the fields required for that task and expect handling controls from that partner.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy current
Our Privacy Policy is checked by the team that operates account access, payments, game sessions and support queues. That matters because wording must match what our systems actually collect. When we add...
Account fields matched
We compare the policy against the fields shown during account opening, including name, contact detail and login credentials. Extra fields cannot be added without a policy check and internal approval.
Device records explained
The policy separates device signals from profile data, so you can see why browser type, IP range and session timing help us protect access and investigate unusual activity.
Wallet data limited
Payment references are handled as account records, not open profile text. JazzCash, Easypaisa, SadaPay and Raast details stay tied to reconciliation, withdrawal checks and support requests.
Provider sharing scoped
Game studios and technical partners receive only the session data needed to load tables, record outcomes or maintain service stability. We avoid sending profile fields when a token is enough.
Retention checks scheduled
We keep records for the time needed for account security, transaction disputes and legal duties in supported regions. Older records are restricted or removed when they are no longer required.
Support access controlled
Only trained support staff can open privacy tickets, and access is logged. Sensitive replies move through protected channels rather than casual chat when identity checks are needed.
How this policy aligns across pages
Our Privacy Policy connects with other legal pages, but it has a narrower job: explaining personal data handling. Terms describe account rules, cookie text explains browser storage, and...
| Privacy Policy | This page explains account data, device records, payment references, partner sharing and your contact paths. It is the main place to understand how eh77 handles personal data. |
|---|---|
| Cookie wording | Cookie text supports this policy by describing browser storage, session tags and preference tools. Where cookies connect to account security, this policy explains the wider data purpose. |
| Terms page | Terms set the rules for account use, but privacy wording explains the data behind those rules. We keep enforcement language separate from how personal records are collected and stored. |
| Promotion terms | Promotion terms may mention eligibility checks, while this policy explains the data used to verify those checks. We do not turn offer pages into privacy explanations. |
| Payment help | Payment help may describe wallet steps, while this policy covers how related references are stored, compared and shared with support when JazzCash, Easypaisa, SadaPay or Raast issues arise. |
| Security messages | Security prompts tell you what action to take after a suspicious login. This policy explains the records behind those prompts, including device changes, location signals and access timing. |
| Support scripts | Support replies must match this policy when staff discuss account data. If a request needs more detail, it is escalated instead of being handled through casual chat lines. |
Policy page signals you can scan
We structure this Privacy Policy so you can move from collection to use, sharing, storage and contact without reading unrelated sales copy. The visible elements are...
Plain data categories
We name the main categories clearly: account details, device signals, payment references and support messages. Each category is linked to a purpose, so the policy does not feel vague.
Local wallet context
JazzCash, Easypaisa, SadaPay and Raast appear where they affect privacy, mainly reconciliation, withdrawal checks and account queries. We avoid treating wallet names as general decoration.
Purpose before sharing
The page explains why data is used before naming partner access. That order helps you see whether a studio, wallet rail or hosting service needs a field for a valid task.
Security wording
Security language is tied to actual controls such as login checks, ticket access and session records. We avoid broad claims and focus on steps that relate to your account.
Request path clarity
Contact routes are separated by privacy concern, wallet reference and urgent access issue. That layout helps your request reach the right team without exposing sensitive details in chat.
Update cues
When privacy wording changes, we keep the page aligned with account screens, payment handling and support scripts. The aim is consistency between what you read and what we operate.