Consent Managers
SL-03A Data Principal may give, manage, review and withdraw consent through a Consent Manager registered with the Data Protection Board of India — and must be able to do so as easily as they gave it. Interoperability is the obligation; this directory is where it is administered.
Registered managers
4
Connected
1
Principals via managers
1,84,200
Consent held through a third party
Not Board-registered
1
Directory
Bharat Consent ExchangeBoard-registered
CM/DPBI/2026/0014
- Principals managed
- 1,84,200
- Connected
- 24 May 2026
- Interoperability test
- Passed 13 days ago
Nagrik Sammati SevaBoard-registered
CM/DPBI/2026/0027
- Principals managed
- 0
- Connected
- —
- Interoperability test
- Passed last month
SecureConsent IndiaBoard-registered
CM/DPBI/2026/0031
- Principals managed
- 0
- Connected
- —
- Interoperability test
- Never tested
OpenConsent CollectiveNot registered
—
- Principals managed
- 0
- Connected
- —
- Interoperability test
- Never tested
What linking a manager actually commits you to
The obligation is not to publish an API. It is that a withdrawal arriving through a Consent Manager has exactly the same effect as one made on your own portal — same propagation, same timeline, same audit record.
Grants arrive with the notice version the principal actually saw
Otherwise you cannot evidence that the consent was informed.
Withdrawals propagate downstream on the same clock
The propagation map does not care where the withdrawal came from.
The artefact trail is unified
One immutable event trail per artefact, regardless of channel.
Suspension of a manager does not invalidate consent already given
It stops new traffic. Existing artefacts stand until withdrawn or expired.