← All news and guides
Data protection

Employee and HRMS Data Under DPDP: A Checklist for HR and IT

DPDP covers employee data too. A checklist for HR and IT: what Section 7(i) allows, which duties still apply, HRMS access, vendors, retention and exits.

Mono Team ·

A quiet open-plan office in late afternoon light with rows of empty desks and a single filing cabinet drawer slightly open, shallow depth of field.

Short answer: yes, the DPDP Act covers your employees' data, and the HRMS is where most of it sits. Your staff are Data Principals and you are the Data Fiduciary. Section 7(i) lets an employer process personal data "for the purposes of employment or those related to safeguarding the employer from loss or liability" without asking for consent, so you may rely on it for payroll, attendance and similar core HR work. It does not switch off the rest of the Act. Security safeguards (Rule 6), breach notice (Rule 7), accuracy, vendor control, retention and erasure still apply to HR data. The core duties start on 13 May 2027.

This is a working checklist for HR and IT. HR decides why each piece of data is held. IT decides where it sits, who can open it and when it goes. It is engineering guidance, not legal advice. Whether an activity fits Section 7(i) is a question for your counsel.

Does the DPDP Act apply to employee data?

Yes. Section 3 applies the Act to digital personal data processed in India, whether it was collected in digital form or on paper and digitised later. An employee record in an HRMS, a payroll file, a scanned ID, an attendance log and an interview scorecard in a spreadsheet are all in scope. A paper file that is never digitised is not.

The Act has no special tier for "sensitive" data such as health, biometrics or salary. Every item is personal data under the same duties, but you will protect bank details and medical records more tightly because a leak hurts more.

The people covered are wider than your payroll list:

  • Current employees, including those on probation and notice.
  • Former employees, whose records you still hold.
  • Candidates and interviewees, including those you rejected.
  • Interns, contractors and freelancers whose data is in your systems.
  • Family members and nominees named in insurance and provident fund forms.
A tidy office desk seen from a low angle with a closed laptop and a stack of plain beige folders, soft morning window light and a blurred open-plan office behind.

Often, yes, for the right purposes. Section 7 lists "legitimate uses" for which a Data Fiduciary may process personal data without the consent route. Clause (i) covers processing "for the purposes of employment or those related to safeguarding the employer from loss or liability, such as prevention of corporate espionage, maintenance of confidentiality of trade secrets, intellectual property, classified information or provision of any service or benefit sought by a Data Principal who is an employee."

Three points follow. First, it is tied to purpose, so you must say which employment purpose each data item serves. Second, it is not a blanket exemption for HR. It removes the need for consent for that use, and nothing more. Third, other clauses of Section 7 may fit parts of the work. Section 7(d), for example, covers processing needed to meet a legal duty to disclose information to the State, which is where statutory filings sit.

The table shows how teams commonly sort their HR processing. The "likely route" column is a starting position to confirm with counsel, not a ruling.

HR activityLikely routeWhat to check
Offer, contract, onboarding recordsLikely route: Section 7(i), employmentWhat to check: Collect what the job needs, not what the form has space for
Payroll, tax and statutory deductionsLikely route: Section 7(i), and Section 7(d) for filings the law requires you to makeWhat to check: Which authority or vendor receives what, and under which law
Attendance, leave, access cardsLikely route: Section 7(i), if tied to employmentWhat to check: Biometric attendance needs a purpose note and tight access
Performance reviews and disciplinary filesLikely route: Section 7(i)What to check: Accuracy: Section 8(3) applies where data is used to make a decision that affects the person
Email, endpoint and data loss monitoringLikely route: Section 7(i), safeguarding the employerWhat to check: Keep it to the stated risk. Record what is monitored and who can read it
Photos and names on the website or social mediaLikely route: ConsentWhat to check: A request with its own notice and an easy way to withdraw
A future-roles talent poolLikely route: ConsentWhat to check: Do not keep rejected candidates' data for another purpose without asking
Candidate applications for a specific roleLikely route: Section 7(a), voluntarily provided for that purposeWhat to check: The purpose is that role. Reuse needs a new ground

