Sector guidesUpdated 22 November 20269 min read

DPDP for HR: Employee Data and the Employment Legitimate Use

What section 7(i) lets employers do without consent, where its limits are, and how HR handles candidates, monitoring, dependants, ex-employees and HR tech under DPDP.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Legal basis
s. 7(i) employment legitimate use
Covered purposes
Employment; safeguarding employer from loss or liability; benefits sought
Notice required for s. 7(i)?
Not under s. 5, but good practice
Breach reporting
Every breach; 72-hour Board report (Rule 7)
Log retention
Minimum one year (Rule 8(3))
Applies from
13 May 2027

Quick answer

Section 7(i) of the DPDP Act lets employers process personal data without consent for employment purposes, and to safeguard against loss or liability such as corporate espionage or trade-secret leaks. It does not cover unrelated uses. From 13 May 2027, Rule 6 security, 72-hour breach reporting, Rule 8(3) one-year log retention and erasure once purposes end still apply to all employee data.

  • Section 7(i) is a legitimate use, so no consent or consent notice is needed for genuine employment purposes.
  • It does not stretch to marketing, selling data or unrelated analytics, and necessity still matters for monitoring.
  • Security, breach, accuracy, retention and grievance duties under section 8 apply in full to employee data.
  • Dependants' data for benefits is covered as a benefit sought by the employee; children's data still triggers section 9.
  • Candidates are not yet employees; give them a notice and take a cautious view of whether s. 7(i) covers recruitment.

Who this is for: HR and people teams, Employers of all sizes, HR tech and payroll vendors, Security teams running employee monitoring, Data Protection Officers

What does section 7(i) let employers do?

Section 7 of the DPDP Act lists "certain legitimate uses" for which a Data Fiduciary may process personal data without consent. 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 and classified information, or provision of any service or benefit sought by a Data Principal who is an employee.

In practice this covers the core HR lifecycle for employees:

  • Onboarding, KYC for payroll, bank details, tax and statutory registrations.
  • Payroll, attendance, leave, performance management and promotions.
  • Benefits administration — insurance, gratuity, reimbursements — that the employee seeks.
  • IT and security monitoring proportionate to protecting confidential information.
  • Disciplinary processes and investigations.
  • Statutory compliance and reporting under labour and tax laws.

Because these are legitimate uses, the consent notice under section 5 is not required for them, and consent-withdrawal mechanics do not apply. Many employers still give a plain-language employee privacy notice; it supports transparency, sets expectations for monitoring and makes it easier to show necessity.

The Rules that make DPDP's obligations operational apply from 13 May 2027.

Where section 7(i) stops

Section 7(i) is broad but not unlimited. Its limits come from its own words and from the rest of the Act.

  • Purpose-bound. "Purposes of employment" and safeguarding against loss or liability. Selling employee data, using it to market products to employees for a third party, or training a commercial AI model on employee content fall outside.
  • Necessity in practice. The Act's consent provisions explicitly require limitation to necessary data, and the legitimate-use structure is purpose-specific. Monitoring that is disproportionate to the risk — keystroke logging of all staff, constant webcam capture, analysis of personal social media — is hard to justify as needed for employment purposes.
  • Other people's data. Section 7(i) covers the employee's data. Customer, vendor and candidate data in HR systems needs its own basis.
  • Children. Dependants under 18 are children; section 9 applies to their data even when the employee provides it for benefits.
  • Not an exemption from section 8. Security (s. 8(5)), breach notice (s. 8(6)), accuracy where data informs decisions (s. 8(3)), erasure once the purpose is served (s. 8(7)), the contact person (s. 8(9)) and grievance redressal (s. 8(10)) all apply.
HR activityFits s. 7(i)?
Payroll and statutory filingsYes
DLP on corporate emailYes, if proportionate
Employee wellness app sharing data with insurer for marketingNo — consent needed
Sentiment analysis of private chatsDoubtful
Training a vendor's general AI model on HR recordsNo

