The DPDP Act for HR Teams: Employee and Candidate Data
What India's DPDP Act means for the candidate and employee data HR holds, and the practical questions to work through with your legal team.
HR is one of the largest holders of personal data in any company. Résumés, offer letters, bank details, identity documents, appraisal notes, medical leave records: almost everything HR touches is about a person. That makes HR one of the first teams that should understand India’s Digital Personal Data Protection Act, 2023 (the DPDP Act).
This guide is not a reading of the law. It is a practical way for HR teams to organise their thinking, find the right questions and take them to the people qualified to answer them.
Why HR data deserves special attention
Three things make HR data different from most customer data.
It covers the whole working life. A person’s record starts when they apply and can continue long after they leave. Data protection thinking needs to cover every stage: sourcing, interviewing, onboarding, employment and exit.
It spreads across many tools. A typical HR stack includes a careers page, an applicant tracking system, interview scheduling, an HRMS, payroll, background verification, learning platforms and a shared drive full of spreadsheets. Each one holds a copy of someone’s data.
Some of it is sensitive by any standard. Health information, financial details, government identifiers and performance assessments can cause real harm if they leak or are misused.
Start with a map of where the data lives
You cannot protect what you cannot find. Before any policy work, build a simple inventory. For each system or process, write down:
- What data it holds. Contact details, identity numbers, bank details, health information, assessments.
- Whose data it is. Candidates, employees, former employees, referees, dependants.
- Why you hold it. The business purpose in plain words, for example “to pay salaries” or “to assess a candidate for a role”.
- Who can see it. Teams, roles and any outside vendors.
- How long you keep it. Your current practice, even if the honest answer is “forever”.
Spreadsheets and email attachments count. They are often where the most sensitive copies end up. If your systems are too large to inventory by hand, discovery tools can help; see how to find the personal data hiding across your systems.
Look at the candidate journey first
Hiring is usually the easiest place to make visible progress, because it is where you first collect someone’s data and where people have the least reason to trust you yet.
Questions worth working through with your legal team:
- What do candidates see before they share anything? Is there a clear notice that explains what you collect and why?
- Is each piece of information necessary? Many application forms ask for details that only matter after an offer.
- What happens to unsuccessful applications? Decide how long you keep them, and whether you ask before keeping a profile for future roles.
- Which vendors receive candidate data? Job boards, assessment platforms, scheduling tools and background verification providers all count.
Then the employee lifecycle
For employees, the same questions apply over a longer period:
- Onboarding: collect what payroll, statutory filings and benefits actually need, and store identity documents somewhere access is controlled.
- During employment: performance notes, monitoring tools and internal investigations all involve personal data. Be clear about who can see what.
- Exit: decide what you keep after someone leaves, for how long and why. Then make sure the deletion actually happens.
Rights requests will come to HR
Data protection laws generally give people ways to ask about, correct or remove their data. Even before you settle the legal details, prepare the operational side:
- Agree how a request reaches the right person, whether it arrives by email, through a manager or via a portal.
- Decide how you confirm the person is who they say they are.
- Know which systems you would need to search. This is where your data map pays off.
- Keep a record of each request and what you did about it.
Your lawyer can tell you which requests you must honour, the timelines involved and any exceptions. Your job is to make sure the process can actually run.
Vendors are part of your footprint
Most HR data is processed by outside software. For each vendor, find out where data is stored, who at the vendor can access it, how they handle deletion and what happens if they have a security incident. Bring the answers to your legal and procurement teams, who can decide what the contracts need to say.
A simple way to begin
If this feels like a lot, start small:
- Build the data map for hiring only.
- Rewrite the candidate notice in plain language and have legal review it.
- Set and enforce a retention period for unsuccessful applications.
- Name one owner for privacy requests in HR.
Then repeat for onboarding, employment and exit. Progress you can show is worth more than a perfect plan that never leaves a slide deck.
For a wider view beyond HR, see our DPDP compliance checklist.
Sammati collects consent per purpose, handles the privacy requests people send you, and tracks the controls and evidence for standards such as ISO 27001 and SOC 2.
Explore SammatiQuestions people ask
Does the DPDP Act apply to employee data?
Employee and candidate records are personal data, so HR teams should assume data protection rules are relevant to them. Exactly which obligations apply, and which exceptions might exist for employment, is a question for your lawyer.
Is candidate data treated differently from employee data?
Candidates and employees have different relationships with you, so the reasons you hold their data, how long you keep it and what you tell them will often differ. Map the two separately and review both with legal counsel.
Who in the company should own this work?
HR owns the processes, IT owns the systems and legal interprets the law. Most companies name one accountable person to coordinate across all three, so decisions do not fall between teams.