DPDP consent management, built into your apps
Clear notices, consent records you can prove, and withdrawals that reach every system and vendor, whether you buy a consent platform or build it.
What each record holds
Consent Manager or consent management?
13 November 2026 is when the Consent Manager registration rules start. For most companies it is not a deadline. What you need is consent management; your main deadline is 13 May 2027.
Registered Consent Manager
- Registers with the Data Protection Board
- Runs a consent platform for other companies
- Indian company with a net worth of at least ₹2 crore
- Registration rules (Rule 4) start on 13 November 2026
Consent management
- Needed by every company that relies on consent
- A clear notice for each purpose
- Consent records you can prove
- A way to withdraw, and withdrawals that are respected everywhere
Still unsure? Read our DPDP Consent Manager decision guide.
What DPDP consent records look like.
Consent you can prove: what each person was told, what they agreed to, and what happened when they changed their mind.
Notice per purpose
A clear notice wherever personal data is collected, for each purpose you use it for.
Versioned notices
Every change to a notice gets a version, so you know what each person saw.
Consent per purpose
Consent recorded separately for each purpose, never bundled into one tick box.
Consent log
Who agreed to which notice version, when, and through which app or channel.
Withdrawal
A way to withdraw from the same place consent was given.
Downstream changes
Withdrawals sent to every system and vendor that received the data.
Itemised notices engineers can build.
Rule 3 of the DPDP Rules sets the minimum a notice must contain. Each part maps to something you can build and test. Our guide to DPDP consent logs shows the schema that ties each consent to the notice version behind it.
Stands on its own
The notice makes sense without the privacy policy or terms behind it (Rule 3(a)). Render it as its own screen or panel, not a link inside a tick box.
Itemised data
One line for each item of personal data, such as name, mobile number or PAN (Rule 3(b)(i)). Generate the list from your field inventory so it changes when the form does.
Purpose and service
Each specified purpose, with the goods, service or use it enables (Rule 3(b)(ii)). Give every purpose an ID that the consent record points to.
Three links
How to withdraw consent, as easily as it was given; how to use your rights; and how to complain to the Data Protection Board (Rule 3(c), Section 5(1)).
A named contact
Contact details of the Data Protection Officer, where there is one, or another person who answers rights requests (Section 6(3)).
Before or with the request
The notice comes with or before the request for consent, never after it (Section 5(1)).
A stored version
Every notice version and language is stored and never edited in place, because you must prove what each person was shown (Section 6(10)).
Notices in 22 languages.
The Act gives each person the option to read the notice and the consent request in English or any language in the Eighth Schedule to the Constitution (Sections 5(3) and 6(3)). Our partner law firm advises on how you meet that; the build below keeps every language in step.
What to build
- Store each notice as data: data items, purpose IDs, contact and links
- One translation per language, tied to the same notice version
- A language switch on the notice and on the consent request
- Log the language shown with each consent record
- Block a new version going live until every language you offer is updated
Eighth Schedule languages
Assamese, Bengali, Bodo, Dogri, Gujarati, Hindi, Kannada, Kashmiri, Konkani, Maithili, Malayalam, Manipuri, Marathi, Nepali, Odia, Punjabi, Sanskrit, Santali, Sindhi, Tamil, Telugu, Urdu.
Buy, build or both.
You don’t always need a consent management platform. We help you choose, then build or integrate it.
Buy a consent platform
We help you choose one, then connect it to your apps, data warehouse and vendors.
Build it into your apps
Consent capture, a consent service and a consent log, built into the systems you already run.
Mix of both
A platform for web and app journeys, with consent and withdrawals passed to your back-office systems.
How we deliver.
Consent is one part of DPDP implementation. We can build it on its own or alongside rights requests, retention and breach workflows.
- Step 1
Find
List every place you collect personal data and the purposes you use it for.
- Step 2
Design
Plan notices, consent records and withdrawals, and choose buy, build or both.
- Step 3
Build
Build or integrate consent capture and the consent log.
- Step 4
Connect
Pass consent and withdrawals to every system and vendor that uses the data.
- Step 5
Evidence
Check the logs and send notice wording to our partner law firm.
Related DPDP services.
DPDP gap assessment
Find every system that holds personal data before you change how consent works.
See the assessmentDPDP implementation
Consent, rights requests, retention and breach workflows, built together.
See implementationDPDP compliance
Everything we do for DPDP, from the first data map to the evidence.
See DPDP complianceDPDP consent management FAQs.
What is the difference between a Consent Manager and consent management?
A Consent Manager is a company registered with the Data Protection Board to run a consent platform for others. Consent management is what every company that relies on consent needs: clear notices, consent records you can prove, and a way to withdraw. Most companies need consent management, not Consent Manager registration.
Is 13 November 2026 a deadline for my company?
For most companies, no. It is when the rules for registering as a Consent Manager start. Registration is for companies that want to run a consent platform for others: an Indian company with a net worth of at least ₹2 crore. Your main deadline is 13 May 2027.
Do we need a consent management platform?
Not always. You need consent records you can prove. Some companies buy a platform; many build consent capture and logging into their own apps. We help you choose, then build or integrate it.
What happens when someone withdraws consent?
We record the withdrawal, stop the processing that relied on it, and pass the change to every system and vendor that received the data. The consent log shows when each step happened.
Can you work with the consent platform we already use?
Yes. We connect it to your apps, data warehouse and vendors, so that consent and withdrawals are respected everywhere your data goes.