LEGAL REFERENCE

Privacy Policy for Your es7 Account

es7 gives you a clear Privacy Policy before you open your account, so you know what data we collect, why we need it, and how your choices are...

Account data explainedPakistan payment contextSecurity checks coveredContact paths included
Browse Lobby Read FAQ
es7 Privacy Policy for Your es7 Account

How We Handle Your Privacy

Our Privacy Policy explains how es7 collects and uses the data needed to create your account, keep access secure, process requests, and maintain records linked to your activity. In supported regions, we may receive payment references from services such as JazzCash, Easypaisa, SadaPay and Raast, but we use those details only to match account transactions, manage risk checks, and answer your requests.

We do not ask for your wallet password, PIN, or banking login. Some data may be retained when required for fraud prevention, account security, dispute handling, or legal record duties. Where local law permits, you can ask us to confirm, correct, or remove certain personal data, subject to checks that protect your account and our service.

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

CONTACT PATHS

Contact Us About Privacy Matters

If you have a Privacy Policy question, start with the contact route connected to your es7 account. Clear requests help us respond faster, especially when you ask about access records, payment references, correction, or removal. We check identity first, because privacy replies should reach only you.

Team online

Account email

Send us the email linked to your es7 account, describe the privacy request, and avoid sharing passwords. We reply with the next step after matching the account details you provide.

Live chat handoff

Chat can collect the privacy topic and route it to the right team. For account data requests, we may move the conversation to email so written identity checks are kept clear.

Security flag

If your privacy concern involves unknown access, wallet references, or changed account details, tell us immediately. We can place extra checks on the account while the privacy request is assessed.

POLICY CHECKS

How We Keep This Policy Accurate

We write this Privacy Policy from the way es7 actually operates: account creation, login protection, payment reference matching, support handling, and record retention. When we change a data...

Account flow mapping

We map privacy wording to the fields you see during account setup, login recovery, and profile edits, so the policy...

Payment reference checks

JazzCash, Easypaisa, SadaPay and Raast references are treated as account matching records. The policy explains this context without asking for...

Access security

Our policy covers login data, device signals, session checks, and alerts used to protect your account. These records help us...

Support records

When you contact us, we keep request history so your privacy matter can be tracked. We limit internal access to...

Retention control

We keep different records for different periods, depending on account security, dispute handling, and legal duties. The policy explains why...

Regional wording

Pakistan access is described with supported regions and where local law permits wording. That keeps the policy practical without making...

Policy Consistency Across es7 Pages

Your privacy expectations should not change from one legal page to another. We keep this Privacy Policy aligned with our related account, cookie, security, and contact wording, so...

Account terms
Account wording and privacy wording use the same labels for profile data, login records, and verification steps, so you are not asked to decode different names for the same record.
Cookie page
Cookie wording explains browser storage and session tools, while this Privacy Policy explains how those signals connect to account security, preference handling, and service measurement.
Security page
Security wording describes protection steps, and this page explains the data used in those steps, including login signals, access alerts, and identity checks for privacy requests.
Contact page
Contact wording tells you where to reach us, while this policy explains what happens to your message, reply history, and identity details after you submit a request.
Promotion wording
If you check any account offer, this Privacy Policy still controls how related data is handled, including eligibility records, notification choices, and support messages about your account.
Payment context
Payment pages may show JazzCash, Easypaisa, SadaPay and Raast steps. This policy explains the privacy role of references created during those account matching checks.
Update labels
When legal wording changes, page labels and dates help you identify the current text. We keep those markers consistent so you know which policy applies.
PRIVACY MARKERS

Privacy Layout You Can Read Quickly

This page is arranged to make privacy choices easier to find before you join or continue using es7. We separate account data, security checks, contact routes, and regional...

Plain section headings Each section names the privacy topic directly, from account data...
Short privacy badges The hero badges highlight the core areas covered by the...
Local wording Pakistan references are included where they affect privacy handling, especially...
Choice signals Where choices are available, the policy points to correction, access...
Contact placement Privacy contact routes appear near the start, so you do...
Date awareness Policy dates and update labels help you confirm you are...

Privacy Policy Questions Before You Join

We collect the details needed to create and protect your account, such as contact data, login records, device signals, and support messages. The Privacy Policy explains why each type is used.

We use JazzCash and Easypaisa references to match account transactions, check request history, and handle disputes. We do not need your wallet PIN, password, or private banking login.

Yes, you can ask us to correct account data where local law permits. We may request identity checks first, especially if the change affects access, payment references, or security alerts.

Yes. Login times, device signals, and session records are covered because they help protect your account and support privacy requests. We use them to detect unusual access patterns.

Retention depends on the record type and the reason it is kept. Some data can be changed or removed sooner, while security, dispute, or legal records may need longer retention.

Only teams that need to handle your request, protect the account, or meet record duties should access it. We keep request history so replies can be tracked clearly.

Do not send wallet PINs, passwords, full banking login details, or screenshots showing private credentials. Share only the account details needed for us to identify and answer your request.