When consent is the route, the Act and Rules set the form. Consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action" (Section 6(1)), and Rule 3 says the notice must be understandable on its own. So do not bury consent clauses inside the offer letter or the employee handbook. Give each optional use its own request, make it truly optional, and record the answer. Withdrawal must be as easy as giving consent (Section 6(4)).

Section 5 ties the notice duty to requests for consent, so the Act does not itself require a Section 5 notice for processing under Section 7(i). Many employers will still publish an employee privacy notice, because staff will ask what is held and why. That is a sound practice choice, not a requirement we can quote.

Which DPDP duties still apply when you rely on Section 7(i)?

All of the general duties in Section 8. Reliance on Section 7(i) changes the basis for processing. It does not remove these:

DutySourceWhat it means for HR and IT
Stay responsible for vendorsSource: Section 8(1)What it means for HR and IT: The payroll bureau, HRMS provider and background-check firm act for you. You answer for their failures
Accurate data behind decisionsSource: Section 8(3)What it means for HR and IT: Where HR data is used to decide something about a person (pay, promotion, exit), it must be complete, accurate and consistent. Fix errors at source, not in a side spreadsheet
Reasonable security safeguardsSource: Section 8(5), Rule 6What it means for HR and IT: Encryption or masking, access control, logs and monitoring, backups, one-year log retention and processor contract clauses
Breach intimationSource: Section 8(6), Rule 7What it means for HR and IT: Tell the Board and each affected person. The Board gets a detailed report within 72 hours. An HR export sent to the wrong list is a breach
Erasure when the purpose endsSource: Section 8(7)What it means for HR and IT: Erase when the purpose is no longer served, unless a law requires you to keep it, and make processors do the same
Grievance redressalSource: Section 8(10), Section 13, Rule 14(3)What it means for HR and IT: A working channel, with a published response period of no more than 90 days

The penalty exposure is the same as for customer data: up to ₹250 crore for failing to take reasonable security safeguards and up to ₹200 crore for failing to give breach notice. The HRMS holds identity numbers, bank accounts and family details for everyone in the company, so it is a high-value target.

Rules 3 and 5 to 16 start on 13 May 2027. Rule 4 (Consent Managers) has been in force since 13 November 2026.

Where does employee personal data actually live? Build the HR data map

Start with a map, as for any DPDP work. The data map guide shows the method. For HR, these are the systems that usually belong on it, and the question to ask of each.

SystemTypical personal dataQuestion for the owner
HRMS coreTypical personal data: Identity, contact, address, family, bank details, ID numbers, job historyQuestion for the owner: Which fields are used, and which were collected "just in case"?
PayrollTypical personal data: Salary, bank account, tax and provident fund details, deductionsQuestion for the owner: Who is the vendor, how is the file sent, and is it encrypted in transit and at rest?
Applicant tracking and job portalsTypical personal data: CVs, contact details, interview notes, assessment resultsQuestion for the owner: How long are rejected candidates kept, and for what purpose?
Attendance, access and CCTVTypical personal data: Biometrics, swipe logs, location, videoQuestion for the owner: Who can view the raw data, and what is the retention period?
Background verificationTypical personal data: ID documents, addresses, education and employment historyQuestion for the owner: Does the vendor delete after the report?
Benefits and insuranceTypical personal data: Dependants' names, dates of birth, medical detailsQuestion for the owner: Is the insurer a processor acting for you or a separate fiduciary?
Email, chat, endpoint and data loss toolsTypical personal data: Messages, file activity, device logsQuestion for the owner: What is monitored, and who has access to the console?
Spreadsheets, shared drives and email attachmentsTypical personal data: Copies of any of the aboveQuestion for the owner: Where are the exports, and who owns deleting them?

The last row is where many HR leaks start. Teams export salary sheets, interview feedback and exit lists to spreadsheets and mail them around. Find those copies and give each a home, an owner and a delete date.

