Showing posts with label privacy engineering. Show all posts
Showing posts with label privacy engineering. Show all posts

Saturday, November 14, 2026

Designing Consent Management for the DPDP Act: Requirements, Integration and a Reference Architecture

For years, consent in most Indian enterprises has meant a checkbox and a link to a privacy policy nobody reads. The Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 put an end to that. Consent is now a record you have to prove, a choice the user can reverse, and a promise tied to a specific purpose. Every system that touches personal data has to respect it, which makes this as much an architecture problem as a legal one. In this post I'll walk through what the law asks for, what a Consent Management Solution (CMS) needs to do about it, how to wire it into the wider enterprise, and a reference architecture you can adapt.

The legal baseline in brief

Start with Section 6. Valid consent must be free, specific, informed, unconditional and unambiguous. It needs a clear affirmative action, and it can only cover the personal data necessary for the stated purpose. Section 6(10) puts the burden of proof on you, the Data Fiduciary: if there's a dispute, you have to show that a notice was given and that consent followed the rules. Sections 6(4) and 6(5) let the Data Principal withdraw consent, and once she does, processing has to stop. Sections 2(g) and 6(7) to 6(9) add the Consent Manager, a registered entity that acts as one point of contact where a person can give, manage, review and withdraw consent across fiduciaries.

Dates matter here. The Rules were notified on 13 November 2025 and come into force in phases. Rule 4, which covers Consent Manager registration, is computed to start on 13 November 2026. Rules 3 and 5 to 16 (notice, state processing, security safeguards, breach intimation, erasure timelines and rights) are computed to start on 13 May 2027. Treat those as interpreted dates until they are officially confirmed. Also note that, as of this writing, the Board hasn't published the application details or assurance standards for Consent Managers.

Consent and notice are one system

Section 5 says every request for consent must come with, or be preceded by, a notice. Rule 3 then spells out what that notice looks like. It has to make sense on its own, in clear and plain language. At a minimum it lists the personal data item by item, states the specific purposes, and describes the goods, services or uses the processing enables. It also has to give a link and explain how the person can withdraw consent (as easily as she gave it), exercise her rights and complain to the Board. Under Section 5(3) she can ask to read it in English or any Eighth Schedule language.

The practical takeaway is that a consent record is only as good as the notice version it points to. Part B of the First Schedule already makes Consent Managers keep the notices that came with each request, and your CMS should do the same. In practice that means three things: a notice service that versions, translates and publishes notices; a purpose registry that both the notice and the consent record refer to; and a consent receipt that ties together the person, notice version, purpose, data items and timestamp in one tamper-evident object.

Key characteristics of a DPDP-ready Consent Management Solution


Turning the law into platform capabilities, a good CMS should have these characteristics.

  • Purpose-granular and unbundled. Capture consent per purpose, never as one blanket flag. Section 6(1) limits consent to data necessary for the purpose, so your model has to link purposes to data items.
  • Affirmative and non-coercive. No pre-ticked boxes and no "by continuing you agree" tricks. The UI SDK should give accept and reject equal weight.
  • Withdrawal parity and propagation. Rule 3 says withdrawing must be as easy as consenting. Behind the scenes, a withdrawal has to reach every downstream system and processor quickly, and they must stop processing.
  • Immutable, verifiable evidence. Log every grant, denial, change and withdrawal as an append-only, hash-chained, signed event that records the notice version, language, channel and what was shown. This is your defence under Section 6(10).
  • Multilingual notices. Support English and the 22 Eighth Schedule languages, with versioned translations.
  • Machine-readable and portable. People should be able to see their history. Consent Managers must provide records in machine-readable form and keep them for at least seven years (First Schedule, Part B). Even as a fiduciary, matching that retention is a sensible benchmark.
  • Interoperable. Use open, documented APIs so you can work with registered Consent Managers and other fiduciaries, as the Act intends.
  • Child and guardian aware. Rules 10 and 11 require verifiable consent for children and for persons with disabilities who have lawful guardians, so you need to model guardian relationships and keep the verification evidence.
  • Policy-driven. Retention, legitimate-use exceptions (Section 7) and re-notice for legacy consent (Section 5(2)) should be configuration, not code.
  • Contact and grievance linked. Each request carries the Data Protection Officer's or another authorised contact, and consent events tie into the grievance workflow under Section 13.