Candidates, interns, contractors and alumni

Not everyone in HR systems is an employee.

  • Job candidates. Section 7(i) speaks of employment purposes, and recruitment is arguably preparatory to employment, but the text does not say so explicitly. A cautious approach: give candidates a Rule 3-style notice at application, rely on the data they voluntarily provide for the application (section 7(a)), and seek consent for anything beyond — talent pools, future roles, background checks by third parties, AI-based assessments.
  • Background verification. Verification vendors are processors if acting on your instructions; get the candidate's consent where you rely on it, and minimise the checks to what the role requires.
  • Contractors and consultants. Their relationship may not be "employment". Use contract terms and notices; apply s. 7(i) only where the relationship genuinely is employment.
  • Interns. Treat as employees where engaged under an employment-type arrangement; if under 18, section 9 applies.
  • Former employees. Retain records required by labour, tax and other laws; erase the rest once the purpose is served. Alumni networks and rehire pools need a clear purpose and usually consent.

AI hiring tools raise extra questions — see AI hiring tools and DPDP.

Employee monitoring and HR AI

Security monitoring is explicitly contemplated by section 7(i) — "prevention of corporate espionage, maintenance of confidentiality of trade secrets". Design monitoring so it is defensible:

  1. Risk-based scope. Monitor corporate systems and data, not personal devices or private life. Focus DLP and insider-risk tooling on access to confidential data.
  2. Transparency. Tell employees what is monitored, why and who can see it.
  3. Access controls. Restrict monitoring dashboards to security; HR access to monitoring data only through a documented investigation process.
  4. Retention. Rule 8(3) requires processing logs to be kept at least one year, then erased; Rule 6(1)(e) requires security logs for one year. Do not keep monitoring data indefinitely.
  5. Accuracy. Where monitoring or AI scores feed decisions — performance ratings, terminations — section 8(3) requires completeness, accuracy and consistency. Provide a route for employees to challenge and correct.

Productivity scoring, attrition prediction and sentiment analysis are higher-risk. If your organisation employs people in the EU, AI used for recruitment, promotion, termination, task allocation or monitoring is Annex III high-risk under the EU AI Act. See EU AI Act high-risk rules for HR tech and enterprise AI copilots.

Dependants, benefits and children's data

Benefits administration brings in data about spouses, parents and children: group health insurance enrolments, nominations for statutory funds, education allowances.

  • Basis. Section 7(i) covers "provision of any service or benefit sought by a Data Principal who is an employee", which supports processing dependants' data to deliver the benefit she asked for. Use it only for that benefit.
  • Children's data. Children under 18 remain protected by section 9. The employee is usually the parent providing consent. Rule 10(1)(a) allows due diligence by reference to reliable identity and age details already available with the fiduciary — your HR KYC records normally satisfy this, so the check can be built into the enrolment flow.
  • Insurers and brokers. They are often separate fiduciaries for underwriting and claims. Share only enrolment data needed and disclose sharing.
  • Health data. Medical leave certificates and wellness programme data are highly sensitive in practice. Limit access to HR staff who need it; keep wellness-programme data separate from performance systems.
  • Nominations. Statutory fund nominations are different from DPDP's right to nominate under Rule 14(4), which concerns exercising data rights.

Security, breach, vendors and employee rights

HR systems hold PAN, Aadhaar-format numbers, bank accounts, salary, medical and disciplinary data — a breach target and an insider-risk target.

  • Rule 6 safeguards: encryption, role-based access in HRMS, logging and review of access to salary and medical data, backups, one-year log retention, and security clauses in contracts with payroll, HRMS, background-verification and benefits vendors.
  • Rule 7 breach notice: every breach of employee data must be notified to affected employees without delay and to the Board, with a 72-hour detailed report. A salary spreadsheet emailed to the wrong distribution list is a breach.
  • Rule 9 contact: publish the contact person for processing questions, including on the intranet for employees.
  • Rights: the Act's access and erasure rights are framed mainly around consent-based processing, and Rule 14(2) describes requests to the fiduciary "to whom she has previously given consent". Their reach over section 7(i) processing is therefore narrower; but grievance redressal under section 13 is available, and responding helpfully to access requests is good practice.
  • Grievances: publish a response period of at most 90 days (Rule 14(3)).

