Purpose
We connect each collection purpose with an account need, such as access, security, payment matching, support handling or compliance with a lawful request.
This Privacy Policy explains how mart99 collects, uses, stores and protects details linked with your account in Pakistan. We keep the policy focused on the data created when...
We collect registration details, contact details, verification records, device signals, login activity, transaction references and messages sent to support. We use these details to create and secure your account, process account activity, detect misuse, meet applicable legal duties and respond to your requests. Payment records may show references connected with JazzCash, Easypaisa, SadaPay, Raast or another supported Pakistani rail, while sensitive payment
credentials remain with the relevant provider. We retain records only for as long as needed for the stated purposes, operational security, dispute handling or legal obligations. Where local law permits access, our processing follows the rules applicable to the service and your supported region. You may contact us to ask about access, correction or deletion, subject to identity checks and records we
must retain.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our support routes are available for privacy questions about account records, verification material, device activity or payment references. Tell us the email or phone number connected with your account, describe the request clearly and avoid sending passwords or complete payment credentials. We may ask for reasonable confirmation before discussing or changing personal details.
Send a request through the account support channel when you want to ask what personal details we hold, why they are used or whether a correction can be made.
If you cannot reach your account, contact support from the registered contact route where possible. We check ownership before discussing login history, verification records or account changes.
Tell us promptly if you notice an unfamiliar login, message or transaction reference. We can review the account event, secure access and explain the privacy steps taken.
Privacy is part of the account operation rather than a separate promise. We limit internal access according to work needs, use account checks before sensitive changes and monitor unusual sign-in patterns. Our...
Account records are available only to staff or service partners who need them for a defined task, such as account security, payment reconciliation, technical support or legal processing.
We may record device type, browser details, approximate network location and sign-in time to identify unusual access patterns and help protect your account from unauthorised use.
When an account or withdrawal needs checking, we use submitted details to compare ownership and activity. Verification material is handled for that purpose and retained under our record rules.
We receive transaction references and status details from supported rails, not your full wallet password or secret PIN. This lets us match account activity while reducing exposure of payment credentials.
Messages, attachments and replies may be stored so we can resolve repeated questions, protect account access and maintain a reliable record of privacy requests.
We keep this policy connected to actual account operations, including sign-in security, local payment matching, identity checks and requests to access or correct personal details.
This page is the privacy reference for mart99 and should be read alongside any account terms that apply to your use of supported services. The privacy principles below remain consistent when details...
We connect each collection purpose with an account need, such as access, security, payment matching, support handling or compliance with a lawful request.
You can ask about the details associated with your account and request correction where a record is inaccurate, subject to checks and lawful retention duties.
We use access controls, account confirmation and activity checks across the same privacy process rather than applying different standards to different account areas.
Records are kept for operational, security, dispute or legal reasons, then removed or restricted when they are no longer needed for those purposes.
Requests connected with Pakistan accounts may involve local payment references, regional access rules and contact details used during account verification.
A payment, hosting or security partner may process limited details for a defined task, while our instructions and account responsibilities remain in place.
If processing changes, we may update this page and show the revised date or a notice through an account channel where that step is appropriate.
The privacy side of mart99 is arranged around the questions that matter when you open or manage an account. You can move from the collection purpose...
Short sections explain why registration, device, support and transaction details may be collected, helping you connect each data type with a practical account need.
Contact options make it easier to ask about access, correction, deletion or an unfamiliar account event without placing sensitive credentials in a message.
Visible privacy cues point to account confirmation, limited internal access and activity checks used when we protect sign-ins or process account changes.
The page uses clear English for Pakistan and names JazzCash, Easypaisa, SadaPay and Raast when payment references form part of a privacy question.
A focused structure helps you distinguish data handling from account conditions, so a privacy request can be directed to the right mart99 support route.
Headings, cards and concise explanations keep the page readable on a phone, tablet or desktop while you check how account details are handled.