What is a legitimate use under the DPDP Act?
A legitimate use under the DPDP Act is one of nine situations, listed in Section 7, where a Data Fiduciary may process personal data without asking for consent. Section 4(1) allows only two grounds: consent, or a legitimate use. If your purpose is not on the Section 7 list, you need consent. Section 7 applies from 13 May 2027, when most of the Act's duties begin.
What are the nine legitimate uses in Section 7?
The list is closed: clauses (a) to (i), with nothing like a catch-all "legitimate interests" ground.
| Clause | The legitimate use | Who mostly relies on it |
|---|---|---|
| 7(a) | A specified purpose for which the person voluntarily gave you her data, unless she indicates she does not consent to that use | Any business |
| 7(b) | The State providing a subsidy, benefit, service, certificate, licence or permit, where the person consented earlier or the data is in a database the Central Government notifies | Government bodies |
| 7(c) | The State performing a function under law, or in the interest of the sovereignty and integrity of India or the security of the State | Government bodies |
| 7(d) | Fulfilling a legal obligation to disclose information to the State | Any business |
| 7(e) | Complying with a judgment, decree or order under Indian law, or a foreign judgment or order on contractual or civil claims | Any business |
| 7(f) | Responding to a medical emergency involving a threat to the life or immediate health of the person or anyone else | Any business, hospitals |
| 7(g) | Medical treatment or health services during an epidemic, outbreak of disease or other threat to public health | Healthcare providers |
| 7(h) | Ensuring safety or providing help during a disaster or a breakdown of public order | Any business |
| 7(i) | Employment purposes, safeguarding the employer from loss or liability, or a service or benefit an employee asks for | Every employer |
How does Section 7(a), voluntarily provided data, work?
Section 7(a) lets you use data a person gave you voluntarily, for the specified purpose she gave it for, until she indicates she does not consent to that use. It is narrow: the purpose is hers, not whatever else you would like to do with the data.
The Act gives two illustrations:
- A customer buys from a pharmacy and asks for the payment receipt by message. The pharmacy may use her number to send the receipt.
- A client asks a real estate broker to find a flat to rent. The broker may use her details for that search. Once she says she no longer needs help, the broker must stop processing her data.
Because 7(a) rests on the person's own choice, the Act treats it like consent for some rights: the right of access (Section 11(1)) and the right to correction and erasure (Section 12(1)) both cover data given with "consent as referred to in clause (a) of section 7".
How does Section 7(i) cover employee data?
Section 7(i) lets an employer process personal data for the purposes of employment, to safeguard itself from loss or liability (the Act's examples are preventing corporate espionage and keeping trade secrets, intellectual property and classified information confidential), and to provide a service or benefit an employee asks for. Payroll, attendance, leave, performance reviews and an insurance scheme the employee opts into fit here.
It does not cover everything an employer might want. Using an employee's photo in an advertising campaign, for example, is hard to fit within an employment purpose, so the safer course is to ask for consent. For candidates, contractors, monitoring and retention, see DPDP and employee data.
Which DPDP duties still apply when you rely on a legitimate use?
Section 7 replaces consent and the consent notice, not the rest of the Act. These duties apply whatever your ground:
| Duty | Provision | Applies to Section 7 uses? |
|---|---|---|
| Notice before or with a consent request | Section 5(1), Rule 3 | No, it is tied to consent under Section 6 |
| Responsibility for your Data Processors, who need a valid contract | Section 8(1), 8(2) | Yes |
| Accuracy when data is used for a decision about the person or shared | Section 8(3) | Yes |
| Reasonable security safeguards, including logs kept for one year | Section 8(5), Rule 6 | Yes |
| Erase data once the specified purpose is no longer served | Section 8(7), Rule 8 | Yes |
| Breach notice to the Board and affected people | Section 8(6), Rule 7 | Yes |
| Access, correction and erasure rights | Sections 11(1), 12(1) | For consent and 7(a) only |
| Grievance redressal and nomination rights | Sections 13, 14 | Yes, no consent limit |
| Verifiable parental consent for children (under 18) | Section 9, Rules 10 to 12 | Yes, except the exemptions in the Fourth Schedule |
On children: Section 9(1) requires verifiable parental consent before processing any child's personal data, and it does not refer to Section 7. A legitimate use alone does not lift that duty; only the classes and purposes in the Fourth Schedule of the DPDP Rules 2025 (Rule 12) do. See children's data under the DPDP Act.
What do the DPDP Rules 2025 add for legitimate uses?
Rule 5 covers only Section 7(b): when the State processes personal data to give a subsidy, benefit, service, certificate, licence or permit, it must follow the standards in the Second Schedule. These include lawful processing, using only the data needed, reasonable accuracy, retention only as long as needed, reasonable security safeguards, an intimation to the person with a contact point, and accountability. Rule 5 applies from 13 May 2027. The Rules add nothing specific for private businesses relying on 7(a) or 7(i).
Example: how a company maps its purposes to a ground
This is a made-up example. "Kitab Cloud" is a fictional Bengaluru SaaS company with 60 employees that sells invoicing software to small shops.
| Purpose | Ground | Why |
|---|---|---|
| Emailing an invoice a customer asked for | Section 7(a) | The customer gave her email for that purpose |
| Monthly product newsletter to the same customers | Consent (Section 6) | Not the purpose she gave the email for |
| Payroll and leave records | Section 7(i) | Employment purpose |
| Monitoring company laptops for leaks of source code | Section 7(i) | Safeguarding the employer from loss, protecting trade secrets |
| Handing records to tax authorities under a legal notice | Section 7(d) | Legal obligation to disclose to the State |
| Staff photos on the marketing website | Consent (Section 6) | Hard to fit within an employment purpose |
Kitab Cloud writes each decision into its record of processing, sends the consent notice only for the two consent-based purposes, and sets an erasure point for every row, because Section 8(7) applies to all six.
How do you apply legitimate uses step by step?
- List every purpose for which you process personal data, not every system. One database can serve several purposes.
- For each purpose, check whether it fits one clause of Section 7 exactly. If it does not, plan for consent.
- For 7(a), write down the purpose the person gave the data for, and build a way for her to say she does not want that use any more.
- For 7(i), check the purpose is about employment, protecting the employer, or a benefit the employee asked for.
- Check for children's data: Section 9 still needs verifiable parental consent unless a Fourth Schedule exemption applies.
- Set the erasure point for each purpose (Section 8(7)) and apply the Rule 6 safeguards to all of it.
- Send the Section 5 notice for consent-based purposes, and keep the whole map up to date before 13 May 2027.
What are the common mistakes and myths about legitimate use?
- Myth: "It is like GDPR's legitimate interests." It is not. There is no balancing test and no open-ended ground; see DPDP vs GDPR.
- Mistake: treating 7(a) as permission for any later use. It covers the specified purpose only, and ends when the person says so.
- Mistake: assuming Section 7 means no duties. Security, accuracy, erasure, breach notice and grievance redressal all still apply.
- Mistake: putting all employee data under 7(i). Uses outside employment purposes need another ground.
- Mistake: not recording the decision. If the Data Protection Board asks, you need to show which ground you relied on for each purpose. Breaching a provision with no specific penalty can cost up to ₹50 crore (the Schedule); see DPDP penalties.
GRC-Flow's AI GRC Analyst helps you work through this purpose by purpose and answers with the provision it relies on, and its RoPA drafts record the ground for each purpose. A person reviews every result: no tool can guarantee compliance.
This guide is general information about the DPDP Act and Rules, not legal advice.
Frequently asked questions
Is legitimate use under the DPDP Act the same as legitimate interest under GDPR?
No. GDPR Article 6(1)(f) lets a business rely on its own legitimate interests after a balancing test. Section 7 of the DPDP Act is a closed list of nine specific uses. If your purpose is not on the list, you need consent.
Do employers need consent to process employee data under the DPDP Act?
Not for employment purposes. Section 7(i) covers processing for the purposes of employment, safeguarding the employer from loss or liability (such as preventing corporate espionage or protecting trade secrets), and providing a service or benefit an employee asks for. Uses outside these purposes need consent or another listed use.
Do I need to give a privacy notice when relying on a legitimate use?
Section 5(1) ties the notice duty to requests for consent under Section 6, so a Section 7 use does not need a Section 5 notice. Telling people what you do with their data is still good practice, and State processing under Section 7(b) has its own intimation duty in the Second Schedule of the DPDP Rules 2025.
Can a customer stop processing under Section 7(a)?
Yes. Section 7(a) applies only while the person has not indicated that she does not consent to the use. In the Act's own illustration, once a client tells a broker she no longer needs help, the broker must stop processing her data.
Can a business use legitimate use for marketing?
Marketing is not one of the nine uses in Section 7. Section 7(a) covers only the specified purpose the person gave the data for, such as sending a receipt, so marketing to that person generally needs separate consent.
Sources
- The Digital Personal Data Protection Act, 2023 (India Code)
- Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), Gazette text)
- PIB: Digital Personal Data Protection Rules, 2025
- GDPR, Article 6 (EUR-Lex)
This guide explains the law in general terms and is not legal advice. Check specific situations with a qualified lawyer.