Before 13 May 2027: map HR data, document s. 7(i) purposes, fix HRMS access, refresh vendor contracts, set retention for ex-employees and candidates, and publish an employee privacy notice.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Document s. 7(i) purposes per HR process

    List each HR activity, the employment purpose it serves and the data it needs.

    DPDP Act s. 7(i)

  2. Identify processing outside s. 7(i)

    Flag talent pools, wellness marketing, alumni networks and AI training for consent or another basis.

    DPDP Act ss. 6, 7

  3. Give candidates a notice at application

    Explain data use, retention and any AI assessment, and seek consent for extras.

    Rule 3

  4. Scope employee monitoring to risk

    Monitor corporate systems for security purposes and tell employees what is monitored.

    DPDP Act s. 7(i)

  5. Restrict HRMS access to salary and medical data

    Apply role-based access and log and review access.

    Rule 6(1)(b), 6(1)(c)

  6. Verify parents for dependants under 18

    Use HR KYC records to confirm the employee is an identifiable adult parent.

    Rule 10(1)(a)

  7. Refresh HR vendor contracts

    Add DPDP safeguard, breach notice, retention and erasure terms for payroll and HRMS vendors.

    Rule 6(1)(f); s. 8(2)

  8. Set retention for ex-employees and candidates

    Keep legally required records, erase the rest, and keep logs one year.

    DPDP Act s. 8(7); Rule 8(3)

  9. Ensure accuracy for HR decisions

    Provide correction routes where data or AI scores inform performance or termination.

    DPDP Act s. 8(3)

  10. Publish an employee contact and grievance route

    Show the contact person and a response period of at most 90 days.

    Rules 9, 14(3)

Key dates

  1. DPDP Rules notified

  2. Rules 6–14 apply to employee data processing

Answers

Frequently asked questions

Do employers need employee consent under the DPDP Act?

Not for employment purposes. Section 7(i) lets employers process personal data without consent for employment and to safeguard against loss or liability, such as preventing corporate espionage or protecting trade secrets, and to provide benefits employees seek. Purposes outside employment, such as third-party marketing, need consent.

Can my employer monitor my work laptop under DPDP?

Section 7(i) supports monitoring to protect confidential information and prevent espionage, so proportionate monitoring of corporate systems is generally permissible without consent. Monitoring should be scoped to risk, transparent, access-controlled and time-limited. Intrusive monitoring of private life or personal devices is much harder to justify.

Does section 7(i) cover job applicants?

The Act does not say explicitly. Recruitment is arguably preparatory to employment, but a cautious approach is to give candidates a notice, rely on the data they voluntarily provide for their application, and seek consent for talent pools, third-party background checks and AI-based assessments.

How long can employers keep ex-employees' data?

As long as labour, tax and other laws require for specific records, which section 8(7) permits. Other data should be erased once the employment purpose is served. Rule 8(3) separately requires processing logs to be kept for at least one year from processing, then erased unless another law requires longer.

Can employees ask HR for a copy of their data under DPDP?

The Act's access right is framed around processing based on consent, so its reach over section 7(i) processing is narrower. Employees can still use the employer's grievance redressal mechanism under section 13, and many employers answer access requests as good practice and to resolve grievances early.

Is a leaked salary sheet a DPDP breach?

Yes. Unauthorised disclosure of personal data is a personal data breach. From 13 May 2027, Rule 7 requires the employer to notify affected employees without delay and the Data Protection Board, with a detailed report within 72 hours. There is no minimum size or harm threshold.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 7(i) (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 8 and 9 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 6, 7 and 8(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 9 and 14 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.