Privacy Policy for Your 66ez Account
66ez keeps your privacy policy clear from the first account step: we explain what we collect, why we need it, and how it supports secure access in Pakistan...
How We Handle Your Data
This Privacy Policy applies when you use 66ez in supported regions, contact our support desk, update your account, or send a transaction reference for checking. We collect only the data needed to operate your account flow, confirm access, reduce misuse, respond to queries, and keep records required for lawful service handling. That may include your name, mobile number, login activity, device signals,
wallet reference numbers, support chat content and security actions linked to your account. We do not sell your personal data. We share limited details only with service providers that help process account security, payment checks, hosting, analytics or customer support, and we require those providers to handle data for the stated purpose.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Work Accountable
Our privacy work is managed through internal checks rather than vague promises. We map each data field to an account purpose, limit staff access by role, and keep support replies tied to...
Purpose mapping
Every main data field in your 66ez account is linked to a service purpose, such as login security, transaction matching, support handling or legal record keeping, so collection stays connected to actual account needs.
Role based access
Support, payment checking and security staff do not need the same level of data access. We separate permissions so a person sees only the records needed to handle the task assigned.
Local payment context
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records, not public profile details. We use them to match your request, handle queries and maintain required service records.
Change checks
When we adjust account screens, support forms or security tools, we check whether the Privacy Policy still describes the data flow accurately before the updated feature reaches your account area.
Retention controls
We keep account and transaction records for as long as needed for service, dispute handling, security or legal reasons. When a record is no longer needed, we remove or reduce it.
Clear request handling
Privacy requests are handled through named contact paths, with ownership checks before personal data is discussed. This keeps your account details from being released through casual or unverifiable messages.
Consistency Across Our Legal Pages
The Privacy Policy works beside our other account terms, but it has its own role. This page explains data collection, use, sharing, storage and your contact choices. Related...
| Terms page alignment | Our terms describe account rules, while this policy explains the personal data behind those rules. When both pages mention verification, this Privacy Policy controls the data handling explanation. |
|---|---|
| Cookie page alignment | Cookie settings may describe browser signals and analytics tools in more detail. This policy connects those signals to wider privacy purposes, including security, service improvement and account session handling. |
| Promotions page alignment | If a promotion needs account eligibility checks, the promotion text may mention the condition. This policy explains how related account records are handled and who may access them internally. |
| Support page alignment | Our support page gives contact routes, while this policy explains what happens to messages, screenshots or references you send. We keep support records only for service and dispute handling needs. |
| Security page alignment | Security notices may discuss access protection, device checks or suspicious activity. This policy explains how those security records are collected, stored and used for account protection decisions. |
| Payment record alignment | Wallet and bank rail references appear in account flows for matching and support. This policy explains their privacy treatment, including limited access and use for transaction checks. |
| Regional access wording | Where another page mentions availability in supported regions, this policy explains that privacy handling still applies to your account data when you interact with 66ez from Pakistan. |
Policy Layout Inside Your Account
We place privacy wording where it helps you make account decisions, not only at the bottom of the site. You may see short privacy reminders near...
Privacy link placement
The Privacy Policy link appears in legal areas and account touchpoints where personal data is requested. This helps you check the reason for collection before you send details.
Short field explanations
Where a form asks for a mobile number, receipt reference or account detail, we aim to keep the field purpose clear so you understand how that entry supports your request.
Support form reminders
Support forms may remind you not to share wallet PINs, unrelated identity files or another person’s data. That keeps privacy requests focused and safer for your account.
Profile edit context
When you update account details, the surrounding copy explains that changes may be logged for security and support reasons, especially when edits affect access or transaction checking.
Session messages
Login and session messages may refer to device or location checks. This policy explains that those signals help protect access and investigate unusual account activity.
Record request cues
When you ask for account data or correction help, the interface may ask for ownership confirmation first. That step protects privacy before any personal record is discussed.