How e666 handles your data
Our Privacy Policy tells you exactly what account, device, KYC, cookie and transaction data we collect when you use e666 in supported regions. Open your account with clearer...
Our privacy posture for Pakistan
This Privacy Policy explains how e666 handles personal data linked to your account where local law permits access to our services. We collect only the data needed to create your account, verify identity, secure logins, process transactions, maintain records, and answer privacy requests. That may include your name, mobile number, CNIC-related verification details, device signals, IP address, session logs, cookie choices, and
transaction references from supported Pakistani rails. We do not sell your personal data. We share limited records only with service partners needed for KYC checks, fraud screening, payment processing, hosting, analytics, customer care, or legal duties. When you use JazzCash, Easypaisa, SadaPay, Raast, or NayaPay, the privacy handling also depends on the rail you select and the records they require.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy current
A privacy page only helps when it matches the way the service actually works. We check this policy against account creation, login security, cookie behaviour, KYC flows, transaction...
Operational ownership
Our product, support, and compliance teams check privacy wording against the live account flow. This keeps descriptions of KYC, login...
Local payment context
We name JazzCash, Easypaisa, SadaPay, Raast, and NayaPay where those rails create records. That helps you understand which transaction references...
Security controls
We protect account data through access controls, encrypted connections, device checks, and staff permission levels. Internal access is limited to...
Retention mapping
We map each record type to a purpose before keeping it. Some logs are short lived, while KYC and transaction...
Cookie choice handling
Cookie settings are separated from account records where possible. You can change browser settings, and we explain how essential cookies...
Change tracking
When privacy wording changes, we update the date on the page and adjust affected sections. Material changes may also be...
How this policy stays consistent
Our privacy wording connects with nearby legal pages without repeating them. The Privacy Policy explains data collection, use, sharing, storage, security, and your choices. Other pages may cover...
| Terms page | Terms explain account rules and service use, while this page explains data handling. If a term requires verification, this policy describes what personal records support that check. |
|---|---|
| Cookie page | Cookie wording focuses on browser storage, identifiers, and preference tools. This policy links those signals to privacy purposes, such as security, analytics, session continuity, and consent choices. |
| KYC wording | Identity checks need careful privacy treatment. This policy explains why verification records are requested, how access is limited, and why some records may remain after account closure. |
| Security wording | Security pages describe account protection, while this policy explains the personal data used for that protection. Device signals, IP logs, and login events are treated as privacy records. |
| Support wording | Support pages explain contact paths; this policy explains how request records are handled. Chat transcripts, email messages, and case IDs may be retained to resolve privacy matters. |
| Transaction wording | Transaction pages describe account balance movement, while this policy explains the related personal records. Rail references, timestamps, and verification outcomes are kept for audit and dispute handling. |
| Update wording | All legal pages should show clear change dates. For privacy, date changes matter because they tell you when data handling language was last checked. |
Visible cues on this privacy page
We designed this page so you can find privacy details without reading every line at once. Section labels separate data collection, sharing, storage, security, and choices. Short chips...