Privacy Policy for your 777tez account
777tez keeps your privacy choices, account data, device signals, and Pakistan payment records in one readable policy so you know what we collect before you open an account...
How our policy works
Our Privacy Policy covers the data we collect when you create or access a 777tez account, verify contact details, use supported Pakistan payment rails, ask support for help, or move through protected areas of the site. We collect only what we need to run account checks, keep session records, match JazzCash, Easypaisa, SadaPay, and Raast activity, answer privacy requests, and meet record-keeping
duties where local law permits. We do not sell your personal data. Some service providers help with hosting, security screening, analytics, payment matching, and support tooling, and we require them to handle your data only for the task assigned. You can ask us about access, correction, deletion, or processing limits through the privacy contact paths below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Why the policy stays clear
We write this policy from the systems we operate, not from generic templates. Each change is checked against account creation, login, payment matching, support handling, and security logging. When a tool changes...
Plain wording
We avoid vague privacy labels and name the account actions involved. That means login data, payment references, support messages, and device signals appear as separate privacy categories.
Pakistan context
The policy names JazzCash, Easypaisa, SadaPay, and Raast because those rails create different references. Clear naming helps you recognise which record belongs to your transaction.
Access controls
Only assigned staff can open privacy cases or payment-linked account records. Access is logged internally so data handling can be traced back to a business need.
Retention checks
We keep records for security, dispute handling, and legal duties, then reduce or remove data when it is no longer required for those purposes.
Session records
Device and IP signals help us protect account access, flag unusual logins, and keep privacy requests tied to the correct profile without exposing extra account content.
Change tracking
When the policy changes, we adjust the date and wording on this page. Material changes are written in direct language so you can compare what shifted.
Same privacy language across pages
Your privacy rights should not change just because you entered from a login screen, a promo board, or a cashier view. We keep related policy pages aligned so...
| Login pages | Login screens collect identifiers, passwords, device checks, and session signals. The Privacy Policy explains why those records exist and how they protect your account access. |
|---|---|
| Cookie notice | Cookie language links back to this policy for device data, preference storage, and security checks. You can read both pages together for a complete privacy view. |
| Terms links | Terms may describe account rules, but privacy handling remains here. When rules mention verification, this policy explains the data used for that check. |
| Promo areas | Promo screens may record eligibility, clicks, or account tags. This policy explains those records as account activity, not as a separate data sale. |
| Withdrawal records | Payout checks create references, timestamps, and identity links. We use those records to verify the request and answer privacy questions about transaction history. |
| Support scripts | Support replies follow privacy wording from this page. Agents should ask only for data needed to identify your account and resolve the stated privacy request. |
| Regional wording | Access may vary by supported regions where local law permits. Privacy wording stays focused on data handling, even when availability language changes elsewhere. |
Privacy layout you can scan
We designed this policy page so privacy choices are easy to find during account setup or later account checks. The page separates collection, use, sharing, retention, security, and...