Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891): Practitioner Guide to India's First Right to Be Forgotten Framework

TL;DR for Practitioners

The Delhi High Court (Justice Sachin Datta), in a 144-page judgment dated 29 May 2026 (2026:DHC:4891), laid down India's first comprehensive Right to Be Forgotten framework for judicial records. Key practice points: (1) plead the right under Article 21 of the Constitution of India, not under the DPDP Act, 2023, because the DPDP Act does not govern court records and courts are not Data Fiduciaries; (2) frame relief as de-indexing — restriction of name-based search — never as deletion of the record; (3) the relief is proportionality-gated, so build a record on privacy harm and absence of public interest; (4) acquitted, discharged, and private-dispute clients are the strongest candidates; (5) the judgment is a single-judge Delhi High Court decision — binding in Delhi subject to appeal, persuasive elsewhere.

Laksh Vir Singh Yadav v. Union of India & Connected Matters, 2026:DHC:4891, a single-judge Bench decision of the Delhi High Court (Justice Sachin Datta, 29 May 2026, petitions allowed with directions), is the governing authority on the Right to Be Forgotten for judicial records in India. The ratio — that this right is a facet of informational privacy under Article 21 of the Constitution of India, enforced by proportionality-gated de-indexing — transfers directly into de-indexing pleadings today, supplementing Section 12(3) of the Digital Personal Data Protection Act, 2023 for non-judicial data. Counsel drafting de-indexing or masking petitions should plead this case alongside K.S. Puttaswamy v. Union of India (2017) 10 SCC 1.

Key Takeaways for Counsel

• Plead the Right to Be Forgotten under Article 21, not the DPDP Act, 2023, for judicial-record de-indexing.
• Frame relief as de-indexing the name as a search key — never as deletion of the underlying record.
• Build a proportionality record: privacy harm, acquittal/private nature, and absence of public interest.

Case Fact Sheet

Ratio Decidendi in One Line

Ratio: Absent comprehensive statutory codification, the Right to Be Forgotten is enforceable as a facet of informational privacy under Article 21 of the Constitution of India, entitling a person to proportionality-gated de-indexing of judicial records from name-based searches without deletion of the record itself.

Statutes Interpreted — and Their Current Form

Who decided this case?

Answer: Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891) was decided by a single-judge Bench of the Delhi High Court, comprising Justice Sachin Datta, who authored the 144-page judgment on 29 May 2026. As a single-judge High Court decision, the ratio binds the Delhi High Court subject to appeal and is persuasive on other High Courts and on coordinate benches.

How did the case reach the Delhi High Court?

Answer: The matter originated in writ petitions under Article 226 of the Constitution of India from 2016 onwards, led by W.P.(C) 1021/2016. The Delhi High Court consolidated more than 30 connected petitions because each sought removal of name-based online access to judicial records, raising a common constitutional question best resolved through a single framework.

What are the facts in brief?

Answer: In Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891), more than 30 petitioners — acquitted accused, parties whose cases were dismissed or settled, and parties to matrimonial and private civil disputes — sought de-indexing and masking because their proceedings surfaced indefinitely on name searches, affecting reputation and livelihood. The petitions sought directions against search engines, a legal database, and the Government.

Doctrinally, the dispute sat at the intersection of Article 21 informational privacy and the Digital Personal Data Protection Act, 2023, which addresses erasure of personal data but does not expressly govern judicial records maintained by courts as a constitutional function.

What issues did the court frame?

Answer: The Delhi High Court framed issues on the existence, statutory basis, and enforcement mechanism of a Right to Be Forgotten for judicial records.

1. Issue 1: Whether the Right to Be Forgotten forms part of informational privacy under Article 21 of the Constitution of India.
2. Issue 2: Whether the Digital Personal Data Protection Act, 2023, comprehensively codifies the right for judicial records.
3. Issue 3: What standard governs de-indexing or masking, and what directions should issue to search engines, the legal database, and MeitY.

What did the court hold?

Answer: In Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891), the single-judge Bench held that the Right to Be Forgotten is enforceable under Article 21 through proportionality-gated de-indexing. Each holding below is pleadable as a standalone proposition.

