Introduction
As the Digital Personal Data Protection Act, 2023 (Digital Personal Data Protection Act, 2023) moves toward operational maturity, Data Fiduciaries are facing a strategic architecture question:
Will the ecosystem stabilise around the Act’s defined actors — Data Principal (DP), Data Fiduciary, Data Processor, and Registered Consent Manager — or will an additional, unregulated consent middleware layer continue to sit between them?
Or will a fifth, unregulated middleware layer continue to sit between them?
This is not a tooling debate. It is a structural question about legal design, accountability, and risk allocation.
Route 1: The Integrated Fiduciary Model
(Data Fiduciary + Registered Consent Manager Directly)
In this model, the Data Fiduciary integrates a compliance interface provided directly by a Registered Consent Manager (Consent Manager).
The Consent Manager provides an integrated compliance package that sits directly on the Data Fiduciary’s platform. There is no separate, unregulated connector layer.
DPDPA / DPDPR Compliance Check
Notice (Section 5): The Consent Manager's Integration renders the notice. Even though the Data Fiduciary "configures" it, the Consent Manager ensures it meets the Rule 3 requirement for itemised, clear, and multi-lingual notices.
Consent (Section 6): Capture is done directly by the Consent Manager. This satisfies the "Affirmative Action" requirement at the source, preventing any "Notice-to-Action" mismatch.
Interoperability (Rule 4): Since the Consent Manager captures the data, the artefact is natively compliant with the MeitY/DPBI API standards. There is no "translation" loss.
Conflict of Interest (Rule 4, Sch 1): You must prove to the Board that your SDK's UI is neutral and doesn't "nudge" users for the Data Fiduciary.
Question 1: Does this make the Consent Manager a Data Processor?
Under this interpretation, yes — by design.
When the Consent Manager enables consent collection and maintains the consent artefact on behalf of the Data Fiduciary, it is performing a processing activity. In that functional sense, it operates as a Data Processor.
However, this is not a standard vendor relationship.
The Consent Manager is a processor with a statutory license and independent obligations under the Act. Those duties cannot be contracted away.
Question 2: Does this make the Consent Manager a Data Fiduciary?
No.
A Data Fiduciary determines the purpose and means of processing personal data. The Consent Manager does neither. It does not decide why data is processed or how it is used.
The Act gives the Consent Manager a fiduciary responsibility toward the Data Principal — meaning a duty of good faith and accountability. But it is not a “Data Fiduciary” in the structural sense.
That distinction matters.
The Consent Manager safeguards the permission layer. The Data Fiduciary owns the processing layer.
Structural Implication
If consent is meant to be managed by a registered, regulated entity, is there conceptual room for an additional unregulated intermediary between the Data Fiduciary and the Consent Manager?
In this interpretation, the answer leans toward no.
Why?
Because:
- The Data Fiduciary understands its own infrastructure best.
- The Data Fiduciary must build the integration necessary to interact with the Consent Manager.
- An unregulated connector adds no statutory protection.
- It introduces an additional dependency without regulatory accountability.
The law allows Data Fiduciaries to manage consent internally. But once a Data Fiduciary chooses to rely on a Consent Manager, inserting a separate unregulated layer raises a governance question: what legal value does that intermediary provide?
Route 2: The Middleware Model
(Data Fiduciary + Unregulated CMP + Registered Consent Manager)
Some in the industry continue to advocate for an additional consent management platform (CMP) or connector layer that captures consent and then synchronizes with a Registered CM.
This model effectively creates four actors:
- Data Principal
- Data Fiduciary
- Data Processor(s)
- Registered Consent Manager
- Plus an unregulated CMP layer
The Structural Weakness
The concern here is not technical capability. It is regulatory symmetry.
If an unregulated middleware captures consent and later syncs it with a Consent Manager, the Data Fiduciary remains dependent on an entity that:
- Has no license
- Bears no independent statutory duty toward the Data Principal
- Faces no direct regulatory consequences under the Act
In a high-stakes enforcement scenario, this layer does not shield the Data Fiduciary. The statutory exposure remains with the Data Fiduciary, including penalties that may extend up to ₹250 Crore.
The question becomes practical:
If the Act creates a regulated role specifically for consent management, why recreate that function through an unregulated intermediary?
Incentive Alignment: Who Protects the Data Principal?
A recurring critique is this:
If the Data Fiduciary selects and pays the Consent Manager, can the Consent Manager truly safeguard the Data Principal?
Let’s unpack that carefully.
Because of the deep technical integration required, the Data Principal does not select the Consent Manager. The Data Fiduciary does.
The Data Fiduciary selects a “licensed consent manager” to manage the consent interface.
The protection for the Data Principal does not arise from commercial independence. It arises from regulatory dependence.
A Registered Consent Manager must:
- Maintain statutory compliance
- Satisfy “fit and proper” requirements
- Meet prescribed financial thresholds
- Avoid regulatory action that could jeopardise its license
- Avoid incurring monetary penalties
Consent Manager survival depends on regulatory standing — not merely client retention. The license is the structural check.
That said, even structural checks can prove porous in practice, and regulatory interpretation may tighten or evolve as enforcement and standards mature.
In effect, the Act creates a licensed intermediary whose accountability runs toward the regulator and the Data Principal, even if its commercial contract runs with the Data Fiduciary.
At present, the law does not mandate that Data Principals select their CM. But the expectation in the ecosystem is that transparency and portability mechanisms may evolve further over time.
Expectation, not a settled fact.
The Open Question: Is There Room for a Fifth Player?
The Act clearly recognizes:
- Data Principal
- Data Fiduciary
- Data Processor
- Registered Consent Manager
It does not explicitly define, regulate, or prohibit an additional CMP class.
So the industry question is:
Will the ecosystem stabilise around a direct Data Fiduciary–Consent Manager integration model?
Or will unregulated middleware persist as a parallel compliance layer?
Our current reading suggests that once a Data Fiduciary opts into the Consent Manager architecture, introducing an unregulated intermediary offers limited legal advantage and adds governance complexity.
That said, implementation practice often evolves differently from legislative theory.
Data Processors today are indirectly regulated through contractual control and Data Fiduciary liability. Over time, regulatory expectations around processors may tighten further. The ecosystem may mature in stages.
But structurally, the intent appears to favour a system where:
- The entity using data (Data Fiduciary) is accountable.
- The entity managing consent (Consent Manager) is licensed.
- Everyone touching a citizen’s “Yes” or “No” sits within a defined regulatory perimeter.
Whether practice fully aligns with that architecture remains an open question.
