Sector guidesUpdated 22 November 202611 min read

DPDP for Marketing Teams: Cookies, Tracking and Consent

How the DPDP Act and Rules apply to cookies, pixels, tracking and marketing consent in India, and what marketing teams must change before 13 May 2027.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Core obligations apply from
13 May 2027
Lawful ground for ad tracking
Consent (section 6), in most cases
Notice standard
Rule 3: standalone, itemised, plain language
Withdrawal
As easy as giving consent (Rule 3(c)(i))
Children
No targeted ads or behavioural monitoring (s.9(3))
Log retention
Minimum one year (Rule 8(3))
Max penalty, 'other provisions'
Up to ₹50 crore per instance

Quick answer

The DPDP Act has no cookie-specific rule, but any cookie, pixel or SDK that processes personal data needs a lawful ground, and for marketing that ground is almost always consent under section 6. From 13 May 2027, Rule 3 requires an itemised, standalone notice, and withdrawal must be as easy as giving consent. Targeted advertising directed at children is prohibited outright by section 9(3).

  • DPDP regulates personal data, not cookies as such; any identifier linked to an individual brings tracking into scope.
  • Marketing, retargeting and ad-measurement tracking will rarely fit a section 7 legitimate use, so plan for consent.
  • Rule 3 notices must itemise the data and purposes; a vague cookie banner will not meet that standard.
  • Withdrawing consent must be as easy as giving it, and processing plus vendor processing must stop afterwards.
  • Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children under 18.
  • Notice, consent and security obligations under the Rules apply from 13 May 2027.

Who this is for: Performance marketing and growth teams, Martech and analytics engineers, D2C and e-commerce brands, Agencies running campaigns for Indian brands, Privacy and compliance leads

Does the DPDP Act regulate cookies and tracking?

Not by name. The Digital Personal Data Protection Act, 2023 never mentions cookies, pixels or SDKs. It regulates the processing of digital personal data, meaning data about an individual who is identifiable by or in relation to that data. That is the test marketing teams should apply to every tag in the container.

What usually counts as personal data in martech

  • Persistent cookie IDs and advertising IDs tied to a browser or device that you can link back to a person.
  • Hashed emails and phone numbers sent to ad platforms for matching. Hashing is pseudonymisation, not anonymisation; the platform matches it precisely because it identifies someone.
  • CRM records, lead-form submissions, WhatsApp opt-ins and UTM-tagged landing data joined to a user account.
  • Session replay and heatmap recordings that capture typed input or account context.

What is likely outside scope

Strictly aggregated analytics that cannot be linked to an individual, and purely technical cookies that hold no personal data, are unlikely to engage the Act. The burden is on you to show the data truly is not linkable. Load balancer cookies are a weak case to worry about; a marketing pixel that fires a hashed email is not.

The practical consequence: treat the cookie banner as one surface of a wider consent system that also covers forms, apps, offline events and data shared with ad platforms.

Which lawful ground covers marketing and ad tracking?

The Act offers two grounds: consent under section 6, or a legitimate use under section 7. Section 7 is a closed list. Its first item covers data a person voluntarily provides for a specified purpose where she has not indicated that she does not consent. The rest covers State functions, legal obligations, court orders, medical emergencies, disasters and employment.

None of those comfortably covers retargeting, lookalike audiences, cross-site measurement or selling audience segments. The voluntary-provision use is narrow: a customer who gives a delivery address for an order has given it for delivery, not for building an ad audience.

Marketing activityLikely ground
Sending an order confirmationLegitimate use, s.7(a) (purpose of the transaction)
Newsletter to a person who opted inConsent
Retargeting pixels and conversion APIsConsent
Uploading customer lists to ad platformsConsent, specific to that purpose
A/B testing on logged-in users with identifiersConsent, or reassess whether data can be de-identified

Consent under section 6 must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to data necessary for the purpose. Pre-ticked boxes, consent bundled into terms of service and "by continuing to browse" banners do not meet that standard.

What must the notice say about tracking?

From 13 May 2027, Rule 3 sets the minimum content of every consent notice. Applied to tracking, that means:

  1. Standalone and self-explanatory (Rule 3(a)): the notice cannot rely on a link to a 6,000-word policy to make sense. The banner or layered notice itself must be understandable.
  2. Itemised description of personal data (Rule 3(b)(i)): list the categories, such as device identifiers, pages viewed, hashed email, and purchase events. "We collect data to improve your experience" is not itemised.
  3. Specified purposes and the uses enabled (Rule 3(b)(ii)): separate analytics, personalisation, advertising measurement and audience sharing, so each can be consented to specifically.
  4. Links and means (Rule 3(c)): a link to the website or app and a description of how to withdraw consent, exercise rights and complain to the Data Protection Board.

