Introduction
From customer lists and financial datasets to legal databases, e-commerce catalogues and datasets used in artificial intelligence, databases have become commercially valuable assets in the digital economy. Their growing economic importance raises a fundamental intellectual property question: if an individual or company spends substantial time, money and resources collecting, verifying and maintaining information, to what extent can the law prevent others from extracting and commercially exploiting that information? In India, the answer does not lie in a standalone database right. Indian law recognises computer databases within copyright law, but unlike the European Union, it does not provide a separate sui generis right protecting investment in databases. Protection must instead be assembled through copyright, confidentiality, contract, technological restrictions and other legal regimes.
Copyright Protection of Databases in India
The principal source of database protection in India is the Copyright Act, 1957, forming a central component of copyright law in India. Section 2(o) defines a “literary work” to include computer programmes, tables and compilations, including computer databases. A database can therefore constitute copyrightable subject matter. However, inclusion within the definition of literary work does not mean that every collection of information automatically receives copyright protection. Section 13 protects “original” literary works, making originality central to the inquiry. What matters is therefore not simply the existence of a database or the expenditure incurred in creating it, but whether the compilation possesses the degree of originality required by copyright law.
An important early Indian decision on database protection is the Delhi High Court’s judgment in Burlington Home Shopping Pvt. Ltd. v. Rajnish Chibber. The plaintiff was in the mail order business and had compiled a database of names and addresses of customers. A former employee is alleged to have copied the database and passed it to a rival company. The Court accepted the labour and skill involved in compiling the database and concluded that the compilation of addresses was susceptible of copyright protection. Another piece of evidence in favour of copying was the fact that the plaintiff’s database had identical entries with the same mistakes. The ruling set the precedent that compilations of commercially valuable information could be protected under Indian copyright law. But the later evolution of the originality standard significantly qualified the extent to which labour and investment alone may justify copyright protection.
The Originality Threshold after Eastern Book Company v. D.B. Modak
The Supreme Court substantially clarified India’s originality standard in Eastern Book Company v. D.B. Modak. The dispute concerned copy-edited versions of Supreme Court judgments published by Eastern Book Company in Supreme Court Cases. Since the underlying judicial decisions themselves could not become the publisher’s private property merely through publication, the Court had to determine whether the editorial additions and modifications made by the publisher possessed sufficient originality to attract copyright.
The Supreme Court rejected a pure ‘sweat of the brow’ approach under which copyright could arise simply because of the substantial labour, time or expenditure that had gone into producing a work. At the exact same time, it didn’t require a high degree of creativity. The Court set forth a standard of exercise of skill and judgement that involved at least a minimal degree of creativity. No automatic copyright would result from mere mechanical labour. This principle has important implications for databases, because many commercially valuable databases are the product of large investment but the highly systematic or mechanical gathering of factual information.
For example, a company may spend crores of rupees in collating publicly available information about restaurants across India. Employees can collect names, addresses, phone numbers and opening hours and enter them into pre-defined fields. The database may be commercially valuable and extremely expensive to maintain but expense alone does not necessarily establish copyright over the information. The position is stronger where the company selects information independently according to particular criteria, develops an original classification system, exercises its judgement in organising the material, produces original descriptions or otherwise imparts an original structure to the compilation. Therefore, after EBC v. Modak, the important question is not just the amount of investment that went into creating the database, but what original skill, judgement and creativity went into its selection or arrangement.
Protection of the Database Does Not Mean Ownership of the Facts
There is also a significant difference between copyright in a database as a compilation and rights in the information contained in the database. Copyright protects original expression and, where appropriate, the original selection or arrangement, but does not normally give ownership of facts themselves. The fact that an organization first records a telephone number, geographical coordinate, market price, sporting result or other fact in a database does not mean that it is privately owned.
For example, a company that does sports analytics may have a very sophisticated database with thousands of statistics on cricket. Copyright may subsist in the manner in which statistics are organised, classified, commented on, presented or selected, if it is sufficiently original. A competitor who copies those protected elements may therefore be liable for infringement. However, the copyright in the database does not necessarily give the company an exclusive right over the historical fact that a particular player scored a particular number of runs in a match. This distinction has become relevant when web scraping, data analytics and artificial intelligence, since businesses may want to access the factual information in a database while not copying its original expressive structure.
The Missing Layer: Sui Generis Database Protection
The difference between copyright protection and investment protection becomes particularly clear when India is compared with the European Union. The EU’s Directive 96/9/EC on the Legal Protection of Databases establishes two distinct forms of protection. First, copyright may protect databases that, by reason of the selection or arrangement of their contents, constitute the author’s own intellectual creation. Second, Article 7 creates a separate sui generis database right where there has been qualitatively or quantitatively a substantial investment in obtaining, verifying or presenting the contents of a database.
The difference between these two rights is important. Copyright focuses primarily on originality, whereas the sui generis regime protects qualifying investment in the database. Consequently, a database may fail to satisfy the originality requirement for copyright while potentially qualifying for sui generis protection because substantial resources were invested in obtaining, verifying or presenting its contents. Subject to the Directive’s conditions and limitations, the database maker can prevent extraction or reutilisation of all or a substantial part of those contents. The Directive also acknowledges repeated and systematic extraction or reutilisation of insubstantial parts where such conduct conflicts with the normal exploitation of the database or unreasonably prejudices the legitimate interests of its maker.
India has no equivalent standalone statutory right. The Copyright Act expressly acknowledges computer databases as potential literary works, but substantial investment in collecting or maintaining information does not independently create an exclusive database right. This produces a potential “investment gap”: a business may devote considerable resources to constructing a commercially valuable database while receiving only limited copyright protection if its selection or arrangement lacks sufficient originality. Indian businesses must therefore look beyond copyright to protect the economic value of their datasets.
Confidentiality and Trade Secrets
One of the most important ways of addressing this gap is through confidentiality, especially in the case of a database that is not open to the public. The value that can be derived from secrecy applies to customer lists, supplier details, proprietary pricing information, market intelligence, business analytics and internal datasets. In these situations, the legal question is not primarily whether each item of information separately falls within the scope of copyright, but rather whether the confidential information has been obtained, made public or used in violation of an obligation of confidence.
The distinction was also important in Burlington Home Shopping, since the customer database which had commercial value had been accumulated and kept by the company and was allegedly obtained by a former employee. At present Indian law does not have a comprehensive independent trade-secret statute; protection for trade secrets and confidential information is instead mainly based on contractual obligations, on the equitable principles concerning breach of confidence and on the power of the courts to enforce confidential relationships. Such protection can be highly effective from a commercial point of view since it does not necessarily require proof of copyright for each individual item of information. The main drawback, however, is that information which has actually entered the public domain can no longer generally be treated as confidential. A restricted internal customer database is therefore legally distinct from a publicly accessible database of information obtainable from independent sources.
Contractual Protection
Contract law also offers a further level of protection for databases. Owners of databases are able to control the way in which authorised users access and make use of the information by means of subscription agreements, licensing arrangements, website terms of use, API agreements and confidentiality clauses within employment contracts. A database provider might allow subscribers to search and use the information for certain purposes while at the same time prohibiting them contractually from carrying out bulk downloads, scraping, redistribution or commercial resale. It is therefore possible for a contract to safeguard commercial interests even if copyright offers only an incomplete remedy.
Even so, contractual protection has certain structural limitations. A contract normally only obliges the parties to whom the obligations apply, while intellectual property rights have a wider reach and apply to third parties as well. In the case where someone obtains the information independently and is not bound by the database owner’s contractual restrictions, it may become considerably more difficult to enforce those restrictions. As a result, contract serves to supplement copyright but does not establish a similar proprietary right over the underlying contents of the database.
Technological Measures and Cyber Law
Businesses also increasingly rely on technological architecture to protect databases. Authentication systems, API keys, rate limits, access controls, anti-scraping mechanisms and automated monitoring can restrict how information is accessed and extracted. These measures can be particularly important where intellectual property law does not prohibit every form of reuse. Rather than claiming ownership over every underlying fact, the database operator controls the technical means through which users obtain access to the information.
Certain forms of unauthorised extraction may also engage the Information Technology Act, 2000. Section 43 addresses specified conduct involving computers and computer systems, including accessing or securing access without permission and downloading, copying or extracting data in specified circumstances. However, cyber law should not be treated as a substitute for a sui generis database right. The two regimes address different legal interests. A database right regulates defined forms of extraction and reutilisation of a protected database, whereas cyber-law provisions principally address conduct relating to access to computers, systems and data. A person lawfully obtaining publicly available information therefore presents a different legal problem from someone bypassing restricted access to obtain a confidential database.
Data Protection as a Separate Regulatory Layer
Where databases contain personal data, India’s data-protection framework creates another relevant legal layer. However, data protection must be distinguished from database ownership. Privacy and data-protection law primarily regulates the processing of personal data and protects the interests of individuals to whom that information relates. It does not ordinarily give the organisation maintaining a database an intellectual property right over that information. Consequently, data-protection obligations may restrict how personal information can be collected, processed or transferred, but they do not perform the same function as copyright or an EU-style sui generis database right.
Databases, Web Scraping and Artificial Intelligence
The limitations of India’s current framework are becoming particularly visible with the growth of artificial intelligence and large-scale web scraping. Consider a company that spends several years assembling millions of publicly accessible product prices, scientific measurements, legal materials or other factual records. Another company may seek to extract those records to train an AI system or develop a competing analytical product without reproducing the original database interface or arrangement. Indian law does not provide a single database-right test capable of resolving the dispute.
Instead, several separate questions arise. The database may or may not contain sufficiently original selection or arrangement to attract copyright. The material extracted may or may not reproduce protected expression. Access may have been governed by contractual restrictions. Technological barriers may have been bypassed. Some information may have been confidential, while other information may have been publicly accessible. The dataset may also contain personal data subject to separate regulatory requirements. The answer to each question may differ. This fragmentation demonstrates the structural consequence of India’s approach: substantial investment in constructing a database does not, by itself, create a general proprietary right over its contents.
Does India Need a Sui Generis Database Right?
There is a plausible economic argument for introducing greater database protection. Data-intensive businesses can invest substantial resources in collecting, verifying, cleaning, updating and maintaining information. If competitors can appropriate the commercially valuable output of that investment without reproducing copyright-protected elements, firms may have weaker incentives to invest in high-quality datasets. A carefully designed database right could potentially strengthen investment incentives in sectors such as financial information, scientific research, mapping, legal technology and artificial intelligence.
The counterargument is equally significant. Facts and data are fundamental inputs for research, competition and innovation. Creating broad proprietary rights over databases could increase costs for researchers, journalists, start-ups, competitors and AI developers and potentially allow private actors to construct legal barriers around information that copyright law deliberately leaves available for reuse. The European model should therefore not automatically be viewed as a gap that India must replicate. It represents a particular policy decision to protect certain investments in databases independently of copyright originality. Whether India should adopt similar approach requires balancing incentives for database creation against competition, access to information and downstream innovation.
Conclusion
Database protection in India is best understood as a layered framework rather than a single proprietary right. The Copyright Act, 1957 provides the foundation by expressly including computer databases within literary works. However, Eastern Book Company v. D.B. Modak demonstrates why investment, labour and expenditure cannot automatically substitute for originality. Copyright may prevent original selection, arrangement or other expressive elements of a database without necessarily conferring ownership over the underlying facts.
The leftover commercial interests are protected, where the relevant requirements are satisfied, through confidentiality and trade-secret principles, contractual restrictions, technological access controls, information-technology law and data-protection regulation. Each regime performs a different function: copyright protects qualifying original expression and compilation; confidentiality protects information possessing the necessary confidential character; contract regulates permitted use between parties; cyber law addresses specified forms of unauthorised access or extraction; and data-protection law governs the processing of personal data.
What India does not presently provide is the additional layer found in the European Union: an independent sui generis right directed at substantial investment in obtaining, verifying or presenting database contents. As databases become increasingly valuable and AI technologies make large-scale extraction and reuse easier, this distinction is likely to become more consequential. The central policy question is therefore not whether Indian law protects databases, it plainly can but whether the existing combination of legal protections achieves the appropriate balance between rewarding investment in data and maintaining access to facts and information as essential inputs for competition, research and innovation.
