DPDP Act and IP management software: what a university must check about inventor data
The DPDP Act for universities: what an IPR cell must check before inventor data goes into IP management software, with section and rule numbers and key dates.
Under the Digital Personal Data Protection Act, 2023, a university deciding how inventor data is used is the Data Fiduciary, and its IP management software vendor is usually a Data Processor. Section 8(1) keeps the university responsible for the vendor's processing. Most duties, including notice, security safeguards and breach intimation, apply from about 13 May 2027.
An IPR cell holds more personal data than it tends to admit. Every invention disclosure carries inventors' names, addresses and nationality, which a patent application on Form 1 asks for. Add phone numbers, contribution percentages, royalty shares, bank details for revenue payouts, student enrolment numbers and years of email. When that record moves from a spreadsheet into IP management software, the Digital Personal Data Protection Act, 2023 decides who answers for it.
This checklist covers what a university should verify, with section and rule numbers, before it signs a software contract or migrates its records. It is practical guidance, not legal advice; your legal office should read the Act and Rules against your own facts.
Who is the Data Fiduciary and who is the Data Processor?
Section 2(i) defines a Data Fiduciary as the person who, alone or with others, decides the purpose and means of processing. Section 2(k) defines a Data Processor as anyone who processes personal data on a fiduciary's behalf. In a typical setup the university is the fiduciary and the software vendor is the processor.
That split has one consequence that matters more than any other. Section 8(1) says the fiduciary remains responsible for complying with the Act, including for processing done by its processor, whatever any agreement says. Section 8(2) allows a fiduciary to engage a processor only under a valid contract. You cannot contract the liability away, so you have to contract for the controls.
When do the obligations start?
MeitY published three notifications on 13 November 2025. The commencement notification, G.S.R. 843(E), brings the Act in over eighteen months. The DPDP Rules, 2025, G.S.R. 846(E), follow the same phases.
| Phase | Date | What applies |
|---|---|---|
| On publication | 13 November 2025 | Definitions (section 2), the Data Protection Board (sections 18 to 26), Rules 1, 2 and 17 to 21 |
| One year later | About 13 November 2026 | Consent Managers: section 6(9) and Rule 4 |
| Eighteen months later | About 13 May 2027 | Sections 3 to 17 (except 6(9)), penalties, and Rules 3, 5 to 16, 22 and 23 |
So the core duties of a fiduciary, from notice to breach intimation, apply from about 13 May 2027 under the notification as published. MeitY consulted in early 2026 on shortening that window, so check the Gazette for any amendment before you plan around the date. I would not wait for it either way. Software contracts signed today will still be running then, and migrating a disclosure archive takes months.
DPDP Act commencement, as notified on 13 November 2025
What lawful basis covers inventor data?
Section 4 allows processing only for a lawful purpose, either with consent or for a "certain legitimate use" under section 7. Two legitimate uses fit an IPR cell. Section 7(a) covers data a person voluntarily provides for a specified purpose, unless they have said they do not consent. Section 7(i) covers processing for the purposes of employment.
Faculty and staff inventors are employees, and their invention disclosures arise from their employment, so section 7(i) and 7(a) will often cover them. Students are not employees. For student inventors and external co-inventors, a clear notice and consent at the disclosure stage is the safer route. If you rely on consent, section 6(10) puts the burden of proving that notice was given and consent obtained on the fiduciary, so the record of consent must sit in the system with the disclosure.
Students under 18 are rare in invention disclosures but not unheard of. Section 9 requires verifiable parental consent for a child's data. The Fourth Schedule exemption for educational institutions is narrow, written for tracking and behavioural monitoring for educational activities or the safety of enrolled children, and I would not stretch it to IP records.
What must the notice say?
Rule 3 sets the contents. The notice must stand on its own and give an itemised description of the personal data, the specified purpose, a description of what the processing enables, and a link or other means to withdraw consent, exercise rights under the Act and complain to the Board. Withdrawal must be about as easy as giving consent, which section 6(4) also requires.
For an IPR cell, the purposes are usually: assessing and protecting the invention, filing and prosecuting patent applications, licensing, and distributing revenue under the IP policy. Say each one. Inventors' names and addresses also become public when a patent application is published, so tell inventors that in the notice.
The vendor checklist
Use this table when you assess IP management software, or when you renew an existing contract. Each row ties a question to its source.
| Check | Source | What to ask the vendor |
|---|---|---|
| Valid processor contract | Section 8(2), Rule 6 | Will you sign a data processing agreement naming the safeguards in Rule 6? |
| Encryption or masking | Rule 6 | Is inventor data encrypted, masked or tokenised at rest and in transit? |
| Access control | Rule 6 | Can access be limited by role, so a reviewer sees only what they need? |
| Logs and monitoring | Rule 6 | Are access logs kept, monitored and retained for at least one year? |
| Backups and continuity | Rule 6 | How is data restored if availability or integrity is compromised? |
| Breach notice to the university | Section 8(6), Rule 7 | How fast will you tell us of a breach, and with what details? |
| Erasure on instruction | Section 8(7), Rule 8 | Can you erase one person's data and certify it, without breaking the patent record? |
| Data location | Section 16, Rule 15 | Where is the data stored and backed up, and who are your sub-processors? |
| Exit | Section 8(7) | In what format do we get our data back, and when is your copy deleted? |
A vendor that cannot answer these in writing has told you something useful.
From disclosure form to a compliant IP record
Breach intimation: what the law requires
Section 8(6) requires the fiduciary to inform the Board and each affected Data Principal of a personal data breach. Rule 7 says affected people must be told without delay, in plain language, covering the nature, extent and timing of the breach, likely consequences, mitigation steps and a contact person. Rule 7 also sets a fuller report to the Board within a fixed number of hours; read the window in the Gazette text of Rule 7 and write it into your incident plan. Your vendor's notice period to you has to be shorter than yours to the Board, or the arithmetic does not work.
Note the definition in section 2(u): a breach includes accidental disclosure and loss of availability, not only theft. A misdirected email with a disclosure attached counts.
Retention, erasure and rights
Section 8(7) requires erasure once consent is withdrawn or the purpose is no longer served, unless retention is necessary to comply with a law. Rule 8(3) requires processing logs to be kept for at least one year. Patent records outlive most purposes: an application can run for 20 years and a licence for longer. Write down why you keep each category of inventor data and for how long, and tie it to the patent and licence lifecycle.
Inventors also have rights: a summary of their data and who it was shared with (section 11), correction and erasure (section 12), and grievance redressal (section 13). Rule 14 requires grievances to be resolved within a period not exceeding 90 days, and section 8(9) requires you to publish a contact for data queries.
What the penalties look like
The Schedule to the Act sets maximum penalties, imposed by the Board after an inquiry.
| Breach | Maximum penalty |
|---|---|
| Reasonable security safeguards not taken, section 8(5) | ₹250 crore |
| Board and affected people not notified, section 8(6) | ₹200 crore |
| Obligations on children's data, section 9 | ₹200 crore |
| Any other breach by a fiduciary | ₹50 crore |
These are ceilings. The realistic risk for a university is a complaint from one inventor, a Board inquiry and the time it consumes.
The checklist, in order
- Map what inventor data you hold, where, and who can see it.
- Decide the lawful basis for each group: employees, students, external co-inventors.
- Rewrite the disclosure form notice against Rule 3.
- Put a processor contract in place that names the Rule 6 safeguards and a breach notice period.
- Confirm data location and sub-processors.
- Set retention periods tied to the patent and licence lifecycle.
- Publish a data contact and a grievance route with a 90-day ceiling.
- Update the university IP policy so it refers to all of this.
If you are still moving off spreadsheets, from spreadsheet to IPMS covers the migration itself, and IP management software for universities covers what to look for beyond data protection.
Zernyx IPMS is an IP lifecycle management platform for universities and research institutions, to manage patents, filings and IP portfolios end to end. Put the questions in the table above to any vendor you assess, including us.
Common questions
When does the DPDP Act apply to universities?
MeitY notified the commencement on 13 November 2025 (G.S.R. 843(E)). Definitions and the Data Protection Board took effect that day. Most obligations of a Data Fiduciary, including sections 4 to 8 and the rights in sections 11 to 14, take effect eighteen months later, around 13 May 2027.
Is a university IPR cell a Data Fiduciary?
The university is, because it decides why and how inventor data is processed. Section 2(i) defines a Data Fiduciary that way. The IPR cell is the part of the university doing the processing, and a software vendor that processes the data on the university's behalf is a Data Processor under section 2(k).
Does the university need consent to store inventor details?
Not always. Section 4 allows processing with consent or for a legitimate use under section 7. Section 7(a) covers data a person voluntarily provides for a specified purpose, and section 7(i) covers employment purposes. Students are not employees, so many universities will rely on a clear notice and consent for student inventors.
What is the penalty for weak security safeguards under the DPDP Act?
The Schedule to the Act allows a penalty of up to ₹250 crore for failing to take reasonable security safeguards under section 8(5), and up to ₹200 crore for failing to notify the Board and affected people of a breach under section 8(6).