Does the DPDP Act apply to employee data?

Yes. The DPDP Act applies to employee data whenever it is processed in digital form, including paper records that are later scanned (Section 3(a)). The employer is the Data Fiduciary and each employee is a Data Principal. Employers need no consent for employment purposes (Section 7(i)), but every other duty still applies. These duties begin on 13 May 2027.

"Employee data" here means any personal data about the people who work for you or want to: candidates, employees, interns, contractors, former staff, and the family members and nominees they give you details of. Section 2(t) defines personal data as any data about an individual who is identifiable by or in relation to that data, so a payslip, a PAN, an attendance log and a performance rating all count.

When can an employer process employee data without consent?

Section 7(i) is the employment ground. It allows processing "for the purposes of employment or those related to safeguarding the employer from loss or liability", and gives as examples preventing corporate espionage, keeping trade secrets, intellectual property and classified information confidential, and providing "any service or benefit sought by a Data Principal who is an employee".

In practice, the ground breaks into three parts:

Part of Section 7(i)Typical HR usesUsually outside it
Purposes of employmentOffer letters, payroll, tax deductions, attendance, leave, appraisals, disciplinary recordsStaff photos in advertising, selling or sharing data for unrelated purposes
Safeguarding the employer from loss or liabilityAccess logs, laptop security tools, preventing leaks of source code or client filesMonitoring unrelated to protecting the business, such as personal social media
A service or benefit the employee asks forGroup health insurance she opts into, a salary advance, a relocation serviceBenefits she did not ask for, sold or marketed to her by a third party

Anything outside these three parts needs another ground: consent under Section 6, or another clause of Section 7, such as 7(d) for disclosing information to the State under a legal obligation. See legitimate use under Section 7 for all nine grounds.

Which DPDP duties still apply to employee data?

Section 7(i) removes the need for consent and for the Section 5 notice. It does not remove the employer's other duties as a Data Fiduciary.

DutyProvisionWhat it means for HR
Stay responsible for your processorsSection 8(1), 8(2)Payroll providers and HR software vendors process data under a valid contract; you stay accountable
Keep data complete, accurate and consistentSection 8(3)Applies when data is used to make a decision about the employee, such as a promotion or termination, or shared with another Data Fiduciary
Reasonable security safeguardsSection 8(5), Rule 6Encryption or masking, access control, logs kept for one year, backups and security terms in vendor contracts
Breach noticeSection 8(6), Rule 7Tell the Board and each affected employee without delay; full report to the Board within 72 hours
Erase when the purpose endsSection 8(7)Unless another law requires you to keep it
Publish a contact for data questionsSection 8(9), Rule 9A DPO or another person who answers questions, named on your website or app
Grievance redressalSections 8(10), 13, Rule 14(3)A way for staff to complain, answered within 90 days at most
Children's dataSection 9, Rule 10Verifiable parental consent for anyone under 18, such as a young intern or an employee's child on an insurance policy
Access, correction and erasure rightsSections 11(1), 12(1)Apply to data given with consent or under 7(a), not to data processed only under 7(i)

The last row surprises many HR teams. The rights to a summary of your data (Section 11) and to correction and erasure (Section 12) are written for data a person gave with consent, including under Section 7(a). Data processed only under 7(i) is not covered by them, but the accuracy duty in Section 8(3) and the grievance route in Section 13 still are, so a sensible employer fixes a wrong record when an employee points it out.

How should employers treat job applicants' data?

The Act does not say whether recruitment is a "purpose of employment" under Section 7(i), and the candidate is not yet an employee. Two grounds are clearer:

  • Section 7(a), voluntarily provided data. A candidate who sends her CV for a specific job has given it for a specified purpose. You may use it for that application until she indicates she does not want that use any more.
  • Consent (Section 6). For anything wider, such as keeping her CV for future openings or running a background check through a third party, ask for consent with a Section 5 notice, and make withdrawal as easy as giving consent (Section 6(4)).

Candidates whose data rests on consent or 7(a) do have the rights of access, correction and erasure. Once a role is filled, erase the CVs of people you did not hire unless they agreed to be kept on file.

One more point: the Act does not apply to personal data the person herself made publicly available (Section 3(c)(ii)(A)). Reading a public professional profile is outside the Act, but the notes, scores and messages you then create about that candidate are your own records and are covered.

Are contractors, interns and gig workers covered by Section 7(i)?

Section 7(i) refers to "the employer" and "a Data Principal who is an employee", and the Act does not define "employee". Whether a consultant, a staffing-agency worker or a delivery partner counts is not settled by the text. The safer course is to treat each group separately: rely on the contract and Section 7(a) for data they give you to do the work, ask for consent for anything wider, and record the decision.

Interns under 18 are children under the Act (Section 2(f)). Section 9(1) requires verifiable consent of a parent before processing a child's personal data, and the Fourth Schedule of the DPDP Rules 2025 contains no exemption for employment. The same applies to the children of employees you add to a health insurance policy; Rule 10(1) lets you verify the parent using reliable identity details you already hold, which an employer usually has for its own staff.

Can employers monitor employees under the DPDP Act?

Monitoring can fit within Section 7(i) when it safeguards the employer from loss or liability: the Act's own examples are preventing corporate espionage and protecting trade secrets, intellectual property and classified information. Security logging is also required: Rule 6(1)(c) asks for logs, monitoring and review to detect unauthorised access, and Rule 6(1)(e) for keeping those logs for one year.

Monitoring that has no link to employment or to protecting the business is harder to justify under 7(i). Write down the purpose of each tool (CCTV, laptop agents, email scanning), what it collects and how long you keep it. That record is what you would show the Data Protection Board if a complaint reached it.

