yo99 Privacy Policy for Pakistan
yo99 keeps your privacy choices, account checks and Pakistan payment records in one clear policy before you open your account. Read how we collect, use and secure data...
How we handle your data
Our Privacy Policy explains how yo99 handles account data for Pakistan where local law permits access. When you create an account, we collect details needed to identify you, protect your sign-in, record game-session activity, and process withdrawal checks linked with JazzCash, Easypaisa, SadaPay or Raast. We use this data to run your account, answer privacy requests, prevent duplicate access, and meet record-keeping
duties that apply in supported regions. We do not sell your personal data. Service partners only receive the fields needed to deliver hosting, verification, fraud screening, messaging, and payment reconciliation. If a rule, bank query, or security concern requires longer retention, we keep the relevant record and remove unrelated data when it is no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Checks behind this policy
We keep this Privacy Policy tied to how yo99 actually operates in supported regions. Each clause is checked against account creation, login security, cashier records, cookie settings and customer-contact workflows before it...
Named internal owner
A privacy lead inside yo99 keeps the policy aligned with account flows, support scripts and record retention rules, so your request is handled under one clear process.
Local rail awareness
The policy reflects how Pakistan payment references appear in our systems, including JazzCash, Easypaisa, SadaPay and Raast entries used for reconciliation and privacy checks.
Access control checks
Staff access to account records is role based. Sensitive fields are limited to teams that need them for verification, payment reconciliation, security checks or privacy replies.
Cookie setting clarity
We explain cookies by purpose, including sign-in stability, fraud prevention, preference storage and basic site measurement, so you can understand what each setting supports.
Retention discipline
Records are kept for account operation, dispute handling, security and legal needs. When a record is no longer required, we remove or anonymise it where our systems allow.
Change tracking
When we update this Privacy Policy, we adjust the date and keep the new wording tied to current account, cashier and support behaviour.
Aligned with our legal pages
This Privacy Policy is written to sit beside our other legal pages without mixed meanings. The same account terms, data categories, contact routes and retention language are used...
| Same data labels | Each legal page uses the same labels for account data, session data, device data, transaction records and cookies, so your rights read consistently from one page to another. |
|---|---|
| Shared contact wording | Privacy contact steps match the routes shown in our account and support pages, which helps you send requests without repeating the same details across different channels. |
| Payment record match | References to JazzCash, Easypaisa, SadaPay and Raast follow the same privacy wording wherever cashier records are mentioned, keeping wallet and transfer data treatment clear. |
| Security language match | Login protection, device checks and fraud screening are described with the same scope across the legal set, so data use is not stretched beyond the stated purpose. |
| Retention wording | Time-based record keeping is described in a consistent way, covering account operation, disputes, security events and legal needs without adding hidden privacy conditions elsewhere. |
| Cookie alignment | Cookie purposes stay the same across our legal pages: session stability, preference storage, fraud prevention and basic measurement. We avoid adding new purposes in separate wording. |
| Rights language | Requests to access, correct or delete data use the same identity-check approach across the site, so we can protect your account before making privacy changes. |
Privacy layout you can scan
The policy page is arranged so you can find privacy details quickly before creating or managing your account. We separate collection, use, sharing, retention, cookies and...
Clear collection blocks
Data collection is grouped by account details, device signals, session activity and transaction records, making it easier to see which privacy purpose each category supports.
Plain purpose labels
Each use of data is tied to a direct purpose such as account access, security checks, support replies, payment reconciliation or cookie preference storage.
Partner sharing section
Where service partners are involved, the layout names the task they support, such as hosting, verification, fraud screening, messaging or payment processing tied to your account.
Retention signals
Retention wording appears close to the data category it affects, helping you understand why some records are kept longer than short-lived session or cookie data.
Rights request area
Access, correction and deletion requests are grouped in one area, with identity-check steps explained so privacy changes do not expose your account to another person.
Update date
The policy date is kept visible near the page heading, so you can see when the current wording was last changed by yo99.