Privacy Policy for your up777 account
Your up777 Privacy Policy explains what we collect, why we collect it, and how we use it when you open an account, verify access, contact us, or request...
How we handle account data
We collect only the data needed to run your up777 account, keep access secure, process requests, and meet checks that apply where local law permits. This can include your account details, contact channel, device signals, IP address, login timestamps, verification files when requested, and transaction references linked to JazzCash, Easypaisa, SadaPay, or Raast. We use this data to confirm that you can
access the service, protect your account from misuse, resolve support questions, and keep records required for operational or legal reasons. We do not sell your personal data. Access to privacy records is limited to staff and service partners who need it for account, security, payment, or support tasks. We retain data only as long as needed for those purposes, then remove or
anonymise it when practical.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to ask about privacy
Privacy questions should reach the team that can read account records, not a general mailbox. When you contact us, include your account ID, the email or phone number you used, and the privacy request you want us to check. We may ask for identity confirmation before sharing or changing data, because policy access must protect your account too.
Live chat privacy ticket
Use live chat when you want a quick privacy ticket created from inside your account. We log the request, mask sensitive fields, and move detailed data questions to the privacy queue.
Email privacy request
Email works for access, correction, or deletion questions that need a written trail. Send your account ID, the request type, and any relevant payment reference without sharing passwords.
Account security check
If your privacy request involves login activity, we compare device records and recent sessions before replying. This helps us avoid releasing personal data to anyone outside your account.
How we keep policy wording current
We treat the Privacy Policy as a live account document, not background copy. Our team checks it when we adjust account verification, add a support route, change storage practice, or update how...
Account data mapping
We map each account field to a clear purpose, such as login access, identity checks, security alerts, or support handling. Fields without a current purpose are flagged for removal.
Local rail references
JazzCash, Easypaisa, SadaPay, and Raast references are treated as transaction records, not public profile data. We use them for reconciliation, payout checks, and dispute handling.
Access controls
Staff access to privacy records is role based. Support teams see what they need for your request, while sensitive verification material stays behind stricter permission checks.
Retention checks
We check retention periods against operational need, security needs, and legal record duties. When records are no longer needed, we delete or anonymise them where practical.
Plain language edits
Policy wording is checked for plain Pakistani English before publication. If a clause affects your account data, we explain the action, the reason, and the contact path.
Partner discipline
Where service partners help with hosting, analytics, security, or payment processing, we restrict their role to the agreed task and require handling that matches this Privacy Policy.
Aligned privacy pages across up777
Your privacy rights should not change depending on which legal page you opened first. We align this page with our account rules, cookie wording, and support scripts, so...
| Terms page match | Our Terms page explains account use, while this Privacy Policy explains data use. When both mention verification, this page controls how documents and checks are handled. |
|---|---|
| Cookie wording link | Cookie wording deals with browser storage and device signals. This Privacy Policy connects those signals to security, session continuity, fraud checks, and preference handling. |
| Support script consistency | Support replies use the same privacy categories shown here: account details, verification material, device logs, contact records, and payment references. That keeps answers predictable. |
| Payment record alignment | Transaction references from JazzCash, Easypaisa, SadaPay, and Raast are described consistently across account help and privacy wording, with no public display of sensitive details. |
| Security page link | Security wording explains how we protect access. This page explains which records support those checks, including login time, IP pattern, device type, and account actions. |
| Regional wording | Access language refers to supported regions and where local law permits. We keep that phrase consistent so privacy wording does not imply wider availability. |
| Update rhythm | When account flows change, we check related legal pages together. If privacy impact changes, this page is updated before the new wording is treated as current. |
Privacy cues built into the page
This page is laid out so you can scan the Privacy Policy without hunting through broad brand copy. Each block points to a real data decision: collection, purpose...