How 66ep Handles Your Data
66ep keeps privacy terms close to your account journey, from opening access in supported regions to using JazzCash, Easypaisa, SadaPay or Raast. Read how we collect, protect, use...
Privacy Position For Pakistan Accounts
This Privacy Policy explains how 66ep collects and handles data when you create an account, verify access, browse the lobby, contact support or use Pakistani payment rails where local law permits. We collect only what we need for account operation, security checks, service messages, transaction records, fraud prevention and legal duties that apply to supported regions. Your payment activity may create records
linked to JazzCash, Easypaisa, SadaPay or Raast, but we do not ask you to place sensitive wallet passwords inside our chat. We keep account records behind access controls, limit staff permissions, and use device checks to spot unusual sessions. If this policy changes, we update the page so you can see the current handling approach before continuing with your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Routes For Privacy Requests
You can reach us about Privacy Policy matters without explaining your request in public spaces. We may ask for account identifiers so we can confirm the request belongs to you, then we route it to the team that handles access, correction or deletion questions.
Live chat privacy queue
Use live chat when you need a quick privacy check tied to account access, login alerts or contact changes. Our agent may move the case to a secure ticket if documents or deeper account tracing are needed.
Email privacy request
Email suits requests that need a written record, such as correcting profile details or asking how long a transaction file is kept. Include your account phone or email, but never send wallet passwords.
Account centre message
The account centre lets you send privacy questions while already signed in, helping us confirm ownership faster. We use that route for status updates when your request involves security logs or payment references.
How We Keep The Policy Reliable
Our privacy wording is based on the way 66ep actually runs account access, local payment checks, device sessions and support records. We avoid vague promises, name the data touchpoints that matter, and...
Account flow mapping
We connect the policy to real account steps, including registration fields, login checks, wallet references and support tickets. That keeps each privacy promise tied to a process we can trace inside our own systems.
Local payment handling
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records, not chat topics. We record confirmation details needed for account service while discouraging you from sharing wallet secrets with support.
Access controls
Staff access to personal records is limited by role, case need and system logs. When a privacy request arrives, we check account ownership before changing contact details or releasing stored account data.
Cookie clarity
Cookies and similar tools help keep sessions stable, remember language choices and detect risky sign-ins. The policy separates necessary account cookies from measurement tools so your choices are easier to understand.
Change discipline
When our data handling changes, we update the Privacy Policy rather than leaving old wording in place. The page is written so you can spot collection points, purposes and contact routes quickly.
Support records
Chat and email records help us answer disputes, track privacy requests and prevent repeated account issues. We keep those records only for service, security and legal needs connected to your account.
How This Policy Fits Other Pages
This page works beside our account terms, cookie page and security wording. Each page has a different job, but they use the same account reality: your identity checks...
| Account terms | The account terms explain what you agree to when using 66ep. This Privacy Policy explains which personal data supports that agreement, such as contact records, verification steps and account security checks. |
|---|---|
| Cookie page | The cookie page focuses on browser storage and session tools. This policy places those tools in context by explaining why they matter for account access, safety checks and site performance. |
| Security wording | Security wording covers protections around login, device signals and account alerts. The Privacy Policy explains how related security data is collected, limited and used when suspicious account activity appears. |
| Support terms | Support terms describe how we respond to messages. This policy explains how those messages become service records, how we confirm account ownership, and why some conversations must move to secure tickets. |
| Transaction rules | Transaction rules describe account balance processes in supported regions. This policy explains the data side, including reference numbers, wallet names, verification files and records needed for audit or dispute handling. |
| Promotions page | Promotions wording may require account checks before rewards are shown. This Privacy Policy explains how eligibility data, communication choices and account status can be used without changing core privacy rights. |
| App access page | App access wording explains how you reach 66ep on mobile. This policy explains related device data, session storage and notification choices used to keep account access stable. |
Privacy Elements You Can Spot
We designed this policy page so you can scan the privacy essentials before opening or continuing an account. The visible elements point to what is collected...
Purpose blocks
Each purpose block explains why a category of data exists, such as account setup, security checks or support follow-up. This helps you link a record to a practical privacy reason.
Local context chips
Short chips naming JazzCash, Easypaisa, SadaPay and Raast show where local transaction records may appear. They do not ask for wallet passwords or private app access.
Rights panel
The rights panel points you toward access, correction and deletion requests where they apply. We explain that identity checks may be needed before action is taken on personal account records.
Retention markers
Retention markers explain why some records may remain after a request, especially security logs, transaction references or dispute files. The aim is to be clear about legal and service needs.
Contact strip
The contact strip keeps privacy routes visible near the policy text. You can choose chat, email or the account centre depending on urgency and the kind of record involved.
Update label
The update label shows when the page was last changed. If wording shifts, you can revisit the policy and compare how collection, use or sharing details are described.