Terms page
Our Terms describe account rules and service use, while this page explains personal data handling. Where both mention verification, this page controls the privacy meaning of that process.
777zy keeps your account, device, contact, and transaction data within a clear privacy process built for Pakistan. Before you open an account, this Privacy Policy explains what we...
This Privacy Policy applies when you use 777zy.app, open your account, contact our support team, verify access, or use account features where local law permits. We collect only the data needed to create and protect your profile, process account activity, meet legal requests, manage security checks, and keep service records accurate. Data may include your name, phone number, email address, login signals,
device details, IP address, payment reference, session activity, and support messages. We do not sell your personal data. We share limited records with payment processors, verification partners, hosting providers, security tools, and support systems only when they need access for their role. We keep records for as long as needed for account, safety, legal, and dispute purposes, then delete or anonymise them
when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write this Privacy Policy from our operating view, not as outside commentary. Each privacy point is tied to an account process, such as sign-in, verification, support, payment reconciliation, security monitoring, or...
Our policy language follows the steps your account actually uses, from registration data to login checks. That keeps the privacy wording connected with real screens, not vague legal phrasing.
JazzCash, Easypaisa, SadaPay, and Raast references are handled as transaction records. We connect them with your account only for reconciliation, support, security checks, and required retention.
Internal access is limited by work role. Support can see account-help details, finance can check transaction references, and technical staff handle system logs needed for platform safety.
We record device, session, and network signals to detect unusual access. These logs support account protection, fraud checks, dispute handling, and safer recovery if your credentials are exposed.
When our privacy handling changes, we amend this page and keep the new wording visible here. Material updates may also be flagged through account or support messages.
Privacy requests are checked against account ownership, legal duties, and retention needs. We aim to answer clearly, even when a record cannot be deleted immediately.
This page focuses only on privacy: what data we collect, why we use it, who may receive it, and how you can contact us. Other legal pages may cover account terms, cookies...
Our Terms describe account rules and service use, while this page explains personal data handling. Where both mention verification, this page controls the privacy meaning of that process.
Cookie wording explains browser storage and tracking choices. This Privacy Policy connects those signals with wider account records, including logins, device checks, and security monitoring.
Promotion wording may require eligibility checks, but privacy handling still follows this page. We use only the account data needed to confirm eligibility and maintain accurate records.
Support replies should match this Privacy Policy when they discuss personal data. If a message sounds unclear, ask us to confirm the relevant section before sharing extra details.
Payment screens may show JazzCash, Easypaisa, SadaPay, or Raast references. This page explains how those references are stored, checked, and linked with your account.
Security alerts may mention devices, passwords, or login locations. This Privacy Policy explains why those signals are collected and how they help protect account access.
App or browser messages may ask for contact confirmation. This policy explains why contact data matters for account recovery, alerts, and privacy request verification.
We place privacy cues near the actions that create records, so you do not need to search for context after sharing data. The policy-side layout highlights consent prompts...