DPDP Rules 2025Updated 22 November 202610 min read

Consent Manager Obligations: First Schedule Part B Explained

The thirteen Part B obligations every registered DPDP Consent Manager must meet, with engineering detail on data-blind sharing, seven-year consent ledgers, disclosures and audits.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
Rule 4(3); First Schedule, Part B, items 1–13
Applies from
Registration (Rule 4 in force 13 Nov 2026)
Record retention
At least 7 years
Disclosure threshold
Shareholdings above 2 per cent
Data access
Shared contents must not be readable by the Consent Manager
Change of control
Prior Board approval required
Enforcement
Board directions, suspension or cancellation (Rule 4(4)–(5))

Quick answer

Under Rule 4(3) and First Schedule Part B of the DPDP Rules, a registered Consent Manager has 13 obligations: route consent to onboarded fiduciaries, never be able to read shared data, keep a consent, notice and sharing record for at least seven years, never sub-contract, keep data secure, act as a fiduciary, avoid conflicts, publish ownership, report audits to the Board and get approval before any change of control.

  • Part B has thirteen obligations that apply to every registered Consent Manager from registration, since Rule 4 came into force on 13 November 2026.
  • Item 2 requires a data-blind design: the Consent Manager must not be able to read personal data shared through its platform.
  • Items 3 and 4 require a consent, notice and sharing record, accessible and exportable in machine-readable form, kept for at least seven years.
  • Item 6 bars sub-contracting or assigning any obligation, which constrains how the platform uses outside vendors.
  • Items 11 to 13 require ownership disclosures above two per cent, Board-reported audits and Board approval before any change of control.

Who this is for: Registered and prospective Consent Managers, Platform and security architects, Compliance and internal audit teams, Data Fiduciaries integrating with Consent Managers, Company secretaries

What obligations does a Consent Manager have?

Rule 4(3) says a Consent Manager has the obligations in Part B of the First Schedule. There are thirteen.

ItemObligation
1Enable consent to an onboarded Data Fiduciary, directly or through another onboarded fiduciary that holds the data
2Make data available or share it so that its contents are not readable by the Consent Manager
3Keep a record of consents given, denied or withdrawn; preceding or accompanying notices; and sharing with transferee fiduciaries
4Give the Data Principal access to the record, a machine-readable copy on request, and keep it at least seven years
5Maintain a website or app, or both, as the primary means of access
6Not sub-contract or assign any obligation under the Act and Rules
7Take reasonable security safeguards to prevent personal data breach
8Act in a fiduciary capacity towards the Data Principal
9Avoid conflicts of interest with Data Fiduciaries, including their promoters and KMP
10Have measures so directors, KMP and senior management create no conflict through interests in fiduciaries
11Publish promoters, directors, KMP, senior management, shareholders above 2%, and bodies corporate where insiders hold above 2%
12Maintain audit mechanisms and report outcomes to the Board
13Not transfer control without the Board's prior approval

These apply from registration. Since Rule 4 has been in force since 13 November 2026, they are live law for anyone the Board registers.

Item 1 describes two flows, illustrated with banks B1 and B2 onboarded onto platform P.

  • Direct. B1 requests consent on P to process X's bank statement. X holds the statement in her digital locker, gives consent to B1 on P, and gives B1 access to the statement.
  • Routed. B1 requests consent; X's account is with B2. X uses P to route consent through B2 to B1 and digitally instructs B2 to send the statement to B1. B2 sends it.

Item 2 requires that the manner of making data available or sharing it is such that its contents are not readable by the Consent Manager.

Engineering patterns consistent with item 2:

  1. Orchestrate, do not carry. The platform issues consent artefacts and instructions; data moves fiduciary to fiduciary.
  2. End-to-end encryption where data does transit. If payloads pass through platform infrastructure, encrypt them to the recipient fiduciary's key so the platform never holds decryption keys.
  3. Metadata minimisation. The platform necessarily knows who consented to whom for what, because item 3 requires a record of it. It should not know the content of the data shared.
  4. Key management separation. Document how keys are generated and held so an independent certifier, under Part A item 9, can verify the platform cannot decrypt.

