
HR collects, stores and processes the most sensitive personal data inside a company.
Under the DPDP Act, 2023, employees and candidates now get enforceable rights over their data.
These rights aren’t optional.
They change how HR must store, track, use and delete employee data across the lifecycle.
This guide explains the three biggest DPDP rights HR teams must operationalise:
(Employee asks: “What data do you have about me?”)
An employee/candidate can request details about their personal data.
✔ what personal data was collected
✔ why it was collected (purpose)
✔ who it was shared with
✔ where it is stored
✔ how long it will be retained
✔ status: active / archived / flagged for deletion
HR cannot deny access unless an exemption applies (national security, investigation, fraud, etc.).
A candidate requested their BGV + stored ID copies.
HR replied that data “cannot be shared for company policy reasons.”
❌ WRONG.
The organisation breached DPDP because:
Result: candidate escalated → legal notice + DPDP complaint filed.
(Employee asks: “Please fix my personal data.”)
Employees can request corrections if data is:
✔ verify identity
✔ verify correct data
✔ record correction request
✔ update in all systems, not just HRMS
✔ notify third parties who received wrong data
✔ provide acknowledgment to employee
A common violation:
✔ correction made in HRMS
❌ not corrected in payroll vendor database
Employees can ask for deletion of personal data when:
But deletion rights are not absolute. If data must be kept for legal/statutory reasons → HR must refuse deletion.
✔ Is there a legal retention requirement?
✔ maintain deletion logs
✔ ensure deletion across all backup systems
✔ remove access permissions
✔ provide confirmation to employee
| Request Type | Recommended Response Time |
| Acknowledge request | within 48 hrs |
| Provide access/correction path | within 5–7 working days |
| Complete deletion post-verification | within 7–14 working days |
| Confirm deletion in writing | same day deletion happens |
These timelines prevent compliance disputes later.
| DPDP Right | What employee requests | HR obligation | When HR can refuse |
| Access | View data + processing purpose | Provide full copy + retention details | Legal exemptions |
| Correction | Fix inaccurate/outdated info | Correct everywhere + confirm | If request unverified |
| Deletion | Remove personal data | Delete + document | Legal retention required |
“Hi ___, we acknowledge your request for access to personal data we hold.
We will share a record of your information, purpose of use and retention timeline within 7 working days.”
“Hi ___, thank you for notifying us.
We will verify supporting documents and correct your information within 5 working days.”
“Hi ___, since the purpose for storing your data has ended, we will delete your records within 7–14 working days and share confirmation once completed.”
Rights don’t exist in isolation.
They connect across lifecycle:
Golden rule:
If purpose ends → retention ends → deletion must follow.
Subject: Acknowledgment of Your DPDP Data Rights Request
Dear <Name>,
We acknowledge receipt of your request under the Digital Personal Data Protection Act, 2023 regarding:
• Access / Correction / Deletion (select as applicable)
We will process this request and respond within the applicable timelines.
If needed, we may contact you to verify your identity or request clarifications.
Regards,
HR Data Protection Team
Most HR leaders understand the rights, but struggle with “What should we actually do now?”
Here’s a practical, step-by-step plan to operationalize Access, Correction & Deletion rights inside HR workflows.
Make it easy for employees to submit requests and avoid chaos.
This helps HR avoid delays and accidental violations.
Basic workflow:
Most HR teams forget this step. Without mapping, you cannot fulfill requests.
Examples of places to map:
Make internal SLAs clear so nothing slips.
Example SLA commitments:
These prevent errors and inconsistent responses.
Create short templates for:
So that deletion doesn’t only happen inside HRMS.
Checklist should include:
Training topics:
DPDP compliance requires proof, not intent.
Record:
Create a trigger rule:
When purpose ends → start retention countdown → schedule deletion
This builds transparency + reduces uncertainty.
Include:
DPDP rights are not theory. Employees will start asking:
If your answer depends on “checking with IT/legal,” you’re already exposed. Rights + consent + retention together form the DPDP compliance triangle.
Build it now and avoid panic later.
.png)