Enterprise-wide integration requirements

A CMS that sits beside your estate instead of inside it won't survive an audit. You're responsible for what your processors do with the data, so integration is where compliance is won or lost.
 

Collection channels

Websites, mobile apps, call centres, branches, kiosks, IVR, partner portals and APIs should all call the same Consent API. Offer lightweight SDKs for JavaScript, Android and iOS, plus a headless mode for assisted channels. There, an agent records the consent and the system sends an OTP to the customer to confirm it.

Enforcement points

Consent you record but never enforce is just paperwork. Hook the CMS into these points:

  • API gateways and service mesh: a policy decision point (PDP) check on purpose before personal data is returned or shared.
  • Data platforms: data lake, warehouse and streaming layers filter or mask records by purpose-level consent, ideally through row and column-level policies.
  • Marketing, CRM and analytics tools: audience syncs consult the consent store, and withdrawal events trigger suppression.
  • Processors and SaaS vendors: contracts and technical connectors that deliver withdrawal and erasure instructions, and confirm completion.
 

Identity, rights and security tooling

Bind each consent to a stable, pseudonymous subject ID from your identity platform. Connect the CMS to your rights-request workflow (access, correction, erasure, nomination), to your data inventory so notices match real data flows, and to the SIEM for monitoring. Breach intimation under Rule 7 and the erasure timelines under Rule 8 both depend on knowing where consented data actually lives.

Integration patterns

I'd go event-driven. The CMS publishes ConsentGranted, ConsentModified and ConsentWithdrawn events to a broker, and each consumer keeps a cached view of consent with an agreed propagation SLA. Reserve synchronous policy calls for high-risk, real-time decisions. Make consumers idempotent, sign every message, and reconcile regularly so you catch drift early.
 

Reference architecture and ideal tech stack

The design below is layered and cloud-neutral, and it rests on one idea: the consent ledger is the source of truth, and everything else holds a derived view that can be verified against it. The product names are examples, so swap in equivalents that fit your hosting and data-residency constraints.


Layer Components Recommended tech stack Design intent
Experience Consent and preference UI, notice renderer, multilingual content React or Angular micro-frontend, native SDKs, WCAG 2.1 AA, i18n with Eighth Schedule fonts Notice-first, symmetric accept and withdraw, no dark patterns
Edge and access API gateway, WAF, bot control, rate limiting Kong, Apigee or Azure API Management; OAuth 2.1 and OIDC; mTLS Authenticated Data Principal sessions; abuse protection
Core services Consent, Notice and Purpose Registry, Preference, Guardian, Grievance services Java/Spring Boot, .NET or Go microservices on Kubernetes; OpenAPI contracts Stateless, versioned, idempotent APIs
Policy Policy decision and enforcement Open Policy Agent or Cedar; purpose-based access control Runtime check of purpose, consent and legitimate-use rules
Eventing Consent event backbone and propagation Kafka or Azure Event Hubs; schema registry; outbox pattern Near real-time withdrawal propagation, replayable
Evidence store Append-only consent ledger and receipts PostgreSQL with hash chaining, or a ledger database; object storage with WORM lock; HSM-backed signing Tamper evidence; retention at or above seven years
Security Identity, keys, secrets, tokenisation Keycloak, Entra ID or Okta; HashiCorp Vault or cloud KMS and HSM; field-level encryption Encryption, masking and virtual tokens per Rule 6
Observability Logs, metrics, traces, alerts, audit OpenTelemetry, ELK or Splunk, SIEM integration Access visibility and logs retained at least one year
Integration Connectors to CRM, data lake, marketing, processors Debezium CDC, Airbyte or custom adapters, a data catalogue for lineage Enterprise-wide enforcement and drift reconciliation

