How 7yyy Handles Your Privacy
7yyy keeps one Privacy Policy for your account data, device signals and payment references, so you can open your account knowing what we collect and why. We built...
Our Privacy Posture In Pakistan
Our Privacy Policy explains how 7yyy collects, uses, stores and protects details linked to your account, device and activity where access is available in supported regions. We collect only what is needed to run your account flow, verify payments, protect logins, settle withdrawals and answer privacy requests. Some records may include mobile numbers, receipt references, device type, IP address, login time and
security flags. We use this data to keep your account accurate, detect misuse, meet legal duties where local law permits, and improve policy clarity. We do not sell your personal data, and we keep retention periods tied to account, security and transaction needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Accurate
We maintain this Privacy Policy as an operating document, not a generic legal page. Our account, payments and security teams check the wording against the data we actually handle inside 7yyy. When...
Data mapping
We map account fields, login records, payment references and contact messages to the matching privacy purpose. That keeps each policy statement tied to a real 7yyy process.
Local payment context
Our policy names JazzCash, Easypaisa, SadaPay and Raast because those records can appear in account checks. We explain them as references, not public profile details.
Security alignment
Device signals, IP records and login timing are described alongside the security checks they support. This helps you understand why some technical data is retained.
Plain wording
We write the policy in Pakistani English so you can read the account, payment and contact sections without legal jargon hiding the meaning of a privacy choice.
Access limits
Internal access to personal data is limited by role. A payment query, login issue or privacy request does not allow every team member to view every record.
Change control
When we adjust a privacy process, we update the page date and the matching section. Material changes are written clearly so you can check what shifted.
Consistent Privacy Across 7yyy Pages
Our Privacy Policy connects with other legal pages, but it keeps its own scope. This page is about personal data, account records, device signals and payment references. When...
| Account terms | Account terms may explain access rules, while this Privacy Policy explains the personal data behind account creation, login checks, profile edits and account closure requests. |
|---|---|
| Cookie wording | Cookie text deals with browser storage and site measurement. This Privacy Policy explains how those signals can connect with your account and device security checks. |
| Payments page | Payment pages describe transaction steps. This policy explains how wallet references, receipt codes, verification outcomes and withdrawal checks are stored and used by 7yyy. |
| Security messages | Security alerts tell you what action may be needed. The Privacy Policy explains why login signals, device flags and risk checks are collected first. |
| Promo notices | Promotional screens may use account activity to show eligible offers. This policy explains what data supports that matching and how you can ask about it. |
| Support records | Support pages explain how to contact us. This policy covers how chat logs, email messages and identity checks are retained after your question is answered. |
| Regional access | Where access depends on supported regions, our legal pages use matching wording. This Privacy Policy explains the data handling tied to those access checks. |
Visible Cues On This Privacy Page
We designed this policy page so the privacy points you need are easy to spot. The layout separates account data, security use, local payment references, contact...
Clear section labels
Each section label tells you which privacy purpose is being explained, such as account records, security checks or contact requests, so you can move straight to the relevant part.
Short policy badges
The badges near the hero summarise the main privacy themes without replacing the full text. They help you see data use themes before reading deeper.
Local wording
Pakistan-specific wording appears where local payment references or supported regions matter. We avoid vague global language when your privacy question needs local context.
Request prompts
Contact prompts show what to include and what not to share. That protects your account while giving us enough detail to handle privacy requests properly.
Retention clarity
Retention statements explain why some account, payment and security records may remain after a transaction or contact message, especially where legal or safety duties apply.
No hidden sale claim
The page states that we do not sell personal data. If a data-sharing purpose exists, the policy connects it to account operation, security or compliance needs.