Privacy Policy for your m999 account
m999 sets out how your account details, wallet records and security signals are handled before you open an account in supported regions. Read this policy to see what...
How we handle your privacy details
This Privacy Policy applies when you access m999 from Pakistan or another supported region where local law permits. We collect account details you provide, wallet references from JazzCash, Easypaisa, SadaPay and Raast, login signals, device checks and messages you send to our team. We use these details to create your account, protect access, process wallet requests, check unusual activity and answer privacy
questions. We do not sell your personal details. We share limited records with payment, security, hosting and service partners only when needed for account operation, legal duties or fraud prevention. Retention periods depend on record type, dispute status and applicable law.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy current
We write this Privacy Policy from our own operating process, not from a template alone. The wording reflects how m999 handles account creation, payment references, security checks, live support records and privacy...
Operational wording
Each policy section is tied to a real m999 process, such as account creation, wallet confirmation, login checks or help replies. This keeps the text practical instead of broad legal filler.
Payment reference scope
JazzCash, Easypaisa, SadaPay and Raast records are described as transaction references, not open access to your wallet. We store only what is needed to reconcile account activity.
Security review path
Login patterns, device signals and failed access attempts may be assessed to protect your account. These checks are limited to security use and are not used to expose private account content.
Correction handling
If your name, phone number or wallet reference is wrong, our team checks the request against account records before making changes. That reduces the risk of another person changing your privacy details.
Retention checks
We keep different records for different periods depending on account activity, support history, transaction disputes and legal needs. When records are no longer required, we remove or anonymise them where possible.
Access limits
Internal access to personal details is limited by role. Support, payment and security staff only see the records needed for their task, and sensitive requests may require extra approval.
Consistency across our legal pages
This Privacy Policy sits beside our other legal pages, but it has its own job. It explains data collection, use, sharing, retention and contact choices. Where another page...
| Terms link | Our account terms explain how you use m999, while this Privacy Policy explains what personal records are created during that use. We keep those roles separate so you can read them clearly. |
|---|---|
| Cookie link | Cookie wording covers browser storage and similar tools. This policy connects those signals to privacy choices, including why security cookies may be needed for account protection. |
| Payments link | Wallet instructions explain how transfers work, while this policy explains how payment references are stored, checked and shared with processors when needed for reconciliation or dispute handling. |
| Security link | Security pages may explain access controls in plain terms. This Privacy Policy states which login signals or device details are collected when those controls are used. |
| Support link | Help pages show how to contact us. This policy explains what happens to chat records, email threads and verification details after you send a privacy or account request. |
| Promotion link | If you check account offers, this policy explains how preference settings and message records may be handled. We do not mix offer content with unrelated personal disclosures. |
| Update link | When a legal page changes, we keep the privacy wording aligned with the actual process. If the data effect changes, this policy is updated in plain Pakistani English. |
Policy page signals you can read
We designed this Privacy Policy page so you can scan important privacy points before creating or using your account. The layout separates collection, use, sharing, storage...
Clear data categories
The policy groups personal details into account, wallet, device, security and support records. This helps you understand which data comes from you and which data is created during account activity.
Purpose statements
Each category is linked to a purpose, such as account access, payment matching, fraud prevention or customer support. We avoid vague wording when a practical reason can be stated.
Sharing limits
The sharing section names the kinds of partners that may receive limited records, including payment processors, hosting providers and security services. It also explains why those partners need the details.
Retention wording
Retention is described by record type and business need instead of one blanket period. That matters because support threads, payment references and security logs may have different legal timelines.
Choice routes
Your options to ask for access, correction or deletion are placed near contact details. We explain that verification may be required before action is taken on sensitive records.
Policy change marker
When wording changes, the page should reflect the newer process clearly. We aim to keep updates readable so you can see how privacy handling may have changed.