Purpose
The reason the choice was asked for, such as a marketing update.
DPDP section
Consent management for the workspace
A consent record names a purpose, a notice version, an application, a time, and a reference your system already uses. This page explains that record. It does not certify legal compliance.
What is stored
Each field has its own place. Nothing here is an identity document, and a readiness score is not part of the consent record.
Notice version
The privacy notice that was current when the person chose.
Opaque reference
An identifier from your own system. The hub does not ask for an identity document.
Status
Requested, granted, denied, withdrawn, or expired.
History
A withdrawal adds an event. The earlier choice stays on the same record.
Audit
The event is written to the company hash chain.
How a change is finished
Implementation is finished when the first consent record is stored and the audit chain has that event. A later change is finished when the new event is on that same chain. A withdrawal is finished when that consent history shows withdrawn.
Read the user guideSupport
Write to the DPDP desk
Account, directory, and workspace questions for this platform go to the support inbox.
[email protected]This inbox is for the platform. A grievance about a listed company still goes to the contact on that company profile.