Terms alignment
Our account terms explain access rules, while this Privacy Policy explains the data behind those rules. The two pages use matching contact routes and avoid conflicting statements about identity checks.
r98 keeps account, device and transaction data rules in one clear Privacy Policy before you open your account. Read how we collect, use, protect and share data for...
This Privacy Policy explains how we handle data when you create an r98 account, sign in, browse the lobby, contact support, or use account-related tools in supported regions. We collect only the data needed to run your account, confirm access, process transaction records, secure sessions and respond to requests. Some data comes from you, such as your mobile number, email address and
account details. Other data is created during use, including device type, IP address, login time, cookie choices and transaction references. When JazzCash, Easypaisa, SadaPay or Raast appears in your account flow, we keep only the relevant reference data needed for account checks, receipts and support handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our Privacy Policy is maintained as an operating document, not a static page. We check it when account flows change, when new support tools are added, and when data handling around Pakistani...
We display update timing so you can tell whether the Privacy Policy has changed after your account was created. Material changes are written in plain language rather than hidden in legal wording.
Only approved team roles can view personal account data needed for support, security or transaction checks. We use role limits so internal access is linked to an actual service need.
We avoid asking for extra personal data when a smaller check will do. For example, a transaction reference may be enough for a support request without asking for unrelated documents.
We use device and session signals to keep account access stable and to spot unusual logins. These signals include browser type, IP address, session timing and security event records.
When a service partner helps with hosting, analytics, security or support tools, we share only the data needed for that task. Partners are not given permission to use it for separate purposes.
Policy edits are checked for clarity before publication. We remove vague wording where possible, define key account data uses and keep contact routes visible near the relevant privacy clause.
Your privacy expectations should not change from one legal page to another. We align this Privacy Policy with account terms, cookie wording, transaction handling text and support clauses so the same data...
Our account terms explain access rules, while this Privacy Policy explains the data behind those rules. The two pages use matching contact routes and avoid conflicting statements about identity checks.
Cookie text connects back to this Privacy Policy so you can see why session cookies, preference cookies and measurement tools exist. We separate essential session use from optional site measurement.
Where the account area lets you update contact details, this policy explains how those changes affect stored data. We keep the wording close to the action you take.
Pages that mention JazzCash, Easypaisa, SadaPay or Raast refer back to the same privacy approach. Transaction references are handled for account matching, receipt checks and support history.
If you choose to receive account alerts or optional offers, the related page links that choice to this Privacy Policy. You can see what contact data is used and why.
Security clauses across r98 use the same explanation for login records, device checks and risk alerts. This avoids mixed wording when you read both account and privacy pages.
Access references use supported regions and where local law permits. The Privacy Policy follows that wording so data handling is described within the same Pakistan-facing account context.
We designed this Privacy Policy so key data points are easy to find. The page separates account data, cookies, transaction references, sharing rules, storage periods and contact routes...