LEGAL REFERENCE

Privacy Policy for your 77rs account

77rs keeps this Privacy Policy close to your account flow: what we collect, why we need it, and how you can ask about it. Open your account in...

Pakistan data contextAccount privacyPayment data handlingSupport contact paths
Explore the Lobby Read FAQ
77rs Privacy Policy for your 77rs account

How we handle your personal data

This Privacy Policy explains how 77rs collects and uses data when you create an account, access the lobby, contact support, or use local payment rails where local law permits. We may process your name, phone number, login details, device signals, payment references, support messages, and verification material needed to keep your account record accurate. We use this data for account access, security

checks, payout handling, service messages, dispute handling, fraud prevention, and legal duties that apply to our operation. We do not sell your personal data. Where we work with payment processors, hosting partners, security tools, or support systems, they receive only the data needed for that task. You can contact us to ask about access, correction, deletion, or limits on how we use

your data, subject to account safety and record-keeping needs.

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

PRIVACY HELP

Ways to reach us about privacy

Privacy questions should reach the team that can trace your account record without asking for more data than needed. Keep your message focused on the account detail you want us to check. We may ask you to confirm access to your phone or email before we share or change personal data.

Team online

Account help desk

Use account support when you need a privacy copy, correction request, or help with a data question tied to your login. We will match your request with the account record before replying.

Payment privacy query

Ask through support if a JazzCash, Easypaisa, SadaPay, NayaPay, or Raast reference appears unclear. We check transaction references against your account without exposing extra payment details.

Security contact

Report account access concerns as soon as you notice them. We may pause sensitive changes, confirm device activity, and check recent sessions before acting on privacy-related account requests.

DATA CARE

How our policy stays practical

We write this policy for real account moments rather than legal display alone. Each privacy point connects to something you may do on 77rs, such as logging in...

Plain account language

We avoid hidden phrasing where possible and describe data by account action. If a term affects your login, payment reference...

Local payment context

Pakistan payment rails create reference numbers, sender names, and timing records. Our policy explains why those details may be checked...

Access checks

Before sharing account data, we verify that the request comes from you. This may include phone, email, login, device, or...

Limited sharing

Partners receive only what they need to complete a task, such as hosting, payment matching, security screening, or customer support...

Record retention

Some data must stay longer for payment disputes, fraud checks, and legal record duties. When those reasons end, we aim...

Policy checks

We revisit wording when account flows, support tools, or payment handling changes. If a privacy change matters, we present it...

Consistency across our legal pages

Your privacy rights connect with other legal pages, but this page stays focused on personal data. We keep the same account terms, contact paths, and payment references across...

Account terms link
Our account terms explain access rules, while this policy explains the personal data used to apply them. Both pages use the same account language to reduce confusion.
Payment wording
When payment records appear in legal pages, they refer to the same local rails and transaction references. This policy adds how those records connect to your personal data.
Security wording
Security sections across 77rs refer to login checks, device signals, and account confirmation. The Privacy Policy explains why those signals may be collected and retained.
Support wording
Support pages tell you how to contact us. This policy explains what support messages may contain, how we connect them to your account, and why replies may require checks.
Region wording
Where access depends on supported regions, we use consistent wording across legal pages. This policy adds how location, device, or access data may help apply those limits.
Retention wording
Other pages may mention records for disputes or account safety. Here we explain that retention depends on legal duties, payment issues, fraud checks, and support history.
Change wording
When we update a legal page, we aim to keep related privacy wording aligned. Material privacy changes are reflected here so your data position remains clear.
PAGE SIGNALS

What this policy page shows you

The privacy layout is built so you can scan the parts that affect your account before reading the full wording. We separate collection, use, sharing, security, retention, and...

Collection points This section shows where data enters 77rs, including account creation...
Use reasons We explain each main use in account terms: access, security...
Sharing boundaries The page identifies categories of partners that may process data...
Your choices You can ask about access, correction, deletion, or reduced use...
Security cues We describe safeguards in practical terms, including access controls, verification...
Update marker Policy updates should be easy to spot when data handling...

Privacy questions for your 77rs account

We may collect your name, phone number, email, login details, device signals, support messages, verification material, and payment references. The exact data depends on how you create, access, and manage your account.

Payment references help us match JazzCash, Easypaisa, SadaPay, NayaPay, and Raast activity to your account. They support reconciliation, payout tracing, dispute handling, and checks for unusual account activity.

No. We do not sell your personal data. We may share limited data with service partners only when needed for hosting, payment processing, support, security screening, or required record handling.

Yes. Contact support with the account detail that needs correction. We may verify your identity first, especially when the change affects login details, payment records, or account access.

Retention depends on the data type and the reason we keep it. Payment records, support history, fraud checks, and legal record needs may require longer storage than basic account preferences.

We use access controls, verification steps, session checks, restricted support permissions, and monitoring for unusual activity. No online system removes every risk, so we also ask you to keep login details private.