Privacy Policy
This page explains the categories of personal data we collect, the reasons we use them and the choices you can raise with us about access, correction or removal.
LEGAL REFERENCE
Privacy Policy for your bit99 account
Your bit99 Privacy Policy explains what account data we collect, why we use it, and how we protect records linked to your activity in supported regions. Open your...
Account data scopePakistan payment recordsCookie choicesSupport request path
How we handle your personal data
This Privacy Policy applies when you access bit99, create or manage an account, contact our team, or use pages available where local law permits. We collect only the data needed to run account access, verify transactions, answer privacy requests, maintain security controls and keep required records. Payment-related data may include receipt references, wallet names, transaction timing and status updates from Pakistan rails,
while sensitive wallet passwords remain outside our systems. We also use device and session signals to protect your account, investigate unusual access and keep the policy record accurate when you ask us to correct or remove eligible data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CONTROLS
Checks behind this Privacy Policy
We keep this policy tied to how bit99 actually works, not to vague legal wording. Our internal checks look at account forms, login systems, support tools, cookie use...
Account form mapping
We match each account field to a stated purpose, such as login access, contact support or payment verification. Optional fields...
Session protection checks
Login time, device type and security events help us spot account access that does not fit your normal pattern. These...
Payment data separation
Wallet references from JazzCash, Easypaisa, SadaPay and Raast are stored as transaction records, not as full wallet access details. This...
Support access levels
Support staff see the account fields needed to solve your privacy request. Deeper records need extra internal permission, so routine...
Cookie purpose labels
Cookies and similar tools are grouped by purpose, including login continuity, fraud prevention and page measurement. Where choices are available...
Retention checks
We keep records for account operation, legal duties, dispute handling and security needs. When data no longer has a valid...
POLICY LINKS
How our privacy pages stay aligned
Your privacy rights should read the same across related bit99 pages. We align this Privacy Policy with cookie, terms and support pages so account data, payment records and security wording do not...
Cookie page
The cookie page deals with browser storage, session tools and measurement tags. It supports this Privacy Policy by showing how device signals work during account access.
Terms page
Terms explain account rules and service conditions, while this policy explains data handling behind those rules. We keep both pages aligned when account verification wording changes.
Support page
Support content tells you how to reach us, but privacy requests need identity checks before we discuss records. This policy explains why those checks are required.
Payment help
Payment help may describe JazzCash, Easypaisa, SadaPay and Raast status steps. This policy explains the privacy side of receipt storage and transaction matching.
Security messages
Security prompts may appear when login activity changes or verification is needed. This policy explains the data signals used to support those account-protection steps.
Update log
When we change policy wording, we keep the meaning consistent with related pages. Material privacy changes are written plainly so you can understand what moved.
Policy layout that helps you decide
We designed this Privacy Policy so you can scan the parts that matter before opening or managing an account. Clear labels, short privacy badges and contact...
Plain section labels
Each policy block has a direct heading, so you can move from collection to use, storage and contact choices without searching through unrelated platform copy.
Local context chips
Short chips mention Pakistan payment rails only where they affect privacy records. They show which receipt references may appear in account-support checks.
Request-first layout
Contact routes appear early because privacy rights are practical only when you know where to ask. We separate quick chat questions from written record requests.
Account safety cues
Security wording explains why login signals, device details and unusual-access checks may be used. The aim is to show purpose, not hide behind technical language.
Rights wording
Access, correction and deletion wording is written in direct language. We also explain when a record must stay for dispute handling, security or legal duties.
Change clarity
If this policy changes, the updated text will focus on what changed in data use, storage or request handling. We avoid burying changes in broad statements.
Questions about your bit99 privacy
We collect account details you provide, login and device signals, support messages, transaction status records and cookie data. Each category must support account access, security, service operation or your privacy request.
No. For JazzCash, Easypaisa, SadaPay, NayaPay or Raast-related checks, we record references such as receipt number, status and time. We do not need your wallet password to process privacy requests.
Device and session data helps us recognise your account session, reduce unauthorised access and investigate unusual activity. It also supports cookie choices and keeps privacy request handling tied to the correct account.
Yes. Contact support with your account identifier and the request you want us to handle. We verify your identity first, then explain what data can be shared under our legal and security duties.
You can ask us to correct eligible account details when they are inaccurate or out of date. Some records, such as transaction history, may need to remain unchanged for audit or dispute reasons.
Retention depends on the record type and purpose. Account, payment-status, security and support records may be kept while needed for operation, legal duties, dispute handling or account protection.
Use live chat for simple privacy questions or email for formal data requests. We may ask for identity checks before discussing account-linked records, because privacy replies must go only to you.