Privacy Policy for your yy99 account
yy99 sets out how your account data, device signals and transaction records are collected, protected and used when you open our lobby from Pakistan. This Privacy Policy keeps...
How we handle your personal data
This Privacy Policy explains how yy99 handles your personal data when you access our site, create an account, contact support or request a transaction check. Account access in supported regions and where local law permits may require identity, device, location and payment-context records so we can keep your profile accurate and reduce account misuse. We collect only what is needed for account
operation, security checks, service messages, transaction tracing and legal requests that apply to us. Your data may be stored with vetted service partners that help us run hosting, fraud screening, customer care and payment-context checks. We keep records for as long as they are needed for these purposes, then remove or anonymise them when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Checks behind this privacy page
We treat this page as an operating document, not filler text. The wording is checked against the account flows we use, including sign-in records, support tickets, verification steps and local rail references...
Scope matching
The policy scope is matched against the account actions you can take on yy99, from opening a profile to asking support about a transaction reference or security alert.
Data minimisation
We ask for data that supports account setup, access checks, fraud prevention and support handling. Extra details that do not help those purposes should not be requested by our team.
Access controls
Privacy requests are handled through controlled support paths. Staff access is limited by role, and account records are opened only when a case or security reason requires it.
Partner checks
When service partners process data for hosting, risk checks or customer care, we require practical controls around access, retention and purpose, rather than open-ended use of your records.
Plain wording
We write policy text in direct Pakistani English so you can understand what is collected, why it is used and which choices you can raise with our support team.
Change tracking
When material privacy wording changes, we update the page date and may show account messages where the change affects how your data is collected or used.
How this policy stays aligned
Our privacy wording is kept consistent with other yy99 legal pages without copying their purpose. This page focuses on personal data, while related pages cover account rules, cookies...
| Terms alignment | Our terms explain account rules, while this page explains data handling behind those rules. The two pages use the same account language so your privacy choices do not feel separate from access steps. |
|---|---|
| Cookie page link | Cookie wording is kept narrower than this Privacy Policy. It deals with browser signals, while this page explains wider account data such as contact details, verification records and support messages. |
| Support wording match | Support scripts follow the same privacy scope used here, so the team asks for only relevant identifiers when checking an account, ticket, rail reference or correction request. |
| Security page fit | Security wording covers access protection, while this page explains the data used to support those controls. That split keeps passwords, device checks and alerts in their proper privacy context. |
| Local rail wording | Where JazzCash, Easypaisa, SadaPay or Raast appear across yy99 pages, this policy explains how related references may be stored for tracing, support and account protection. |
| Retention consistency | Retention wording is checked against support, risk and transaction record needs. We avoid keeping data longer than needed for account operation, dispute handling or legal requests that apply to us. |
| Consent language | Consent prompts, cookie banners and privacy text use compatible wording. That helps you understand whether a data action is required for service access or optional for a setting. |
Privacy layout cues you can scan
This privacy page is arranged so you can find the data point you care about without reading unrelated copy first. Labels, badges and short sections point...
Scope badges
The badges near the hero summarise the policy areas covered on yy99, including account data, security checks and Pakistan rail context, before you reach the longer legal wording.
Purpose labels
Section headings are written around purpose, not vague legal phrases. You can quickly see whether a paragraph covers collection, use, storage, sharing, correction or account support.
Local cues
Names such as JazzCash, Easypaisa, SadaPay and Raast appear only where privacy context needs them, so rail references do not distract from the wider data handling explanation.
Contact blocks
Support cards separate email, chat and transaction-data questions. That layout helps you choose the right path while keeping sensitive account details out of the wrong channel.
Retention signposts
Retention wording is placed near collection and purpose wording because those points belong together. You can see why data is kept before reading how long it may remain.
Change cues
Where policy wording changes, date and account-message cues help you spot updates. We aim to keep changes visible without turning the page into a long legal archive.