TaxCalc.pk
Protect company IP from rogue developers in Pakistan. Learn Section 13 Copyright Ordinance rules, contractor vs employee assignment, and NDA terms.
By Syed Asad Hussain Zaidi · 8 September 2026
Author Note / Last Updated: Updated September 2026 by Syed Asad Hussain Zaidi | Advocate High Court | Senior Technology, Venture Capital & IP Counsel. Pakistan has rapidly emerged as a tier-one global IT hub, exporting billions of dollars in enterprise software engineering, software-as-a-service (SaaS) platforms, artificial intelligence models, and mobile applications to North America, Europe, and the Middle East. However, beneath this explosive growth lies a dangerous, pervasive legal misconception that threatens early-stage startups and established software houses alike: the false belief that paying a software developer or software house automatically vests ownership of the source code and copyright in the paying client. Under Pakistani jurisprudence, nothing could be further from the truth. In the absence of a meticulously drafted, statutorily compliant written intellectual property assignment agreement, the individual human developer who typed the source code remains the legal copyright owner under the Copyright Ordinance, 1962, even if the company paid every invoice in full. This legal disaster routinely surfaces at the worst possible moments: during institutional venture capital due diligence, preceding an international M&A acquisition, or when a disgruntled co-founder or lead engineer walks away, forks the proprietary GitHub repository, and launches a competing application. This legal guide provides tech founders, Chief Technology Officers (CTOs), and corporate counsel with an exhaustive roadmap to navigating software copyright, the "work-for-hire" doctrine, developer assignment agreements, and source code ownership under Pakistani law. --- The Statutory Framework: Who Actually Owns Software Code in Pakistan? Software in Pakistan is protected as a literary work under the Copyright Ordinance, 1962 (as amended by the Copyright (Amendment) Act, 1992). A. Section 13: The Author as the First Owner The fundamental premise of Pakistani copyright law is codified in Section 13 of the Copyright Ordinance, 1962: "Subject to the provisions of this Ordinance, the author of a work shall be the first owner of the copyright therein..." In software engineering, the "author" is not the venture capitalist who financed the venture, nor the product visionary who drew the wireframes. The author is the software architect or developer who drafted the code. B. The Section 13(b) "Contract of Service" Exception Section 13(b) establishes the statutory exception for corporate employment: "in the case of a work made in the course of the author's employment under a contract of service or apprenticeship, the employer shall, in the absence of any agreement to the contrary, be the first owner of the copyright therein..." To qualify under Section 13(b), two strict legal conditions must be met: Contract of Service (Employment): The developer must be a bona fide legal employee subject to direct corporate oversight, provident fund/EOBI deductions, salary slips, and regular working hours. Course of Employment: The software must be created directly within the scope of the employee’s assigned job duties during work hours. If a senior backend engineer develops an autonomous machine-learning script on their personal laptop over the weekend, the employer cannot claim automatic Section 13(b) ownership without a comprehensive written assignment agreement. --- The Devastating Freelancer & Vendor Trap: "Contract FOR Services" The single greatest legal vulnerability in the Pakistani tech ecosystem arises when companies hire external agencies, third-party software development houses, or independent freelancers. Under Pakistani law, an independent contractor or external software house operates under a "Contract FOR Services", not a "Contract OF Service". THE RULE OF LAW: Payment of money does not convey copyright. Under Pakistani statutory law, an invoice marked "Paid in Full" merely confers upon the client an implied, non-exclusive license to use the software. It does not transfer the copyright. The developer retains the legal right to license that exact same code to your direct competitors, or sue you for copyright infringement if you modify or redistribute the source code! To transfer legal ownership, the parties must execute an express written Deed of Assignment complying with Section 14 of the Copyright Ordinance. --- Statutory Requisites of an IP Assignment Agreement (Section 14) Under Section 14 of the Copyright Ordinance, 1962, an assignment of copyright is legally void unless it satisfies strict statutory mandates: Mandatory Written Instrument: Oral assignments, Slack messages, WhatsApp chats, or verbal handshakes are completely void ab initio. The assignment must be in writing and signed by the assignor (developer) or their legally authorized agent. Identification of Specific Rights Assigned: The agreement must explicitly enumerate the assigned rights—including the exclusive right to reproduce, compile, modify, adapt, create derivative works, reverse engineer, distribute, license, and commercialize the software in object code and source code formats. Territorial Scope: The agreement must explicitly state that the assignment is valid worldwide in perpetuity. If territory is omitted, Pakistani courts may construe the assignment as limited strictly to Pakistan. Duration: If no period of assignment is stated, the assignment may be interpreted under local principles as expiring after five years, reverting rights back to the developer. The agreement must explicitly stipulate "in perpetuity for the full statutory copyright term and any extensions thereof". Valid Monetary Consideration: Under the Contract Act, 1872, an assignment without distinct, lawful consideration is void. The agreement must explicitly link the assignment to the financial remuneration paid to the developer or agency. --- Drafting Architecture: Anatomy of a Bulletproof Software IP Agreement To ensure that a venture capital auditor or High Court judge upholds your corporate IP title, an Intellectual Property Assignment and Proprietary Information Agreement (PIIPA) must incorporate these specialized legal clauses: A. The "Present Assignment" Formulation (Avoiding Future Promises) Many poorly drafted Pakistani contracts state: "The Developer agrees to assign all rights to the Company." This wording represents a mere covenant to assign in the future; it does not transfer immediate legal title. If the developer absconds, you must sue them for specific performance. The agreement must employ immediate present-tense assignment language: "The Developer hereby unconditionally, irrevocably, and perpetually assigns, transfers, and conveys to the Company, immediately upon creation, all right, title, and interest worldwide in and to all Intellectual Property, source code, scripts, algorithms, documentation, and architecture..." B. Statutory Waiver of Moral Rights (Section 62) Under Section 62 of the Copyright Ordinance, 1962, the author retains "special rights" (moral rights) even after an economic assignment: Paternity Right: The right to be identified as the author. Integrity Right: The right to restrain any distortion, mutilation, or modification of the work prejudicial to their honor or reputation. In software development, continuous code refactoring, bug fixes, and feature additions technically "modify" the code. A disgruntled developer could invoke Section 62 to restrain you from altering their codebase. The assignment agreement must contain an absolute, irrevocable waiver of all moral rights to the maximum extent permitted by law. C. Background Technology vs. Foreground IP Carve-Outs Developers routinely utilize pre-existing libraries, personal boilerplates, or third-party open-source components. The contract must delineate: Foreground IP: All code, architectures, and documentation developed specifically for the project—transferred 100% to the company. Background IP: Any pre-existing code owned by the developer prior to the engagement. If incorporated into the deliverables, the developer must grant an unconditional, perpetual, irrevocable, royalty-free, worldwide license to use, modify, and sub-license that Background IP as part of the overall software. D. Open-Source Software (OSS) Warranty & Indemnity Unregulated developers frequently copy code snippets from open-source repositories licensed under viral copyleft licenses such as GPL v2 or GPL v3. If GPL code is integrated into your proprietary software, the copyleft license mandates that your entire proprietary source code must be made publicly available for free. The agreement must contain a strict warranty: The developer shall not introduce any Open Source Software without prior written authorization from the CTO. The developer shall indemnify the company against any copyright infringement claims or licensing contamination resulting from unauthorized OSS usage. E. The "Further Assurances" and Power of Attorney Clause If your company later files a patent in the United States, Europe, or Pakistan, patent offices require the original inventors to execute formal assignment deeds. If the developer has left the company or refuses to cooperate, prosecution stalls. The contract must include a Power of Attorney clause designating the Company’s officers as the developer’s true and lawful attorney-in-fact to execute all patent or copyright assignment forms on their behalf if the developer cannot be reached or refuses to sign. --- Dispute Scenarios: The "Rogue Lead Developer" & Litigation Remedies When IP ownership breaks down, disputes escalate rapidly. Consider the classic tech scenario: Civil Remedy: High Court Injunction (Order XXXIX Rules 1 & 2 CPC) If an assignment agreement is in place, the company can immediately approach the High Court exercising original civil jurisdiction or the Special IP Tribunal to obtain an ex-parte temporary injunction: Restraining the rogue developer from disclosing, commercializing, or deleting the code. Directing the recovery of company laptops, credentials, and digital repositories under an Anton Piller order (search and seizure of digital assets executed by a court-appointed Local Commissioner). Criminal Remedy: PECA 2016 & Copyright Violations If a developer alters root administrative passwords, deletes repositories, or injects ransomware logic, their conduct transcends civil breach of contract and constitutes criminal cyber offenses under the Prevention of Electronic Crimes Act, 2016 (PECA): Section 3 (Unauthorized Access to Information System): Up to 3 months imprisonment. Section 4 (Unauthorized Copying or Transmission of Critical Data): Up to 6 months imprisonment. Section 5 (Interference with Critical Information System): Up to 2 years imprisonment. Section 66 of Copyright Ordinance, 1962: Criminal copyright piracy punishable with imprisonment up to 3 years and substantial fines. The company can lodge a formal complaint with the FIA Cyber Crime Wing (CCW), triggering criminal asset seizures and forensic hardware imaging. --- Registering Software Copyright with the Copyright Office (IPO-Pakistan) While copyright protection arises automatically upon creation under the Berne Convention, formal registration with the Copyright Office, IPO-Pakistan (Karachi/Lahore/Islamabad) provides decisive evidential advantages: A. The "Clean Source Code Deposit" Protocol To protect trade secrets while satisfying the registry deposit requirement, IPO-Pakistan does not require the entire multi-gigabyte codebase. Under standard prosecution practice: Deposit the first twenty-five (25) and last twenty-five (25) pages of source code in hard copy or optical media. Proprietary encryption keys, API access tokens, and sensitive cryptographic functions may be legally redacted (blacked out), provided that the structural syntax and flow of the program remain evident. B. Evidentiary Weight in Court Under Section 60 of the Copyright Ordinance, 1962, the Register of Copyrights is prima facie evidence of the particulars entered therein. A certified copy of the copyright certificate shifts the entire burden of proof in court onto the infringer, allowing rapid grant of interlocutory injunctions. --- Due Diligence Checklist for Founders, VCs, and Software Houses Before closing an institutional funding round or launching an enterprise SaaS application, complete this IP ownership audit: [ ] Audit All Historical Contributors: Review git commit logs across every repository. Identify every engineer who contributed code since the initial commit. [ ] Verify Signed Assignment Agreements: Confirm that every past and present employee, intern, freelancer, and vendor has executed a valid, signed written assignment under Section 14. [ ] Execute Retroactive Confirmatory Assignments: If early developers wrote code without contracts, execute a formal Confirmatory Deed of Copyright Assignment supported by nominal consideration to cure the title defect. [ ] Segregate Background IP: Ensure agency vendor contracts explicitly list pre-existing frameworks and grant perpetual, royalty-free commercial licenses. [ ] Enforce Strict OSS Compliance: Scan repositories using automated license auditors to confirm zero contamination from GPL/AGPL copyleft libraries. [ ] Secure Cryptographic Infrastructure: Mandate company-owned hardware, enforce Single Sign-On (SSO) with multi-factor authentication, and ensure individual developers never possess unmonitored sole custody of cloud infrastructure. [ ] Register Flagship Platforms: File formal copyright applications with IPO-Pakistan for your core proprietary platforms to secure conclusive statutory certificates of ownership. --- Conclusion: Securing Your Enterprise Technology Assets Source code is the foundational economic engine of modern tech enterprises. Allowing developers or external contractors to build your company’s core technology without executing airtight intellectual property assignment agreements is corporate Russian roulette. Under the Copyright Ordinance, 1962, clear statutory protocols exist to secure flawless corporate title. Implementing comprehensive employee invention assignment agreements, freelancer deeds of assignment, and IPO-Pakistan copyright registrations transforms vulnerable code into valuable, fundable, and unassailable intellectual property. For strategic advice on software copyright registration, developer assignment drafting, open-source compliance, or emergency source code recovery litigation, contact our Technology & IP Practice Group at TaxCalc.pk / Zaidi & Associates.