Other · 11 min read · 15 min 41 sec listen · Published 3 August 2026

How an Open-Source Photo Archive Platform Challenged a Government Takedown Order — and Won

A developer built an open-source photo archive, only to face a government blocking order. Advocate Sudhir Rao explains the legal design and procedural challenge that kept the platform alive under Indi

How an Open-Source Photo Archive Platform Challenged a Government Takedown Order — and Won
One of my clients recently had a case which I am explaining below and if you are stuck in such similar situation, here is what to do.

Note: Due to attorney-client privilege, I cannot disclose complete case details or identify the actual parties involved. However, I am sharing the essential facts and legal approach so that if you find yourself in a similar situation, you can understand the available solutions and legal remedies.

TL;DR: Building a public media archive in India means you are an intermediary under the IT Act. That comes with mandatory takedown and compliance duties — you can't design your way out of them. But with a robust structure, clear policies, and quick legal challenge to procedurally flawed orders, you can minimize the risk of sweeping platform takedowns and keep your archive alive.

Key Facts of the Case

  • Vikram Singh, a developer from Indore, built "ArchiveIndia" — an open-source, public photo and video library where any user could submit content anonymously.
  • The platform had no signup, no IP logging, no real-name requirements. Every submission went through manual review before publication to filter out spam and NSFW material.
  • In early September 2024, the Government issued a blocking order under Section 69A of the Information Technology Act, directing the entire ArchiveIndia subdomain to be blocked because of a few politically sensitive user uploads.
  • Vikram initially consulted a local lawyer who told him to comply fully. The entire archive went dark overnight. He then approached the Chamber of Advocate Sudhir Rao.
  • The challenge centred on procedural defects: the Review Committee had not examined the specific offending URLs, there was no individualised assessment, and the blanket domain blocking was disproportionate.
  • After a writ petition was filed, the court modified the order, limiting the blocking only to the identified URLs and allowing ArchiveIndia to resume operations with specific safeguards in place.

No, there is no realistic architecture that lets you sidestep government takedown orders while fully complying with Indian law. The moment you operate a platform that hosts third‑party content, you are an “intermediary” under Section 2(1)(w) of the Information Technology Act, 2000. And intermediaries are bound by two separate but overlapping obligations.

First, the safe harbour under Section 79 of the IT Act protects you from liability for user‑generated content — but only as long as you follow the Intermediary Guidelines and Digital Media Ethics Code, 2021. That means when you receive actual knowledge in the form of a court order or a government‑notified takedown notice, you must remove or disable access to that specific content within 36 hours. Refusing to do so strips you of the safe harbour. You then risk criminal and civil liability yourself.

Second, Section 69A of the IT Act allows the Central Government to block public access to any information through any computer resource. The blocking procedure has built‑in safeguards: the Secretary‑level committee must record reasons, the Review Committee must examine the blocking, and the blocking order must be limited to the specific URLs. But once a properly issued order lands on your desk, you must comply.

So the short answer is this. You cannot legally design a platform that renders government blocking orders toothless. What you can do is build a transparent, well‑documented compliance mechanism and litigate aggressively when an order is overbroad or procedurally flawed. And that’s precisely how ArchiveIndia survived.

Advice in Such Cases

Consult with Lawyer: The very basic and important step to start is talk to Lawyer / advocate. You should not hesitate in paying his consultation fee i.e. might be in range of Rs. 10,000 to 50,000 depends case to case. He is helping you in this situation to come out. He is expert in the domain and can help you explain the procedure which you might have never explored. A good lawyer can get the issues resolved much faster than you think.

Don’t wait until the blocking order lands. Have a lawyer review your platform’s content policy, terms of use, and compliance process from day one. The IT Rules impose detailed duties on intermediaries — publishing your contact details, appointing a Grievance Officer, acknowledging complaints within twenty‑four hours, and resolving them within fifteen days. Missing any of these can weaken your standing.

