Analytics and Tracking

DPDP Act

Also called Digital Personal Data Protection Act

India's data protection law, built on plain-language notice and explicit consent for almost every use of personal data.

Quick facts: DPDP Act

Category
Analytics and Tracking
Also called
Digital Personal Data Protection Act
Level
Intermediate
Affects
Consent wording, form design, children's targeting, vendor contracts
Where to see it
Your consent platform, CRM consent fields, privacy notice, vendor agreements
In this article4
  1. How the DPDP Act works
  2. Why the DPDP Act matters
  3. Where the DPDP Act goes wrong
  4. How to act on it

How the DPDP Act works

The Digital Personal Data Protection Act covers digital personal data processed in India, and processing carried out elsewhere when it relates to offering goods or services to people in India. It uses its own vocabulary: the person is the Data Principal, the organisation deciding what happens to the data is the Data Fiduciary, and a registered Consent Manager can act as the single place where a person grants and withdraws permissions.

Consent is the backbone. It has to be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and accompanied by a notice in plain language that explains what data is collected and why. The notice must also be available in the languages listed in the Constitution’s Eighth Schedule. Withdrawal has to be as easy as giving consent was, and the Act carves out a small set of legitimate uses where consent is not the basis.

Why the DPDP Act matters

For businesses in Nepal and the wider region, India is often the nearest large market and a common source of outsourced development, hosting and agency work. The Act reaches both directions: selling into India, and handling Indian residents’ data on someone else’s behalf.

It also has teeth in an area marketers touch daily. Children’s data requires verifiable consent from a parent or guardian, and behavioural advertising directed at children is prohibited outright. If your audience skews young, that is a targeting question, not just a legal one.

Where the DPDP Act goes wrong

The first mistake is assuming that European compliance covers it. The two overlap, but the Act leans far harder on consent and does not offer a broad legitimate-interests route for marketing, so a lawful basis that works in Europe may have no equivalent here.

The second is bundling. Consent to marketing tucked inside acceptance of terms and conditions is not unconditional or specific, so it fails on its own wording. The third is the missing exit: sites that make signing up a single tap and withdrawal a support ticket. The Act’s detailed rules have been introduced in stages, so confirm the current position before relying on any specific obligation.

How to act on it

Write the notice first, in plain language, saying what you collect and what you will do with it, and plan for translation rather than treating it as an afterthought. Then separate marketing consent from every other agreement in your forms, and give it its own tick box that starts empty.

Build the withdrawal route at the same time as the sign-up route, log both, and check which of your vendors touch Indian users’ data. Keeping a proper consent log makes almost every other requirement easier to answer, because you can show what a person agreed to and when they changed their mind.

Do and do not

Do

  • Write the notice in plain language and plan translations
  • Give marketing consent its own empty tick box
  • Build withdrawal at the same time as sign-up

Do not

  • Bundle marketing consent into terms and conditions
  • Assume European compliance covers Indian requirements
  • Run behavioural advertising aimed at children

Questions people ask about this

Does the DPDP Act apply to a business in Nepal?

It can. Processing carried out outside India falls within the Act when it relates to offering goods or services to people in India. A Nepali business selling to Indian customers, or handling Indian users' data for a client, should treat itself as in scope. Purely domestic operations with no Indian customers generally are not, but take advice if that changes.

Is GDPR compliance enough for India?

It is a strong head start, not a substitute. Much of the groundwork transfers: knowing what data you hold, why, and who processes it. The gaps are in the details, particularly the reliance on consent for marketing, the notice language requirements, and the rules on children's data. Map your existing basis for each activity against the Act rather than assuming coverage.

Can I keep marketing to someone who withdraws consent?

No. Withdrawal has to be as easy as giving consent, and once it happens you must stop the processing that relied on it and arrange for your processors to do the same. Build the stop into your systems rather than into a person's memory, and keep the dated record of the withdrawal alongside the original agreement.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.