1. Holding 1: The Right to Be Forgotten is an essential facet of informational privacy under Article 21 of the Constitution of India, because indefinite online availability of judicial-proceeding data can harm reputation, employment, and personal life, particularly for the acquitted.
2. Holding 2: The Digital Personal Data Protection Act, 2023, including the Section 12(3) right to erasure, does not comprehensively codify the right for judicial records, and courts are not Data Fiduciaries; the gap is filled through Article 21.
3. Holding 3: Relief is proportionality-gated, not automatic, balancing individual privacy against public interest, judicial transparency, and the nature of the proceedings, with public officials and matters of public concern receiving less protection.
4. Holding 4: Google is directed to de-index the relevant judgments, orders, and reportage from name-based search results for the petitioners; Indian Kanoon is directed to restrict name-based search for the petitioners' records while retaining access by case number, citation, court, and date; and MeitY is directed to ensure intermediary compliance and file a compliance affidavit.
5. Holding 5: Petitioners have liberty to additionally seek masking before the courts that originally rendered the concerned judgments and orders.

Why does the Right to Be Forgotten judgment matter today?

Answer: Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891) matters because it converts the informational-privacy recognition of K.S. Puttaswamy v. Union of India (2017) 10 SCC 1 into an operable remedy and supplies the missing layer that the Digital Personal Data Protection Act, 2023 leaves open for judicial records. It gives counsel a concrete, court-endorsed remedy — de-indexing without deletion — and establishes a compliance mechanism through MeitY. Its persuasive reach into other High Courts and any Supreme Court of India review is still to be tested.

The Court's own framing of the de-index-not-delete distinction is the pleadable formulation:

"What changes is only that the concerned name (whether an individual or an entity) ceases to function as an unlimited retrieval key that instantly and effortlessly surfaces the record for any casual internet user who happens to search that name."

— Delhi High Court, Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891)

Current Statutory Framework (as of 2026-06)

Answer: The right rests on Article 21 of the Constitution of India, which is unchanged, supplemented by the Digital Personal Data Protection Act, 2023 for non-judicial personal data. The Delhi High Court read the DPDP Act as not reaching judicial records, so the constitutional route remains the operative basis for court-record de-indexing.

Article 21, Constitution of India → (unchanged)

Article 21 continues to be the home of informational privacy following K.S. Puttaswamy v. Union of India (2017) 10 SCC 1. The ratio of 2026:DHC:4891 transfers in full because it is rooted in this stable constitutional provision rather than in any statute liable to amendment.

Right to erasure → Section 12(3), Digital Personal Data Protection Act, 2023

Section 12(3) of the Digital Personal Data Protection Act, 2023 gives data principals a right to erasure of personal data held by Data Fiduciaries. The Delhi High Court held this does not comprehensively cover judicial records, so for court records the ratio transfers via Article 21, not via the DPDP Act; the statute remains relevant only for de-indexing requests against non-judicial Data Fiduciaries.

Practice Implications

For counsel drafting de-indexing petitions for acquitted or discharged clients

• Anchor the petition in Article 21, not the DPDP Act, 2023. Plead the Right to Be Forgotten as a facet of informational privacy under Article 21 of the Constitution of India and cite both Laksh Vir Singh Yadav (2026:DHC:4891) and K.S. Puttaswamy (2017) 10 SCC 1.
• Frame relief as de-indexing the name, never deletion. Mirror the Court's distinction — seek restriction of the name as a search retrieval key while expressly conceding access by case number, citation, court, and date.
• Build a proportionality record. Document concrete privacy harm (employment loss, reputational injury), the acquittal or private nature of the proceeding, and the absence of any genuine public interest in the petitioner's identity.

For counsel advising legal databases, search engines, and court aggregators

• Audit search architecture against the de-index-without-delete standard. Confirm the platform can suppress name-based retrieval for specified records while retaining citation-, case-number-, and court-based access.
• Build a court-order intake workflow. Establish a process to receive, verify, and action judicial de-indexing directions promptly, and to evidence compliance, given MeitY's compliance-affidavit oversight role.
• Map exposure to MeitY oversight. Treat the Information Technology Act, 2000 intermediary obligations as now extending into the judicial-records domain and prepare compliance documentation accordingly.

For matrimonial and family-law counsel

• Offer de-indexing as supplementary post-disposal relief. Advise clients in divorce, maintenance, and domestic-violence matters that masking of personal identifiers and de-indexing of records is now available under 2026:DHC:4891.
• Use the originating-court liberty. Invoke the Court's grant of liberty to seek masking before the court that rendered the order, in addition to any de-indexing direction against platforms.
• Stress the proportionality threshold. Set client expectations that relief is case-by-case and strongest where the matter is genuinely private rather than of public concern.

Twin-citation formula

In any Right to Be Forgotten or de-indexing matter, pair Laksh Vir Singh Yadav v. Union of India with:

• K.S. Puttaswamy v. Union of India, (2017) 10 SCC 1 — for the foundational recognition of informational privacy under Article 21 of the Constitution of India.

💡 Advising on de-indexing or platform compliance? Veritect Legal AI tracks every privacy and intermediary-liability development, the full Article 21 informational-privacy line of authority, and the evolving Right to Be Forgotten framework. Explore Veritect Legal AI →

Downstream applications and interpretations

• As India's first comprehensive Right to Be Forgotten framework for judicial records, Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891) has not yet been tested on appeal or applied by other High Courts; its persuasive influence and any Supreme Court of India review are still to develop, so no downstream authority can yet be cited.

Practitioner FAQ

Can an acquitted client obtain de-indexing of the criminal proceeding under this framework?

Yes, subject to a proportionality assessment. Under Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891), an acquitted or discharged person can seek de-indexing of the proceeding from name-based search results as a facet of informational privacy under Article 21 of the Constitution of India. The acquittal weighs strongly in favour of relief, but the court will still balance it against any genuine public interest in the matter; relief is not automatic.

Does the order require deletion of the judgment from the court website or legal databases?

No. The Delhi High Court distinguished de-indexing from deletion. The judgment remains fully available through its case number, citation, court, and date on the court website and on legal databases. Only the petitioner's name stops working as a search retrieval key. Counsel should frame relief as restriction of name-based retrieval, not removal of the record, to align with the framework in 2026:DHC:4891.

Is the DPDP Act, 2023 the correct statutory hook for a de-indexing petition?

Not for judicial records. The Delhi High Court held in 2026:DHC:4891 that the Digital Personal Data Protection Act, 2023 — including the right to erasure under Section 12(3) — does not comprehensively codify the Right to Be Forgotten for judicial records, and courts are not Data Fiduciaries in this context. Counsel should plead the right under Article 21 of the Constitution of India, citing K.S. Puttaswamy v. Union of India (2017) 10 SCC 1, rather than relying on the DPDP Act for court-record de-indexing.

Is this single-judge Delhi High Court judgment binding on other High Courts?

No. Laksh Vir Singh Yadav v. Union of India (2026:DHC:4891) is a single-judge decision of the Delhi High Court. It binds the Delhi High Court subject to appeal and is persuasive only — not binding — on other High Courts. As India's first comprehensive Right to Be Forgotten framework for judicial records, its persuasive influence elsewhere and any Supreme Court of India review remain to be developed; counsel outside Delhi should cite it as persuasive authority.

What technical and compliance steps should a legal database or search engine prepare?

Platforms that index judicial records should build the capability to restrict name-based search for specified records while preserving access by case number, citation, court, and date — the precise relief contemplated in 2026:DHC:4891. They should also prepare to respond to court-directed de-indexing orders and, where relevant, to MeitY compliance oversight. Counsel advising such platforms should audit current search architecture against the de-index-without-delete standard.

What is MeitY's role under this judgment?

The Delhi High Court directed the Ministry of Electronics and Information Technology (MeitY) to ensure compliance by intermediary platforms and to file a compliance affidavit before the Court. This extends MeitY's enforcement footprint, traditionally exercised over user-generated content under the Information Technology Act, 2000, into the judicial-records domain. The compliance-affidavit mechanism creates a live, court-supervised enforcement channel that practitioners can invoke if a platform fails to act on a de-indexing direction.

Cross-references

• Student summary: Laksh Vir Singh Yadav v. Union of India — Summary & Exam Relevance.
• Glossary: informational privacy; proportionality; right to erasure.
• Related practitioner articles: tech-data-law data-protection case-analysis cluster.

Source

This analysis is freshly researched from Veritect's Tier-1-sourced report of the actual judgment. The underlying decision is Laksh Vir Singh Yadav v. Union of India & Connected Matters, W.P.(C) 1021/2016 & Connected Matters, decided by the Delhi High Court (Justice Sachin Datta) on 29 May 2026, neutral citation 2026:DHC:4891, available from the Delhi High Court. Statutory text cross-referenced from India Code; the current statutory position should be verified against egazette.gov.in before advising on a live matter. This analysis is for informational purposes and does not constitute legal advice.

Beyond this brief Preview — access the full Veritect Legal AI platform

This guide covers the ratio, holdings, current statutory framework, and first-order practice implications of India's first Right to Be Forgotten framework for judicial records. The full Veritect Legal AI platform carries the complete proportionality-factor breakdown, model de-indexing and masking pleadings, the Article 21 informational-privacy line of authority, and the platform-compliance workflow for legal databases and search engines.

Access Veritect Legal AI →