If you do find yourself staring at a blocking order, resist the instinct to just take everything down. A blanket domain block often overreaches. Specialist counsel can scrutinize the order for procedural gaps and push for a URL‑specific approach. In ArchiveIndia’s case, the earlier general‑practice lawyer advised full compliance, costing weeks of darkness. The outcome changed only when the procedural arguments were raised before the right forum. Make no mistake, the procedural nuances here — the Review Committee’s composition, the evidence of national security or public order risk, the proportionality of the measure — are areas where an advocate who regularly handles Section 69A challenges brings a critical edge.

Applicable Sections of Law

  • Section 2(1)(w) of the Information Technology Act, 2000 – defines “intermediary” broadly, covering any entity that receives, stores, or transmits electronic records on behalf of another person.
  • Section 79 of the IT Act – provides the safe harbour protection, conditional on due diligence and compliance with government directions.
  • Section 69A of the IT Act – empowers the Central Government to block public access to any information for specified reasons, subject to procedural safeguards.
  • Rule 3(1)(d) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 – requires an intermediary to remove or disable access to specific content within 36 hours upon receiving a government direction.

Jurisdiction — Where to File the Case

A platform owner challenging a blocking order under Section 69A typically approaches the High Court under Article 226 of the Constitution, filing a writ petition. The jurisdiction lies where the cause of action arises — usually where the platform’s registered office is located or where the blocking order’s effect is felt. For ArchiveIndia, the petition was filed in the High Court of Madhya Pradesh, Indore Bench. Choosing the right territorial jurisdiction matters deeply. It can affect procedural speed and the bench’s familiarity with digital rights issues.

Limitation Period

While the Limitation Act, 1963 doesn’t prescribe a fixed statutory period for a writ petition challenging a blocking order, courts apply the principle of laches. You must act without unreasonable delay. In practice, if you sleep on the matter for six months or longer, the court may refuse to interfere. In Vikram’s case, the petition was moved within ten days of the blocking order — it sent a strong signal that the matter was urgent and not an afterthought. Condonation of delay is possible, but never bank on it.

Interim Reliefs Available

The most powerful weapon in a writ petition against a blocking order is an interim stay. Under Article 226, the High Court can direct that the blocking be kept in abeyance pending final hearing. This is effectively an interim injunction couched in constitutional relief. In ArchiveIndia’s matter, the court granted a modified interim order: the domain was unblocked while the specific challenged URLs remained inaccessible. Filing early and demonstrating urgency are key. Without interim relief, the archive would have stayed dead for months while the case crawled forward. A well‑argued interim application can breathe life back into the platform within weeks.

If You Are the Victim

  • Don’t panic and dismantle your entire platform. Comply only with what the order specifically asks — if it specifies URLs, block those; if it’s a domain block, seek legal counsel immediately.
  • Preserve every piece of correspondence — the blocking order, the review committee meeting notice, anything that shows the government’s reasoning.
  • Do not delete any user data or logs. Even if you normally don’t track users, metadata about the submission itself may help your legal argument.
  • Engage a lawyer who has handled Section 69A challenges before. The procedural terrain is niche, and a generalist may miss the openings that save your platform.
  • Notify your users, transparently, about what has happened and what you are doing to restore access. The goodwill matters.

Documents You Must Keep Ready

  • Copy of the blocking order or takedown notice — preserve the original email or hard copy.
  • Platform architecture documents showing how content is submitted, reviewed, and published.
  • Terms of Service and Privacy Policy that were in effect when the flagged content was uploaded.
  • Records of any complaints received through your grievance redressal mechanism prior to the government order.
  • Details of the specific URLs or content items in dispute — screenshots, metadata, submission time stamps.
  • Correspondence with any government agency, including email headers.
  • Identity proof of the platform owner or authorised representative (Aadhaar or PAN).

What Evidence Is Required?

  • The original blocking order — a primary document that the court will scrutinize for procedural defects.
  • Screenshots or logs showing that the flagged content was user‑generated and not produced by the platform itself.
  • Affidavit from the content reviewer explaining the manual review process, to establish that the platform had no editorial hand in selecting the controversial material.
  • Records from the Review Committee, if any were shared — these can expose gaps in the blocking procedure.
  • Expert opinion on the technical feasibility of URL‑specific blocking, as opposed to domain‑wide blocking, to argue proportionality.
  • Copies of relevant Supreme Court judgments like Shreya Singhal v. Union of India (2015), which laid down the procedural safeguards.

