Privacy Policy for your 9ooo account
9ooo gives Pakistan account holders a clear Privacy Policy before the lobby opens, so you know what data we collect, why we use it and how long we...
How this policy applies in Pakistan
This Privacy Policy explains how 9ooo handles personal details linked to your account where local law permits access to our service. We collect data you provide during account setup, security checks, support contact and wallet activity, then use it to run the account, protect balances, process requests and meet record duties that apply to us. Payment references from Pakistani rails can appear
in account logs, but we do not ask you to share private wallet passwords or one-time codes. We may update this policy when our account flow, verification steps or legal duties change, and the current wording on this page is the version you should read before opening or continuing your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep the policy practical
We write this page for real account use, not legal decoration. Our checks focus on the points you actually touch: joining, identity matching, payment references, device access, support transcripts and security alerts...
Account flow mapping
We map each data point to the account step where it appears, such as phone entry, password reset, login check or support message. That helps us remove unclear wording from this page.
Local rail awareness
JazzCash, Easypaisa, SadaPay and Raast references are treated as account records, not as wallet access rights. We record transaction identifiers only when needed for matching or support.
Access controls
Internal access to personal data is role based. Support can see what is needed to solve your request, while deeper security logs are limited to staff handling account protection.
Device signals
We may record browser, IP, device and session signals to spot unusual access. These checks protect your account record without asking you to share private wallet credentials.
Retention checks
Records are kept for account operation, dispute handling, security and legal needs. When a record no longer has a valid purpose, we aim to remove or reduce it safely.
Plain English edits
We avoid heavy legal phrasing where clearer wording works. The aim is that you can understand what we collect, what we use, and how to contact us.
Where this policy fits
Our legal pages work together, but this page stays focused on privacy. If another page explains account rules, cookies or promotions, this page explains the data side of...
Privacy cues across your account area
We place privacy cues where you are likely to need them, not only on this page. Short labels near forms, support prompts and security screens remind...
Form labels
When a form asks for a phone, email or name, the label should make the purpose clear. We avoid asking for extra details unless the account step needs them.
Security prompts
Login alerts and password reset screens may refer to device or session checks. These prompts link back to the privacy approach described here, so you know why signals are used.
Support reminders
Support screens remind you not to send wallet passwords, one-time codes or unnecessary documents. If proof is needed, we ask only for the part linked to your request.
Wallet references
Where JazzCash, Easypaisa, SadaPay or Raast appears in your account history, the record is used for matching and support. It does not give us access to your wallet.
Update notices
If this policy changes, we keep the wording clear and dated within the page area. You can read the new version before continuing with sensitive account actions.
Account controls
Your account area may let you update contact details or password settings. Privacy handling for those changes includes security logging and checks against unusual access patterns.