LEGAL REFERENCE

Privacy Policy for your f77 account

Our Privacy Policy explains what personal data we collect when you open an f77 account, verify payments, contact support, or use the lobby where local law permits. Read...

Account data usePakistan payment contextCookie choicesRequest channels
f77 Privacy Policy for your f77 account

How we handle your personal data

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

CONTACT ROUTES

Contact us about privacy requests

Privacy requests should reach the team that can verify your account safely. Use the contact route tied to your f77 profile, and include only the details needed to identify your account. We may ask for extra checks before sharing or changing records.

Team online

Email privacy desk

Send account data requests from the email linked to your f77 profile. We check ownership first, then route access, correction, deletion, and restriction queries to the right privacy handler.

Live chat handoff

If you start in chat, our support team can create a privacy ticket without exposing full records in the chat window. Sensitive replies move to your verified email.

Payment query path

For JazzCash, Easypaisa, SadaPay, NayaPay, or Raast record questions, share the reference number only after we confirm account ownership and explain why it is needed.

POLICY CHECKS

How we keep this policy current

We treat this Privacy Policy as an operating document, not a spare legal page. The policy is checked against account flows, cashier screens, support scripts, cookie tools, and...

Account flow checks

When the account form changes, we check whether new fields affect this policy. If data use changes, the wording is...

Security log scope

Login time, IP range, device type, and session signals help us detect unusual access. We keep these records for security...

Cashier record match

Payment references are compared with cashier activity so privacy wording reflects actual handling. We avoid asking for full wallet access...

Cookie wording control

Cookie labels are checked against the tools running on f77 pages. When a new measurement tag is added, the cookie...

Support script alignment

Support replies are matched with this policy so you receive consistent privacy explanations. Agents are told not to request documents...

Retention checks

We keep records only as long as needed for account service, payment disputes, security, and legal duties. Older records are...

PAGE ALIGNMENT

Same privacy rules across f77 pages

Your privacy rights do not change when you move between our account area, cashier, lobby, promotions page, or support channel. This section explains how related pages stay aligned with the same data...

01

Account page

The account page uses your profile data for login, verification, and contact preferences. Any privacy request raised there follows the same checks described in this policy.

02

Cashier page

The cashier page records transaction references, status updates, and wallet labels. Those records are handled under this policy, whether the rail is JazzCash, Easypaisa, SadaPay, NayaPay, or Raast.

03

Lobby page

The lobby may record session activity, device signals, and language choices. We use that data for access security, page stability, and account continuity, not for selling your profile.

04

Promotions page

When you check the promo board, we may record eligibility signals and account status. Those records help apply terms fairly and stay connected to your privacy choices.

05

Support page

Support messages can include screenshots, transaction references, or identity details. We keep them within privacy controls and restrict access to staff handling your case.

06

Cookie page

Cookie settings explain browser storage, measurement tools, and preference choices. They sit beside this policy so you can manage tracking without reading scattered wording.

07

Security page

Security notices describe access protection, password handling, and device checks. They connect with this policy because those controls rely on limited personal and technical data.

VISIBLE MARKERS

Policy cues you can see

We place privacy cues where they matter, not only at the bottom of the site. When you create an account, adjust cookies, contact support, or enter the cashier...

Date marker The policy page shows a clear date marker when wording...
Short field labels Account fields use plain labels so you know what is...
Cookie banner link The cookie banner links back to privacy wording and preference...
Request access point Privacy request routes appear near account and support areas. That...
Cashier explanations Cashier screens explain why transaction references may be needed. We...
Security prompts When extra verification appears, the prompt should explain the privacy...

Privacy questions before you join

We collect account details, contact data, login signals, device records, payment references, support messages, and verification files when needed. Each category supports account access, security, service delivery, or legal record duties.

No, we do not sell your personal data. We share limited records only with service providers that help with hosting, security, payment matching, analytics, support, or legal compliance.

We use JazzCash and Easypaisa references to match account activity, confirm transaction status, and resolve disputes. We ask for only the reference detail needed for that specific privacy or cashier query.

Yes. Contact us from your verified account email and explain what needs correction. We may ask for proof before changing records that affect identity, withdrawals, or account security.

Support chats are kept while needed for service follow-up, account disputes, security checks, and legal duties. When the reason ends, records are removed or reduced where practical.

Cookies help remember preferences, measure page performance, and protect sessions. You can adjust available browser storage choices through the cookie controls linked from this Privacy Policy.

Only staff and service providers with a work need can access relevant records. Access is limited by role, and sensitive requests are checked before any data is shared.