Rethinking DPDP’s Compressed Timelines: What the Applause Is Missing
Most commentary around DPDP’s compressed timelines has been celebratory. Speed is being equated with seriousness. Urgency with progress.
We chose to wait.
Not to be contrarian, but to let the applause fade before asking a harder question:
What does this direction signal about how the law will actually be interpreted and enforced?
What follows is not a reaction to timelines. It reflects how we at truConsent read the law’s trajectory as a constitutional and operational framework.
What the January 22 Signal Really Was
This did not feel like consultation. It felt like expectation-setting.
The January 22 closed-door discussion with large technology companies appears to have served a clear purpose: normalising compressed timelines as the new baseline.
Foreign MNCs were the first audience. That matters.
Once urgency is accepted at that scale, it rarely stays contained. Banking, healthcare, telecom, and other regulated sectors will follow. This looks less like an exception and more like sequencing.
Urgency is being positioned as default behaviour, not a special case.
What Is Being Prioritised First
What also stood out was what the government wants operationalised first:
- State access
- Data retention
- Traffic logs
- Exemption frameworks
- Cross-border controls
At the same time, citizen-facing safeguards remain structurally underprepared.
The Data Protection Board is still missing, yet enforcement is accelerating.
A rights-based law cannot begin by fully activating state-side powers while the primary adjudicatory mechanism remains absent.
In India, rights often survive because courts and citizens act as correctives.
That corrective weakens when enforcement moves faster than institutions.
Why Downplaying Change Undermines the Law Itself
The assertion that accelerated provisions do not require meaningful change is not just technically questionable. It is philosophically revealing.
When compliance is framed as something that can be absorbed with minimal effort, the message to industry is implicit but clear: this law does not require deep attention.
Less time is not urgency. It is often an invitation to look for the easiest path through.
Data protection, done seriously, demands deliberate choices. About retention. About access. About accountability. These are not changes organisations can make responsibly under compressed timelines without trade-offs.
When the law is positioned as “easy to comply with,” the risk is not infrastructure strain. The risk is shallow engagement.
At scale, that leads to:
- Superficial implementations
- Checkbox compliance
- Over-retention to stay “safe”
- Systems built to pass scrutiny, not uphold rights
A law that protects fundamental rights cannot be treated as friction to be minimised.
When speed becomes the primary signal, seriousness is quietly deprioritised. And that weakens the law long before any technical failure does.
Where the Law Starts Contradicting Itself
The real risk isn’t compressed timelines. It’s ecosystem fragility.
India’s privacy ecosystem is still evolving. Interpretations are fluid. Tooling is maturing. Even solution providers are learning in real time.
When Enforcement Undermines Privacy-by-Design
Blanket data retention mandates collide directly with privacy-by-design and purpose limitation.
Mandating year-long retention of personal data and traffic logs incentivises organisations to retain everything “just in case.”
When that happens, principles stop guiding behaviour and start becoming decorative language.
Principles become optional. Enforcement does not.
That is the moment a rights-based law begins to drift into a procedural regime, hollowed out by its own operational priorities.
Startup Exemptions and the Risk of a Two-Tier Privacy Regime
Privacy cannot be a fundamental right in theory and a scaled obligation in practice.
Proposed exemptions for startups may appear pragmatic, but they introduce a structural contradiction.
Selective seriousness creates:
- Different expectations
- Different risk thresholds
- Different standards of accountability
Over time, this fragments the privacy regime.
A foundational rights framework depends on universality. Once privacy obligations vary primarily by organisational size or convenience, the law starts resembling a compliance menu rather than a constitutional commitment.
That weakens the DPDP Act’s credibility not just as regulation, but as a rights framework.
These observations are offered in the spirit of strengthening the DPDP framework as it moves from intent to implementation. A measured approach now can help ensure the law achieves its objectives without unintended dilution.