Keep logs that prove the data-blind property, not just architecture diagrams.

Item 3 requires a platform record of three things for each Data Principal:

  • (a) consents given, denied or withdrawn by her;
  • (b) notices preceding or accompanying requests for consent; and
  • (c) sharing of her personal data with a transferee Data Fiduciary.

Item 4 adds three duties: give her access to the record; on request and under the terms of service, provide the information in machine-readable form; and maintain the record for at least seven years, or longer if agreed with her or required by law.

A design that satisfies this:

FieldPurpose
event_id, timestampOrdering and integrity
principal_refWho
fiduciary_id, transferee_idTo whom, and onward sharing
purpose_id, notice_hashWhat she was told, with the notice text stored by hash
actiongiven / denied / withdrawn / shared
channelApp, web, API

Make the ledger append-only and tamper-evident, for example with hash-chained entries. Export to JSON or CSV for the machine-readable copy. Store notices by content hash so you can prove exactly what text accompanied a request years later.

Note that the seven-year Consent Manager record is separate from the one-year minimum that Rule 8(3) places on Data Fiduciaries for processing logs. See one-year log retention.

Items 5 to 8: channel, no outsourcing, security, fiduciary duty

Item 5: website or app as primary channel. The Consent Manager must develop and maintain a website or app, or both, as the primary means through which Data Principals access its services. Integrations into partner apps can exist, but the Consent Manager's own interface is the anchor.

Item 6: no sub-contracting or assignment. The Consent Manager shall not sub-contract or assign the performance of any of its obligations under the Act and the Rules. This does not obviously prohibit using cloud infrastructure or software tools, but it does mean the Consent Manager cannot hand an obligation, such as maintaining the record or responding to Data Principals, to another company to perform. Map each Part B obligation to an internal owner and document how vendors support, rather than perform, it. Take legal advice on borderline vendor arrangements.

Item 7: reasonable security safeguards. The Consent Manager must take reasonable security safeguards to prevent personal data breach. Rule 6, which lists minimum safeguards for Data Fiduciaries from 13 May 2027, is a sensible benchmark: encryption, access control, logging and monitoring, backups and contract clauses. See reasonable security safeguards.

Item 8: fiduciary capacity. The Consent Manager acts in a fiduciary capacity in relation to the Data Principal. Design choices such as default settings, the order in which fiduciaries are shown, and nudges should favour the individual's interests, not those of fiduciaries paying for onboarding.

Items 9 to 11: conflicts of interest and public disclosures

Item 9 requires the Consent Manager to avoid conflicts of interest with Data Fiduciaries, including in respect of their promoters and key managerial personnel.

Item 10 requires measures so that no conflict arises from directors, KMP or senior management holding a directorship, financial interest, employment or beneficial ownership in Data Fiduciaries, or having a material pecuniary relationship with them. Part A item 7 requires both items to be embedded in the memorandum and articles.

Item 11 requires easily accessible publication on the website or app of:

  • (a) promoters, directors, KMP and senior management;
  • (b) every person holding more than two per cent of the company's shares;
  • (c) every body corporate in whose shareholding any promoter, director, KMP or senior manager of the Consent Manager holds more than two per cent, as on the first day of the preceding calendar month; and
  • (d) anything else the Board directs in the interests of transparency.

Item 11(c) implies a monthly refresh. Build a disclosure pipeline: collect declarations from each insider, reconcile with share registers, and publish a dated page each month. "Body corporate" is defined broadly in the Schedule note to include companies, firms, financial institutions, scheduled banks, public sector enterprises and other incorporated associations.

Items 12 and 13: audits and change of control

Item 12 requires effective audit mechanisms to review, monitor, evaluate and report the outcome to the Board, periodically and whenever the Board directs, on:

  • (a) technical and organisational controls, systems, procedures and safeguards;
  • (b) continued fulfilment of the registration conditions in Part A; and
  • (c) adherence to obligations under the Act and Rules.