How the flow works


  1. The experience layer fetches the active notice version for a purpose and language from the Notice and Purpose Registry and renders it, itemising data and purposes.
  2. The Data Principal acts affirmatively. The Consent Service validates the request, writes an event with the notice hash, and issues a signed consent receipt.
  3. The outbox publishes ConsentGranted to the broker. Consumers update their local consent views.
  4. At runtime, gateways and data services ask the policy engine whether purpose P may use data D for subject S. Denials are logged.
  5. On withdrawal, the same path fires in reverse. Consumers stop processing, processors acknowledge, and the ledger records completion, which closes the loop for audit.

If you plan to operate as a registered Consent Manager and not just run a CMS for your own business, you'll need more. Add multi-fiduciary onboarding and consent routing between fiduciaries, and design the platform so it can't read the personal data it passes along, as Part B of the First Schedule requires. Part A also calls for independent certification against the Board's standards, and Part B bars you from sub-contracting your obligations.
 

Security integrity and compliance mapping

Rule 6 sets the minimum security bar for every Data Fiduciary, and it covers processing done by your processors too. It asks for encryption, obfuscation, masking or virtual tokens; access controls; logs and monitoring to spot unauthorised access; backups for continuity; one-year retention of relevant logs and data unless another law says longer; security clauses in processor contracts; and sensible technical and organisational measures. Here's how I'd translate that into design choices.

  • Encryption and tokenisation (Rule 6(1)(a)): TLS 1.3 in transit, AES-256 at rest, envelope encryption with HSM-held keys, and field-level encryption or tokens for identifiers such as mobile number and email in the consent store.
  • Access control (6(1)(b)): least privilege, RBAC plus attribute-based rules, privileged access management with just-in-time elevation, and mutual TLS between services.
  • Logging and monitoring (6(1)(c), (e)): immutable audit logs of every read of consent and personal data, streamed to the SIEM, with anomaly alerts and one-year minimum retention.
  • Resilience (6(1)(d)): multi-zone deployment, tested backups, defined RPO and RTO, and ledger replication so evidence survives an incident.
  • Integrity of evidence: hash-chained events, periodic anchoring of ledger digests in a separate store, digital signatures on receipts, and time-stamping from a trusted source.
  • Processor assurance (6(1)(f)): contractual clauses and automated attestations for withdrawal and erasure.
  • Data minimisation in the CMS itself: store identifiers and purpose references, not the personal data being consented to, which also fits the Consent Manager rule that contents must not be readable by it.
  • Breach readiness (Rule 7): runbooks that use consent and lineage data to scope affected Data Principals quickly, supporting the intimation duties and the 72-hour report to the Board.
  • Secure SDLC: threat modelling, SAST and DAST in the pipeline, dependency scanning, and penetration tests aligned with ISO/IEC 27001 and, for Significant Data Fiduciaries, the additional obligations in Rule 13.

Practical roadmap

Most obligations are computed to apply from 13 May 2027, so a phased plan is realistic.

  1. Discover (now): inventory personal data, purposes, processors and existing consents. Classify legitimate-use cases under Section 7 so you do not over-collect consent.
  2. Design: define the purpose taxonomy, consent data model and event schemas. Draft Rule 3-compliant notices and run them through legal review.
  3. Build the core: consent ledger, notice registry, policy engine and SDKs, then migrate one high-volume channel.
  4. Integrate and enforce: connect CRM, marketing and data platforms and onboard processors. Test withdrawal end to end.
  5. Operate: dashboards for consent rates and propagation latency, periodic reconciliation, notice re-versioning, and readiness to integrate with registered Consent Managers once the Board publishes its standards.
 

Conclusion

The DPDP Act makes consent a system of record. The notice says what the person agreed to, the ledger proves she agreed, and the enforcement layer makes sure every system acts on it, including when she changes her mind. Build those three as one platform, secure it to the Rule 6 standard, and expose it through open APIs. You'll be ready for the regulator and for Consent Managers when they arrive. This is an engineering view, not legal advice, so check your design with counsel and keep an eye on Board publications and any official confirmation of the commencement dates.