Interactive Checklist

C-23 Notice & Consent Privacy Engineer & Enterprise Architect

The Consent Manager Integration Checklist

Integration checklist for connecting enterprise applications with statutory Consent Managers registered under Section 6(9) and Rule 4.

Statutory Source: Ch. 11: r.4 registration check, interop boundary per surface, evidence reconciliation, grievance coordination

Total Verification Points: 5 Audit Checks

C-23Ch. 11: r.4 registration check, interop boundary per surface, evidence reconciliation, grievance coordination

The Consent Manager Integration Checklist

The CM-boundary decision aid

Readiness Score

0 / 5 checks

Statutory Registration Verification: Verify Consent Manager's active registration with the Board under Rule 4.

Section 6(9) & Rule 4

Interoperable API Contract: Integration conforms to MeitY / DPBI standardized consent artifact schema.

Rule 4

HMAC Signature Verification: Every incoming consent/withdrawal payload cryptographically verified via CM public key.

Chapter 11

Real-Time Revocation Webhook: Consent withdrawal events received from CM propagated instantly to deletion queues.

Section 6(4) & Section 6(8)

Grievance Routing Interop: Mechanism to receive and coordinate grievances routed through the Consent Manager.

Section 6(8) & Section 13

State automatically persisted in browser localStorage

Statutory Grounding & Legal Perimeter

Mandatory statutory clauses, rules, and gazette requirements enforceable under this checklist.

Enforceable Provisions:

Section 6(7)

Section 6(8)

Section 6(9)

Rule 4

Statutory Context:

This checklist is directly anchored in Ch. 11: r.4 registration check, interop boundary per surface, evidence reconciliation, grievance coordination. Failure to maintain verifiable affirmative proof of compliance exposes the enterprise to severe adjudication penalties under Section 33 (Schedule) of the DPDP Act.

Target Architecture & Impacted Systems

Enterprise applications, stores, and integration surfaces evaluated by this checklist.

View Full Systems Topology (SYS-001..014) →

In-Scope System Nodes:

SYS-001 Architecture Spec →

Customer App & Web Portal

Public client boundary & untrusted intake surface for notices and consent capture

SYS-002 Architecture Spec →

Core Lending Monolith & Transaction Store

Domestic production database and primary system of record for loan servicing

SYS-010 Architecture Spec →

Consent Ledger & Policy Decision Point

Immutable consent event store and Policy Decision Point issuing authority tokens

Associated Operational Controls (54 OBLs)

Control Master Matrix obligations directly tested by this checklist.

Open Control Matrix →

OBL-05 Workpaper →

Control Dossier OBL-05

Audit & Implementation Guidance

Best practices for establishing evidence, avoiding traps, and conducting periodic assurance.

Evidence Retention Standard

Do not rely solely on policy documents or statements of intent. Ensure verifiable evidence artifacts (cryptographic logs, test manifests, signed DPA agreements, or automated crawler receipts) are archived for at least 1 year.

Common Implementation Trap

Avoid declaring compliance based on frontend UI alone. The Data Protection Board evaluates the full data pipeline, including database persistence, read replicas, cache invalidation, and third-party processor synchronization.

Previous Checklist

C-22 — The Vendor PoV Checklist

Next Checklist

C-24 — The AI/Model Registry Checklist