The Rules do not fix the audit frequency or format, so design an annual cycle as a baseline and be ready for ad hoc Board-directed audits. Map controls to each Part B item, collect evidence continuously, and keep audit reports ready to submit.

Item 13 says control of the company cannot be transferred by sale, merger or otherwise except with the previous approval of the Board and subject to conditions it specifies. "Control" carries its Companies Act, 2013 meaning. Build Board approval into any term sheet that could shift control, as a condition precedent.

Board enforcement. Under Rule 4(4) the Board can, after a hearing, direct measures to restore adherence. Under Rule 4(5) it can suspend or cancel registration and give protective directions, by reasoned written order, after a hearing. Under Rule 4(6) it can call for information at any time. Treat the Board as a supervisor with continuous visibility, not a one-time licensor.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Document both consent flows

    Show how direct and routed consent work on your platform, mirroring the B1 and B2 illustration.

    Part B, item 1

  2. Prove the platform is data-blind

    Use end-to-end encryption or direct fiduciary-to-fiduciary transfer so the platform cannot read shared contents.

    Part B, item 2

  3. Build an append-only consent ledger

    Record consents, notices and sharing events, with access and machine-readable export, retained for at least seven years.

    Part B, items 3 and 4

  4. Map every obligation to an internal owner

    Ensure no obligation is sub-contracted or assigned to another company.

    Part B, item 6

  5. Publish a monthly ownership disclosure

    List insiders, shareholders above two per cent and bodies corporate where insiders hold above two per cent.

    Part B, item 11

  6. Set up a Board-reportable audit cycle

    Audit controls, continued Part A eligibility and obligation adherence, and be ready for directed audits.

    Part B, item 12

  7. Add Board approval to control-change deals

    Make prior Board approval a condition of any sale, merger or transaction shifting control.

    Part B, item 13

Key dates

  1. Rule 4 in force; Part B binds registered Consent Managers

  2. Rule 14 rights publication and 90-day grievance ceiling apply to Consent Managers

Answers

Frequently asked questions

Can a Consent Manager see the personal data it helps share?

No. Item 2 of Part B of the First Schedule requires that personal data be made available or shared in a way that its contents are not readable by the Consent Manager. The platform may record that consent was given and data shared, but should not be able to read the data itself.

How long must a Consent Manager keep records?

At least seven years under Part B item 4(c), or longer if agreed with the Data Principal or required by law. The record covers consents given, denied or withdrawn, the notices accompanying consent requests, and each sharing of her data with a transferee Data Fiduciary.

Can a Consent Manager outsource its obligations?

No. Part B item 6 prohibits sub-contracting or assigning the performance of any obligation under the Act and Rules. Vendors can support the business, but the Consent Manager must itself perform each obligation. Take legal advice on borderline vendor arrangements.

What ownership details must a Consent Manager publish?

Under Part B item 11, its promoters, directors, key managerial personnel and senior management; every shareholder holding more than two per cent; every body corporate in which those insiders hold more than two per cent, as on the first day of the preceding month; and anything else the Board directs.

Do Consent Managers have grievance obligations under DPDP?

Yes. Rule 14 requires Consent Managers, as well as Data Fiduciaries, to publish how Data Principals can exercise rights and to publish a grievance response period not exceeding 90 days. Rule 14 applies from 13 May 2027, while Part B obligations already apply from registration.

Can a Consent Manager be sold?

Only with the Data Protection Board's previous approval. Part B item 13 says control of the company cannot be transferred by sale, merger or otherwise without that approval and fulfilment of any conditions the Board specifies.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 4(3)–(6) (official text)
  • Digital Personal Data Protection Rules, 2025 — First Schedule, Part B, items 1–13 (official text)
  • Digital Personal Data Protection Act, 2023 — Section 6(7)–(9) (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.