Layered design that works

  • Layer 1: purposes in plain language, with equal-weight Accept and Reject controls and a Choose option.
  • Layer 2: per-purpose toggles, the itemised data list and the vendors each purpose involves.
  • Layer 3: the full privacy notice, consistent with layers 1 and 2.

Section 5 also requires notice for consents obtained before the Act commenced, as soon as reasonably practicable. If your CRM holds historic opt-ins, plan a re-notice campaign. See the privacy notice template for wording.

How should withdrawal and suppression work?

Rule 3(c)(i) requires that withdrawal be possible with ease comparable to giving consent. If consent took one tap on a banner, withdrawal should take roughly one tap from a persistent control, not an email to a support address.

On withdrawal, section 6 requires the Data Fiduciary to stop processing within a reasonable time and cause its Data Processors to stop as well. Section 8(7) then requires erasure once the purpose is no longer served, unless the law requires retention.

Engineering the suppression path

  • Store consent as an event log: subject identifier, purpose, notice version, timestamp, channel, and state (given, withdrawn).
  • Propagate withdrawal to the tag manager so tags stop firing on the next page load.
  • Push suppression to ad platforms and email providers through their APIs, and remove the person from uploaded audiences.
  • Keep a minimal suppression list so the person is not re-imported from another source.

Interplay with one-year retention

Rule 8(3) requires every Data Fiduciary to keep personal data, traffic data and processing logs for at least one year from the date of processing for the Seventh Schedule purposes. Withdrawal stops marketing use; it does not oblige you to destroy the audit trail before that year is up. Restrict access to those logs so they cannot be reused for marketing. More detail: consent and withdrawal UX.

What are the rules on children and targeted advertising?

Section 9(3) prohibits a Data Fiduciary from tracking, behavioural monitoring or targeted advertising directed at children, meaning anyone under 18. Unlike GDPR-style age-of-consent rules, the threshold is 18 for all purposes unless the Government lowers it for fiduciaries that process data in a verifiably safe manner under section 9(5).

Rule 12 and Part B of the Fourth Schedule carve out narrow purposes where section 9(1) and 9(3) do not apply. Two matter for marketers:

  • Item 5: processing to ensure information, services or advertisements likely to have a detrimental effect on a child are not accessible to her.
  • Item 6: processing to confirm that a Data Principal is not a child, and to carry out due diligence under Rule 10.

Neither item permits profiling a child for advertising. Section 9(2), which bars processing likely to cause a detrimental effect on a child's well-being, is not exempted at all.

What to change

  • Exclude known or likely under-18 users from retargeting audiences and lookalike seeds.
  • Do not run behavioural targeting on youth-oriented products without an age assurance step.
  • Brief agencies in writing: the brand is the Data Fiduciary and carries the penalty exposure of up to ₹200 crore for children's obligations.

See age verification and DigiLocker tokens.

How do agencies, ad platforms and martech vendors fit in?

The brand that decides why and how customer data is used is the Data Fiduciary. Under section 8(1) it stays responsible for processing carried out on its behalf. A Data Processor may be engaged only under a valid contract, and Rule 6(1)(f) requires that contract to include appropriate provisions for reasonable security safeguards.

PartyTypical role
BrandData Fiduciary
Agency running campaigns on the brand's accountsData Processor (usually)
Email and SMS platformData Processor
CDP, analytics or session replay toolData Processor
Ad platform using data for its own purposesLikely a separate Data Fiduciary for those purposes

Assess each role on the facts. An ad network that uses your pixel data to improve its own models is deciding purposes for itself.

Contract terms to add

  • Process only on documented instructions and for listed purposes.
  • Honour withdrawal and erasure within defined timelines.
  • Report any personal data breach to the brand without delay, so the brand can meet Rule 7.
  • Retain logs for the one-year period required by Rule 8(3), then erase.

The DPA clauses template has copy-ready wording.

What should marketing teams do before 13 May 2027?

