The protection of computer programs under intellectual property law is one of the most consequential and contested questions in the history of modern legal systems. Software drives virtually every sector of the contemporary economy – from financial systems and medical devices to communications infrastructure and consumer entertainment. The legal framework that governs who owns software, what rights that ownership confers and how those rights may be enforced determines the incentive structures for an industry whose global output runs into trillions of dollars annually. Getting that framework right – protecting genuine creative investment while preserving the freedom to build, compete and innovate – is among the most important challenges that intellectual property law faces.
India’s approach to this question locates computer programs within the copyright framework rather than the patent system, a choice that aligns Indian law with the consensus position of the major international intellectual property agreements and with the domestic legislation of most significant software-producing jurisdictions. The Copyright Act, 1957, as amended in 1994 and again in 2012, treats computer programs as a species of literary work, grants their authors a comprehensive bundle of exclusive rights and provides a set of specifically calibrated exceptions designed to permit legitimate uses – backup copying, interoperability research, security testing – that would otherwise fall within the scope of those rights. Understanding this framework, its historical development, its specific provisions and its judicial interpretation is essential for any practitioner, developer or enterprise operating in India’s technology sector.
This article offers a comprehensive examination of copyright in computer programs under Indian law – moving through the legislative history, the statutory definition and classification of programs as literary works, the conditions for copyright subsistence, the ownership rules, the exclusive rights and their specific content, the exceptions carved out for legitimate use, the enforcement mechanisms available to rights holders, the treatment of open source software and the emerging questions raised by artificial intelligence-generated code.
Legislative History – From Analogue Statute to Digital Framework
The Copyright Act, 1957 was enacted in a technological environment in which computers were large institutional machines, software was inseparable from the hardware on which it ran and the question of whether programs deserved independent intellectual property protection had barely been posed. The Act made no mention of computer programs in its original form. The first legislative recognition of software within the Indian copyright framework came through the Copyright (Amendment) Act, 1984, which amended the definition of “literary work” in Section 2(o) to include computer programmes recorded on any disc, tape, perforated media or other information storage device – a formulation that tied the protection of software to its physical fixation on a tangible medium.
The technological limitations of the 1984 formulation became apparent as computing evolved and software ceased to be predominantly distributed on physical media. The Copyright (Amendment) Act, 1994 undertook a more fundamental revision of the software provisions, amending Section 2(o) to its current form, which includes computer programmes, tables and compilations including computer databases within the definition of literary work without any reference to physical medium. The 1994 amendment also introduced specific exceptions tailored to computer programs under what are now Sections 52(1)(aa), (ab) and (ac), recognizing that the standard literary work exceptions were inadequate to address the particular uses – backup copying, interoperability research, reverse engineering – that software requires.
The Copyright (Amendment) Act, 2012 made further changes relevant to software, primarily in the context of technological protection measures and rights management information. Section 65A prohibits the circumvention of effective technological protection measures applied to a work, including software. Section 65B prohibits the removal or alteration of rights management information attached to a work. These provisions were directed at the digital piracy environment and at the protection of digital rights management systems – technologies widely used to control access to and copying of commercial software products.
The trajectory of Indian copyright legislation in relation to software reflects a progressive engagement with the specific characteristics of software as a creative and commercial product, moving from the initial assimilation of programs into the literary work category through the development of software-specific exceptions to the protection of technical enforcement measures. The framework that results is workable, broadly aligned with international standards, and, in important respects, more nuanced than a simple application of literary copyright principles would produce.
Computer Programs as Literary Works – The Statutory Classification
Section 2(o) of the Copyright Act, 1957 defines “literary work” as including computer programmes, tables and compilations including computer databases. The use of “including” rather than “meaning” confirms that the definition is illustrative and that literary works encompass other categories of text-based creation beyond those listed. The inclusion of computer programs within the literary work category is the foundational choice of the Indian software copyright framework and it carries significant doctrinal consequences.
The classification of programs as literary works means that they attract the same term of protection, the same ownership rules and the same bundle of exclusive rights as novels, poems, technical manuals and other forms of literary expression – subject to the specific exceptions introduced by the 1994 amendments. It also means that the requirement of originality applicable to literary works governs the subsistence of copyright in programs, that the first ownership rules under Section 17 and its provisos apply to software creation and that the moral rights provisions of Section 57 are, in principle, available to program authors.
The literary work classification also has significant limitations. Literary copyright protects expression, not ideas. The idea-expression dichotomy – the principle that copyright subsists in the particular way in which an author has expressed an idea, not in the idea itself – applies with full force to computer programs. The algorithm that a program implements, the logical structure of the processing it performs, the functional objective it achieves – none of these are protected by copyright. What is protected is the specific source code in which the programmer has expressed the program and to a more limited extent the object code into which that source code is compiled. A competitor who independently writes a program that performs the same function through different code does not infringe the copyright in the original program, even if the two programs are functionally equivalent and achieve identical results.
This limitation is commercially significant and practically important. It means that copyright alone is an imperfect vehicle for the protection of software innovation. The functional value of a program – the efficiency of its algorithms, the novelty of its data structures, the cleverness of its computational approach – lies precisely in the domain that copyright does not protect. Software companies that wish to protect genuine technical innovation in their programs must look to trade secret law, which protects confidential source code against misappropriation and potentially to patent law for the protection of technical inventions that meet the specific and demanding requirements of patentability under Indian law – a topic examined elsewhere on this platform.
The Requirement of Originality
Copyright subsists in a literary work if it is original. Section 13(1)(a) of the Copyright Act provides that copyright shall subsist in original literary, dramatic, musical and artistic works. The Act does not define “original” but Indian courts, drawing on the common law tradition, have held that originality in copyright law requires that the work originate from the author – that it be the product of the author’s independent effort and not copied from another source – without requiring that it display any particular level of creative achievement or aesthetic merit.
The Supreme Court’s decision in Eastern Book Company v. D.B. Modak (2008) addressed the originality requirement in the specific context of a compilation – a category closely related to computer programs in that both involve the selection and arrangement of elements. The Court held that the standard of originality in India requires not mere labour and effort but a “minimal degree of creativity” – a departure from the pure “sweat of the brow” approach and an alignment with the creativity-based standard adopted in the United States in Feist Publications v. Rural Telephone Service (1991). The Court held that a work displaying no creative selection, arrangement or expression – one that is entirely mechanical in its production – does not attract copyright protection, even if its creation required substantial labour and investment.
Applied to computer programs, the Eastern Book Company standard means that copyright subsists in programs that reflect the programmer’s original creative choices in structuring, expressing and organizing the code – the choice of data structures, the design of algorithms, the organization of modules, the naming conventions, the commenting style, the overall architectural approach. A program that is purely mechanical – a direct and rote translation of a mathematical formula into executable code with no element of creative decision-making – may fall below the originality threshold, though in practice virtually any non-trivial program involves sufficient creative decision-making to satisfy the requirement comfortably.
The originality requirement has particular significance in the context of automatically generated code – programs produced by compilers, code generators, integrated development environments or artificial intelligence coding assistants. Where the “programmer” has done no more than specify inputs to an automated system that generates code mechanically, the question of whether the resulting program is the product of original human creative effort – and therefore capable of attracting copyright – becomes genuinely difficult. This question is examined further in the context of AI-generated code below.
Ownership of Copyright in Computer Programs
The rules governing first ownership of copyright in computer programs follow the general framework of Section 17 of the Copyright Act, with the provisos to that section playing a particularly important role in the software context.
Where a programmer creates a program independently – writing code in their personal capacity, without any employment relationship or commission from another party – the programmer is the first owner of the copyright in the program as a matter of course under the general rule of Section 17. Independent contractors who create software for their own purposes, individual developers who create open source contributions in their personal time and entrepreneurs who write code for their own startup products are all first owners of the copyright in their programs absent any contrary agreement.
The position changes dramatically where software is created in the course of employment. Proviso (b) to Section 17 provides that where a work is made by the author in the course of their 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 in the work. The practical consequence is that the overwhelming majority of commercially significant software – programs written by employees of technology companies in the course of their duties – is owned by the employing company rather than the individual programmers who wrote it. The developer who writes a feature for their employer’s product has no copyright in that code; it vests in the employer from the moment of creation.
The distinction between a contract of service (employment) and a contract for service (independent contracting) is legally significant but practically contested in the software industry, where the use of contractors, freelancers and outsourced development teams is pervasive. A programmer engaged as an independent contractor rather than as an employee does not, in the absence of an express assignment clause in the engagement contract, transfer copyright to the commissioning party under proviso (b). Proviso (c) to Section 17, which vests copyright in the commissioning party where a work is made in pursuance of a commission, may apply, but its scope is more limited and its operation depends on the specific circumstances of the engagement.
For software companies that commission development work from independent contractors – whether domestic freelancers, outsourced development teams or overseas service providers – the implication is clear and frequently overlooked: without an express written assignment of copyright in the engagement contract, the commissioning company may not own the copyright in the code it has paid for. This is one of the most practically important points in all of Indian software copyright law and it is a trap into which many technology businesses fall when they fail to include adequate intellectual property assignment clauses in their development contracts.
Joint Authorship and Collaborative Development
Modern software development is almost invariably collaborative. Enterprise applications are written by teams of dozens or hundreds of developers working on interconnected modules under version control systems. Open source projects involve contributions from geographically dispersed developers who may never interact directly. The copyright implications of this collaborative structure raise questions of joint authorship and joint ownership that the Copyright Act addresses imperfectly.
Section 2(z) of the Act defines a “work of joint authorship” as a work produced by the collaboration of two or more authors in which the contribution of one author is not distinct from the contribution of the other author or authors. This definition requires not merely collaboration but a specific form of non-severable collaboration – where the individual contributions are so intertwined that they cannot be separately identified and attributed. In many software development contexts, this condition is met: the code written by individual developers is merged into a shared codebase in a manner that makes individual attribution of specific lines or modules impractical.
Where a program is a work of joint authorship, the copyright vests in all the joint authors jointly. Each joint owner may independently licence the work on a non-exclusive basis but cannot assign the copyright or grant exclusive licences without the consent of all joint owners. In the corporate context, where all developers are employees and the employer is first owner of each employee’s contribution under the proviso to Section 17, joint authorship questions are absorbed into employer ownership and present no practical difficulty. In the open source context, where contributors retain their individual copyrights, the question of who may licence and on what terms the aggregate work of many contributors can become genuinely complex.
The Exclusive Rights in Computer Programs
Section 14(b) of the Copyright Act sets out the exclusive rights that constitute copyright in a computer program. These are the rights to do any of the acts specified in clause (a) – that is, the full range of literary work rights including reproduction, distribution, public performance, communication to the public, translation and adaptation – and additionally the right to sell or give on commercial rental or offer for sale or for commercial rental any copy of the computer programme. The proviso to Section 14(b) states that commercial rental does not apply in respect of computer programmes where the programme itself is not the essential object of the rental.
The commercial rental right is a right that does not exist for other literary works. Its inclusion in Section 14(b) reflects the specific economics of software distribution, where the ability to rent copies of a program could, if uncontrolled, substitute for sale and significantly damage the market for the work. The proviso that excludes cases where the program is not the essential object of the rental addresses situations where software is incidentally included in a rented product – a car with embedded software, a medical device with control software – and prevents the rental right from extending to every product that incorporates code.
The reproduction right in Section 14(a)(i) is the most practically significant right in the software context. Any copying of a program – whether to a hard drive during installation, to RAM during execution, to a backup medium for archival purposes or to a server for deployment – constitutes reproduction and falls within the copyright owner’s exclusive right absent a specific exception or licence. The scope of the reproduction right and the extent to which it is qualified by the specific software exceptions, is the central practical question in software copyright enforcement.
The adaptation right under Section 14(a)(vi) covers the creation of derivative programs based on the original. A programmer who modifies or extends an existing program without the copyright owner’s authorization is potentially infringing the adaptation right. This right is particularly significant in the context of software customization, where businesses frequently modify licensed software products to meet their specific requirements and in the context of software development tools that generate code based on existing templates or frameworks.
The communication to the public right under Section 14(a)(iii) is engaged by the making available of programs through software-as-a-service platforms, cloud computing environments and online software distribution channels. The upload of a program to a web server for access by users constitutes communication to the public and requires the authorization of the copyright owner. The deployment of pirated software in a cloud environment – a form of infringement that has grown as cloud computing has become the dominant model for software delivery – engages this right.
Exceptions Specific to Computer Programs
The 1994 amendment introduced three software-specific exceptions under Sections 52(1)(aa), (ab) and (ac) of the Copyright Act. These exceptions recognize that the standard fair dealing provisions are inadequate for the specific uses that software requires and they provide carefully calibrated permissions for backup copying, functional investigation and interoperability research. The fair dealing exception under Section 52(1)(a) expressly does not apply to computer programs – a deliberate exclusion that makes the three specific exceptions the only fair dealing-type protection available in the software context.
Section 52(1)(aa) permits the making of any copy or adaptation of a computer program by the lawful possessor of the copy of the program, if such copy or adaptation is necessary for the utilization of the program for the purpose for which it was supplied or for archival purposes and to protect against loss, destruction or damage in order only to be used in the event that the original copy of the computer programme becomes unusable. This provision protects the right of legitimate software users to make backup copies of programs they have lawfully acquired. A company that purchases a software licence and makes a backup copy on an archival server exercises this right. The exception is limited to the lawful possessor – a person who has obtained the copy without authorization cannot claim the backup right – and to purposes of utilization or archival protection. The backup copy cannot be distributed to others, used for commercial purposes or retained after the original copy becomes usable again.
Section 52(1)(ab) permits the doing of any act necessary to observe, study or test the functioning of a computer program in order to determine the ideas and principles which underlie any element of the program while performing the acts of loading, displaying, running, transmitting or storing the program. This provision addresses the specific question of whether running a program to study how it works infringes the copyright in the program. It provides that the acts of loading, displaying, running, transmitting and storing a program for the purpose of observing and studying its functioning are not infringement. The exception is limited in scope: it protects the act of observation and study but does not extend to the reproduction of the program’s code or to the creation of a competing program based on what is discovered. Its principal value is in protecting the legitimate analysis of programs for security research, competitive benchmarking and academic study.
Section 52(1)(ac) permits the making of copies or adaptations of a computer program for the purpose of interoperability of an independently created computer programme with other programmes. This is the most commercially significant of the three software exceptions and the one most frequently engaged in litigation. It protects reverse engineering of software for the purpose of achieving interoperability – the ability of independently created programs to work together. A developer who decompiles a proprietary program to understand the interfaces and protocols needed to create a compatible application exercises this right. The exception is modelled on the equivalent provisions in the European Software Directive and reflects the policy judgment that copyright in software should not be used as a tool to prevent the development of compatible or interoperable programs, particularly where the information needed for interoperability is not otherwise available.
The interoperability exception is narrow and conditions the permitted activity carefully. The decompilation or reverse engineering must be for the specific purpose of interoperability with an independently created program – not for any other purpose, including the creation of a competing program with equivalent functionality. The information obtained through the exercise may only be used for the interoperability purpose and may not be given to others unnecessarily or used to create a program that is substantially similar to the decompiled program. These limitations reflect the judgment that the interoperability purpose justifies the exception, while preventing the exception from becoming a general licence for reverse engineering and copying.
Technological Protection Measures and Section 65A
Section 65A of the Copyright Act, introduced by the 2012 amendment, provides that any person who circumvents an effective technological protection measure applied for the purpose of protecting any of the rights conferred by the Act, with the intention of infringing such rights, shall be punishable with imprisonment extending to two years and a fine. “Technological protection measure” means any technology, device or component that, in the normal course of its operation, controls access to a work or protects any of the rights under the Act.
The anti-circumvention provision is directed at the practical enforcement problem created by digital copying. A copyright owner who applies digital rights management technology to a software product – encryption that prevents unauthorized copying, access controls that limit use to licensed users, authentication systems that verify licence validity – would be substantially undermined if users could freely circumvent those technical protections. Section 65A makes circumvention a criminal offence, providing a legal complement to the technical protection.
Section 65A(2) provides a series of exceptions to the anti-circumvention prohibition, recognizing that some forms of circumvention serve legitimate purposes. The exceptions include circumvention for the purpose of doing acts permitted under the Act, for enabling interoperability with other programs as permitted under Section 52(1)(ac), for conducting encryption research, for enabling access to lawfully obtained programs by persons with disabilities who cannot otherwise access the work, for national security and law enforcement purposes and for testing the security of a computer or computer network with the authorization of its owner.
The encryption research exception and the security testing exception are particularly important in the software industry, where security researchers routinely probe the protections of software systems – with or without the authorization of the software owner – to identify vulnerabilities. Section 65A(2) provides a legal basis for authorized security testing that would otherwise potentially constitute both copyright infringement and circumvention of technological protection measures.
Key Cases in Software Copyright
Microsoft Corporation v. Yogesh Popat & Anr. (2007) is among the most important Indian decisions on software copyright infringement. The Delhi High Court granted an injunction against the sale of computers pre-loaded with unlicensed copies of Microsoft software, holding that the installation of software on computers for sale without the copyright owner’s authorization constituted infringement of the reproduction right. The decision affirmed that pre-installation of unlicensed software is infringement regardless of whether the infringer charges separately for the software or bundles it with hardware.
Microsoft Corporation v. Mr. Deepak Raval (2006) addressed the criminal dimensions of software piracy. The Delhi High Court held that wilful infringement of copyright in computer programs attracts criminal liability under Section 63 of the Copyright Act and that courts may take cognizance of such offences without a complaint from the rights holder. The decision reinforced the availability of criminal enforcement as a tool against commercial software piracy.
SAP AG v. Abhineet Jain (2010) involved the infringement of enterprise software copyright through unauthorized installation and use of SAP’s enterprise resource planning software. The Delhi High Court granted an injunction and awarded damages, holding that the unauthorized reproduction of enterprise software constitutes infringement regardless of whether the infringer uses the software for internal purposes or for commercial distribution.
Eastern Book Company v. D.B. Modak (2008) addressed the originality standard for compilations and computer databases – a category within the definition of literary work that overlaps significantly with software in its structural characteristics. The Supreme Court’s holding that Indian copyright law requires a minimal degree of creativity rather than mere labour – overruling the lower court’s application of the pure sweat of the brow standard – has direct implications for the copyrightability of software, particularly simple or formulaic programs.
Tata Consultancy Services v. State of Andhra Pradesh (2004) addressed the question of whether computer software is “goods” for the purposes of sales tax, a question with significant implications for the taxation of software transactions. The Supreme Court held that software, both packaged and customized, constitutes goods within the meaning of the relevant taxation statute. While this decision was not a copyright case, its characterization of software as a tangible commodity with intellectual property dimensions has informed subsequent discussions about the nature of software transactions in multiple regulatory contexts.
Crop Science Pty Ltd. v. P.K. Khaitan (2011) involved the misappropriation of source code by a former employee who used confidential programming developed in the course of employment to create a competing product. The Delhi High Court granted injunctive relief, holding that the source code constituted confidential information as well as a copyrighted literary work and that its unauthorized use by a former employee was both a breach of confidentiality and an infringement of copyright. The decision affirmed the availability of both copyright and trade secret remedies for source code misappropriation – a combination of remedies that provides comprehensive protection for software developers against employee theft of code.
Autodesk Inc. v. Mr. Prashant Goel (2010) involved the infringement of copyright in computer-aided design software through the sale of unlicensed copies. The Delhi High Court granted an injunction and significant damages, holding that the commercial distribution of unlicensed copies of software constitutes infringement and that the copyright owner is entitled to both compensatory and exemplary damages where the infringement is deliberate and commercial in character.
Source Code, Object Code and the Scope of Protection
A computer program exists in at least two forms: the source code – human-readable instructions written in a programming language by the programmer – and the object code – the machine-readable binary representation of those instructions generated by a compiler. The question of whether copyright protection extends to both forms and how the idea-expression dichotomy applies to each, has significant practical implications.
Indian law, consistent with international practice, protects both source code and object code as expressions of the program. The Act does not distinguish between the two forms and the definition of “computer programme” – examined below – is broad enough to encompass both. The object code is a transformation of the source code through compilation, but it is the same program in a different form and the copyright that subsists in the program extends to both its source and compiled representations.
The idea-expression dichotomy operates differently at the two levels. In source code, the expressive dimension is relatively clear – the programmer’s choices of variable names, function organization, commenting style, algorithm implementation and overall code structure are all expressive choices that copyright protects. In object code, the expressive dimension is less visible – the binary representation is generated mechanically by the compiler and reflects the structure of the source code only abstractly. However, courts in India and internationally have consistently held that object code is protected by copyright as an expression of the original program, regardless of its opacity to human readers.
The question of what constitutes a “substantial part” of a computer program for infringement purposes – a question that the Act addresses only obliquely through the general principle that copyright means the right to do or authorize the doing of acts in respect of a work or any substantial part thereof – is particularly difficult in the software context. In literary works, the substantial part inquiry examines the qualitative importance of what has been taken rather than merely its quantitative extent. Applied to software, this means that the copying of a small but critical module – the algorithm at the heart of a program’s functionality, the security module that defines its value – may constitute infringement of a substantial part even if the copied portion represents a small percentage of the total codebase.
Open Source Software and the Copyright Framework
Open source software – software distributed under licences that permit free use, modification and redistribution of the source code – presents a distinctive application of copyright principles. Open source is not an absence of copyright; on the contrary, it depends entirely on copyright for its legal effect. Open source licences are contractual instruments that grant permissions to users of software that would otherwise be reserved exclusively to the copyright owner. The permission to copy, modify and redistribute open source code is granted by the copyright owner through the licence terms and its exercise is conditional on compliance with those terms.
The most widely used open source licences include the GNU General Public License in its various versions, the MIT License, the Apache License, the BSD License and the Mozilla Public License. Each of these licences grants different permissions and imposes different conditions on the use of the licensed software. The copyleft licences – the GPL family – require that any derivative works be distributed under the same licence terms, creating a self-perpetuating open source requirement. The permissive licences – MIT, Apache, BSD – impose fewer conditions and permit the integration of open source code into proprietary products under certain circumstances.
The enforceability of open source licences under Indian law has not been definitively addressed by any Indian court. The general principles of contract law under the Indian Contract Act, 1872 apply and there is no doctrinal reason why open source licence terms should be unenforceable – they represent a valid offer of permissions conditional on acceptance of terms and acceptance occurs through the exercise of the licensed rights. The practical question of enforcement – whether an open source rights holder has standing to sue for licence violation, what remedy is available for a GPL violation that fails to release derivative source code and how damages would be assessed in the absence of a commercial transaction – remains unanswered in the Indian judicial context.
For technology companies in India that incorporate open source components in their commercial products – a near-universal practice in the software industry – understanding and complying with open source licence obligations is both a legal requirement and a practical necessity. The failure to comply with GPL obligations, for example, by incorporating GPL-licensed code in a proprietary product without releasing the combined source code, constitutes both a breach of the licence conditions and potentially an infringement of the copyright in the open source component. This risk is particularly acute for companies that use open source components without maintaining adequate records of what has been incorporated and under what licence terms.
Software as a Service and the Communication Right
The shift from packaged software distributed on physical media to software delivered as a service through the internet – the software-as-a-service model that now dominates enterprise software and consumer applications – has significant implications for the copyright analysis of software use. When a user accesses software-as-a-service, they do not download or install a copy of the program – they access the program remotely through a browser or client interface, with the program running on the service provider’s servers.
The copyright implications of this model differ from those of traditional software distribution in important respects. The user does not reproduce the program in the traditional sense – no permanent copy is created on the user’s device. The service provider, who runs the program on its servers, makes copies for the purpose of providing the service – a reproduction that requires the copyright owner’s authorization as part of the service licence. The communication to the public right under Section 14(a)(iii) is potentially engaged by the making available of the program to users through the service, though the precise application of this right to software-as-a-service – as distinct from the communication of content through a service – is not clearly established.
For software copyright owners, the transition to the SaaS model has both advantages and disadvantages. The advantage is that the program is never distributed in a form that can be copied and shared without authorization – the source code and compiled program remain on the service provider’s servers, inaccessible to users. The disadvantage is that the traditional licensing framework – per-seat licences, installation licences, volume licences – does not translate directly to a service model and new licensing structures that accurately reflect the SaaS model’s economic character must be developed.
Artificial Intelligence Generated Code – The Emerging Frontier
The rapid development of artificial intelligence tools capable of generating functional computer code – GitHub Copilot, OpenAI’s Codex, Google’s Gemini Code Assist and similar systems – has introduced questions about software copyright that Indian law is entirely unprepared to answer. These tools are trained on vast datasets of existing open source and publicly available code and they generate new code in response to natural language prompts or partial code inputs from developers. The legal questions they raise are fundamental and urgent.
The first question is whether AI-generated code can attract copyright protection at all. As discussed above, copyright in a literary work requires that the work be original – the product of the author’s independent creative effort. Where code is generated by an AI system in response to a developer’s prompt, the human contribution is the specification of the desired outcome rather than the creative act of writing the code. Whether this is sufficient to meet the originality requirement – and whether the developer who prompts the AI system is the “author” of the generated code within the meaning of Section 2(d)(i) – is a question that Indian courts have not addressed.
Section 2(d)(vi) of the Act, which provides that in the case of a computer-generated literary, dramatic, musical or artistic work, the author shall be the person who causes the work to be created, offers a partial answer. If AI-generated code is a “computer-generated literary work” within this provision, copyright vests in the person who causes the AI to create the code – presumably the developer who provides the prompt or specification. However, the adequacy of this provision for highly autonomous AI generation, where the human contribution is minimal and the system exercises substantial creative judgment, is doubtful. The provision was enacted in a context where “computer-generated” meant code produced by deterministic algorithms under direct human programming control, not by large language models trained on billions of lines of code.
The second question concerns the training data. AI coding tools are trained on large corpora of open source code. Where that code is licensed under terms that restrict its use – including use as training data for commercial AI systems – the training process may constitute infringement of copyright in the training code. This question is the subject of active litigation in the United States, where a class action has been filed against GitHub and Microsoft alleging that GitHub Copilot’s training on open source code and generation of code that reproduces licensed material violates the licences under which the training code was released. The resolution of this litigation will have significant implications for AI coding tools globally, including their legal status under Indian law.
The third question concerns the outputs of AI coding tools. Where an AI system generates code that reproduces or closely resembles copyrighted code from its training data – a phenomenon that has been demonstrated empirically – the generated code may itself infringe the copyright in the training code. This question involves the same issues of substantial copying and idea-expression dichotomy that arise in conventional software copyright infringement analysis, but applied to outputs generated by a system that has been trained on the copyrighted work rather than directly copied from it.
These questions will shape the legal landscape for AI-assisted software development in India over the coming decade. In the absence of statutory guidance and judicial precedent, practitioners and technology companies must navigate significant uncertainty – an uncertainty that is likely to persist until either the legislature intervenes or the courts are presented with cases that require direct engagement with these issues.
Criminal and Civil Enforcement
The enforcement framework for copyright in computer programs combines civil remedies under the general provisions of the Copyright Act with criminal penalties that reflect the commercial scale of software piracy in India.
The civil remedies available under Section 55 of the Act include injunctions, damages or an account of profits at the plaintiff’s election and delivery up of infringing copies and the materials used to make them. In software copyright cases, injunctions are the remedy most commonly sought at the interim stage – the combination of the low marginal cost of software reproduction and the high speed at which infringing copies can be distributed means that a delay between filing suit and obtaining relief can result in catastrophic commercial harm to the rights holder. Indian courts, including the Delhi High Court and Bombay High Court, have routinely granted ex parte interim injunctions in commercial software infringement cases where the rights holder can demonstrate a prima facie case of infringement and the risk of irreparable harm.
The Criminal penalties under Section 63 of the Act provide for imprisonment for a term not less than six months but which may extend to three years and a fine not less than fifty thousand rupees but which may extend to two lakh rupees, for wilful infringement of copyright. Section 63B provides specific enhanced penalties for the knowing use of infringing copies of computer programs – imprisonment of a minimum of seven days but up to three years and a fine of not less than fifty thousand rupees. The inclusion of a minimum sentence and minimum fine in Section 63B reflects the legislative judgment that software piracy is a serious commercial crime warranting mandatory custodial punishment.
The search and seizure powers under Section 64 permit a police officer not below the rank of sub-inspector to seize without warrant all copies of a work in respect of which they have reason to believe that copyright has been infringed, along with all plates used or likely to be used for making infringing copies. In the software context, “plates” extend to hard drives, servers and any other storage media used to store or distribute infringing copies. These powers have been actively used in anti-piracy raids conducted by rights holders in cooperation with law enforcement agencies.
Conclusion
Copyright in computer programs under Indian law is a framework of considerable depth and practical importance. The classification of programs as literary works, established by legislative amendment and affirmed by judicial interpretation, provides a solid doctrinal foundation that aligns Indian law with international standards and gives software developers a comprehensive set of rights in their creative work. The software-specific exceptions – for backup copying, functional study and interoperability – provide necessary flexibility for legitimate use without undermining the rights holder’s core economic interests. The anti-circumvention provisions protect the technical enforcement measures that rights holders deploy in the digital environment.
The challenges that remain are real and growing. The idea-expression dichotomy, the originality threshold and the substantial part inquiry all require continued judicial development as software grows in complexity and ubiquity. The open source ecosystem raises enforcement questions that Indian courts have not yet been asked to resolve. The software-as-a-service model requires a rethinking of the licensing concepts through which software rights are commercially exercised. And the emergence of artificial intelligence as a tool for code generation introduces questions about authorship, originality and training data that the current statutory framework is fundamentally ill-equipped to answer.
For practitioners advising technology companies, developers and enterprises in India, this framework is the foundation of every software rights analysis. Understanding it – its provisions, its exceptions, its judicial interpretation and its limits – is the starting point for effective legal advice in an industry whose products and processes are increasingly central to every aspect of economic and social life.
References
- The Copyright Act, 1957, Sections 2(d)(vi), 2(o), 13, 14(a), 14(b), 17, 52(1)(aa), 52(1)(ab), 52(1)(ac), 55, 63, 63B, 64, 65A, 65B – https://copyright.gov.in/Documents/CopyrightRules1958.pdf
- The Copyright (Amendment) Act, 1994 – https://copyright.gov.in
- The Copyright (Amendment) Act, 2012 – https://copyright.gov.in/Documents/Amendment_Act2012.pdf
- Eastern Book Company v. D.B. Modak, (2008) 1 SCC 1 (Supreme Court of India) – https://indiankanoon.org/doc/1023365/
- Tata Consultancy Services v. State of Andhra Pradesh, (2004) 3 SCC 98 (Supreme Court of India) – https://indiankanoon.org/doc/1536697/
- Microsoft Corporation v. Yogesh Popat & Anr. (2007), Delhi High Court – https://indiankanoon.org/doc/1598285/
- Microsoft Corporation v. Mr. Deepak Raval (2006), Delhi High Court – https://indiankanoon.org/doc/1054528/
- SAP AG v. Abhineet Jain (2010), Delhi High Court – https://delhihighcourt.nic.in
- Autodesk Inc. v. Mr. Prashant Goel (2010), Delhi High Court – https://indiankanoon.org/doc/1317128/
- Crop Science Pty Ltd. v. P.K. Khaitan (2011), Delhi High Court – https://delhihighcourt.nic.in
- Feist Publications Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991) – https://supreme.justia.com/cases/federal/us/499/340/
- Berne Convention for the Protection of Literary and Artistic Works – https://www.wipo.int/treaties/en/ip/berne/
- TRIPS Agreement, Article 10 – https://www.wto.org/english/docs_e/legal_e/27-trips.pdf
- WIPO Copyright Treaty, 1996, Article 4 – https://www.wipo.int/treaties/en/ip/wct/
- EU Software Directive (Directive 2009/24/EC) – https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009L0024
- Copyright Office of India – https://copyright.gov.in
Compulsory Licensing Copyright Act Copyright Act 1957 Copyright Infringement Copyright Law Copyright Rules Deceptive Similarity Indian IP Framework Indian Patent Law Indian Trademark Law Intellectual Property Law IP Law India Patent Claims Patent Enforcement Patent Infringement Patent law Patent Revocation Patent Rule Patents Act 1970 Section 3 Section 29 The Patent Act 1970 Trademark Infringement Trademark Registration Trade Marks Act 1999 Trade Marks Rules 2017 TRIPS Compliance