LEGAL REFERENCE

Privacy Policy for Pakistan accounts

Our Privacy Policy explains what on777 app collects when you open an account, verify access, use support, or send payment records through Pakistan channels where local law permits...

Account data scopeJazzCash record handlingEasypaisa request trailSadaPay and Raast context
Explore the Lobby Read FAQ
on777 app Privacy Policy for Pakistan accounts

How our privacy policy applies

This Privacy Policy applies to on777 app account activity in supported regions of Pakistan, including sign-in checks, wallet record matching, customer care chats, device protection, and account verification. We collect only the details needed to run your account flow, confirm payments, answer your privacy requests, and reduce misuse of accounts. Some records may be kept because banking, dispute, security, or tax rules

require a traceable history. We do not sell your personal data. When we use service partners for hosting, analytics, messaging, or payment checks, we require them to handle data for the stated purpose only. If local law permits access in your area, you can open your account with a clearer view of how privacy rights work.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

Contact us about privacy

Privacy requests need a clear route, not a generic inbox loop. Use the contact path that matches your concern and include your...

Privacy inbox Send data access, correction, or removal requests through...
Live support handoff If your privacy concern starts during a chat...
Payment record query For JazzCash, Easypaisa, SadaPay, or Raast mismatches, share...
CHECKED WORDING

How we keep wording current

A Privacy Policy only helps if it matches how the service actually works. We check this page against account forms, payment record screens, support scripts, and security tools...

Account form match

We compare the policy with the fields shown when you join, including mobile number, password setup, and verification details. If...

Payment trace mapping

JazzCash, Easypaisa, SadaPay, and Raast records create transaction references. The policy explains why those references are stored and how they...

Security signal checks

Device type, IP range, session time, and failed access attempts may be logged to protect your account. We describe those...

Support transcript controls

Support chats can contain payment references or identity details. We train support to keep privacy requests separate from casual service...

Retention reason checks

Some records are kept longer for payment disputes, misuse prevention, or legal duties. We link retention to a reason, so...

Partner access limits

Hosting, messaging, and analytics partners may process limited data for us. We keep their access tied to service tasks and...

Privacy policy matches our pages

This policy sits beside our account terms, cookie wording, and support rules. Each page has a different job, yet the data language must stay aligned. We avoid scattered...

Account terms alignment
The account terms explain conduct and access rules, while this policy explains data handling. We keep both aligned so verification, suspension, and correction requests use the same account identifiers.
Cookie wording alignment
Cookie wording covers browser storage and measurement tools. This policy connects that activity to wider privacy rights, including how session data helps secure sign-ins and reduce repeated verification prompts.
Support rules alignment
Support rules explain how to contact us, while this policy explains what happens to the records you share. We align both so chat transcripts and privacy requests are not confused.
Payment page alignment
Payment screens show JazzCash, Easypaisa, SadaPay, and Raast references. This policy explains why those references matter for account matching, dispute checks, and verified responses to privacy questions.
Security page alignment
Security wording covers account protection tools. This policy explains the personal data side, including device logs, suspicious access markers, and when we may need to confirm your identity.
Promo board alignment
Promo areas may display account-specific eligibility data. This policy explains how those account signals are used without turning privacy wording into a promotion or broad platform pitch.
Change notice alignment
When privacy wording changes, related pages are checked too. That keeps account, cookie, payment, and support wording moving together instead of leaving old text in active pages.
PAGE MARKERS

Visible privacy layout markers

We designed this page so privacy details are easy to spot before you open an account. The layout separates data collection, use, sharing, retention, and your request routes...

Plain section labels Each section uses direct labels rather than legal padding. You...
Local context chips Pakistan payment names appear as context chips because privacy questions...
Short request paths Contact routes are shown near the policy text so you...
Data category grouping Account, device, payment, support, and security records are grouped separately...
Retention cues Retention wording is placed near the reasons for keeping records...
Rights-focused wording Request language stays close to practical actions: access, correction, removal...

Privacy questions before you join

We collect details needed to create and protect your account, such as mobile number, login credentials, verification records, device signals, and support messages. Extra data is requested only when account checks require it.

Payment references help us match your account activity with a transaction trail, resolve disputes, and answer privacy requests correctly. We store the reference, timing, and related account record rather than unrelated wallet content.

Yes. Send a privacy request through our contact route and complete any identity check we need. We will tell you which record categories we hold and what can be shared under applicable rules.

You can ask us to correct inaccurate account details. Some records, such as completed payment references or security logs, may need to remain unchanged because they support audits, disputes, or account protection.

We share limited data with service partners only when they help run hosting, support, security, messaging, analytics, or payment matching. We do not sell your personal data to outside advertisers or unrelated parties.

Retention depends on the record type and reason. Support chats, payment references, verification checks, and security logs may have different timelines because disputes, legal duties, and account protection needs are different.

Use the privacy contact path and include only the details needed to identify your account or transaction. For JazzCash, Easypaisa, SadaPay, or Raast issues, a reference number helps us locate the record.