Six months is enough time to fix consent properly if work starts now.

  1. Inventory tags and data flows: export the tag manager, list every pixel, SDK and server-side API, and record what personal data each sends and where. Use the data mapping guide.
  2. Classify each purpose: transactional (legitimate use), analytics, personalisation, advertising, audience sharing.
  3. Rebuild the banner and forms to Rule 3: itemised, per-purpose, equal-weight choices.
  4. Wire consent to tags: no marketing tag fires before an affirmative choice.
  5. Build the withdrawal path across web, app, email footer and WhatsApp.
  6. Re-notice historic opt-ins under section 5 and suppress those who do not respond where consent quality is doubtful.
  7. Update processor contracts and agency briefs.
  8. Test: run a clean browser, reject all, and confirm with network logs that nothing personal leaves the page.

Remember that section 43A of the IT Act and the SPDI Rules continue to apply until 13 May 2027, so existing commitments do not lapse during the transition.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Audit every tag, pixel and SDK

    Record the personal data each sends, the destination and the purpose, and remove dead tags.

    Rule 3(b)(i)

  2. Split purposes into separate consents

    Keep analytics, personalisation, advertising and audience sharing as distinct, specific choices.

    Section 6

  3. Block marketing tags until consent

    Configure the tag manager and server-side events so nothing fires before an affirmative choice.

    Section 6

  4. Publish an itemised Rule 3 notice

    Make the banner understandable on its own and link to rights, withdrawal and Board complaint routes.

    Rule 3

  5. Offer one-step withdrawal

    Provide a persistent privacy control, email footer link and app setting with equal ease to giving consent.

    Rule 3(c)(i)

  6. Propagate suppression to vendors

    Remove withdrawn users from ad audiences and messaging lists through vendor APIs.

    Section 8(7)

  7. Exclude children from targeting

    Keep under-18 users out of behavioural targeting, audiences and lookalike seeds.

    Section 9(3)

  8. Add security clauses to martech contracts

    Include safeguards, breach reporting, retention and erasure duties in every processor agreement.

    Rule 6(1)(f)

  9. Retain consent and processing logs

    Keep consent events and processing logs for at least one year with restricted access.

    Rule 8(3)

Answers

Frequently asked questions

Do I need a cookie banner under the DPDP Act?

Not because of a cookie rule, but you need a consent mechanism for any tracking that processes personal data for marketing. A banner is the usual way to collect that consent on the web. From 13 May 2027 it must present a Rule 3 notice: standalone, itemised data, specified purposes, and clear routes to withdraw consent, exercise rights and complain to the Board.

Can I rely on legitimate interest for analytics in India?

No. The DPDP Act has no general legitimate-interest ground like GDPR. Section 7 lists specific legitimate uses, and routine analytics or advertising is not among them. If analytics data identifies individuals, rely on consent or redesign the analytics so it is genuinely aggregated and not linkable to a person.

Is a hashed email personal data under DPDP?

In practice, yes. A hashed email is used precisely because an ad platform can match it to a known individual. That makes it data about an identifiable person, so uploading hashed customer lists to an ad platform is processing personal data and needs a lawful ground, which for advertising will usually be consent.

Can I show 'Accept all' bigger than 'Reject'?

It is risky. Section 6 requires consent to be free and unambiguous, and Rule 3 requires withdrawal to be as easy as giving consent. A design that nudges users towards acceptance undermines the claim that consent was freely given. Equal visual weight for accept and reject is the safer pattern.

What happens to my existing email list on 13 May 2027?

Section 5 requires that people whose consent was obtained before the Act commenced be given notice as soon as reasonably practicable. Send a Rule 3 style notice to your list, offer an easy opt-out, and stop using records where you cannot show how consent was obtained.

Can we target ads to teenagers under DPDP?

No. Section 9(3) prohibits tracking, behavioural monitoring and targeted advertising directed at children, and a child is anyone under 18. The Fourth Schedule exemptions only allow processing to keep harmful ads away from children or to confirm a user is not a child, not to target them.

Who is liable if our agency misuses customer data?

The brand, as Data Fiduciary, remains responsible under section 8(1) for processing carried out on its behalf. You may have contractual remedies against the agency, but the Board's penalty exposure sits with the fiduciary. Choose agencies carefully and put Rule 6(1)(f) security clauses and breach reporting into the contract.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 3 (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 5, 6 and 9(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 8(3) and Seventh Schedule (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 12 and Fourth Schedule, Part B (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.