Recommended Articles
Legal & Policy

India's Supreme Court Just Made Child Safety a Compliance Category

By Angeled · October 17, 2026 · Legal & Policy
India's Supreme Court Just Made Child Safety a Compliance Category
India's Supreme Court Just Made Child Safety a Compliance Category

In October 2026, a two-judge bench of India's Supreme Court — Justices J.B. Pardiwala and K. Vinod Chandran — ordered the creation of a national database for the coordinated detection and removal of child sexual exploitation and abuse material (CSEAM). The ruling, in Just Rights for Children Alliance vs S. Harish, builds on the Court's September 23, 2024 judgment and goes much further: it converts child safety from a moderation problem into a regulated compliance obligation, complete with prescribed technology, human review, reporting timelines, and the prospect of monetary penalties.

For founders building social, messaging, AI-generation, or creator platforms, this is the compliance category you must now design for.

What the Court ordered

The Court directed the Union Government to establish a National Hash & URL List Database used exclusively for CSEAM detection and removal. Key design principles:

  • Perceptual hash-matching and URL listing as the detection backbone. Crucially, the database stores verified identifiers and links — not the abusive material itself.
  • Three-analyst verification. Every entry requires independent assessment by at least three trained human analysts before listing.
  • Immediate removal. Intermediaries must take down matching material at once, without waiting for further verification.
  • No escape through indirectness. Promotions of tools enabling sexually abusive manipulation of children's images, and links directing users to CSEAM, cannot stay online merely because they contain no explicit depiction or comply with a platform's "advertising standards." Content must be examined as a whole — captions, keywords, links, and the function of promoted tools.

Timelines and reporting obligations

The ruling imposes hard operational timelines:

  • Unknown-origin CSEAM: report within two hours — either after complaint resolution or within two hours of removal following due diligence, a court order, or government intimation.
  • Known-origin CSEAM: database-matched removals must be reported to the database authority through weekly consolidated reports.
  • Reporting UX: a clearly labeled CSEAM reporting category, accessible within two steps.
  • Accountability infrastructure: trained human review, digitally signed findings, complaint tracking, reasoned responses, and separately disclosed CSEAM compliance reporting subject to independent audit.

The Court also noted that platform-by-platform detection lets material removed from one intermediary persist on others — the core justification for a coordinated national database.

Penalties: beyond safe-harbour loss

One of the most consequential holdings: the Court said that loss of safe-harbour protection under Section 79 of the IT Act is insufficient to address systemic regulatory defaults. It asked the Union Government to consider proportionate monetary penalties for platform defaults — described in reporting as "exemplary fines."

That framing matters. Safe-harbour loss is retrospective and litigation-driven; monetary penalties are administrative and scalable. If implemented, non-compliance becomes a quantifiable line item rather than a theoretical liability.

Why this reaches every founder, not just big platforms

The database approach is deliberately intermediary-neutral. Any service that hosts user-generated content, links, or ads could fall within scope. Founders should note:

  • AI image tools face the "indirect promotion" test. If your tool can manipulate children's images and your ads or listings promote that capability, the Court's logic applies even without explicit depiction.
  • Reporting to the U.S.-based NCMEC is not enough. The Court reiterated that intermediaries must report to the authorities specified under POCSO, not rely solely on the National Center for Missing & Exploited Children.
  • Grievance redress must be real. The Court criticized confusing reporting channels and inadequate grievance-handling capacity, and demanded correction of erroneous entries — wrongful removal of lawful content is an explicit concern.

A compliance checklist for platforms

  1. Integrate perceptual-hash and URL-list matching into upload and link-sharing pipelines.
  2. Build a two-step CSEAM reporting flow with trained human reviewers and digitally signed findings.
  3. Implement two-hour reporting for unknown-origin material and weekly consolidated reporting for known-origin matches.
  4. Maintain audit trails, independent audits, and a grievance redressal mechanism that can correct erroneous entries.
  5. Review advertising policies — tool promotions and redirect links get whole-content scrutiny.
  6. Map POCSO reporting obligations in your operating jurisdictions; don't default to NCMEC-only.

The bottom line

The Court recognized internet access as a fundamental right, including for children, while permitting proportionate safeguards — and it explicitly said child safety requires digital-safety awareness, age-appropriate education, and victim support, not merely removal. But the regulatory direction is unmistakable: child safety is becoming a defined compliance category with prescribed technology, timelines, and penalties. Founders who build these systems now will treat them as infrastructure. Those who wait will treat them as emergencies.

Sources: Reporting by The Bar Bulletin, October 17, 2026.

Read Next