How 999f handles your data
999f keeps your account, lobby and local payment data in one privacy framework, so you can open an account knowing what we collect and why. This policy explains...
Privacy stance for Pakistan accounts
Our Privacy Policy explains how we collect, use, store and protect data when you open a 999f account in Pakistan where local law permits. We collect only what is needed for account access, wallet checks, service messages, fraud prevention and support. Payment references from JazzCash, Easypaisa, SadaPay and Raast are used to match transactions with your wallet, not to publish private banking
data in the lobby. We also handle device data, IP ranges, cookies and session logs so your account can be secured across phone browsers and app-style web views. You can ask us to correct data, explain a privacy choice or close an account record subject to legal retention rules. This page is written for you, so each section says what data is
involved and why we use it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about privacy choices
Privacy requests should reach the team that can verify and act on them safely. Our privacy mailbox, live chat handoff and ticket form all reach the same case queue, so you do not need to repeat sensitive details. We respond with the next step, any identity check needed and the likely timeframe for the request.
Privacy email
Email us from the address on your 999f account so our privacy team can match your request safely. We may ask for a light identity check before we change or release account data.
Live chat handoff
Use live chat from 10:00 to 02:00 PKT for a privacy handoff, then keep sensitive documents inside the secure ticket link. Chat agents do not ask for full wallet PINs or passwords.
Account ticket
Open a ticket when your request includes screenshots, wallet references or device details. The ticket keeps the privacy case separate from general support, with access limited to the staff assigned to resolve it.
How we keep policy wording accurate
Privacy text is useful only when it matches the systems behind it. We check this page against account forms, transaction matching, device logs and support workflows before publishing...
Policy owner
A named internal owner keeps this page aligned with how our account, wallet and lobby systems collect data. When a...
Payment data separation
JazzCash, Easypaisa, SadaPay and Raast references are stored apart from game-session logs where our systems allow. That separation helps us...
Session log checks
We log sign-in time, device type, IP range and security events to protect account access. The policy explains these logs...
Retention calendar
Data is kept only for operational, legal and dispute needs, then removed or made non-identifying when the period ends. We...
Plain language edits
We write policy text in local English so you can understand what is collected before you join. Legal phrases are...
Change record
Material edits are dated inside the policy page and checked against support scripts. If a request arrives after an edit...
Consistent privacy pages across 999f
Our Privacy Policy is checked against the cookie page, account terms and help-centre scripts so your rights are described the same way wherever you read them. The aim...
| Account terms | Account terms explain access rules, while this policy explains the data behind those rules. We keep both pages aligned so identity checks, wallet security and closure requests do not conflict. |
|---|---|
| Cookie page | The cookie page gives a closer look at browser storage, while this policy places cookies beside account and security data. Both pages use the same cookie names and purposes. |
| Support scripts | Support replies are matched to the policy wording, so privacy agents do not promise more or less than the page says. This keeps email, chat and ticket answers consistent. |
| Wallet flow | Cash-in and withdrawal screens collect reference data for matching and safety checks. The same terms appear here, so you can see why a payment reference is requested. |
| Security alerts | Security alerts may use device, IP and session data to protect your account. The privacy wording explains that use before alerts appear in email or account messages. |
| Retention rules | Retention wording is shared across related pages so old records are handled in a consistent way. If a record type needs a longer legal period, we say so clearly. |
| Rights requests | Correction, access and closure requests follow the same route across policy pages. We ask you to use account-linked contact details so our team can verify the request safely. |
Visible cues on this policy page
This page is laid out so you can scan privacy points before you open an account. Labels show which data relates to account access, wallet matching, cookies, security...