What should IT do about HRMS access, logs and vendors?

A close view of a rack of plain brass keys on hooks inside an open wooden key cabinet, shallow depth of field, warm light, no tags or readable text.

Rule 6(1) lists the minimum safeguards. Here is what each looks like for an HRMS and the systems around it.

  • Role-based access, down to the field. Split roles for recruiting, payroll, HR business partners and managers. Managers see their own reports only.
  • Encryption and masking. Encrypt data in the database and in backups. Mask identity and bank numbers on screens and exports unless the task needs them. Rule 6(1)(a) names encryption, obfuscation, masking and virtual tokens.
  • Strong sign-in. Single sign-on and multi-factor authentication for the HRMS, payroll and admin consoles. No shared logins.
  • Joiner, mover, leaver control. Remove access when a person leaves or changes role. Review the HR admin list on a schedule and keep the review as evidence. Our Rule 6 checklist covers the wider control set.
  • Logs and monitoring. Record who viewed, changed or exported employee records, and review the logs. Rule 6(1)(c) asks for visibility on access, and Rule 6(1)(e) asks you to keep logs and personal data for one year to support detection and investigation, unless another law requires longer.
  • Backups and recovery. Rule 6(1)(d) asks for reasonable continuity measures, such as backups. Test restoring the HRMS and payroll.
  • Vendor contracts. Rule 6(1)(f) asks for suitable security terms in each processor contract, wherever that applies. List each HR vendor, what it receives, where it is hosted, its breach notice period and what it does with your data at contract end.

Check AI features too. Many HR suites ship résumé screening, interview summaries and chat assistants. A tool that reads the HR folder to answer staff questions can show one person another's salary if permissions are wrong. Decide which AI features are on, what data they read and whether the vendor trains on it. Use permission-aware retrieval so the assistant sees only what the asker may see. If an HR vendor is breached, the notice duty still falls on you, so ask each one how fast it would tell you.

How long can you keep employee data after someone leaves?

Only as long as the purpose lasts or a law requires. Section 8(7) says to erase personal data when the purpose is no longer served, unless retention is necessary for compliance with a law. For HR that second clause matters. Tax, payroll, provident fund, gratuity and other labour and company law records often have their own retention periods, and those periods differ by record.

The Act and Rules do not give you a schedule for HR records, and we do not list periods here. Build the schedule with counsel and keep it as a table:

RecordWhy you keep itLaw or reason relied onKeep untilOwner
Payroll and tax recordsWhy you keep it: Statutory filings and auditsLaw or reason relied on: To be confirmed by counselKeep until: A dateOwner: Finance
Employment contract and exit papersWhy you keep it: Disputes, references, statutory recordsLaw or reason relied on: To be confirmed by counselKeep until: A dateOwner: HR

Then design for it. At exit, move the record from the live HRMS to a restricted archive. Stamp each record with a purge date. Use a legal hold flag, set by a named person, when counsel says a record must stay for a dispute. Section 17(1)(a) removes most Chapter II duties where processing is necessary for enforcing a legal right or claim, but Sections 8(1) and 8(5) stay, so the archive still needs security. Counsel decides when that exemption applies.

The mechanics of deleting across systems and processors are in our post on automating DPDP erasure. Treat employee exit as one more trigger for the same task list.

How should you handle employee rights requests and grievances?

Section 11 gives a right to a summary of data and the other parties it was shared with. Section 12 gives rights to correction, completion, updating and erasure. Both are worded around consent "including consent as referred to in clause (a) of section 7". Whether they reach data processed only under Section 7(i) is a point for counsel, and employers may read it differently.

The practical answer does not depend on that. Employees will ask what you hold, will ask for corrections to their records and will complain. Run one channel for all of it:

  • Publish how an employee makes a request, as Rule 14(1) asks you to do on your website or app. An intranet page and a named HR contact are the minimum for staff.
  • Log each request, decision and reply, with the reason for any refusal, such as a legal retention duty.
  • Route grievances through the same system, with the published response period of no more than 90 days (Rule 14(3)).
  • Handle nominations. Section 14 lets a person nominate someone to exercise rights on death or incapacity.

