Privacy Policy for your fy99 account
fy99 keeps your account, device and transaction data under a clear Privacy Policy before you open your account. We explain what we collect, why it is needed for...
How we handle your privacy
This Privacy Policy explains how fy99 handles data linked to your account, sign-in activity, device checks, support messages and transaction references. When you use fy99 in supported regions, we collect only the data needed to create your account, secure access, process wallet checks, handle withdrawals, answer support requests and meet record duties that apply to our service. We may receive payment reference
data from JazzCash, Easypaisa, SadaPay or Raast, but we do not ask you to share sensitive wallet passwords with us. We also use technical logs to spot duplicate access, protect sessions and keep the policy record accurate. If you ask us about your data, we verify your account first so that privacy requests are handled by the rightful account holder.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep the policy current
Our Privacy Policy is written from the systems we operate, not copied from a generic template. When account flows, support tools or payment reference handling change, we check...
Account flow mapping
We map each account step to a data purpose, from mobile number checks to session records. That makes the policy...
Payment reference scope
JazzCash, Easypaisa, SadaPay and Raast records are treated as transaction references, not as permission to enter your wallet. Our policy...
Support script checks
We compare support replies with the Privacy Policy so agents do not ask for data that is not needed. If...
Access log purpose
Device, browser and IP records help us protect sessions and spot suspicious access. The policy describes this use in plain...
Retention reminders
Records are not kept simply because storage is available. We set retention reasons for account, support and transaction data, then...
Policy change record
When wording changes, we keep an internal record of what changed and why. That helps our team answer your question...
How related policies stay consistent
Privacy wording works better when it fits the rest of the account terms. We align this page with cookie, security and account rules so you are not given...
| Cookie page link | The cookie page explains browser storage, while this Privacy Policy explains the data purposes behind it. We keep both pages aligned so cookie choices are not separated from account privacy context. |
|---|---|
| Account terms fit | Our account terms cover your obligations, while this policy covers our data handling. Where account checks involve identity or transaction records, both pages use matching wording and matching examples. |
| Security wording match | Security content describes protection steps, and the Privacy Policy explains the data those steps require. This avoids vague claims and keeps session monitoring, password checks and account alerts in one clear frame. |
| Support process link | Support pages tell you how to contact us, while this policy says how support messages are stored and used. We align the two so your help request has a visible privacy route. |
| Payment record context | Transaction pages may show JazzCash, Easypaisa, SadaPay or Raast references. This policy explains how those references are used for matching, dispute checks and withdrawal verification without asking for wallet passwords. |
| Promo board privacy | If you check the promo board, account eligibility may require limited data checks. This policy explains that use without turning a promotion screen into a separate privacy rulebook. |
| Change timing | When a related page changes, we check whether privacy wording also needs an update. This keeps account data, support data and technical logs described with the same timing and terms. |
What stands out on this page
This Privacy Policy is arranged so you can scan the parts that matter before you open an account. The layout separates collection, use, sharing, security, retention...
Plain section labels
Each section uses direct labels such as account data, technical logs and support records. You can move through the policy without decoding legal shorthand or guessing which paragraph applies to your request.
Local examples
We use Pakistan-based examples where they help explain privacy handling, including mobile wallets and bank transfer references. The examples are there to clarify data use, not to broaden what we collect.
Action paths
Where the policy mentions access, correction or deletion, we point you toward the right contact route. That keeps privacy rights practical rather than hidden in a long legal paragraph.
Short purpose statements
Data purposes are written in short statements before any extra context appears. You can see whether a record is for account access, security, transaction matching or support handling.
Careful sharing wording
When third-party service providers are mentioned, we explain the type of task they perform. We avoid broad language that could make data sharing sound wider than our operating need.
Request readiness
The contact section tells you what to include and what not to share. That reduces back-and-forth and helps us handle your privacy request without collecting extra data.