Account terms
Our account terms explain how you may use md777; this Privacy Policy explains what data supports that account relationship and how we handle it.
md777 keeps your Privacy Policy clear before you open your account, so you know what we collect, why we use it, and how your rights work in Pakistan...
This Privacy Policy explains how md777 handles personal details when you create an account, verify access, contact our help team, or use services in supported regions where local law permits. We collect only what is needed for account setup, identity checks, security monitoring, payments context, and service records. We may also keep device and session data to protect your account from unauthorised
access. Pakistani payment names may appear in our logs when a transaction is linked to your account, but we do not ask you to place private wallet passwords inside md777. We keep records for operational, legal, and dispute-handling reasons, then restrict or remove them when they are no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you want to ask about this Privacy Policy, update account details, or question a data entry, contact us from inside your md777 account where possible. Using the signed-in route helps us match your request to the correct record without asking for extra proof.
Send privacy requests from your logged-in account inbox so we can confirm the account link, check recent changes, and respond without exposing details through an open channel.
Our help desk can route privacy questions to the account team, including requests about correction, access, deletion where allowed, and payment record references tied to your profile.
If you cannot access your account, email us with your registered phone or email only; never include wallet passwords, card PINs, or full identity images unless requested securely.
Our Privacy Policy is written from the way md777 actually operates account records. We connect policy wording to registration forms, payment references, device checks, customer support logs, and security controls, so the...
We map each account form field to a reason in this Privacy Policy, including contact details, login credentials, verification data, and settings used to protect your session.
JazzCash, Easypaisa, SadaPay, NayaPay, and Raast references are treated as account records, not public profile details, and are restricted to teams handling checks and disputes.
We record login time, device type, IP range, and failed access attempts to detect unusual activity and help restore account control when you contact us.
Staff access to personal records is limited by work role, with internal logs showing when account data was viewed, changed, or used for a privacy request.
Records are kept only while they serve account operation, legal, dispute, fraud-prevention, or finance purposes, then moved into restricted status or removed when suitable.
When we change data handling, we update this Privacy Policy and align linked account screens so you can see the current basis before sharing new details.
This page sits beside our account terms, cookie controls, and payment record wording. Each page has a different job, but the privacy meaning stays aligned, so your account data is not described...
Our account terms explain how you may use md777; this Privacy Policy explains what data supports that account relationship and how we handle it.
Cookie choices cover browser storage and device signals, while this Privacy Policy explains how those signals may connect with your account security record.
Payment screens show transaction steps; this Privacy Policy explains how linked references from JazzCash, Easypaisa, SadaPay, NayaPay, and Raast are stored.
Support replies follow this Privacy Policy when asking for identity checks, correcting details, or handling account access questions from Pakistan-based account holders.
Login alerts and password reset messages use the same privacy approach, with limited data shown and fuller account details kept behind secure access.
If a campaign creates an account record, this Privacy Policy explains the contact details, consent status, and retention approach used for that record.
Deletion requests are assessed under this Privacy Policy, with finance, dispute, and security records separated from details that can be removed sooner.
We have shaped the Privacy Policy layout so you can scan what matters before creating or managing an md777 account. The page separates collection, use, sharing...
Each privacy section uses plain labels so you can move between account data, payment references, security logs, contact choices, and rights without decoding legal phrases.
The badges at the start point to the records most relevant in Pakistan, including account data and local payment context, before the full wording begins.
We use examples such as login checks, wallet references, and support requests so the Privacy Policy connects to actions you recognise inside md777.
Your rights are described as real account actions, including access, correction, restriction, objection, and deletion where applicable under the relevant local framework.
Privacy contact routes are placed near the policy wording, so you do not need to search separate screens when you want to raise a data question.
When privacy wording changes, we aim to make the change visible on this page and align the related account screens without delay.