Legal Guide
Pakistan has no general consolidated data protection act yet — but your exposure is real sector-by-sector, and your foreign contracts already assume a statute that exists.
Quick answer: Businesses in Pakistan handle personal data under a patchwork: the Prevention of Electronic Crimes Act 2016 criminalises unauthorised access and identity misuse; sector regulators (State Bank of Pakistan for financial institutions, PTA for telecom, PSEB/technology-zone rules for export businesses) impose confidentiality and data-handling expectations; and a general Personal Data Protection Bill has been in process without remaining enacted. Cross-border software and services clients, in practice, apply GDPR-style requirements contractually. The safe posture: behave as a purpose-limited controller even before the statute forces it.
The patchwork, properly named
- PECA 2016: criminalises unauthorised access to information systems, identity crime, and misuse of personal information; is the enforcement baseline for incidents
- State Bank of Pakistan rules: customer-data handling, outsourcing, and data localisation expectations for banks, EMIs, and payment system operators
- PTA / telecom regime: subscriber data retention, AMAS/number-data duties
- NADRA data: separate restrictions on the national identity database and the data tied to it
- Pending general bill: successive drafts of a Personal Data Protection Bill propose consent, purpose limitation, notice, and sensitive-data controls; tables and thresholds have shifted – design to the principles, not the current draft’s numbers
Cross-border transfers: contract-first readiness
Until a statute regulates transfers, the operative rule for outbound projects is the customer’s own law: European (GDPR) and UK clients require processor terms, transfer mechanisms, and breach-notice clauses as domestic practice. Pakistani vendors that align their operations lease-by-lease – consent and notice in onboarding, least-privilege access, vendor DPAs, incident playbook – fill tender gates that foreign buyers apply regardless of Statute domesticity. Alignment is also what our technology industry practice is hired for.
Incidents and investigations
After a breach, PECA leaves room for electronic-crime reporting; but the first hours matter internally: identify what is exfiltrated, preserve access logs, and coordinate customer notifications, since contractual notice terms are usually short (24–72 hours). Companies considering a foreign investment should note that due diligence reviews privacy posture on both sides – our foreign investment and regulatory compliance teams handle these workstreams.
A minimum viable compliance baseline
- Data inventory: what is collected, why, where it lives, who has access
- Notice and consent language in onboarding, site terms, and vendor contracts
- Access controls and least privilege, with joiner-mover-leaver review
- Vendor DPAs and outsourcing notifications, especially for cross-border processing
- An incident playbook with a named owner and a 48-hour internal clock
For a data-audit or contract review before signing foreign software deals, contact Axiom Chambers through the consultation page.