DPDP Rules 2025Updated 22 November 20269 min read

DPDP Rule 5: Government Processing for Subsidies, Benefits and Licences

Rule 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.

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

Provision
Rule 5(1)–(2); Second Schedule (a)–(h)
Act basis
Section 7(b) legitimate use
In force from
13 May 2027
Who
State and its instrumentalities
Covers
Subsidy, benefit, service, certificate, licence, permit
Three bases
Under law, under policy, using public funds
Also used by
Rule 16 (research, archiving, statistics)

Quick answer

Rule 5 of the DPDP Rules, 2025 requires the State and its instrumentalities, when processing personal data under section 7(b) of the Act to provide or issue a subsidy, benefit, service, certificate, licence or permit, to follow the Second Schedule standards: lawful, purpose-limited, minimised, accurate processing with limited retention, security safeguards, intimation to the Data Principal with a contact and rights link, and accountability. It applies from 13 May 2027.

  • Rule 5 governs the section 7(b) legitimate use, which lets the State process personal data without consent for subsidies, benefits, services, certificates, licences and permits.
  • Rule 5(2) explains three bases: under law, under policy or executive instruction, and using public funds from consolidated, public account or authority funds.
  • The Second Schedule sets eight standards, (a) to (h), including data minimisation, accuracy, limited retention and security safeguards.
  • Standard (g) requires intimation to the Data Principal with a contact person and a link to exercise her rights under the Act.
  • Private vendors running government schemes as Data Processors need contracts and controls that let the State meet these standards.

Who this is for: Central and State government departments, Public sector undertakings and local authorities, GovTech vendors and system integrators, Welfare scheme implementation agencies, Digital public infrastructure teams

What does DPDP Rule 5 require of government?

Section 7(b) of the DPDP Act lets the State and any of its instrumentalities process personal data without consent to provide or issue a subsidy, benefit, service, certificate, licence or permit to a Data Principal, in specified circumstances. That is a significant power, so the Act lets the Rules attach conditions to it.

Rule 5(1) supplies those conditions in one sentence: processing under this rule "shall be done following the standards specified in Second Schedule".

So Rule 5 does not create a new power. It puts guard rails on an existing legitimate use. In practice:

  • Who: the State (as defined in the Act) and its instrumentalities, such as ministries, departments, local authorities and public bodies.
  • What: subsidies, benefits, services, certificates, licences and permits, "by whatever name called".
  • How: following eight Second Schedule standards, covering lawfulness, purpose limitation, minimisation, accuracy, retention, security, intimation to the individual and accountability.
  • When: from 13 May 2027, together with most other operational rules.

The same Second Schedule also governs processing for research, archiving or statistical purposes under Rule 16. That is a useful parallel: one set of public-interest standards for two different exemptions. See the research exemption.

Under law, under policy, or using public funds

Rule 5(2) explains what it means for a subsidy, benefit, service, certificate, licence or permit to be provided or issued on each of three bases.

BasisRuleMeaning
Under law5(2)(a)Provision or issue in exercise of a power or performance of a function by the State or its instrumentalities under any law in force
Under policy5(2)(b)Provision or issue under any policy or instruction of the Central or a State Government in exercise of its executive power
Using public funds5(2)(c)Provision or issue by incurring expenditure from, or with receipts accruing to, the Consolidated Fund or public account of India or a State, or the funds of a local or other authority

Why this matters:

  • Executive schemes are covered. A scheme launched by government order, without a dedicated statute, still falls within Rule 5 through clause (b).
  • Funding is a test in itself. Clause (c) brings in programmes financed from public money even where the delivery mechanism is administrative.
  • Local bodies count. Clause (c)(ii) explicitly includes local and other authorities within India or under government control, using their own funds.

For any scheme, document which basis applies. That record is the starting point for showing that the section 7(b) legitimate use, and therefore Rule 5, is the right ground rather than consent.

The eight Second Schedule standards

The Second Schedule requires appropriate technical and organisational measures to ensure effective observance of eight standards, in accordance with applicable law.

ClauseStandard
(a)Processing is carried out in a lawful manner
(b)Processing is for the uses in section 7(b) (or the purposes in section 17(2)(b) for research)
(c)Processing is limited to personal data necessary for those uses
(d)Reasonable efforts to ensure completeness, accuracy and consistency
(e)Data retained only until required for the use, or for compliance with law
(f)Reasonable security safeguards to prevent breach, including processing by Data Processors
(g)For section 7(b) processing, intimation to the Data Principal with a contact person, a link and description of means to exercise rights, and consistency with other applicable standards
(h)Accountability of whoever determines purpose and means

The standards mirror private-sector duties. Clause (c) is data minimisation. Clause (d) parallels section 8(3) accuracy. Clause (e) parallels section 8(7) erasure. Clause (f) parallels Rule 6. Clause (g) parallels Rules 3 and 9.

The key difference is that there is no consent to withdraw. The intimation in clause (g) informs rather than asks, and the Data Principal's remedy is to exercise her rights or complain, not to switch processing off.

Clause (g): what the citizen must be told

Clause (g) is the most operational standard. Where processing is under section 7(b), it must be undertaken while giving the Data Principal an intimation and:

  1. (g)(i) giving the business contact information of a person who can answer, on behalf of the Data Fiduciary, her questions about the processing of her personal data;
  2. (g)(ii) specifying the particular communication link to the fiduciary's website or app, or both, and describing any other means by which she may exercise her rights under the Act; and
  3. (g)(iii) processing in a manner consistent with other standards that apply under Central Government policy or any law.