Our rights-request workflow post describes the design. It is written for customers, and works for staff too.

What about interns, contractors and group companies?

Minors. A child is anyone under 18 (Section 2(f)). Section 9(1) requires verifiable consent of a parent or lawful guardian before processing a child's data. If you take on interns or apprentices under 18, flag them in the HRMS, and ask counsel how Section 9 and any employment rules apply.

Contractors and agency staff. Decide who is the Data Fiduciary for each person. A staffing agency may decide purposes for its own workers, while you decide them for the access data you hold. Write it into the contract and the data map.

Group companies and global HR platforms. Sending HR data to a parent or a global HRMS is often a transfer abroad. Section 16 lets the government restrict transfers to countries it notifies, and none is notified as of November 2026. DPDP does not require data to stay in India, though hosting there avoids future restrictions. Record each transfer in the data map.

What order should HR and IT work in before 13 May 2027?

  • Name the owners. HR owns purposes, notices and retention. IT owns systems, access, logs and deletion. Counsel owns the reading of each ground.
  • Map the HR systems and the spreadsheets around them. Use the table above.
  • Sort each purpose into Section 7(i), another Section 7 clause or consent. Move optional uses out of the offer letter.
  • Fix access first. Role-based access, multi-factor sign-in and leaver checks cut breach risk fastest.
  • List and review HR vendors. Check contracts for security terms, breach notice and deletion at the end.
  • Set the retention schedule and purge dates. Include candidates and former employees.
  • Stand up one request and grievance channel for staff.
  • Publish an employee privacy notice listing purposes, retention, vendors and a contact point.

Mono's DPDP implementation work covers this kind of system work with your engineers, and a gap assessment is a way to start. Mono is not a law firm, and your counsel signs off on the legal grounds.

Sources: Digital Personal Data Protection Act, 2023, Sections 2(f), 3, 5, 6, 7(a), 7(d), 7(i), 8, 9, 11 to 14, 16, 17(1)(a) and the Schedule (penalties). Digital Personal Data Protection Rules, 2025, Rules 1, 3, 6, 7 and 14, notified 13 November 2025. Both texts are on dpbi.gov.in. Last reviewed 20 November 2026.

FAQ

Does DPDP apply to employee data?

Yes. Section 3 applies the Act to digital personal data processed in India, which includes records in an HRMS, payroll files and scanned documents. Employees, former employees, candidates, interns and contractors are all Data Principals, and the employer is the Data Fiduciary. The core duties start on 13 May 2027.

Do you need employee consent to process HR data under DPDP?

Not for purposes that fit Section 7(i), which covers processing for the purposes of employment or to safeguard the employer from loss or liability. Optional uses, such as publishing staff photos or keeping rejected candidates in a talent pool, are better handled with consent. Counsel should confirm which route fits each purpose.

Is HR data exempt from DPDP duties if you rely on Section 7(i)?

No. Section 7(i) removes the need for consent for that use only. The Section 8 duties still apply: reasonable security safeguards under Rule 6, breach intimation under Rule 7, accuracy where data drives decisions, control of processors, and erasure when the purpose ends unless a law requires retention.

How long can you keep an ex-employee's data under DPDP?

Only while the purpose lasts or a law requires you to keep it. Section 8(7) requires erasure once the purpose is no longer served, unless retention is necessary for compliance with a law. Build a retention schedule with counsel that names the law behind each record, then set purge dates and restrict access to archived records.

Can employees ask to see or delete their data under DPDP?

Sections 11 and 12 give rights of access, correction and erasure, but they are worded around consent and Section 7(a), so how far they reach data held under Section 7(i) is a question for counsel. In practice, run one channel for staff requests and grievances, keep a log, and refuse erasure only where a legal retention duty applies.

Get your HR systems ready for DPDP.