Terms alignment
The Terms explain account rules, while this Privacy Policy explains data use. We keep both aligned so identity checks, access controls and records handling follow the same account facts.
bx77 keeps your account data, device signals and Pakistan payment records described in one clear Privacy Policy. Read it before you open an account so you know what...
This Privacy Policy sets out how bx77 collects, uses, stores and shares data linked to your account, device, session activity and payment records in supported regions of Pakistan, where local law permits. We collect only the data needed to create and protect your account, confirm transactions, manage support requests, check unusual access and maintain the service. Payment details linked to JazzCash, Easypaisa,
SadaPay and Raast may be recorded as transaction references, status updates and verification records; we do not ask you to share wallet passwords. We may keep records for legal, security and dispute-handling needs, then remove or reduce them when they are no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write this policy from the way bx77 actually handles accounts, payments and support cases. Our checks focus on plain wording, Pakistani payment context and practical security steps...
A named internal function owns this Privacy Policy and checks it against account, payment and support workflows. That prevents wording...
When we adjust data handling, the policy text is checked before publication. We keep internal change records so support can...
Our policy names JazzCash, Easypaisa, SadaPay and Raast because those rails create different reference fields. We map those fields carefully...
Account access, password reset and device checks are reflected in the privacy wording. If we use a device signal to...
Our support team receives privacy handling steps for account requests, wallet references and identity checks. This helps you get consistent...
We check whether records still serve legal, security or dispute needs. When a record is no longer required, we aim...
Our Privacy Policy works with our other legal pages, but it has its own job: explaining data handling. We keep wording aligned so your account rights, payment records and support steps do...
The Terms explain account rules, while this Privacy Policy explains data use. We keep both aligned so identity checks, access controls and records handling follow the same account facts.
Cookie text and privacy text are checked together because device and browser signals often overlap. This policy explains why those signals may be used for security, session continuity and fraud checks.
Payment pages may describe transaction flow, while this policy explains the records created by that flow. JazzCash, Easypaisa, SadaPay and Raast references are treated as account-linked data.
Support wording must match this policy when your request involves access, correction or deletion. That keeps chat and email replies consistent with the privacy rights described here.
Security text explains protection steps; this policy explains the data behind them. Login alerts, device signals and unusual activity checks are covered without asking for more data than needed.
Where local law permits, access wording is kept consistent across legal pages. This policy then explains the data records created when you open, verify and use your account.
Legal pages are checked as a set before changes go live. This reduces mixed messages about account records, privacy requests and how long bx77 may keep required data.
This page is built to make privacy details easier to scan before you open your account. Headings separate collection, use, sharing, storage and contact points, while...
Each section uses direct labels so you can find account data, payment records and contact choices without digging through legal wording. The layout is meant for quick checks on mobile screens.
The chip row names the Pakistan rails linked to transaction records. It shows where JazzCash, Easypaisa, SadaPay and Raast data may appear inside the policy without turning this page into a payment page.
Cards separate privacy actions such as access, correction, deletion and record questions. This keeps support steps clear, especially when you need to send a request from the same phone used for bx77.
The page keeps returning to your choices: asking what we hold, correcting wrong account details and raising concerns. We avoid broad platform talk so the privacy message stays focused.
Lock, shield and receipt icons mark sensitive areas like login checks and transaction records. These cues help you see which parts of the policy relate to account protection.
Contact details sit near the practical privacy steps rather than at the end only. That helps you act quickly when your question involves data access, wallet references or identity checks.