Rule 16 — DPDP Rules, 2025
Processing of personal data for research, archiving or statistical purposes shall be exempt from the provisions of this Act to the extent that the processing complies with the standards specified in the Second Schedule. Second Schedule standards include: (a) personal data shall not be used for any purpose other than research, archiving or statistical purposes; (b) personal data shall be de-identified to the extent reasonably practicable; (c) research results shall not be published in a form that identifies any Data Principal; (d) appropriate security safeguards shall be in place; (e) personal data shall not be transferred outside India except in accordance with the provisions of this Act.
Source: Digital Personal Data Protection Rules, 2025. Official text available at truconsent.io/resources/dpdp-rules.pdf.
Rule 16 and the Second Schedule set the conditions for the research exemption. Calling an activity 'research' is not sufficient — the processing must meet all Second Schedule standards simultaneously. The most important constraints are that research data cannot be re-used for commercial purposes, results cannot identify individuals, and de-identification must be applied to the maximum extent practicable. Academic research, public health studies, and government statistical surveys that genuinely meet these standards can benefit from the exemption.
A university public health department processes de-identified patient records from partner hospitals to study disease prevalence patterns. Results are published in aggregate, no individual is identified, data is not used commercially, and it is deleted after the study concludes. This meets the Second Schedule standards.
An e-commerce company's 'research team' analyses purchase data to optimise product recommendations. This is commercial product development — it uses personal data for a commercial purpose and the results benefit the company commercially. The research exemption does not apply.
One Licence, No Middlemen: Why India Does Not Need CMPs Beside Consent Managers
The industry has settled on a neat split: the Consent Manager serves the Data Principal, and a CMP serves the Data Fiduciary. I think it is wrong. India built one consent intermediary on purpose. Here is why the unlicensed CMP layer adds risk without adding value.
19 Oct 2026
What DPDPA Rule 6 Actually Requires in Every Data Processor Contract
Rule 6's security safeguards obligation doesn't stop at your organisation's boundary, it flows downstream to every vendor who touches personal data on your behalf. Most processor contracts in use today don't reflect this, and the liability gap lands squarely with the Data Fiduciary.
11 Jul 2026
Outsourcing Data Processing Doesn't Outsource Liability Under DPDPA
Under India's DPDPA, engaging a KYC provider, cloud vendor, or email platform doesn't transfer your legal accountability, it multiplies it. Here's what Data Fiduciaries must contractually lock down before handing personal data to any processor.
11 Jul 2026