Data Principal Rights: Access, Correction and Grievance Workflow
A rights-request workflow covering identity verification, access information, correction, erasure, nomination, withdrawal and grievance.
A rights inbox without ownership and system search is only a promise. The company must know how to verify the requester and document the answer.
The DPDP framework is phased. The 14 November 2025 commencement notification brought specified institutional and enabling provisions into force immediately; section 6(9), section 27(1)(d) and rule 4 follow after one year; most operating duties and rules follow eighteen months after Gazette publication. As of 22 June 2026, readiness should distinguish current law from future-state DPDP controls.
The Act provides rights relating to access information, correction and erasure, grievance redressal and nomination, subject to its framework.
Rule 14 requires published request methods and a grievance-response period not exceeding ninety days when operative.
Withdrawal, correction, erasure and grievance are different actions even when submitted in one message.
What the organisation should understand
- The DPDP framework is phased. The 14 November 2025 commencement notification brought specified institutional and enabling provisions into force immediately; section 6(9), section 27(1)(d) and rule 4 follow after one year; most operating duties and rules follow eighteen months after Gazette publication. As of 22 June 2026, readiness should distinguish current law from future-state DPDP controls.
- The Act provides rights relating to access information, correction and erasure, grievance redressal and nomination, subject to its framework.
- Rule 14 requires published request methods and a grievance-response period not exceeding ninety days when operative.
- Withdrawal, correction, erasure and grievance are different actions even when submitted in one message.
- Identity verification should prevent account takeover without collecting unnecessary new documents.
The five-point review
| Check | What to examine |
|---|---|
| Request | Access, correction, erasure, withdrawal or grievance. |
| Identity | Reasonable match to account and risk. |
| Scope | Systems, processors and period. |
| Exception | Legal retention and third-party rights. |
| Response | Decision, action and escalation. |
Practical example
A user emails ‘delete everything’ from an unlinked address. Support asks for full Aadhaar. A safer workflow uses logged-in or limited account verification and distinguishes deletable profile data from legally retained invoices.
How to apply the framework
Create request categories and service targets. Route high-risk identity or legal issues to privacy review rather than frontline improvisation.
Maintain a ledger showing verification, searches, decisions, processor instructions, completion and communication.
Operating workflow
Define the processing or incident precisely
Identify the people, data, system, purpose, owner, vendor and transaction or event. Review request, identity and scope together. Do not start from a policy template or software feature; start from what the business and system actually do.
Separate current duties from future-state DPDP readiness
Apply the 14 November 2025 commencement notification provision by provision. Continue complying with currently operative IT, CERT-In, telecom, banking, insurance, employment, consumer, contract and criminal-law requirements. Build the future DPDP process now, but do not describe a scheduled rule as already legally operative.
Preserve proof and improve the system
Keep the approved decision, notice or workflow version, access or event logs, vendor evidence, user communications and remediation record. Update product design, role access, retention, support scripts or incident playbooks so the same weakness does not recur.
Action checklist
- Publish request channels.
- Use proportionate verification.
- Classify multi-part requests.
- Search systems and vendors.
- Explain retained records.
- Document closure.
Evidence to keep
- Request record
- Verification
- Search checklist
- Decision memo
- Response log
Warning signs
- Full Aadhaar for every case
- Only one profile searched
- Vendors omitted
- Another person’s data disclosed
- No grievance target
Finin2min takeaway
Privacy governance is an operating system, not a policy PDF. The data map, purpose, access, vendor, retention, user workflow, incident response and evidence file must all tell the same story.