How long can employers keep employee data?

Section 8(7) requires you to erase personal data once it is reasonable to assume the specified purpose is no longer served, unless retention is necessary to comply with any law. For employee data that means three layers:

  1. Records another law requires you to keep, such as tax and labour records: keep them for the period that law sets, and no longer.
  2. Logs of processing: keep them for at least one year (Rule 6(1)(e)).
  3. Everything else, such as old CVs, exit-interview notes and expired ID copies: erase once the purpose ends.

The fixed three-year erasure period in the Third Schedule (Rule 8(1)) applies only to large e-commerce, online gaming and social media platforms, not to employers as such. See DPDP data retention for the full rules.

Example: how an employer maps its HR data

This is a made-up example. "Chai Ledger" is a fictional Pune fintech company with 120 employees, an HR software vendor, a payroll provider and a group health insurance policy.

DataGroundErase when
CVs for an open roleSection 7(a)The role is filled, unless the candidate agreed to stay on file
CVs kept for future openingsConsent (Section 6) with a noticeConsent is withdrawn or the stated period ends
Payroll, PAN and bank detailsSection 7(i)After the period tax and labour laws require
Laptop security agent and access logsSection 7(i), Rule 6Logs kept at least one year, then on the security policy's schedule
Employees' children on the insurance policySection 7(i) plus verifiable parental consent (Section 9(1))The employee leaves or removes the dependant
Team photos on the careers pageConsent (Section 6) with a noticeConsent is withdrawn

Chai Ledger also checks that its contracts with the HR software vendor and payroll provider include security terms (Rule 6(1)(f)), and adds HR data to its breach plan, because a leaked salary sheet triggers the same Rule 7 duties as leaked customer data.

What should employers do to comply, step by step?

  1. List every HR purpose and the systems behind it: recruitment, onboarding, payroll, benefits, attendance, monitoring, exit.
  2. For each purpose, decide the ground: Section 7(i), Section 7(a) or consent. Record it in your record of processing.
  3. Find where sensitive identifiers sit: Aadhaar, PAN and bank details often end up in spreadsheets and shared drives, not only in the HR system.
  4. Check every vendor that touches HR data has a valid contract with security terms (Section 8(2), Rule 6(1)(f)).
  5. Apply the Rule 6 safeguards to HR systems, including one-year logs.
  6. Send a Section 5 notice for every consent-based purpose, such as keeping CVs or using staff photos.
  7. Set erasure points for former employees and rejected candidates, keeping only what other laws require.
  8. Publish a contact for data questions and give staff a grievance route (Section 8(9), Section 13).
  9. Add HR data to your breach response plan before 13 May 2027.

What are the common mistakes and myths about employee data?

  • Myth: "Employees signed a contract, so DPDP does not apply." The Act applies; the contract and Section 7(i) only remove the need for separate consent for employment purposes.
  • Mistake: a blanket consent clause in the offer letter. Consent must be free, specific, informed, unconditional and unambiguous (Section 6(1)), and an employee can withdraw it at any time (Section 6(4)). Relying on consent for payroll makes payroll depend on something she can withdraw; Section 7(i) is the better fit.
  • Mistake: forgetting candidates and former staff. They are often the largest and oldest part of an HR data set.
  • Mistake: treating the HR vendor as responsible. Under Section 8(1) the employer stays responsible for processing done on its behalf.
  • Myth: "Small companies are exempt." Section 17(3) lets the government notify some Data Fiduciaries, including startups, to whom Section 5, Sections 8(3) and 8(7), and Sections 10 and 11 will not apply. Do not assume an exemption until one is notified and covers you (see DPDP Act exemptions). See DPDP penalties for what is at stake.

GRC-Flow's personal data discovery scans HR exports for Aadhaar, PAN, phone numbers and children's data, so you can see where employee data sits before you map it, and the DPDP registers track grievances and breaches. You can start with the free DPDP website check. A person reviews every result, and no tool can guarantee compliance.

This guide is general information about the DPDP Act and Rules, not legal advice.

Frequently asked questions

Do employers need employee consent under the DPDP Act?

Not for employment purposes. Section 7(i) lets an employer process personal data for the purposes of employment, to safeguard itself from loss or liability, and to provide a service or benefit an employee asks for. Purposes outside these, such as using staff photos in advertising, need consent or another ground in Section 7.

Do I have to give employees a DPDP privacy notice?

The Section 5 notice is tied to requests for consent under Section 6, so processing under Section 7(i) does not need one. You still need a notice for anything you ask employees to consent to, and telling staff how you use their data is good practice.

Does the DPDP Act cover job applicants?

Yes, if their data is digital. The Act does not say whether recruitment counts as a purpose of employment under Section 7(i). Data a candidate sends you for a job application can often rest on Section 7(a), data voluntarily given for a specified purpose, until the candidate says she no longer wants that use; otherwise ask for consent.

How long can an employer keep former employees' data?

Section 8(7) requires erasure once the purpose is no longer served, unless another law requires you to keep it. Keep what tax, labour or other laws require for as long as they require, keep security logs for at least one year (Rule 6(1)(e)), and erase the rest on a schedule.

What is the penalty if an employer leaks employee data?

Failing to take reasonable security safeguards to prevent a breach can attract a penalty of up to ₹250 crore, and failing to notify the Board and affected people up to ₹200 crore (the Schedule to the Act). The Data Protection Board decides the amount case by case.

Sources

  1. The Digital Personal Data Protection Act, 2023 (India Code)
  2. Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), Gazette text)
  3. PIB: Digital Personal Data Protection Rules, 2025

This guide explains the law in general terms and is not legal advice. Check specific situations with a qualified lawyer.