How Courts Typically Approach Such Cases

Indian High Courts are now quite aware of the chilling effect of overbroad blocking orders. After the Shreya Singhal judgment, there is a clear emphasis on procedural fairness and proportionality. A court will first check whether the Central Government followed the three‑stage safeguard: examination by the designated officer, approval by the Secretary‑level committee, and review by the Committee. If the order fails to specify exactly which URLs should be blocked, or if the reasons are cursory, the court is likely to grant relief. But the court will also balance free speech concerns against national security claims. So documentation, transparency, and evidence of your good‑faith compliance are everything.

  • Day 1–7: Receipt of blocking order; consultation with specialist advocate; drafting of writ petition and interim stay application.
  • Week 2–3: Filing the petition in the High Court; mention for urgent listing; obtaining an interim order (stay/modification).
  • Month 1–3: Government files its reply; the petitioner files a rejoinder; matter is listed for final hearing.
  • Month 4–6: Final arguments; judgment reserved and pronounced. If the court upholds the order, an appeal lies to the Supreme Court.
  • Execution: If the order is struck down or modified, the platform resumes operations immediately as per the court’s direction.

Understanding the Costs

The total cost of a matter like this varies significantly from one case to the next — it depends on the complexity of the dispute, the forum involved, the number of hearings, and the specific facts of your situation. There is no single fixed figure that applies to everyone.

A professional advocate can give you an accurate estimate only after reviewing all your facts and documents in a consultation.

Can the Matter Be Settled Out of Court?

Settlement isn’t typical for a government blocking order, but it’s not impossible. In some instances, the Review Committee may agree to narrow the scope of the blocking after a representation is made, avoiding litigation altogether. This is a form of executive resolution. Under the IT Rules, you are also entitled to a hearing before the Review Committee. If you can persuade the Committee at that stage that the content doesn’t meet the criteria of Section 69A — or that domain‑wide blocking is disproportionate — the order may be rescinded or modified without ever stepping into a courtroom. And that is often the fastest route back online.

Common Mistakes People Make

  • Immediately complying with an overbroad blocking order without seeking legal advice — the blanket takedown becomes the default, and reversing it later is tougher.
  • Not appointing a Grievance Officer as required by the IT Rules, which weakens your safe harbour defence and gives the government a ready ground to issue directions.
  • Destroying or altering logs and metadata after receiving a notice, believing it will protect users. That can be seen as obstruction.
  • Engaging a lawyer who doesn’t regularly handle Section 69A and IT Rules litigation. Domain‑specific experience matters because the interplay between safe harbour, procedural review, and constitutional proportionality is easy to get wrong.
  • Ignoring the pre‑litigation representation to the Review Committee — many platform owners don’t realise they can beat the blocking order without a court fight if they present a strong case early.
  • Failing to keep users informed, which leads to reputational damage and loss of community support that can sometimes influence the regulatory mood.

FAQs People Normally Have

Can I be arrested just for running a public archive where users post restricted content?

Not if you follow the IT Rules. Section 79 shields you from criminal liability for third‑party content, provided you act promptly on takedown notices and blocking orders. Arrest would typically require direct involvement in creating or actively publishing the prohibited material.

Will open‑sourcing my platform or mirroring content bypass a blocking order?

No. A blocking order under Section 69A is addressed to intermediaries and telecom service providers. They are legally bound to block access. If your site is blocked at the ISP level, mirrors become practically ineffective unless users circumvent through VPNs, and running mirrors yourself can expose you to further liability.

How quickly must I respond to a government takedown notice?

36 hours from receipt of the direction. The clock starts ticking the moment the order is communicated to you. Non‑compliance means you lose safe harbour and may invite criminal proceedings.

Is there any way to get advance notice of a blocking order?

Rarely. In emergency cases, the designated officer can pass an interim blocking order without a hearing. However, the Review Committee must meet within seven working days to confirm or revoke it. If you aren’t notified, the order can sometimes be challenged on due process grounds.

This article is general legal information, not legal advice. Consult a qualified advocate about your specific situation.

Advocate Sudhir Rao, Supreme Court of India

Was this article useful?

/5 (0 ratings)