DPDP Consent Managers Explained for Startups

DPDP Consent Managers Explained for Startups

2 min read

DPDP · consent manager · startups · India · privacy

Authors

PandaONE Team

What a Consent Manager is under India’s DPDP Act, who can register (₹2 Cr net worth), and how early-stage SaaS should think about consent UX vs becoming a CM.

You saw “Consent Manager” in a DPBI headline and wondered if your Series A SaaS needs to become one. Usually: no.

Consent Manager is a defined role in the Digital Personal Data Protection Act, 2023 — not a marketing label. MeitY has opened registration; DPBI runs the portal.

Act text: MeitY PDF · ops news: registration portal post · Inc42.

Plain definition (from the Act)

Section 2(g): a Consent Manager is a person registered with the Board who acts as a single point of contact so a Data Principal can give, manage, review and withdraw consent through an accessible, transparent and interoperable platform.

Section 6 adds the operating rules:

  • Consent itself must be free, specific, informed, unconditional, unambiguous, with clear affirmative action (s.6(1)).
  • Withdrawal must be as easy as giving consent (s.6(4)); fiduciary (and processors) must cease processing within a reasonable time unless another legal basis applies (s.6(6)).
  • Principals may exercise consent via a Consent Manager (s.6(7)); the CM is accountable to the principal (s.6(8)) and must be Board-registered under prescribed conditions (s.6(9)).

Picture a regulated consent switchboard — not “another cookie banner SaaS.”

Should your startup register?

QuestionLikely answer for early SaaS
Are you incorporated in India?Required
Net worth ≥ ₹2 Cr?Required
Is consent mediation your product?Only then does CM registration make sense
Do you just need compliant consent UX?Build/integrate — don’t force a CM license

Most seed/Series A products should not contort into Consent Managers. Focus on fiduciary basics: purpose limitation, working withdrawal, security — safeguards guide.

Even as a consumer of the ecosystem:

  1. Expect APIs / standards for reading and honoring consent state across services.
  2. Stop hard-coding irreversible processing when consent is withdrawn.
  3. Design audit trails — who consented, which purpose, which version of notice.
  4. Separate marketing consent, essential processing, and employment data flows.

Product UX that ages well

  • Purpose-specific toggles (not one mega-consent)
  • Easy withdrawal in-account, not only email-to-support
  • Clear “what we still process after withdrawal” copy
  • No dark patterns that re-check consent after every login

Security still sits underneath

A perfect consent ledger does not help if an IDOR dumps the user table. Pair privacy work with offensive testing on PII surfaces — AI pentest / proof-backed findings.

Timeline reminder

Consent Manager registration is the now milestone. Broader rights/obligations/enforcement are reported for May 2027 — builders’ checklist.

Consent Managers are regulated infrastructure for India’s consent layer. Startups should understand the role, watch the approved list on DPBI, and ship fiduciary-grade consent and security. Registration is a product strategy call for a narrow set of companies — not a universal obligation.

Sources & further reading

Featured on ScrollLaunchFeatured on CodeHype