Skip to content
TrustOS

DPDP Act guide

Notice and consent under the DPDP Act

Consent is the main ground for processing personal data under the DPDP Act, and a notice is what makes that consent informed. Both depend in practice on knowing every purpose you use data for, and being able to stop when someone says no.

The law as of October 2026.

In shortAs of October 2026

  1. Notice comes before or with the consent request, in clear and plain language.
  2. People can ask for the notice in English or any of the 22 Eighth Schedule languages.
  3. Consent must be specific to a purpose; bundled consent is a risk.
  4. Withdrawal must reach every system and processor, as well as the banner.

What the notice has to do

When you ask for consent, you give the person a notice first or at the same time. It should say what personal data you collect and the specific purpose, how they can withdraw consent, how they can exercise their rights, and how they can complain to the Board. It has to be clear and plain, and readable on its own, without the person having to piece it together from other documents.

The person can ask to read the notice in English or in any of the 22 languages in the Eighth Schedule of the Constitution. For a D2C brand that takes orders over WhatsApp in Gujarati and Hindi, an English only privacy policy behind a link is unlikely to meet that test.

Withdrawal has to work in practice

A Data Principal can withdraw consent at any time, and it should be as easy as giving it. After that you stop processing for that purpose, and you have your processors stop too, within a reasonable time.

Many consent programmes fail at this point. The banner records the withdrawal, but the CRM, the SMS vendor and the analytics tool never hear about it. Withdrawal is an operational task that has to reach every system.

When the duties apply

The notice and consent duties of Data Fiduciaries apply in Phase 3, around 13 May 2027 as notified, unless amended. Consent Managers, which can collect and manage consent on a person's behalf, are covered from Phase 2, around 13 November 2026.

Where TrustOS fits

TrustOS links each notice to the purposes in your data inventory, so a notice changes when a purpose changes. Notices can be published in the 22 Eighth Schedule languages, and consent records are tamper evident, with the notice version the person saw.

When someone withdraws, TrustOS creates the follow up work for each connected system and processor, and keeps the confirmation. Your lawyers decide what the notice says; TrustOS does not replace legal advice.

Free toolPrivacy notice checkerCheck what your notice contains against the Act and the Rules, with the fix for each gap.

Official sources

This guide explains the law in plain words as of October 2026. It is not legal advice. Dates that depend on notifications can change, so check the official text before you rely on them.

Watch a withdrawal travel

One switch in the Privacy Centre, every system that used it

A customer turns off WhatsApp offers. The consent record changes, and the withdrawal goes to each system and processor that relied on it, until every one has confirmed. Sample data.

PRIVACY CENTRERitika ShahLoan account PL-88213Offers on WhatsAppWithdrawn · 09:14ConsentrecordCON-2026-2291tamper evidentWhatsApp senderConnector · number suppressedCRMConnector · consent flag updatedEmail platformProcessor · removed from listsSMS vendorProcessor · confirmed in writingData warehouseConnector · record taggedAd audiencesTask · marketing ops, done6 of 6 systems confirmed by 10:44 · kept with the consent record

Questions

Common questions

Do we need fresh consent from existing customers?

The Act requires a notice for consent given before it commenced, as soon as reasonably practicable. Whether you rely on that earlier consent or seek it again for a given purpose is a judgement your legal adviser should make with you.

Can one notice cover all our products?

It can, if it states each purpose clearly and lets people consent to each one separately. A long general policy that lists everything without a choice is weaker.

Is a cookie banner enough?

A banner can be one way to give notice and collect consent on a website. It is not enough on its own if the choices it records do not reach the systems that use the data.

See it with your data

Show us where your personal data lives. We will show you TrustOS running on it.

A 30 minute walkthrough on Google Meet with someone who knows the Act and the product. You leave with a view of your first phase, the owners and the effort.

Or get a rollout proposal in two minutes
  1. Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
  2. Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
  3. Step 3A first phase you can planModules, owners and effort, written down for you to keep.