Data Privacy · Module 02
Individuals have a right to see, correct and erase what you hold about them. This turns that right into a workflow with a clock, an owner and an evidence trail.
Primary DPDP sectionsSec. 11–14
How it works
Every request runs the same pipeline against a clock that starts on receipt, so status is a fact drawn from the catalogue rather than an email thread.
01
Self-service portal, email or API — all channels land in one queue
02
Identity proofed before any data is disclosed
03
Catalogue returns every store holding this Principal's data
04
Third-party personal data removed before release
05
Delivered in a portable format, evidenced
The statutory clock runs across all five stages, with escalation before the deadline rather than after it.
Capability
The requester sees what is held and how it is processed — assembled from the catalogue rather than from an email thread.
Identity verified before disclosure, response inside the statutory window, extendable only where the law allows.
Automated intake and fulfilment at volume, with third-party data redacted or anonymised before release.
Rights fulfilled inside the statutory window at volume, with the identity check, the redaction and the evidence produced as a by-product of the workflow.
DPDP alignment
What the Digital Personal Data Protection Act, 2023 requires, and the control that satisfies it.
| Section | What the Act requires | How the product satisfies it |
|---|---|---|
| Sec. 11 | The Principal may obtain a summary of personal data being processed, the processing activities, and the identities of other Fiduciaries with whom it has been shared. | The summary is generated from the live catalogue and the consent ledger, including sharing lineage — so recipients are named from records rather than reconstructed from memory. |
| Sec. 12(1) | The Principal may request correction, completion and updating of their personal data. | Corrections propagate to every store the catalogue identifies, and the propagation itself is evidenced, so accuracy is fixed estate-wide rather than in one system. |
| Sec. 12(3) | The Principal may request erasure, and the Fiduciary must erase unless retention is necessary for a specified purpose or legal compliance. | Erasure executes against the discovered store list; legal-hold and retention exceptions are recorded with the basis relied on, so a refusal is defensible. |
| Sec. 13 | The Fiduciary must provide a readily available grievance redressal mechanism and respond within the prescribed period. | Grievances are first-class tickets with their own clock, routed to the DPO, and evidenced end to end for the Board. |
| Sec. 14 | The Principal may nominate an individual to exercise their rights in the event of death or incapacity. | Nomination is captured, verified and honoured as an authorised path into the same rights workflow. |
Rights failures fall in the residual ₹50 Cr band, but they are the most visible: every missed DSAR is a Principal with a live grievance and a direct route to the Data Protection Board.
Solutions by industry
The sectors carrying the most DPDP exposure for this control, each with its own threat model and regulators.
A DPDP readiness walkthrough maps your obligations to the controls that already exist, and names the gaps that do not.
