DPDP Act under the scanner: what the Supreme Court challenge means for Indian businesses

The DPDP Act is under a Supreme Court challenge. The headlines are loud. The instinct is to wait. Three things are still true: The Act has not been stayed. The DPDP Rules, 2025 are moving through notification. Your customers are already auditing vendor DPDPA posture. Privacy readiness work should not pause. The judgment may sharpen the edges of the law. But Indian businesses should continue preparing for DPDPA compliance now.
What Changed
The DPDP Act was enacted in August 2023 as India’s first dedicated personal data protection law.
After its enactment, writ petitions were filed before the Supreme Court by RTI activists, journalists, civil society groups and members of the legal community. These petitions challenge specific parts of the law, not the entire idea of data protection.
The most prominent challenge concerns the amendment made by the DPDP Act to Section 8(1)(j) of the Right to Information Act, 2005.
Before the amendment, RTI authorities could deny disclosure of personal information only after applying certain public-interest tests. The older provision allowed disclosure where a larger public interest justified it. It also carried an important safeguard: information that could not be denied to Parliament or a State Legislature could not be denied to a citizen.
The DPDP Act simplifies this language and creates a broader exemption for information relating to personal information.
That change is now under constitutional scrutiny.
Petitioners argue that the amendment may weaken transparency, especially around information concerning public servants, public institutions, qualifications, assets, disciplinary records and other matters of public interest.
Some petitions also raise concerns around:
- ✓independence of the Data Protection Board;
- ✓breadth of the Government’s rule-making powers;
- ✓lack of explicit exemptions for journalism, research and public-interest reporting;
- ✓possible chilling effects on transparency and accountability.
For businesses, the important point is simple:
A constitutional challenge has started. Compliance has not stopped.
What the Law Actually Says
The DPDP Act continues to apply unless the Supreme Court specifically stays or strikes down relevant provisions.
As of now, there is no general stay on the DPDP Act.
That means Indian businesses must continue preparing for the core obligations under the law.
The practical obligations remain broadly unchanged:
- ✓collect personal data only with valid consent or recognised legitimate use;
- ✓provide clear and accessible privacy notices;
- ✓use personal data only for the purpose communicated;
- ✓keep data only as long as necessary;
- ✓maintain reasonable security safeguards;
- ✓support data principal rights;
- ✓manage grievances;
- ✓notify personal data breaches as required;
- ✓ensure processors and vendors handle data properly.
The Supreme Court challenge mainly tests whether certain provisions of the Act are constitutionally valid, especially where privacy intersects with RTI, public interest, press freedom and government powers.
It does not give private businesses a free pass to ignore compliance.
For an SMB, CA firm, recruitment agency, D2C brand, training institute or SaaS company, the message is clear:
The legal debate may continue, but your operational duties are already visible.
The Act’s penalty structure also remains relevant. The DPDP Act provides for significant financial penalties for specific failures, including penalties that may reach up to ₹250 crore for certain categories of non-compliance.
So the business question is not:
“Will the Supreme Court change something?”
The better question is:
“Which parts of our data handling are already weak, regardless of what the Court decides?”
What Businesses Should Do Now
Businesses should not pause DPDPA readiness because of the constitutional challenge.
They should use this period to close practical gaps quietly before customers, partners, regulators or auditors ask harder questions.
Area of Focus
Action Required
Data Mapping
List where personal data sits across CRMs, HR systems, ATS tools, spreadsheets, WhatsApp groups, vendor portals, backups and cloud folders. Identify owners and access rights.
Consent Flows
Review every collection point: website forms, app screens, WhatsApp opt-ins, offline forms, candidate forms and customer onboarding journeys. Remove vague consent and pre-ticked boxes.
Privacy Notice
Rewrite your privacy notice in plain language. State what data is collected, why it is collected, how long it is retained, who it is shared with and how users can raise requests.
Retention Schedule
Define how long each category of personal data is retained. CVs, customer records, invoices, support tickets and marketing leads should not be kept forever by default.
Vendor Contracts
Review contracts with payroll providers, cloud tools, email platforms, payment gateways, CRMs, marketing tools and outsourced processors. Add data protection obligations where missing.
Rights Request Process
Create a dedicated email, owner and SLA for access, correction, erasure and grievance requests. Do not wait until the first request arrives.
Breach Response
Prepare a breach response runbook. Identify who acts in the first 24–72 hours, who informs leadership, who handles customer communication and who coordinates with vendors.
Leadership Briefing
Train founders, CXOs, sales heads and ops leads to answer basic privacy questions from customers and enterprise buyers.
Trust Signal
Publish a clear privacy page, assessment summary or DPDPA readiness statement to show customers that privacy is being handled seriously.
The correct operator mindset is:
Do not wait for perfect legal clarity. Fix the obvious operational gaps first.
Most DPDPA work is not exotic legal work.
It is disciplined business housekeeping:
- ✓know what data you collect;
- ✓know why you collect it;
- ✓know where it is stored;
- ✓know who can access it;
- ✓know when it should be deleted;
- ✓know what happens if something goes wrong.
What Is Still Uncertain
Some issues remain genuinely uncertain because the Supreme Court challenge and final regulatory implementation are still evolving.
Businesses should track these areas, but not use them as an excuse to pause.
- ✓RTI and Personal Data Disclosure
The biggest open question is how the Supreme Court will interpret the amended RTI exemption for personal information.
The Court may uphold the amendment, strike it down, or read it down to preserve public-interest disclosure.
This matters most for public authorities, journalists, civil society, public-sector entities and government-linked data ecosystems.
For most private businesses, this is important to understand but does not directly change everyday DPDPA obligations.
- ✓Press, Research and Public-Interest Exemptions
The Act does not contain a strong, standalone exemption for journalism, academic research, public-interest investigation or whistle-blowing.
The Supreme Court may influence how these areas are interpreted.
This is especially relevant for:
- ✓media companies;
- ✓research organisations;
- ✓civic-tech platforms;
- ✓public-interest publishers;
- ✓platforms hosting user-generated reporting.
- ✓Independence of the Data Protection Board
Petitioners have raised concerns about the appointment, tenure and removal of members of the Data Protection Board.
The question is whether the Board has sufficient independence to adjudicate privacy-related matters fairly.
Businesses should watch this because the Board will be the primary enforcement body under the Act.
- ✓Scope of Government Rule-Making Power
Many operational details are expected to come through rules, notifications and regulatory practice.
These include areas such as:
- ✓consent manager requirements;
- ✓significant data fiduciary thresholds;
- ✓children’s data obligations;
- ✓security safeguards;
- ✓breach notification procedures;
- ✓cross-border transfer restrictions.
The Supreme Court’s observations may influence how broadly these powers are used.
- ✓Final Shape of Compliance Timelines
The compliance calendar may evolve as rules and enforcement mechanisms mature.
But the direction of travel is clear: India is moving toward a formal privacy compliance regime.
Businesses that wait for the last notification will have less time, more pressure and higher remediation costs.
Top Mistakes to Avoid
Businesses should avoid these common errors while reading the Supreme Court challenge.
- ✓Assuming the DPDP Act Has Been Stayed
It has not been stayed.
A constitutional challenge does not automatically pause a law. Unless the Court grants a stay or strikes down a provision, the law continues to operate.
Waiting on this assumption is risky.
⸻
- ✓Treating the RTI Issue as a Private-Sector Compliance Escape Route
The RTI challenge is important, but it does not remove the privacy obligations of private businesses.
A recruitment agency, CA firm, D2C brand, SaaS company or training institute cannot use the RTI debate as a reason to delay privacy notices, consent flows, retention rules or vendor reviews.
⸻
- ✓Waiting for Final Rules Before Doing Anything
Some details may still evolve, but the core work is already obvious.
You do not need final rules to begin:
- ✓data mapping;
- ✓consent cleanup;
- ✓privacy notice updates;
- ✓vendor review;
- ✓retention planning;
- ✓breach response preparation.
Waiting for final precision often becomes an excuse for inaction.
⸻
- ✓Thinking Compliance Is Only a Legal Document Exercise
Most DPDPA gaps are not hidden inside policy PDFs.
They sit in:
- ✓website forms;
- ✓HR spreadsheets;
- ✓WhatsApp groups;
- ✓old CV folders;
- ✓marketing databases;
- ✓vendor exports;
- ✓shared drives;
- ✓forgotten SaaS tools.
A perfect privacy policy cannot fix messy operations.
⸻
- ✓Ignoring Customer and Vendor Pressure
Regulators are not the only pressure point.
Large customers, banks, insurers, platforms and enterprise buyers are already asking vendors about privacy posture.
A weak DPDPA posture can quietly block deals before any regulator gets involved.
⸻
- ✓Underestimating Retention Risk
Data that should have been deleted becomes breach surface.
Old resumes, dormant customer data, unused leads, outdated KYC copies and stale employee records create silent risk.
Retention is one of the easiest controls to start and one of the hardest to reconstruct later.
⸻
- ✓Treating the Supreme Court Case as the Main Event
The case matters.
But for most Indian businesses, the main event is still operational readiness.
The better question is not:
“What will the Supreme Court decide?”
The better question is:
“If a customer, employee or regulator asked us tomorrow how we handle personal data, could we answer clearly?”
SaralPrivacy Practical Checklist
Use this as a quick internal tracker.
- ✓Data map completed with owner per system.
- ✓Privacy notice updated in plain language.
- ✓Consent flows reviewed across web, app, WhatsApp and offline forms.
- ✓Retention schedule defined for major data categories.
- ✓Vendor contracts reviewed for data protection clauses.
- ✓Rights request inbox and owner assigned.
- ✓Breach response runbook created.
- ✓Access controls reviewed.
- ✓Leadership briefed on DPDPA basics.
- ✓Public privacy/trust page updated.
If three or more of these are still open, the Supreme Court case is not your biggest problem.
Your data operations are.
Bottom Line
The DPDP Act is in force.
The Supreme Court is reviewing parts of it.
The rules and enforcement framework are evolving.
Your customers are already watching.
None of this is a reason to pause compliance.
The businesses that come out ahead will not be the ones that tracked every hearing but fixed nothing. They will be the ones that used this uncertainty window to map their data, clean up consent, tighten vendors, define retention and prepare for breaches.
Verified digital trust is built by what you do this quarter — not by what the bench rules next year.
Sources
- 1.The Digital Personal Data Protection Act, 2023 — Gazette of India Extraordinary, Part II, Section 1, No. 45, dated 11 August 2023 (S.O. 3544(E))[Gazette]
- 2.Digital Personal Data Protection Act 2023, Section 44(3), which substitutes Section 8(1)(j) of the RTI Act 2005 — verify against MeitY official Act text published on India Code portal[Act text]
- 3.Verify current status of Supreme Court Writ Petition(s) challenging DPDPA — check Supreme Court of India case status portal for any interim orders; as of available information no general stay has been granted[Court judgment]
- 4.Digital Personal Data Protection Act 2023, Schedule 1 — Penalties; Item 1 specifies up to ₹250 crore for failure to take reasonable security safeguards under Section 8(5)[Act text]
- 5.Digital Personal Data Protection Rules 2025, notified via Gazette of India — verify specific rules covering consent managers (Rule 4), breach notification timelines, and SDF criteria to assess what is resolved vs. still pending[Notified Rules]
- 6.DPDP Rules 2025 — verify Rule on breach notification to Data Protection Board; confirm exact prescribed timeline and whether 72-hour window is the notified standard or an approximation[Notified Rules]
- 7.Digital Personal Data Protection Act 2023, Sections 11–14 — right to information (S.11), correction and erasure (S.12), grievance redressal (S.13), nomination (S.14)[Act text]
- 8.Digital Personal Data Protection Act 2023, Section 7 — Certain Legitimate Uses; lists exhaustive categories where processing is permitted without consent[Act text]
Get daily briefings by email
2-min reads, plain English, every morning. Free forever.
Need expert guidance?
Our team helps Indian businesses turn DPDPA readiness into a visible trust signal.
Get Consultation →