Legal terms for your 9bob account
9bob puts account terms, privacy duties, payment rules and complaint routes in one legal area so you can check the conditions before you open your account. This page...
How our legal wording applies
Our legal terms describe the relationship between you and 9bob when you create an account, access the lobby, use wallet functions or contact us about a dispute. Availability can depend on your location, device, identity checks and local rules, so access is intended only for supported regions where local law permits. We do not state a universal permission for every address in
Pakistan, and we may pause access if documents, payment ownership or account details do not match. JazzCash, Easypaisa, SadaPay and Raast references on this page are included to explain how local wallet records can support verification, refund tracing and complaint handling under our account terms.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about legal questions
Legal questions need a clear trail, so we separate account help from policy contact. When you write to us, include your account email, date, payment reference if relevant and a short description of the issue. We use those details to match your request with the correct record.
Policy email
Use our policy mailbox for terms, privacy and complaint queries. We answer with the account records we can verify, and we may ask for extra documents before giving a case-specific reply.
Live help escalation
If live help cannot settle a legal wording question, ask for escalation. The support team will attach chat details, wallet references and account status before sending the matter onward.
Payment evidence path
For JazzCash, Easypaisa, SadaPay or Raast matters, send the transaction ID and wallet name. We use that record to trace timing, ownership and any correction due under policy.
How we keep policies clear
Our legal pages are written for account decisions, not decoration. We keep definitions close to the actions they affect, such as wallet use, identity checks and complaint handling...
Plain language drafting
We avoid legal clutter where a direct sentence works. Each clause is linked to an account action, such as access...
Account flow checks
Policy wording is checked against the account screens you actually use. If a rule concerns verification, we compare it with...
Local context
Pakistan payment references are included only where they affect legal handling. Wallet names help explain receipt tracing, ownership checks, refund...
Change control
When terms change, we keep the updated wording aligned across related pages. That reduces conflict between privacy clauses, wallet rules...
Document handling
Identity files and wallet evidence are handled for account verification and dispute checks. We ask only for records needed to...
Support record trail
Case replies rely on logged messages, timestamps and account status. This helps us explain why a term applied, what was...
Legal pages that work together
This legal page sits beside our privacy, cookie and terms pages. Each one covers a different legal angle, yet the wording must stay consistent. If you read across...
| Terms page | The terms page sets account duties, access conditions and wallet rules. This legal page explains the same posture in shorter form, so both pages point to the same obligations. |
|---|---|
| Privacy page | The privacy page explains how account data is collected and used. This page connects that privacy wording with legal requests, identity checks and complaint evidence for your account. |
| Cookie page | The cookie page covers browser storage and session tools. This legal page links that handling to account access, security checks and records used when a dispute is raised. |
| Payment rules | Wallet rules explain how payment evidence is checked. This page shows why JazzCash, Easypaisa, SadaPay and Raast references may matter in ownership, timing or refund questions. |
| Security wording | Security clauses cover login protection, document matching and account holds. This page explains the legal reason those checks can apply before access or wallet action continues. |
| Complaint process | Complaint wording tells you what to send and where to send it. This page keeps that route visible, with the account details we need for a clear response. |
| Change notices | Policy updates must not conflict across pages. We align wording so a change in terms, privacy or wallet rules does not leave you with mixed instructions. |
Visible cues on this legal page
The legal area is built to help you find the right clause quickly. Headings mark the topic, short chips show the records that may matter, and...
Clause-led headings
Each heading names the legal action it affects, such as account terms, privacy duties or complaint handling. That structure helps you move from question to relevant clause quickly.
Evidence chips
Short chips identify records that may support a case. They do not replace the full policy, but they remind you which wallet receipt or account detail may help.
Card separation
Contact routes, policy checks and page alignment appear in separate cards. This reduces confusion between asking a question, proving a transaction and reading a clause.
Direct answers
FAQ answers are written around legal actions, not general service claims. Each answer tells you what the policy means and which record may be needed.
Consistent labels
We reuse the same legal labels across related pages. Account, wallet, verification and complaint wording should mean the same thing wherever you read it.
Readable order
The page starts with scope, then moves to contact, policy checks, related pages and questions. That order mirrors how legal issues usually reach our team.