Citation: (2008) 105 DRJ 721; 150 (2008) DLT 769; 2008 (6) AD (Del) 381 (Delhi High Court, 29 May 2008)
Jurisdiction: High Court of Delhi, exercising inherent jurisdiction under Section 482 of the Code of Criminal Procedure 1973
Bench: Justice S. Muralidhar (Single Judge)
Parties: Avnish Bajaj (Petitioner, Managing Director of Baazee.com India Pvt Ltd) v State (NCT of Delhi) (Respondent)
I. Introduction
The decision of the Delhi High Court in Avnish Bajaj v State (NCT of Delhi) occupies a foundational place in Indian cyber jurisprudence as one of the earliest judicial attempts to grapple with criminal liability of intermediaries and their officers for third-party content hosted on digital platforms.[1] Delivered at a time when the Information Technology Act 2000 had barely been tested in the criminal courts, the judgment was forced to answer a question for which Indian law possessed no settled answer: when an anonymous user lists illegal content on an online marketplace, who bears the criminal consequence , the platform, its managing director, both, or neither?
The case arose out of the listing of an obscene MMS clip on Baazee.com (an online auction website later acquired by eBay), and culminated in criminal proceedings against the company’s Managing Director, Avnish Bajaj, personally. The judgment is significant not merely for its outcome but for the manner in which it exposed the inadequacy of India’s pre-2008 intermediary liability regime, and for the legislative correction it precipitated. This comment examines the facts, the Court’s reasoning, and the broader doctrinal and policy implications of the decision, before situating it within the trajectory of subsequent case law, particularly the eventual disposal of the connected proceedings by the Supreme Court.
II. Facts of the Case
On 27 November 2004, at approximately 8:30 PM, Ravi Raj, a student of the Indian Institute of Technology, Kharagpur, using the pseudonym “alice-elec,” listed an item for sale on Baazee.com described as “DPS Girls having fun!!! full video + Baazee points.” The listing offered, for a price, a video clip purportedly depicting two minor students of a Delhi school engaged in a sexually explicit act, which was to be delivered to purchasers as an email attachment rather than hosted on the website itself.
Although Baazee.com maintained automated content filters intended to detect and block objectionable listings, the filters failed to flag the item, in part because terms such as “sexual,” “dps,” and “RKP” were either absent from or inadequately weighted in the filter’s keyword list. The listing therefore remained active on the platform. On 27 November 2004, a user alerted the company through its “Community Watch” mechanism that the listing was pornographic. The company nonetheless did not deactivate the item until the morning of 29 November 2004 , a gap of approximately thirty-eight hours , during which period eight identifiable buyers across different Indian cities purchased the clip, the company having earned a commission on each transaction.
Following media attention and a police complaint, the Delhi Police Crime Branch registered a First Information Report and investigated the matter. A chargesheet was filed naming three accused: Ravi Raj (the seller), Avnish Bajaj (Managing Director of Baazee.com India Pvt Ltd, later renamed eBay India Pvt Ltd), and Sharat Digumarti (Head of Trust and Safety, responsible for content moderation). The Metropolitan Magistrate, by an order dated 14 February 2006, took cognizance of offences under Sections 292 and 294 of the Indian Penal Code 1860 and Section 67 of the Information Technology Act 2000, and summoned all three accused for trial.[2] Ravi Raj remained absconding throughout the proceedings. Bajaj, who had earlier been granted bail by the Delhi High Court in December 2004,[3] filed the present petition under Section 482 of the Code of Criminal Procedure 1973 seeking quashing of the criminal proceedings against him in his personal capacity.
III. Issues Before the Court
• Whether a prima facie case under Section 292 of the Indian Penal Code (sale and distribution of obscene material) was made out against Baazee.com India Pvt Ltd, and derivatively against Avnish Bajaj as its Managing Director.
• Whether a prima facie case under Section 67 of the Information Technology Act 2000, read with Section 85 of that Act (offences by companies), was made out against Bajaj personally.
• Whether Indian criminal law recognises an automatic or vicarious liability attaching to a company director for offences attributed to the company, particularly where the company itself has not been arraigned as an accused.
• Whether the conduct in question amounted to “publishing” or “transmitting” obscene material within the meaning of Section 67 of the IT Act, given that the video clip itself was never hosted on or transmitted through the website, only the textual advertisement.
IV. Arguments of the Parties
Petitioner’s submissions: Counsel for Bajaj, led by Mr Arun Jaitley and Mr Sidharth Luthra, Senior Advocates, contended that the obscene video clip was never hosted on Baazee.com; only a textual listing was displayed, and the clip itself was transmitted directly between seller and buyer as an email attachment outside the platform’s control. It was argued that the Indian Penal Code does not recognise any doctrine of automatic vicarious criminal liability of a director for offences of a company, particularly where the company itself had not been made an accused[4] , relying on the Supreme Court’s ruling in State of Madras v C V Parekh and on the constitutional bench decision in Standard Chartered Bank v Directorate of Enforcement regarding corporate criminal liability.[5] Counsel further argued that even if Section 85 of the IT Act created a basis for deemed liability of persons in charge of a company, such liability presupposed that an offence had first been established against the company, and could not be invoked to prosecute a director where the company itself was not a party to the prosecution.[6]
Respondent’s submissions: The State, represented by Ms Mukta Gupta, Senior Standing Counsel, argued that the website had constructive knowledge of the obscene listing through its own Community Watch alert mechanism, that its filters were demonstrably inadequate (failing to catch even explicit keywords), and that the company continued to profit from the transaction by charging commission even after acquiring knowledge of the listing’s nature. It was submitted that this combination of inadequate due diligence, actual or imputed knowledge, and continued commercial benefit was sufficient to make out a prima facie case of strict liability against the company under Section 292(1) IPC, and that Section 85 of the IT Act independently created liability for persons “in charge of and responsible to the company for the conduct of its business” at the relevant time, regardless of whether the company itself was separately arraigned.
V. Judgment / Holding
The Delhi High Court partially allowed the petition. With respect to the Indian Penal Code offences under Sections 292 and 294, the Court discharged Avnish Bajaj, holding that the Penal Code does not recognise a concept of automatic criminal liability attaching to a company director merely by virtue of his office, where the company itself had not been arraigned as an accused.[7] However, the Court declined to quash the proceedings under Section 67 read with Section 85 of the Information Technology Act 2000, holding that a prima facie case survived against Bajaj on this limb, since Section 85 of the IT Act , unlike the general provisions of the Penal Code , expressly creates a statutory mechanism of deemed liability for persons in charge of a company’s business at the time an IT Act offence is committed, irrespective of whether the company is separately arraigned.[8] The proceedings under Section 67 of the IT Act against Bajaj were therefore allowed to continue, while bail conditions previously imposed were continued.
VI. Ratio Decidendi
The binding principle that emerges from the judgment is twofold. First, the general principles of corporate criminal liability under the Indian Penal Code do not permit a director to be prosecuted vicariously for an offence attributed to the company unless the company itself is made an accused, since the Code contains no provision analogous to Section 141 of the Negotiable Instruments Act 1881[9] or Section 85 of the IT Act that statutorily deems such liability.[10] Second, where a special statute such as the Information Technology Act contains its own deeming provision for offences by companies (Section 85), that provision can sustain a prima facie case against a person in charge of the company’s affairs even without the company being separately arraigned as an accused, provided the chargesheet sets out specific averments connecting that individual to knowledge of, or responsibility for, the contravention.[11]
VII. Critical Analysis and Observations
The reasoning in Avnish Bajaj, while doctrinally coherent on the narrow question of corporate criminal liability, reveals a deeper and more troubling tension in how Indian law approached intermediary regulation in the pre-2008 era , a tension this comment considers from several angles.
First, the inconsistency between the IPC and IT Act findings deserves scrutiny. The Court’s bifurcated approach , discharging Bajaj under the Penal Code while sustaining the IT Act charge , produces an anomalous result on facts that are, in substance, identical. The underlying conduct attributed to Bajaj (his position as Managing Director and his asserted knowledge of the listing through the Community Watch mechanism) is the same under both statutes; what differs is purely the existence of a deeming provision in one statute and its absence in the other. This suggests that the outcome in Avnish Bajaj turned less on any considered judgment about Bajaj’s actual culpability and more on an accident of statutory drafting. A regime in which criminal liability for substantively identical conduct depends on which of two overlapping penal statutes happens to contain a vicarious liability clause is difficult to defend as principled criminal jurisprudence, and arguably exposed company officers to selective and unpredictable prosecution.
Second, the judgment under-theorises the distinction between a host and a publisher. A central feature of the case , repeatedly stressed by the defence but not squarely resolved by the Court at the Section 482 stage , is that the obscene video clip itself was never hosted on or transmitted through Baazee.com; only a textual advertisement was displayed, while the clip was exchanged directly between buyer and seller by email. Treating the operator of a marketplace that merely displayed a sale advertisement as potentially as culpable as the seller who actually transmitted the obscene material blurs a distinction that is fundamental to almost every comparable intermediary liability regime, including the United States’ Communications Decency Act[12] and the European Union’s E-Commerce Directive,[13] both of which differentiate sharply between a platform’s liability for content it hosts and its liability for transactions merely facilitated through it. The Court’s willingness to let the IT Act charge proceed on a prima facie basis, without engaging more rigorously with this distinction, arguably extended Avnish Bajaj’s personal exposure further than the underlying conduct warranted.
Third, the decision must be read against the backdrop of Section 79 of the IT Act as it then stood.[14] The pre-2008 version of Section 79 offered intermediaries only a limited defence, requiring proof that the offence was committed without their knowledge or that they had exercised “due diligence” , without specifying what due diligence entailed. The Court, in effect, was being asked to interpret an undefined statutory standard against a nascent and largely self-regulated industry. Judged in this light, the decision can be read sympathetically: the Court was not so much expanding criminal liability as exposing how thin the existing safe-harbour protection actually was. Viewed this way, Avnish Bajaj functions less as a precedent establishing broad intermediary liability and more as a diagnostic of a legislative vacuum , a reading borne out by the fact that Parliament moved swiftly to overhaul Section 79 through the Information Technology (Amendment) Act 2008,[15] introducing a more structured safe-harbour regime conditioned on the intermediary not initiating the transmission, not selecting the receiver, and not modifying the information, alongside an obligation to take down unlawful content upon receiving actual knowledge or a government notification.
Fourth, the eventual judicial correction of this line of reasoning is itself instructive. The connected proceedings against the third accused, Sharat Digumarti, travelled to the Supreme Court, which in Sharat Babu Digumarti v State (NCT of Delhi) held that once Section 79 of the amended IT Act grants conditional immunity to intermediaries, and given that the IT Act is a special law dealing comprehensively with electronic records, prosecution for the same conduct under the general provisions of the Penal Code (Section 292) is impermissible once the matter falls within the specific regulatory scheme of the IT Act.[16] The Supreme Court’s reasoning on this point turned specifically on the principle that a special law excludes the application of a general law where the two cover the same field.[17] The Supreme Court’s eventual quashing of the proceedings against the company and, in substance, the vindication of the position originally pressed by Bajaj’s counsel suggests that the Delhi High Court’s 2008 reasoning, while a reasonable application of the law as it then stood, ultimately rested on legislative provisions that proved too imprecise to bear the weight placed on them, and that needed both legislative amendment[18] and appellate correction[19] before a stable equilibrium was reached.
Fifth, the policy dimension of the case remains relevant well beyond its facts. The arrest of a sitting CEO over a third-party listing sent a chilling signal to India’s nascent internet industry at a formative period of its growth, raising legitimate concerns about whether criminal exposure of this kind was proportionate to the degree of control a marketplace operator could realistically exercise over millions of user-generated listings. At the same time, the underlying conduct , a 38-hour delay in removing flagged content involving minors, continued profiteering through commission even after notice, and admittedly inadequate filtering , illustrates why some baseline standard of platform accountability is indispensable, particularly where child sexual abuse material is involved. The lasting value of Avnish Bajaj lies precisely in this unresolved tension: it forced Indian law to confront, for the first time, the question of how much responsibility a digital intermediary should bear for harms it did not originate but plausibly could have prevented , a question that remains live today in debates over the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021[20] and the due diligence obligations they impose on social media and e-commerce platforms.
VIII. Conclusion
Avnish Bajaj v State (NCT of Delhi) is best understood not as a definitive statement of intermediary liability but as a transitional judgment, decided at a moment when Indian cyber law lacked the doctrinal vocabulary to deal with platforms that neither created nor directly transmitted unlawful content, yet profited from and exercised imperfect control over the environment in which it circulated. The Court’s discharge of Bajaj under the Penal Code, while sustaining the IT Act charge, reflects a defensible but ultimately uneasy compromise that exposed the inadequacy of the pre-2008 Section 79 safe harbour more than it settled any enduring principle of platform responsibility.
The decision’s lasting significance lies in its catalytic effect: it directly informed the 2008 overhaul of intermediary liability provisions under the IT Act and anticipated, by over a decade, the due diligence and takedown obligations that now form the backbone of India’s platform regulation framework. Read together with the Supreme Court’s subsequent disposal of the connected Digumarti proceedings, the case offers a useful case study in how a single, factually narrow criminal prosecution can shape the architecture of an entire regulatory regime. For students of cyber law, Avnish Bajaj[21] remains essential reading , not for the precision of its final holding, but for the clarity with which it exposed a legislative gap that Indian law has spent the better part of two decades trying to close.
AUTHOR- SUHANI SHARMA
BBA LLB 5TH YEAR
ARMY LAW COLLEGE, PUNE
[1]Avnish Bajaj v State (NCT of Delhi) (2008) 105 DRJ 721; 150 (2008) DLT 769; 2008 (6) AD (Del) 381 (Delhi High Court).
[2]ibid.
[3]Avnish Bajaj v State (NCT of Delhi), Bail Application No 2284 of 2004 (Delhi High Court, 21 December 2004).
[4]Avnish Bajaj (n 1); see also State of Madras v C V Parekh (1970) 3 SCC 491 (Supreme Court of India).
[5]Standard Chartered Bank v Directorate of Enforcement (2005) 4 SCC 530 (Supreme Court of India).
[6]Information Technology Act 2000 (Act No 21 of 2000) s 85.
[7]Avnish Bajaj (n 1).
[8]ibid.
[9]Negotiable Instruments Act 1881 (Act No 26 of 1881) s 141.
[10]Information Technology Act 2000 (Act No 21 of 2000) s 85.
[11]Avnish Bajaj (n 1).
[12]Communications Decency Act 1996, 47 USC s 230 (United States).
[13]Directive 2000/31/EC of the European Parliament and of the Council of 8 June 2000 on certain legal aspects of information society services, in particular electronic commerce, in the Internal Market (‘Directive on electronic commerce’) [2000] OJ L178/1, arts 12-15.
[14]Information Technology Act 2000 (Act No 21 of 2000) s 79 (as it stood prior to the 2008 amendment).
[15]Information Technology (Amendment) Act 2008 (Act No 10 of 2009), amending s 79 of the Information Technology Act 2000.
[16]Sharat Babu Digumarti v State (NCT of Delhi) (2017) 2 SCC 18 (Supreme Court of India).
[17]ibid [22]-[24].
[18]Information Technology Act 2000 (Act No 21 of 2000) s 79 (as amended by Act No 10 of 2009).
[19]Sharat Babu Digumarti (n 21).
[20]Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021.
[21]Avnish Bajaj (n 1).
