Quick answer
Under section 7 of the DPDP Act, 2023, a Data Fiduciary may process personal data without consent only for listed "certain legitimate uses": data voluntarily provided for a specified purpose, State subsidies and functions, legal obligations, court orders, medical emergencies, epidemics, disasters and employment. It is a closed list, not a GDPR-style legitimate interests test, and section 8 duties still apply from 13 May 2027.
- Section 7 is a closed list; there is no open-ended legitimate interests balancing test in the DPDP Act.
- Section 7(a) covers data a person voluntarily gives for a specified purpose without indicating she does not consent.
- Employment purposes are a legitimate use, including preventing corporate espionage and protecting trade secrets.
- Security, accuracy, breach and retention duties under section 8 and the Rules apply whatever the lawful ground.
- State processing for subsidies and benefits under section 7(b) must follow the Second Schedule standards in Rule 5.
- Record which section 7 clause you rely on for every processing activity before 13 May 2027.
Who this is for: Product and engineering leads, HR and people teams, Healthcare providers, Government departments and vendors, Data Protection Officers
What are "legitimate uses" under the DPDP Act?
Section 4 of the DPDP Act allows personal data to be processed only for a lawful purpose, and only on one of two grounds: consent given under section 6, or certain legitimate uses listed in section 7. If a processing activity fits neither, it is unlawful, however useful it is to the business.
Section 7 is deliberately narrow. It is a fixed list of situations where Parliament decided that asking for consent would be impractical, pointless or against the public interest. It is not a general "legitimate interests" ground of the kind found in Article 6(1)(f) of the GDPR, so there is no balancing test where you weigh your business interest against the individual's rights. If your use case is not on the list, you need consent.
Two practical consequences follow:
- No consent notice is needed for processing under section 7, because the section 5 notice duty attaches to requests for consent. For State processing under section 7(b), however, the Second Schedule still requires an intimation to the Data Principal with a contact person and a link to exercise rights.
- Everything else still applies. Reasonable security safeguards (Rule 6), breach intimation (Rule 7), the one-year log retention minimum (Rule 8(3)), accuracy where data is used for decisions, and erasure once the purpose is served all bind you regardless of the lawful ground.
The safest engineering habit is to treat the lawful ground as a mandatory field on every entry in your processing inventory, with the exact clause cited.
The nine section 7 grounds at a glance
| Clause | Legitimate use | Typical example |
|---|---|---|
| 7(a) | Data voluntarily provided for a specified purpose, where the Data Principal has not indicated she does not consent | A customer gives her phone number to a pharmacy so it can send the bill |
| 7(b) | State or its instrumentalities providing a subsidy, benefit, service, certificate, licence or permit | A welfare scheme using records already in a State database |
| 7(c) | State performing a function under law, or in the interest of sovereignty, integrity or security of India | Statutory functions of a department |
| 7(d) | Fulfilling a legal obligation to disclose information to the State | Disclosures a law requires you to make |
| 7(e) | Complying with a judgment, decree or order | Responding to a court order |
| 7(f) | Responding to a medical emergency involving a threat to life or health | Ambulance or hospital triage |
| 7(g) | Medical treatment or health services during an epidemic or threat to public health | Outbreak response |
| 7(h) | Safety or assistance during a disaster or breakdown of public order | Evacuation lists |
| 7(i) | Employment purposes or safeguarding the employer from loss or liability | Payroll, attendance, preventing corporate espionage, protecting trade secrets, providing employee benefits |
Most private companies will only ever rely on 7(a), 7(d), 7(e), 7(f) and 7(i). Clauses (b), (c), (g) and (h) are written mainly for the State and for emergencies. Read each clause in the official text before relying on it; the conditions in the statute are narrower than a one-line summary suggests.
Section 7(a): the "voluntarily provided" ground
Section 7(a) is the ground most likely to be stretched, so it deserves care. It applies where a Data Principal voluntarily provides her personal data for a specified purpose and has not indicated that she does not consent to its use for that purpose.
Three conditions must all hold:
- Voluntary provision. She gave the data herself, not via a broker, scraper or inference model.
- Specified purpose. The purpose was clear at the moment of provision. A phone number typed into a delivery form is for delivery.
- No objection. She has not opted out or otherwise signalled refusal.
What 7(a) does not cover is reuse for a different purpose. A number collected for delivery updates cannot be moved into a marketing list or a lookalike-audience upload on the strength of 7(a). That secondary use needs consent with a Rule 3 notice.
Engineering pattern
- Tag every field at collection with a
purpose_idandlawful_basis = "s7a". - Block downstream joins where the consuming service's purpose differs from the field's tag.
- Record any objection (an opt-out, a "do not contact" flag) and make it a hard filter in every pipeline that reads the field.
Note that 7(a) processing is treated like consent for some rights: the access and correction/erasure rights in sections 11 and 12 are framed around data processed on consent or under section 7(a), so build those request flows to cover 7(a) data too.
Section 7(i): employment purposes
For HR and IT teams, section 7(i) is the workhorse. It allows processing for the purposes of employment or to safeguard the employer from loss or liability, and the Act names examples: preventing corporate espionage, maintaining confidentiality of trade secrets, intellectual property and classified information, and providing any service or benefit sought by an employee.
What usually fits:
- Payroll, tax deductions and statutory filings.
- Attendance, leave and access-control logs for offices.
- Endpoint security and data-loss-prevention monitoring proportionate to the risk.
- Employee benefits such as insurance enrolment.
What is risky to place under 7(i) without further thought:
- Candidate data before an offer. A job applicant is not yet an employee; check whether consent or 7(a) is the better fit (see AI hiring tools).
- Monitoring beyond what is needed, such as continuous webcam analytics or keystroke biometrics. The ground is "for the purposes of employment", which implies necessity.
- Family members' data (dependants for insurance) — process only what the benefit requires.
- Reuse for unrelated analytics or model training, for example feeding performance reviews into a general-purpose model.
The employer remains a Data Fiduciary with full duties: Rule 6 safeguards over HR systems, Rule 7 breach intimation to every affected employee, and contracts with payroll and HRMS processors. For a fuller treatment, see HR and employee data.
State, legal and emergency grounds
State processing — 7(b) and 7(c)
Clause 7(b) lets the State and its instrumentalities process personal data to provide or issue subsidies, benefits, services, certificates, licences or permits. Rule 5 defines "under law", "under policy" and "using public funds", and requires processing to follow the Second Schedule standards: lawful processing, purpose limitation, data minimisation, reasonable accuracy, retention only as long as needed, reasonable security safeguards, an intimation to the Data Principal with a contact person and a link to exercise rights, and accountability of whoever determines purpose and means. Private vendors building these systems should design to those standards. See State processing for subsidies and benefits.
Legal obligations and court orders — 7(d) and 7(e)
Where a law obliges you to disclose information to the State, or a judgment, decree or order requires processing, you do not seek consent. Keep a register of the legal instrument, the requesting authority and the data released. Rule 23 and the Seventh Schedule separately allow the Central Government to call for information, and may restrict you from telling the Data Principal where disclosure would prejudice sovereignty or security.
Health and safety — 7(f), 7(g) and 7(h)
Medical emergencies involving a threat to life, treatment during epidemics, and safety measures during disasters or breakdowns of public order are covered. Scope these narrowly in time: an emergency ground does not justify retaining the data indefinitely afterwards.
Common mistakes when relying on section 7
- Treating 7(a) as legitimate interests. "The user gave us the data" does not make every later use lawful. The purpose is fixed at the point of provision.
- No documented basis. If the Board inquires, you need to show which clause you relied on and why. An inventory row that says "legitimate use" without a clause is weak evidence.
- Assuming no consent means no duties. Security, breach intimation, the one-year minimum retention of data and logs under Rule 8(3), and erasure after the purpose are all live obligations.
- Forgetting processors. Under section 8(1) the Data Fiduciary is responsible for processing done on its behalf. A payroll vendor operating under 7(i) still needs a contract with security clauses (Rule 6(1)(f)).
- Mixing grounds in one pipeline. A data warehouse table combining 7(i) HR data with consent-based marketing data makes purpose enforcement hard. Separate them or tag at row level.
- Using emergency grounds after the emergency. Delete or re-base the data once the emergency purpose is served.
- Ignoring children. Section 9 duties for children's data sit on top of the lawful ground, subject to the Fourth Schedule exemptions in Rule 12.
What to do before 13 May 2027
The core fiduciary obligations in the Rules apply from 13 May 2027, and section 7 sits inside the part of the Act that commences on the same date. That leaves roughly six months to clean up lawful bases.
A practical sequence:
- Inventory. List every processing activity with purpose, data categories, systems and processors. The data mapping guide shows a schema.
- Assign a basis. For each row, choose consent (s.6) or a specific section 7 clause. If neither fits, stop the processing or plan a consent flow.
- Test 7(a) claims. For each 7(a) row, confirm voluntary provision, a specified purpose and an objection mechanism.
- Fix notices. Where you move a use to consent, build a Rule 3 notice and a withdrawal path as easy as giving consent. See consent requirements.
- Wire the controls. Enforce purpose tags at query time, keep processing logs for at least one year under Rule 8(3), and set erasure jobs for when the purpose is served.
- Review annually. Products change; a basis that was right at launch may not fit a new feature.
Further reading on suhasbhairav.com
- BlogAI Agents in Regulated Industries: Finance and Healthcare Use Cases
- BlogGDPR for AI Agents: Consent, Minimization, Auditability
- BlogAI risks in healthcare products: governance & safety
- AI Use CasesAI Agent Use Case: Hr Departments Using Employee Surveys to Identify Engagement Risks
- AI SkillsAGENTS.md Template for Privacy and Data Governance Agents
Key dates
DPDP Act receives assent; section 7 lists legitimate uses
DPDP Rules notified; Board provisions in force
Section 7 and core fiduciary obligations, including Rules 5 to 16, apply
Answers
Frequently asked questions
Can I process personal data without consent under the DPDP Act?
Can I process personal data without consent under the DPDP Act?
Yes, but only for the legitimate uses listed in section 7 of the DPDP Act, 2023, such as data voluntarily provided for a specified purpose, legal obligations, court orders, medical emergencies, disasters and employment. If your purpose is not on that closed list, you need valid consent under section 6 with a Rule 3 notice.
Does the DPDP Act have a legitimate interests ground like GDPR?
Does the DPDP Act have a legitimate interests ground like GDPR?
No. The DPDP Act has no open-ended legitimate interests ground or balancing test. Section 7 lists specific "certain legitimate uses", and anything outside those clauses requires consent. Teams porting GDPR records of processing should re-map every legitimate-interests activity to either consent or a named section 7 clause.
Is employee data processing allowed without consent in India?
Is employee data processing allowed without consent in India?
Generally yes. Section 7(i) permits processing for employment purposes and to safeguard the employer from loss or liability, including preventing corporate espionage and protecting trade secrets. The processing still has to be for employment and proportionate, and the employer must meet security, breach and retention obligations under the Rules.
What does voluntarily provided mean under section 7(a)?
What does voluntarily provided mean under section 7(a)?
It means the Data Principal herself gave the personal data for a specified purpose and has not indicated that she does not consent to that use. It covers the purpose that was clear when she provided it, not later reuse such as marketing or model training, which needs separate consent.
Do I need a privacy notice for legitimate use processing?
Do I need a privacy notice for legitimate use processing?
The section 5 and Rule 3 notice is tied to requests for consent, so it is not required for section 7 processing in general. For State processing under section 7(b), the Second Schedule requires an intimation with a contact person and a link to exercise rights. A transparent privacy policy is still good practice.
Do data principal rights apply to legitimate use processing?
Do data principal rights apply to legitimate use processing?
Partly. The access right in section 11 and the correction and erasure rights in section 12 are framed around data processed on consent or under section 7(a). Grievance redressal and nomination are broader. Design request handling to cover 7(a) data alongside consented data, and check the statute for other grounds.
Legal references and sources
- Digital Personal Data Protection Act, 2023 — Section 7 (official text)
- Digital Personal Data Protection Act, 2023 — Section 4(1)(b) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 5 and Second Schedule (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 8(3) (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
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.
Related guides
- DPDP Act 2023DPDP Consent Requirements: Free, Specific, Informed and UnambiguousWhat valid consent means under section 6 of the DPDP Act and Rule 3: the five qualities, clear affirmative action, necessity, withdrawal parity and proof of consent.
- Sector guidesDPDP for HR: Employee Data and the Employment Legitimate UseWhat 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.
- DPDP Rules 2025DPDP Rule 5: Government Processing for Subsidies, Benefits and LicencesRule 5 and the Second Schedule set the standards the State must follow when it processes personal data without consent to provide subsidies, benefits, services, certificates, licences or permits.
- Templates & playbooksDPDP Data Mapping and Inventory: Step by StepA step-by-step method to build a DPDP data map and personal data inventory that feeds Rule 3 notices, Rule 6 security, Rule 7 breach scoping, Rule 8 retention and rights requests.
- DPDP Act 2023DPDP Act 2023 Explained in Plain EnglishA plain-English guide to India's Digital Personal Data Protection Act, 2023: who it covers, what it requires, penalties up to ₹250 crore, and what applies from 13 May 2027.
- DPDP Act 2023DPDP Act vs GDPR: Side-by-Side Comparison for Tech TeamsA row-by-row comparison of India's DPDP Act 2023 and Rules 2025 with the EU GDPR: scope, lawful bases, children, rights, breach timelines, DPOs, transfers and penalties.