Delivery options for a scheme portal or app:

  • An intimation screen at application or enrolment, before data is processed.
  • The same content on acknowledgement slips, SMS confirmations and printed forms for assisted channels such as common service centres.
  • A permanent page on the department's portal with the contact person and rights request route.

The Rule does not require the intimation to be itemised in the way Rule 3 requires for consent notices. Still, telling citizens what data is used and why is good practice and helps meet the lawfulness and accountability standards. Keep the contact in clause (g)(i) staffed: it is the first place grievances will arrive.

What private vendors running government systems must do

Much government processing runs on systems built and operated by private companies. Under the Act, the government body is the Data Fiduciary and the vendor is usually a Data Processor. Clause (f) of the Second Schedule extends security safeguards to "processing undertaken by it or on its behalf by a Data Processor", and clause (h) places accountability on whoever determines purpose and means.

For a GovTech vendor, that translates into concrete deliverables:

  • Contract clauses covering security safeguards, retention limits under clause (e), breach notification to the department, and return or deletion at contract end.
  • Field-level minimisation. Collect only fields the scheme actually needs, as clause (c) requires. Push back on "collect everything in case" requirements.
  • Data quality controls. Validation, deduplication and correction workflows that support clause (d).
  • Retention configuration. Scheme-specific retention schedules, with deletion jobs, rather than indefinite storage.
  • Audit evidence. Access logs, change logs and security reports the department can use to show accountability.

Note that Rule 6 security safeguards and Rule 8(3) one-year log retention apply to all Data Fiduciaries, including government bodies, alongside Rule 5. See reasonable security safeguards and the DPA clauses template.

Children's data and interplay with other rules

Benefits often go to or through children: scholarships, nutrition schemes, health programmes. Item 2 of Part B of the Fourth Schedule exempts processing for providing or issuing any subsidy, benefit, service, certificate, licence or permit under law, policy or public funds, in the interests of a child, under section 7(b), from section 9(1) (verifiable parental consent) and section 9(3) (tracking, behavioural monitoring and targeted advertising). The condition is that processing is restricted to the extent necessary for that provision or issuance.

Section 9(2), the prohibition on processing likely to cause a detrimental effect on a child's well-being, is not exempted.

Other interplay to track:

  • Rule 23 and the Seventh Schedule let authorised persons call for information from fiduciaries for State functions under law. That is a separate route from section 7(b) processing.
  • Section 17(2)(a) of the Act allows the Government to exempt notified State instrumentalities from provisions of the Act. Rule 5 applies where no such exemption has been notified.
  • Rule 7 breach intimation applies to government fiduciaries like any other.

See children's data exemptions and section 7 legitimate uses.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Identify the Rule 5(2) basis for each scheme

    Record whether each subsidy, benefit or licence is provided under law, under policy, or using public funds.

    Rule 5(2)

  2. Minimise fields collected

    Limit data to what is necessary for the scheme's use and remove optional fields that serve no scheme purpose.

    Second Schedule (c)

  3. Set scheme-specific retention

    Define how long data is needed for the use or by law and automate deletion after that.

    Second Schedule (e)

  4. Publish the intimation and contact

    Tell citizens about processing, give a contact person and a link to exercise rights.

    Second Schedule (g)

  5. Put security clauses in vendor contracts

    Require processors to apply reasonable security safeguards and report breaches.

    Second Schedule (f)

  6. Assign accountability

    Name the officer or body that determines purpose and means and owns compliance with the standards.

    Second Schedule (h)

Key dates

  1. Rule 5 and the Second Schedule apply to State processing under section 7(b)

Answers

Frequently asked questions

Can the government process my personal data without consent under DPDP?

Yes, in specified cases. Section 7(b) of the DPDP Act allows the State and its instrumentalities to process personal data without consent to provide or issue subsidies, benefits, services, certificates, licences or permits. From 13 May 2027, Rule 5 requires that processing to follow the Second Schedule standards.

What are the Second Schedule standards in the DPDP Rules?

Eight standards: lawful processing; processing only for the specified uses; data minimisation; reasonable accuracy and completeness; retention only as long as required or by law; reasonable security safeguards; intimation to the Data Principal with a contact person and rights link; and accountability of the person determining purpose and means.

Does Rule 5 apply to schemes created by government order?

Yes. Rule 5(2)(b) covers subsidies, benefits and similar provisions issued under any policy or instruction of the Central or a State Government in exercise of executive power. Rule 5(2)(c) also covers provision using public funds.

Will citizens be told when government uses their data under Rule 5?

Yes. Clause (g) of the Second Schedule requires an intimation to the Data Principal, with the business contact of a person who can answer questions about the processing and a link and other means to exercise her rights under the Act.

Do private companies have obligations under DPDP Rule 5?

Indirectly. Vendors that run government systems usually act as Data Processors. The Second Schedule requires security safeguards for processing done on the fiduciary's behalf, so departments will need contracts requiring vendors to support minimisation, retention limits, security and accountability.

When does DPDP Rule 5 come into force?

Rule 5 comes into force on 13 May 2027, eighteen months after the DPDP Rules were published on 13 November 2025, under Rule 1(4). Departments and their vendors should use the time before then to map schemes to a Rule 5(2) basis, minimise fields, set retention schedules and publish intimations with a contact person.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 5 (official text)
  • Digital Personal Data Protection Rules, 2025 — Second Schedule (official text)
  • Digital Personal Data Protection Act, 2023 — Section 7(b) (official text)
  • Digital Personal Data Protection Rules, 2025 — Fourth Schedule, Part B, item 2 (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.