How to Choose Your Consent Management Approach as Rule 4 Takes Effect

    DPDP Consent Manager or CMP? See what Rule 4 changed in November 2026, what starts in May 2027, and how to choose the right consent management approach.

    OneConsentBlog
    9 min read
    Tuesday, 17 November 2026
    How to Choose Your Consent Management Approach as Rule 4 Takes Effect

    Rule 4 of the Digital Personal Data Protection Rules, 2025 took effect on 13 November 2026 and opened registration for Consent Managers under the Digital Personal Data Protection Act, 2023 (DPDP Act). For a business that collects customer data, the decision ahead is wider than registration. Your team has to decide how it will manage consent across its digital and in-store channels and the systems behind them.

    A registered DPDP Consent Manager and a consent management platform (CMP) play different roles. Once you know the difference, you can decide which work stays in-house and where onboarding with a Consent Manager may apply before the wider consent provisions begin on 13 May 2027.

    What Rule 4 and the DPDP Consent Manager Framework Change for Data Fiduciaries

    The Act defines a Consent Manager as a person registered with the Data Protection Board of India who acts as a single point of contact through which a Data Principal can give, manage, review and withdraw consent. Data Principals are the individuals to whom the personal data relates. A business that determines the purpose and means of processing personal data is a Data Fiduciary.

    On 14 November 2026, the Ministry of Electronics and Information Technology launched the application portal at dpbi.gov.in. Companies incorporated in India can apply if they meet the First Schedule conditions. One condition is a net worth of at least ₹2 crore, alongside adequate technical and financial capacity. Applicants also need independent certification of their platform against the standards and assurance framework that the Board publishes. The Board assesses each application and publishes the particulars of the entities it registers. Buyers can check a provider's registration claim against that list. Press reports in mid-November 2026 indicated that the government had yet to appoint the Board's Chairperson and Members. Timing of the first registrations is open until it does.

    Rule 4 does not require a business to register as a Consent Manager or to appoint one. From 13 May 2027, individuals will have the option of managing their consent through a registered Consent Manager. Notices and consent evidence stay the Data Fiduciary's responsibility.

    Consent Manager vs CMP: Which One Does Your Business Need?

    A registered Consent Manager under the DPDP Act is a regulated entity. Once the relevant provision commences on 13 May 2027, it gives individuals a single point of contact for consent across the Data Fiduciaries onboarded on its platform. The First Schedule requires it to ensure that personal data shared through its platform is not readable by it. It must also avoid conflicts of interest with Data Fiduciaries and perform its obligations without subcontracting. Consent Managers keep consent records for at least seven years.

    A consent management platform is software that a business uses to run its own consent operations across its customer channels. Operating one needs no registration under Rule 4. From 13 May 2027, where consent is the ground for processing and a question arises in a proceeding, the Data Fiduciary must be able to demonstrate that it gave notice and obtained consent. A business that collects consent in its own channels needs this business-side capability. Onboarding with a registered Consent Manager does not replace it.

    Three Consent Management Approaches and How to Choose

    A business can maintain its own consent management systems, onboard with a registered Consent Manager, or combine both. All three are operating models with no separate status under the Act. Individuals decide whether to use a registered Consent Manager, and the business decides whether to onboard.

    Evaluation area

    Own systems or CMP

    Registered Consent Manager

    Combined approach

    Primary role

    Manages business-side consent operations

    Enables individuals to manage consent through its platform

    Supports both

    Consent records

    Maintained by the business

    Keeps records of actions on its own platform; the business keeps its own records

    Maintained across both roles

    Consent withdrawal

    Business-managed workflows

    Enables withdrawal through its platform

    Requires coordinated updates

    CRM and POS integration

    Controlled by the business

    Depends on onboarding and integration

    Combined integration

    Registration under Rule 4

    Not needed to operate a CMP

    Board registration required

    Only the Consent Manager entity registers

    Customer preferences

    Can cover wider marketing preferences

    Limited to its consent management role

    Can cover both

    Your choice depends on how the business collects and shares personal data. Many customer touchpoints can make a CMP useful without requiring the business to onboard with a registered Consent Manager. Onboarding is worth evaluating where customers may want to manage consent through a platform that several Data Fiduciaries use.

    Decision signal

    What it tells the business

    Multiple customer touchpoints

    A CMP may be needed to manage consent across channels

    Multiple business systems

    Integration and synchronisation capabilities carry more weight

    Data sharing between organisations

    Onboarding may be relevant where customers choose a registered platform and the business participates in it

    Internal technology capability

    How far the business can maintain its own consent processes

    The Rules place duties on the Consent Manager towards the Data Fiduciaries onboarded on its platform and contain no express duty on a Data Fiduciary to onboard. Published legal commentary differs on how far a business must be able to interface with a Consent Manager that an individual chooses. You can plan on that basis by keeping onboarding optional and making sure your systems can act on a consent or withdrawal that arrives through any channel. Assign one executive to own the decision across technology and business functions. Appointing a Data Protection Officer is a separate requirement that applies only to businesses the Central Government notifies as Significant Data Fiduciaries.

    How Consent Needs Differ Across Industries

    Consent is one of the grounds for processing personal data under the Act. Some activities rely on other permitted grounds. Processing that a specific legal requirement demands, such as an applicable KYC obligation, may not depend on consent. Promotional communication may be a separate consent-based activity. Teams should identify the applicable ground for each purpose before they design a consent workflow. For children's personal data, the Act adds requirements that include verifiable parental consent, subject to prescribed exemptions.

    Industry

    Customer data touchpoints where consent may be relevant

    What to evaluate

    Retail

    Loyalty registration, POS, website and app

    Consistency across stores, CRM and campaigns

    BFSI

    Loan applications, onboarding and marketing

    Purpose-specific consent and evidence

    F&B

    App registration, reservations and WhatsApp

    Preferences across ordering and marketing systems

    D2C

    Website, checkout and campaigns

    Consent synchronisation with the CRM

    Real estate

    Enquiry forms, site visits and follow-ups

    Lead communication permissions

    EdTech

    Student and parent registrations

    Children's data requirements and parental consent

    Manufacturing

    Employee, dealer and supplier interactions

    Data handling across HR and partner systems

    Telecom

    Onboarding, service requests and call centres

    Communication preferences across channels

    What Should You Check Before Investing in a CMP?

    Rule 4 mandates none of the checks in the table; they are recommended procurement practice for any DPDP consent management solution, purchased from a vendor or built in-house. Ask the vendor to demonstrate the platform on one of your own customer journeys.

    Criterion

    What to confirm with the vendor

    Consent collection

    Coverage of website, app, POS and offline forms

    Purpose management

    Separate consent for each purpose

    Withdrawal

    The steps that follow when a customer withdraws consent

    System integration

    Synchronisation with CRM, loyalty and marketing platforms

    Record keeping

    Retrieval of the consent date, the notice shown and later changes

    Customer experience

    A simple way for customers to review and change preferences

    Security and governance

    Access controls, audit mechanisms and accountability

    Scale

    Support for multiple brands, business units and volumes

    Vendor accountability

    Ownership of implementation, maintenance and support

    Cost and implementation time depend on the number of collection channels and integrated systems, with existing consent records and notice languages adding to the scope. Keep a provisional budget line for Consent Manager onboarding, because press coverage of the portal launch notes that the position on fees is unclear.

    Read more on the two roles in Consent Manager vs Data Fiduciary

    Can Your CRM, POS and Marketing Systems Act on Consent Changes?

    After an individual withdraws consent for a purpose, each connected system needs the updated status before it next processes data for that purpose. For promotional messaging that relies on consent, the CRM and the messaging provider need the latest status before they send a campaign. Withdrawal for one purpose leaves untouched the personal data that the business processes for other purposes on a different ground. Different system architectures can meet this need. From 13 May 2027, a withdrawal may also arrive through the DPDP Consent Manager framework.

    OneConsent's Consent and Preference Management module captures purpose-specific consent and records each withdrawal, with preferences synchronised across connected systems. A consent management platform in India such as OneConsent operates on the business side and is not a registered Consent Manager. DPDP compliance software supports these operations. Responsibility for DPDP obligations stays with the business.

    What to Prepare Before 13 May 2027

    The activities in the table apply under any of the three approaches. Onboarding with a registered Consent Manager is a separate evaluation for businesses where it applies. For consent that an individual gave before the Act commenced, the Act allows processing to continue until the individual withdraws it. The Data Fiduciary gives those individuals a notice as soon as reasonably practicable, under a provision that commences on 13 May 2027. Legal teams should assess processing that rests on other grounds purpose by purpose. Legal counsel should also confirm how the business will respond when a Data Principal chooses to use a registered Consent Manager.

    Preparation activity

    Responsible team

    Identify all customer data collection touchpoints

    Business and operations

    Review notices and purposes for processing

    Legal and compliance

    Check existing consent records and notice versions

    Compliance and IT

    Plan the notice to customers who gave consent before the Act commenced

    Legal and marketing

    Test consent withdrawal across connected systems

    IT and marketing operations

    Identify activities that rely on consent and those that rely on certain legitimate uses

    Legal and compliance

    Review Data Processor and vendor arrangements

    Legal and procurement

    Assign ownership for ongoing consent management

    Business, IT and compliance

    Assess Your DPDP Consent Management Gaps with OneConsent

    Managing consent across customer channels involves three things: purpose-specific consent records, a working withdrawal process and current preferences in the systems that use them. If your team is weighing the DPDP Consent Manager model against a platform for its own channels, the OneConsent team can review how you collect and record consent today. You then receive personalised findings on gaps and integration needs. Visit the OneConsent consent platform to see how it supports purpose-specific consent and withdrawal management. Your team can then book a demo to review its own consent journeys.

    Frequently Asked Questions

    Have more questions?

    Search our full DPDP knowledge base for more answers.

    See it live

    See OneConsent in action

    Get a personalised walkthrough of how OneConsent helps your teams stay DPDPA compliant.

    • 30-minute walkthrough
    • DPDPA-ready by design
    • Tailored to your stack