Account terms
Our account terms explain what you agree to when you join r99. This Privacy Policy explains the data side of those actions, including identity checks, login records and support history.
LEGAL REFERENCE
How r99 Handles Your Privacy
r99 keeps account, device and transaction data in a privacy flow built for Pakistan, with clear choices before you open your account where local law permits. This Privacy...
Account dataCookie choicesTransaction recordsPakistan support
What This Privacy Policy Covers
This Privacy Policy applies when you browse r99, create an account, contact our team or complete a transaction in supported regions of Pakistan. We collect only the data needed to run account access, security checks, payment matching, fraud controls, support replies and required record keeping. That can include your name, phone number, email address, login activity, device signals, cookie choices, payment reference
numbers and messages you send to us. We do not sell your personal data. We share limited details only with service providers that help us run hosting, account safety, analytics, payments, support or lawful requests. When a JazzCash, Easypaisa, SadaPay or Raast reference is checked, we use it to match your transaction to your r99 account and to resolve privacy or support
queries.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
Policy Checks Built Into r99
We write this policy from the way r99 actually handles accounts, not from a template. The privacy checks below explain how we limit access, keep records useful and reduce unnecessary data movement...
Access control
Only staff with a work reason can open account privacy records. Access is separated by task, so payment matching, security checks and support replies do not all expose the same fields.
Payment matching
JazzCash, Easypaisa, SadaPay and Raast references are used to match transactions, not to build unrelated profiles. We keep reference trails so you can query a payment-linked privacy record.
Device signals
We may record device type, browser details and IP signals to protect logins and spot account misuse. These checks support privacy by limiting unauthorised access to your r99 account.
Cookie controls
Cookies help remember sessions, language settings and basic analytics choices. Where choices are available, you can adjust non-essential cookies while security cookies remain active for account protection.
Record periods
We keep records only for account operation, dispute handling, fraud prevention and legal duties. When a record is no longer needed, we remove it or reduce it where practical.
Policy changes
When this Privacy Policy changes, we update the page so you can see the current approach. Important changes may also appear inside your account or through support channels.
POLICY LINKS
How Our Privacy Pages Stay Consistent
Privacy wording should connect cleanly with the rest of our legal pages. We align this policy with our account rules, cookie wording and support process so you are not asked to follow...
Cookie wording
Cookie details are written to match this Privacy Policy. Session cookies, preference cookies and analytics cookies are described in the same practical language, so your choices stay clear.
Support records
Support pages refer back to this policy when a conversation includes personal data. That includes chat logs, email threads, account checks and attachments you send to prove a privacy request.
Transaction disputes
When a payment query becomes a privacy matter, this policy controls how we handle the data. Transaction references are checked against account records without exposing more detail than needed.
Security alerts
Security messages and privacy actions use the same verification standard. If we detect risky account activity, we may limit data sharing until your identity is confirmed through approved steps.
Regional access
Access wording across r99 refers to supported regions and where local law permits. This Privacy Policy follows that approach when explaining data handling for Pakistan account activity.
Update requests
Requests to correct, export or remove eligible data are routed through one privacy process. This keeps account terms, support replies and policy outcomes aligned for your r99 profile.
Privacy Layout Elements You Can Spot
This page is arranged so you can scan the Privacy Policy without losing the legal meaning. Each visible element points to a specific privacy topic, from...
Clear hero message
The opening section states the privacy purpose first, so you know this page is about account data, transaction records, cookies and your choices rather than general r99 features.
Short data chips
The chip row highlights data categories linked to privacy handling. Labels stay short because the full legal context sits in the policy body, support routes and question section.
Local context
Pakistan payment names appear only where they help explain privacy records. JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction data tied to your account.
Plain request paths
Contact blocks show how to ask about your data without searching across unrelated pages. Each route explains what we need before we can discuss or change account records.
Verification cues
Security wording appears beside privacy actions because we must confirm identity before sharing personal records. This reduces the risk of account data going to the wrong person.
Question format
The question section turns legal wording into practical answers. It covers access, correction, cookies, payment references and account closure effects without changing the policy position.
Privacy Policy Questions For r99
We collect data needed for account access, verification, payments, support and security. This may include contact details, login activity, device signals, cookie choices, transaction references and messages you send to us.
Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account. They also help resolve disputes, confirm support requests and keep a clear privacy trail.
Yes, you can ask us to correct eligible account data. We may request verification first, especially if the change affects identity, payment records, account access or previous support conversations.
We share limited data with service providers that support hosting, payments, analytics, security and customer care. We also respond to lawful requests where required, while limiting the data shared.
Cookies keep your session active, remember preferences and help us understand basic site performance. Some cookies are needed for security, while optional analytics cookies may depend on available choices.
Some records may be kept after closure for disputes, fraud prevention, accounting and legal duties. When retention is no longer needed, we remove or reduce eligible data where practical.
Use in-account help, email or chat and state your exact request. Add your registered contact details and any related transaction reference so we can verify you and respond accurately.