DPDP Consent Managers Go Live on 13 November 2026: What Indian Website and App Owners Need to Know
Abhay Singh
Author


Why everyone is talking about 13 November
If you run a website, a mobile app, an online store, or even a simple “Contact us” form, you have probably seen the letters DPDP all over your LinkedIn feed lately. You have probably also seen two very different messages: “Everything changes on 13 November!” and “Relax, nothing happens until 2027.”
The real picture sits somewhere in the middle, and it is more useful than either headline.
13 November 2026 is a genuine milestone in India’s data protection law. But it is mainly about a new kind of company called a Consent Manager. It is not the day ordinary businesses suddenly face penalties. The big obligations (privacy notices, security safeguards, breach reporting and more) are scheduled for 13 May 2027.
So can you wait? Not really. Building a proper consent system touches your database, your forms, your marketing tools and your vendors. That takes months, and May 2027 will arrive faster than your next big release.
In this guide to DPDP Act compliance, we explain in simple words what the DPDP Consent Manager rule changes on 13 November, what it does not change, and how to get your website or app ready for the DPDP Rules 2025.
A quick note before we start: we are a web development, app development and digital marketing company, not a law firm. This article explains what the official documents say so you can plan your technology. For advice on your specific situation, please speak to a qualified lawyer.
The 60-second summary
What starts on 13 November 2026: Rule 4 of the DPDP Rules, 2025 and section 6(9) of the DPDP Act. Companies that want to work as Consent Managers can apply to the Data Protection Board for registration.
What does not start that day: the Act’s penalty provisions for ordinary businesses. These, along with the main duties on notice, consent, security and breach reporting, are scheduled for 13 May 2027.
Is a Consent Manager compulsory for your business? Nothing in Rule 4 says so. It sets out who can register as a Consent Manager and what they must do.
How big can DPDP penalties get? Up to ₹250 crore for failing to take reasonable security safeguards. That is a maximum, not a fixed fine.
What should you do now? Map the personal data you collect, rewrite your privacy notices, make consent management and withdrawal easy, tighten security, and prepare a data breach notification plan.
DPDP vocabulary in plain English
India's data protection law, the DPDP Act, uses a few terms that sound heavy but are simple:
Data Principal: the person the data is about. Your customer, app user, newsletter subscriber or job applicant.
Data Fiduciary: whoever decides why and how personal data is used. That is usually you, the business.
Data Processor: someone who handles data on your behalf. Think of your hosting provider, CRM, email tool, SMS gateway, or the agency that manages your website.
Consent Manager: a registered company that gives people one place to give, manage, review and withdraw their consent across different businesses.
Data Protection Board of India: the body set up under the Act. It registers Consent Managers and conducts inquiries.
The DPDP timeline: three dates that matter
Date | What starts | Where it is written |
|---|---|---|
13 November 2025 | Rules 1, 2 and 17 to 21: short title, definitions and the working of the Data Protection Board | Rule 1(2) |
13 November 2026 | Rule 4 (Consent Manager registration) and section 6(9) of the Act | Rule 1(3) and the Act’s commencement notification |
13 May 2027 | Rules 3, 5 to 16, 22 and 23 (notice, security safeguards, breach reporting, erasure, children’s data, rights and more), plus the Act’s main obligations and penalty provisions | Rule 1(4) |
Why May 2027? It is eighteen months after the DPDP Rules 2025 were notified.
Date note: the Gazette notification (G.S.R. 846(E)) is dated 13 November 2025, and most legal summaries count from that date. A few summaries mention 14 November. Rule 4 starts “one year after publication”, so check the official Gazette for the exact day before you plan around it.
What exactly is a DPDP Consent Manager?
Imagine you use a loan app, an insurance website, a fitness app and an online store. Today, each of them has its own privacy settings. If you change your mind about sharing your data, you have to visit each one separately.
A Consent Manager is designed to fix that. Under section 6 of the Act, a person can give, manage, review or withdraw consent through a Consent Manager. The Consent Manager is accountable to that person and acts on her behalf. To do this work, it must be registered with the Data Protection Board.
Think of it as a single dashboard for consent, run by a regulated company instead of by each business separately.
Who can become a Consent Manager?
Under Rule 4 and the First Schedule, an applicant must, among other things:
be a company incorporated in India;
have a net worth of at least ₹2 crore;
show sound finances, adequate capacity and a management team with a record of fairness and integrity; and
have its interoperable consent platform independently certified as meeting the standards the Board publishes.
Applications go to the Board in the manner the Board publishes on its website. The Board can register an applicant, or reject the application and give its reasons.
What must a Consent Manager do?
The rules set strict obligations. In simple terms, a Consent Manager must:
make sure the personal data passing through its platform is not readable by the Consent Manager itself;
keep records of consents given, denied and withdrawn, the notices shown, and the sharing of data;
give users access to those records, provide them in machine-readable form on request, and keep them for at least seven years;
act as a fiduciary for the user, avoid conflicts of interest, and publish details about its promoters, directors and larger shareholders;
take reasonable security safeguards, run audits, and not outsource its core obligations; and
get the Board’s approval before control of the company changes hands.
The Board can also suspend or cancel a registration after giving the Consent Manager a hearing.
Does your business have to use one?
Rule 4 deals with how Consent Managers register and behave. It does not tell ordinary businesses to adopt one. For now, think of Consent Managers as a new layer of the ecosystem that your systems may one day need to talk to. That is a good reason to build your own consent system in a clean and flexible way.
Five myths about 13 November
Myth 1: “Penalties start on 13 November 2026.” Not for ordinary businesses. The Act’s penalty provisions (section 33 and the Schedule) are scheduled to start on 13 May 2027, together with the main obligations. What starts on 13 November 2026 is the Consent Manager registration framework.
Myth 2: “Every business must connect to a Consent Manager.” Rule 4 is about who can register as a Consent Manager and what they must do. It does not instruct ordinary businesses to use one. Section 6(7) says a person may use one.
Myth 3: “We have a cookie banner, so we are covered.” A banner can be a good starting point, but the rules ask for more. Your notice must make sense on its own, describe the specific personal data and purposes in plain language, and explain how to withdraw consent, exercise rights and complain to the Board (Rule 3). Also, a consent tool on your website is not the same thing as a registered Consent Manager.
Myth 4: “We are too small to matter.” The law talks about duties of a Data Fiduciary, which is defined by what you do with personal data, not by your headcount. Some extra duties apply only to big players. For example, the erasure timelines in Rule 8 cover only large e-commerce, online gaming and social media platforms, and Significant Data Fiduciary duties apply only to entities the government notifies. But basics like security safeguards and breach notification apply broadly. Do not assume you are exempt unless a notification or your lawyer says so.
Myth 5: “Our vendor handles security, so it is not our problem.” Rule 6 says the Data Fiduciary must protect personal data, including processing done on its behalf by a Data Processor, and expects the contract with that processor to include security safeguards. Your hosting company, CRM, email tool and even the agency that manages your website are part of your risk picture.
DPDP Act compliance: what changes for ordinary businesses on 13 May 2027
1. Privacy notices (Rule 3)
Your notice must make sense on its own, without the reader needing other documents. It has to explain in clear, plain language what personal data you collect (an itemised description) and why, including the goods, services or uses that the data enables. It must also give the link to your website or app and explain how people can withdraw consent (with ease comparable to giving it), exercise their rights, and complain to the Board.
2. Consent (section 6 of the Act)
Consent must be free, specific, informed, unconditional and unambiguous, and it must be given through a clear affirmative action. People can withdraw it at any time, and withdrawing should be about as easy as giving it. After withdrawal, you must stop processing within a reasonable time and make sure your processors stop too, unless the law allows or requires you to continue.
3. Security safeguards (Rule 6)
At a minimum, the rule expects:
encryption, obfuscation, masking or virtual tokens to protect personal data;
controls over who can access your systems;
logs, monitoring and review, so you can detect, investigate and fix unauthorised access;
backups or other measures so you can keep operating if data is lost or compromised;
retention of those logs and relevant data for one year, unless another law requires otherwise;
security clauses in your contracts with data processors; and
appropriate technical and organisational measures overall.
4. Data breach notification (Rule 7)
If you become aware of a personal data breach, two sets of messages follow.
To each affected person, without delay: what happened, when and how far it went; what it could mean for them; what you are doing about it; what they can do to protect themselves; and who they can contact.
To the Board: a description without delay. Then, within 72 hours (or a longer period if the Board allows it on your written request), detailed information: the events and reasons behind the breach, mitigation steps, any findings about who caused it, fixes to prevent a repeat, and a report on what you told the affected people.
5. Retention and erasure (Rule 8)
Large platforms (e-commerce entities with at least two crore registered users in India, online gaming intermediaries with at least fifty lakh, and social media intermediaries with at least two crore) must erase personal data for most purposes once three years have passed since the user last interacted. They must warn the user at least 48 hours in advance. Separately, Rule 8(3) says personal data, related traffic data and logs must be kept for at least one year for specified purposes.
6. Contact point, rights and grievances (Rules 9 and 14)
Publish, prominently on your website or app, the contact details of your Data Protection Officer (if applicable) or of a person who can answer privacy questions. Publish how people can exercise their rights, and run a grievance system that responds within a reasonable time not exceeding 90 days.
7. Children’s data (Rule 10)
Before processing a child’s personal data, you need verifiable consent from a parent, and you must do due diligence to check that the parent is an identifiable adult (the Rules define an adult as someone who has completed 18 years).
8. Cross-border transfers and large players (Rules 13 and 15)
Personal data can be transferred outside India, subject to requirements the government may specify. Significant Data Fiduciaries (a category the government notifies) must carry out a Data Protection Impact Assessment and an audit once every twelve months.
DPDP penalties: what the maximum fines look like
What goes wrong | Section of the Act | Maximum penalty |
|---|---|---|
Not taking reasonable security safeguards | 8(5) | Up to ₹250 crore |
Not notifying the Board and affected people of a breach | 8(6) | Up to ₹200 crore |
Not meeting the extra obligations for children’s data | 9 | Up to ₹200 crore |
Not meeting the extra obligations of a Significant Data Fiduciary | 10 | Up to ₹150 crore |
Breaching any other provision of the Act or Rules | — | Up to ₹50 crore |
These are upper limits set in the Schedule to the DPDP Act, 2023. The Board decides after an inquiry, and the amount depends on the facts of the case.
From law to product: building a consent management system
This is where we put on our engineering hats. The law does not hand you an architecture, but it does hand you requirements: show a clear notice, capture specific consent, let people withdraw easily, protect the data, and be ready to show what happened. Here is a practical way to build for that. Please treat it as good engineering practice, not as a legal checklist.
Principle 1: Treat consent as data, not as a checkbox
A tick on a form is not enough if you cannot show later what the person saw and agreed to. A simple approach is an append-only consent ledger. You never edit or delete old rows. You only add new ones, and the latest row for each user and purpose tells you the current status.
The rules for Consent Managers themselves (records of consents given, denied or withdrawn, and the notices shown) are a useful model for what a good record looks like.
-- Replace app_user with the database role your application connects with.
-- 1) The purposes your business actually uses (one row per purpose)
CREATE TABLE consent_purposes (
purpose_code TEXT PRIMARY KEY, -- e.g. 'order_updates', 'marketing_email'
description TEXT NOT NULL, -- the plain-language text shown to the user
is_optional BOOLEAN NOT NULL DEFAULT TRUE -- optional purposes must not block the service
);
-- 2) Append-only ledger: one new row for every consent decision
CREATE TABLE consent_ledger (
id BIGSERIAL PRIMARY KEY,
user_ref TEXT NOT NULL, -- pseudonymous ID, never an email or phone number
purpose_code TEXT NOT NULL REFERENCES consent_purposes (purpose_code),
notice_ver TEXT NOT NULL, -- which version of the notice the user saw
action TEXT NOT NULL CHECK (action IN ('given', 'denied', 'withdrawn')),
channel TEXT NOT NULL CHECK (channel IN ('web', 'android', 'ios', 'api')),
created_at TIMESTAMPTZ NOT NULL DEFAULT now()
);
CREATE INDEX idx_consent_ledger_lookup
ON consent_ledger (user_ref, purpose_code, created_at DESC);
-- 3) Current status per user and purpose (the latest row wins)
CREATE VIEW consent_current AS
SELECT DISTINCT ON (user_ref, purpose_code)
user_ref, purpose_code, action, notice_ver, created_at
FROM consent_ledger
ORDER BY user_ref, purpose_code, created_at DESC, id DESC;
-- 4) Keep the history trustworthy: the app can add and read rows, never edit or delete them
REVOKE ALL ON consent_ledger FROM app_user;
GRANT SELECT, INSERT ON consent_ledger TO app_user;
GRANT USAGE ON SEQUENCE consent_ledger_id_seq TO app_user;
GRANT SELECT ON consent_purposes, consent_current TO app_user;Why this structure works: the application role can only add and read rows, so nobody can quietly rewrite history. The view gives every service one simple place to read the current status, and the index keeps that check fast. Erasure and retention need their own controlled process, for example a scheduled job that runs under a separate, restricted database role. Agree those rules with your legal advisor before you build them.
Principle 2: Tie consent to purposes
The Act asks for consent that is specific. So avoid one giant “I agree to everything” switch. Give each purpose its own code, such as order updates, product recommendations or marketing emails, and store a separate decision for each.
Principle 3: Check consent before you act
Do not rely on your marketing team to remember. Make your code check. Here is an illustration in Node.js with Express and PostgreSQL (adapt it to your own stack). It checks consent, records new decisions and announces withdrawals:
// consent.js - Node.js, Express and PostgreSQL ('pg'). Illustrative, not production-ready as-is.
import express from 'express';
import { pool } from './db.js'; // your pg Pool
import { eventBus } from './events.js'; // your queue or event emitter
const ACTIONS = new Set(['given', 'denied', 'withdrawn']);
const CHANNELS = new Set(['web', 'android', 'ios', 'api']);
// 1) Read the current decision for one user and one purpose
export async function hasConsent(userRef, purposeCode) {
const { rows } = await pool.query(
`SELECT action
FROM consent_current
WHERE user_ref = $1 AND purpose_code = $2`,
[userRef, purposeCode]
);
return rows[0]?.action === 'given';
}
// 2) Guard: run a route only if the user agreed to that purpose.
// It fails closed: if we cannot check consent, we do not continue.
export function requireConsent(purposeCode) {
return async (req, res, next) => {
try {
if (await hasConsent(req.user.ref, purposeCode)) return next();
return res.status(403).json({ error: 'consent_required', purpose: purposeCode });
} catch (err) {
return next(err);
}
};
}
// 3) Record a decision, and tell the other systems when it is a withdrawal
export const consentRouter = express.Router();
consentRouter.use(express.json());
consentRouter.post('/consent', async (req, res, next) => {
try {
const { purposeCode, action, noticeVer, channel } = req.body;
if (!purposeCode || !noticeVer || !ACTIONS.has(action) || !CHANNELS.has(channel)) {
return res.status(400).json({ error: 'invalid_request' });
}
await pool.query(
`INSERT INTO consent_ledger (user_ref, purpose_code, notice_ver, action, channel)
VALUES ($1, $2, $3, $4, $5)`,
[req.user.ref, purposeCode, noticeVer, action, channel]
);
if (action === 'withdrawn') {
// CRM, email tool, analytics and data processors subscribe to this event
await eventBus.publish('consent.withdrawn', {
userRef: req.user.ref,
purposeCode,
at: new Date().toISOString(),
});
}
return res.status(201).json({ status: 'recorded' });
} catch (err) {
if (err.code === '23503') return res.status(400).json({ error: 'unknown_purpose' });
return next(err);
}
});
// Usage in your app:
// app.use('/api', authMiddleware, consentRouter);
// app.post('/api/newsletter/send', authMiddleware, requireConsent('marketing_email'), sendNewsletter);Two choices here are worth copying. The guard fails closed, so a database error never turns into accidental processing. And a withdrawal publishes an event, so your CRM, email tool and analytics can react on their own instead of relying on someone to remember.
Principle 4: Make withdrawal travel
When someone withdraws consent, that decision must reach every system that uses the data: your CRM, email platform, analytics, ad audiences and any data processors. A simple event (for example, “consent.withdrawn”) that all those systems listen to is far safer than a manual to-do list. After withdrawal, processing should stop within a reasonable time.
Principle 5: Design the screens honestly
Good UI/UX design is part of compliance here. Some habits that help:
Write notices in plain language (and consider offering them in the languages your users speak).
Make withdrawal as easy as giving consent. If it took one tap to agree, it should not take five screens to say no.
Avoid pre-ticked boxes. They are hard to square with a “clear affirmative action”.
Do not bundle unrelated purposes together or make consent for optional things a condition of using the service.
Put a simple “Privacy and consent” page in the account settings where people can review and change their choices.
Principle 6: Secure the whole pipeline, not just the database
Rule 6 talks about access control, logging, monitoring, backups and processor contracts. In practice that means:
keep secrets (API keys, database passwords) out of your app code and repositories;
give every service and team member the minimum access they need;
log access to personal data and actually review the logs;
keep an up-to-date list of third-party scripts, plugins and vendors that touch personal data; and
test your backups and your breach-response plan before you need them.
Here is the full consent flow at a glance, from notice to deletion:
Step | What happens | What to build | Why it matters |
|---|---|---|---|
1. Show the notice | The user sees a plain-language, versioned notice before any consent is requested | A notice component with a version number | Rule 3 asks for a clear notice that stands on its own |
2. Ask per purpose | The user makes a separate choice for each purpose | A purposes table and one toggle per purpose | Consent must be specific (section 6) |
3. Record the decision | Every choice is saved as a new, time-stamped row | An append-only consent ledger | You can show what was agreed, when, and on which notice |
4. Check before acting | Each feature or campaign checks the current status first | A consent guard that fails closed | No consent for a purpose means no processing for it |
5. Let people withdraw | The user changes their mind from account settings | A withdrawal screen and API, as easy as giving consent | Section 6(4): withdrawal should be as easy as consent |
6. Spread the change | Every connected system hears about the withdrawal | A withdrawal event sent to CRM, email, analytics and processors | Section 6(6): processing must stop within a reasonable time |
7. Clean up and prove it | Retention jobs run and access to personal data is logged | Scheduled deletion jobs, access logs and monitoring | Rules 6 and 8 |
What this means for marketing and SEO teams
Digital marketing and SEO run on personal data: leads, email lists, retargeting audiences and tracking tags. A few practical questions to ask your team:
Where did each contact in our database come from, and what did they agree to?
Do our forms explain clearly what we will do with the data, for each purpose?
Do our tracking tags and ad pixels run only for people who agreed to that purpose (where consent is your legal basis)?
Can someone unsubscribe or withdraw as easily as they signed up?
Do we have written agreements with the agencies and tools that handle our data?
These questions are good marketing hygiene even before any deadline.
Your DPDP readiness plan
This week (before 13 November):
List every place your website, app and forms collect personal data.
Note which vendors, plugins and scripts receive that data.
Decide who in your team owns privacy questions.
November to January:
Rewrite your privacy notices in plain language, with clear purposes.
Design the consent and withdrawal screens.
Review contracts with your processors for security clauses.
February to April:
Build the consent ledger, purpose checks and withdrawal events.
Tighten access control, logging and backups.
Write and rehearse a breach-response plan that can meet the 72-hour step for the Board.
By May 2027:
Publish your contact point and grievance process.
Test everything end to end, and train your team.
Review your plan with a lawyer.
What could still change
The law is new, and the details are still being filled in. Keep an eye on:
the Data Protection Board’s application process and standards for Consent Managers, which the Board is to publish;
government notifications on Significant Data Fiduciaries and on cross-border transfer requirements;
court cases, as challenges to the Act are reported to be pending before the Supreme Court; and
any change to the timeline. A proposal to shorten it for some entities was discussed in January 2026, but as far as we could find, the official dates remain 13 November 2026 and 13 May 2027.
Always confirm the latest position on the official MeitY and e-Gazette pages.
Frequently asked questions
What happens on 13 November 2026 under the DPDP Act?
Rule 4 of the DPDP Rules, 2025 and section 6(9) of the Act start. This allows eligible companies to apply to the Data Protection Board to be registered as Consent Managers.
Is a Consent Manager mandatory for my business?
Rule 4 does not require ordinary businesses to use one. Under section 6(7), a person may give, manage, review or withdraw consent through a Consent Manager.
When do DPDP penalties begin?
The penalty provisions are scheduled to start together with the main obligations on 13 May 2027.
What is the maximum penalty under the DPDP Act?
Up to ₹250 crore, for failing to take reasonable security safeguards. Other maximums are ₹200 crore (breach notification and children’s data), ₹150 crore (Significant Data Fiduciary duties) and ₹50 crore (other breaches).
How quickly must a data breach be reported?
Affected people and the Board must be informed without delay. The Board must then receive detailed information within 72 hours, or a longer period if the Board allows it on a written request (Rule 7).
Does a small business need to comply with the DPDP Act?
The law applies based on what you do with personal data, not only on your size. Some duties apply only to large or notified entities, and the government can notify exemptions for some classes. Ask a lawyer rather than assuming.
Is the DPDP Act being challenged in court?
Reports indicate that challenges are pending before the Supreme Court. As far as we could find, the timeline has not been paused, but please check for updates before making decisions.
How TakenCode can help
Consent touches almost everything we build: websites, mobile apps, SaaS products, CRM systems, UI/UX design, SEO and digital marketing campaigns. That is why we see DPDP readiness as an engineering and design challenge too.
If you would like a second pair of eyes on your setup, our team can run a DPDP technical readiness review. We look at where your website or app collects personal data, how consent and withdrawal work, which third-party scripts and vendors touch the data, and where your security basics need work. You get a practical, prioritised to-do list.
Please note that this is a technical review. It is not legal advice and it is not a certification of legal compliance.
Explore our services or talk to our team. You can find more guides on the TakenCode blog.
Disclaimer
This article is for general information only and is not legal advice. Laws, rules and government notifications can change, so please verify the current position on official sources and consult a qualified lawyer before acting. Last updated: 3 November 2026.
Official sources
Explore more from TakenCode
TakenCode Techlogic LLP builds high-performance websites, mobile apps, SaaS platforms and CRM systems, and supports them with UI/UX design, digital marketing and SEO. If this guide raised questions about your own setup, these pages are a good next step:
TakenCode: who we are and how we work
Our services: web development, app development, SaaS solutions, CRM systems, UI/UX design, digital marketing and SEO optimization
More guides on the TakenCode blog: cybersecurity, web development and digital marketing insights
Contact TakenCode: book a call about a DPDP technical readiness review for your website or app

