fun92 Privacy Policy for Pakistan accounts
fun92 puts your account data, login records and wallet references into one Privacy Policy written for Pakistan access. Read it before you open your account, then keep it...
How we handle your account data
Our Privacy Policy explains what we collect when you create or use a fun92 account where local law permits. That includes your name, mobile number, login activity, device markers, wallet references and messages sent to our service team. We use those records to keep account access clear, process wallet-related requests, check unusual login activity and answer privacy requests from you. We do
not ask you to share wallet PINs, full card secrets or private banking passwords. Where a payment reference is needed, we keep only the details required to match your request with the correct account record. We may retain records for account security, dispute handling and legal duties in supported regions. When retention is no longer needed, we remove or anonymise data in
line with the policy.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact routes for privacy requests
You can contact us about the Privacy Policy through the same account channels you use with fun92. We ask for enough detail to locate your record, then we confirm your identity before taking action. This keeps privacy requests tied to you rather than to anyone else using your phone or email.
Email privacy desk
Send your privacy request with your registered mobile number, account name and the date range you mean. We match it to your fun92 records before sharing, correcting or closing any data held for you.
In-account chat
When you contact us from a logged-in session, we can confirm your device and recent access events more quickly. The Privacy Policy explains why that identity check protects your account file.
Wallet reference help
For JazzCash, Easypaisa, SadaPay or Raast questions, include the transaction reference rather than a full wallet PIN or banking secret. Our policy says we never ask for private wallet passcodes.
How we keep the policy reliable
We keep the Privacy Policy close to real account handling rather than detached legal wording. Our service, risk and product teams check the text when account flows change...
Local wording
We write policy terms in clear Pakistani English so you can understand how your account data is handled in supported...
Access logs
The policy describes login records, device markers and session activity because these help us spot access that does not match...
Wallet handling
JazzCash, Easypaisa, SadaPay and Raast references are treated as matching records. We use them to connect your request with your...
Retention schedule
Our policy explains why some records stay for dispute handling, security checks or legal duties. When those reasons no longer...
Correction trail
If you ask us to correct account details, we keep a small record of the change. That trail helps show...
Escalation path
Privacy requests that need extra checks are passed to a trained account team. The policy explains that we may ask...
Aligned across our privacy pages
The Privacy Policy connects with other fun92 legal pages so you are not left guessing. Each page handles a different part of account data, but the language stays...
Privacy layout you can scan
We shaped the Privacy Policy page so you can find the clause you need without reading every line first. Headings, short labels and account examples sit...
Plain headings
Each section title states the data area it covers, such as account setup, login records or wallet references. That structure helps you move straight to the privacy point affecting your request.
Short labels
We use short labels beside complex policy areas so legal wording is easier to scan. Labels do not replace the policy text; they help you find the right clause faster.
Data examples
The page uses account examples from fun92, such as mobile numbers, session records and transaction references. These examples show the kind of data involved without asking you to share secrets.
Choice markers
Where you have a privacy choice, the page marks it clearly. This may include contact preferences, cookie settings or requests to correct details already linked with your account.
Security cues
Security-related clauses are grouped so you can see how login records, device signals and account checks work together. The aim is clear handling, not hidden collection.
Local context
Pakistan wallet references are named where they matter, including JazzCash, Easypaisa, SadaPay and Raast. This keeps the policy relevant to the account flows you actually use.