Account creation
The account terms describe what you must provide to join. This Privacy Policy explains how those details are collected, checked, stored, and used after your 92e account is created.
LEGAL REFERENCE
92e Privacy Policy for Pakistan accounts
92e puts account data, device signals, wallet records and support chats under one Privacy Policy written for Pakistan access where local law permits. Open your account knowing how...
Account data scopeWallet record carePakistan access wordingRequest paths
How 92e handles your account data
Our Privacy Policy explains how we collect account data when you open or use a 92e account in supported regions of Pakistan. We keep the policy tied to real actions: registration, login, wallet funding, payout checks, live chat, and security alerts. We record only what we need to run the account, meet fraud controls, handle disputes, and respond to your privacy requests.
Payment references from JazzCash, Easypaisa, SadaPay, and Raast are used to match wallet activity with your account, not to create public profiles. Where local law permits access, we retain records for operational, security, and legal reasons, then remove or anonymise data when it no longer has a valid purpose under our retention schedule. You can contact us about access, correction, or removal
when the record is eligible.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Reach us about your privacy rights
Privacy requests need a clear route, so we keep account help separate from general lobby chat. Use the same email or phone linked to your 92e account where possible. That helps us confirm you before we share, correct, restrict, or remove eligible records.
Team online
Account email
Send a privacy request from the account email and include the phone number linked to your 92e wallet. We match the request before changing, exporting, or removing any eligible records.
Live chat handoff
If you start in live chat, ask for a privacy handoff rather than sharing full documents in the chat window. We will move the request to a safer account-check process.
Wallet query route
For JazzCash, Easypaisa, SadaPay, or Raast record questions, provide the transaction reference and date. We use those details only to locate the wallet entry tied to your account.
CHECKED SIGNALS
How we keep the policy accurate
A Privacy Policy is useful only when it matches the service behind it. We check the wording against account screens, wallet queues, chat tools, security logs, and retention...
Event mapping
We map each policy line to a real account event: registration, login, wallet update, identity check, support chat, or security...
Local rail checks
Our privacy contacts work with operations staff who see how JazzCash, Easypaisa, SadaPay, and Raast references arrive in the wallet...
Game record tags
We separate live table activity, sportsbook records, and slot session logs in our internal tagging. The Privacy Policy explains these...
Retention controls
Retention periods are linked to support disputes, security checks, and legal duties. When a record no longer has a valid...
Plain wording
We write for Pakistani English, so policy wording avoids imported legal slang where plain wording works. You should be able...
Access logging
Access controls limit who can view personal records, and admin actions are logged. This helps us answer privacy requests with...
POLICY MATCH
How our policy pages stay aligned
The Privacy Policy does not stand alone. We align it with account terms, cookie notices, wallet wording, and support scripts so the same data practice is not described in conflicting ways. This...
Wallet records
Wallet screens show transaction status, while this policy explains the data trail behind each entry. JazzCash, Easypaisa, SadaPay, and Raast references are kept with your account ledger.
Cookie wording
Cookie notices cover browser storage and device signals. The Privacy Policy connects those signals to login protection, session continuity, fraud checks, and preference storage across supported access points.
Support transcripts
Support pages explain how to contact us. This policy explains how chat transcripts, email threads, screenshots, and identity checks are stored when they become part of a privacy request.
Security alerts
Security messages may ask you to confirm access or update credentials. The Privacy Policy explains why we process device data, login times, and alert history during those checks.
Data requests
Request wording is kept consistent across help forms and account emails. Whether you ask for access, correction, or removal, we use the same identity-matching steps before acting.
Policy dates
Date stamps help you see when privacy wording changed. We connect updates to actual process changes, such as new wallet record fields, retention edits, or safer contact handling.
What the privacy page makes visible
We designed this page to make privacy choices easier to scan before you open an account. The layout separates data categories, rights, retention, security, and local...
Data categories
We group account details, wallet references, device signals, gameplay logs, and support records into clear categories. That helps you see which data belongs to which account action.
Rights panel
The rights section explains how you can ask to access, correct, or remove eligible records. It also sets out when legal or security reasons may require retention.
Retention labels
Retention wording is tied to purpose rather than vague storage claims. We explain why records may be held for account safety, dispute handling, wallet checks, or legal duties.
Security wording
Security sections explain login checks, device signals, admin access, and record controls. We describe these measures so you understand how privacy protection works inside the account flow.
Local context
Pakistan wording is included where it matters, especially around wallet references and supported regions. JazzCash, Easypaisa, SadaPay, and Raast records are described as account-matching data.
Update stamp
The policy keeps a visible update date so you know when wording changed. If a privacy process is adjusted, the page should reflect that change clearly.
Privacy Policy questions from Pakistan
We collect details needed to create and protect your account, such as contact data, login records, device signals, wallet references, support messages, and checks required for account safety.
JazzCash and Easypaisa references are used to match wallet activity with your 92e account, resolve funding or payout questions, and support fraud checks. They are not posted publicly.
Yes. Contact us from your account email and explain what needs correction. We may ask for identity matching before editing records, especially where wallet or security data is involved.
You can request removal of eligible records. Some data may need to be retained for legal, security, dispute, or wallet reconciliation reasons before it can be removed or anonymised.
Retention depends on the record type and purpose. Wallet entries, security logs, support transcripts, and account details may follow different timelines based on operational and legal needs.
Access is limited to authorised staff who need records for account support, wallet checks, security work, or privacy requests. Admin access is controlled and logged for accountability.