If a college club collects names, phone numbers and college IDs through a registration form, it is probably a Data Fiduciary under the DPDP Act, 2023. The Act's duties then apply. The main ones are a consent notice that says why each item is collected, use of the data only for that purpose, a way to withdraw consent, security safeguards, notice to affected people after a breach, and a way for people to ask for correction or erasure. Most of these take effect around 13 May 2027, not now [1][6][7].
Who counts as a Data Fiduciary
The PIB backgrounder defines a Data Fiduciary as an entity that decides why and how personal data is processed, alone or with others [1]. A student club that designs its own registration form and picks the questions fits that definition. No source we read covers college events directly, so this reading is ours, not a ruling.
A vendor does not take the duty away. The Act says a fiduciary remains responsible for its processors' handling of data, even if an agreement says otherwise [2]. If the club uses a ticketing or form tool, that tool's privacy terms do not shift the legal duty onto it.
Consent and purpose
Processing is lawful only on consent or on one of the Section 7 "certain legitimate uses". That list is treated as closed [3][5]. Section 7 covers data a person gives voluntarily for a specified purpose, without indicating objection. One commentary stresses that this reaches only the purpose the data was given for, "and no more" [3][5].
So a registration for a Saturday workshop does not license adding that person to a sponsor mailer or a list for future fests. Those uses would likely need fresh consent. Each fiduciary must issue a separate, clear consent notice stating the specific purpose of collection [1]. The notice must stand alone, use plain language and list the personal data collected [6][7]. Withdrawing consent must be as easy as giving it [5].
| Duty | What it means for a club | Source |
|---|---|---|
| Consent notice | Separate, plain-language, names the purpose | [1][6] |
| Purpose limit | Use registration data only for the stated purpose | [3][5] |
| Withdrawal | As easy as giving consent | [5] |
| Breach notice to people | Without delay, in plain language | [1] |
| Breach report to the Board | Within 72 hours, unless the Board permits longer | [8] |
| Rights requests | Answer access, correction or erasure within a maximum of 90 days | [1][9] |
| Contact point | Publish a contact for data queries | [1] |
Students under 18 and the parental consent conflict
A "child" is anyone who has not completed 18 years [3]. Most college students are adults. First-years or students from school-linked programmes may not be. Section 9 requires verifiable parental or guardian consent before processing a child's data. It also bars tracking, behavioural monitoring and targeted advertising aimed at children [4].
The sources disagree on education. The PIB backgrounder says child-data consent is needed "unless the processing relates to essential services such as healthcare, education or real-time safety" [1]. Other commentary treats parental consent as absolute, with no education carve-out [4]. We could not verify the exception in the statutory text we read. Until this is settled, get guardian consent through the form for any event open to minors. Do not rely on an education exception.
Breaches and rights requests
If personal data is breached, the fiduciary must tell affected people without delay, in plain language. The message should cover what happened, the likely impact, the steps taken and a contact for help [1]. A detailed report to the Data Protection Board is due within 72 hours, or longer if the Board permits [8].
Requests for access, correction, update or erasure must be answered within a maximum of 90 days [1][9]. The practical first step is to know where registration data sits and who can export or delete it. Write down which accounts hold the data.
Crew access and handover
The Act does not say how volunteers should be given access. The purpose limit still points one way: give people only the data they need. Check-in crew need a scan view, not the full list of registrations with phone numbers and uploaded files. Our guide on checking in 2,000 people without long queues explains how to split gates and move problem cases into a separate lane, which also limits how many people see personal details.
When one team hands over to the next, the logins and records should move in a planned order. They should not stay in one officer's personal account. Our post on handing over a college club to the next team covers how to move every account out of personal names.
Reminders need care too. Do not send confirmations to people who have not agreed to that channel, and tie each reminder to the purpose in the notice. The post on reducing no-shows at a free college event describes two-channel reminders, which should go only to people who signed up for them.
Key dates and penalties
The Rules were notified on 13 November 2025, although PIB and some law-firm notes give 14 November [1][6]. Consent Manager provisions and Rule 4 take effect after 12 months, around November 2026. Notice, consent, security, breach and rights duties take effect after 18 months, around 13 May 2027 [6][7]. One compliance guide lists 6, 12, 18 and 24-month phases that do not match these dates, so we would not rely on its schedule [7].
Penalties are large in the Act's text. They reach Rs 250 crore for failing reasonable security safeguards, Rs 200 crore each for failing to notify breaches and for child-related violations, and Rs 50 crore for other violations [1]. These are maxima for large fiduciaries. A student body is more likely to face complaints than the top penalty bands.
Significant Data Fiduciary status brings impact assessments and independent audits. Sources disagree on whether a numerical threshold exists. One gives 10 million data principals, another says the Act sets none [10]. A student club is very unlikely to be notified [10].
Our view
Our view: for a college club, the most useful step is to hold less data. Ask only for what the event needs, make the purpose clear on the form, and delete registrations after the event unless someone has agreed to be contacted again. Keep a written list of who can see what. This costs little and covers most of the duties above, whatever the final reading of the child rules turns out to be.
What we could not verify
We did not open the official MeitY copies of the Act and the Rules. The links are listed, but we could not check their wording. The details above rest on secondary sources and the PIB backgrounder [1]. The education exception for child data is unresolved in our reading, and the notification date differs by a day between sources. This post explains the law. It is not legal advice. For a specific event involving minors or sponsor data, check with your college office or a lawyer.
FAQ
Does the DPDP Act apply to a student club that runs free events?
It likely does if the club collects personal data such as names, phone numbers or IDs, because the club decides why and how that data is used [1]. Free events are not exempt under the sources we read.
When do the main duties start?
Notice, consent, security, breach and rights duties take effect after 18 months from the Rules' notification, around 13 May 2027 [6][7].
Can we reuse registration data for sponsor mailers?
Not without fresh consent. Section 7 covers only the purpose the data was given for, so reuse for sponsor mailers would likely fall outside it [3][5].
Do we need parental consent for first-year participants?
If a participant is under 18, the sources say verifiable parental consent is needed [4]. The PIB backgrounder mentions an education exception, but we could not verify it in the statutory text [1].
What happens if registration data is leaked?
Affected people must be told without delay in plain language. A detailed report is due to the Board within 72 hours, unless it permits longer [1][8].
Sources
- DPDP Rules, 2025 Notified: https://static.pib.gov.in/WriteReadData/specificdocs/documents/2025/nov/doc20251117695301.pdf
- DATA FIDUCIARY OBLIGATIONS in The Digital Personal Data Protection Act, 2023. DPPA AND INTERPRETATION 8: https://www.dpdpa.com/dpdpa2023/chapter-2/section8.html
- DPDP Act 2023 Full Text, Interactive Reference: https://cadp.in/resources/official-texts/dpdp-act-2023/
- 1 The Digital Personal Data Protection Act, 2023 (ACT NO. 22 OF 2023): https://www.progressive.in/assets/DPDP%20Act_2023.pdf
- DPDP Act Obligations for Data Fiduciaries, Notice, Consent, Security, Breach, Erasure: https://consiva.ai/dpdp/data-fiduciary-obligations
- DIGITAL PERSONAL DATA PROTECTION RULES, 2025: https://www.ilflaw.com/publications/digital-personal-data-protection-rules-2025-notified/
- DPDP Rules, 2025: Compliance Timeline for Data Fiduciaries (as at September 2026) - MirvoLegal: https://www.mirvolegal.com/insights/dpdp-rules-2025-compliance-timeline/
- Rule 7 of Digital Personal Data Protection Act, 2023 DPDP Rules 2025: https://www.dpdpa.com/dpdparules/rule7.html
- DPDP Act 2023 and DPDP Rules 2025: Compliance Guide: https://www.ey.com/en_in/insights/cybersecurity/decoding-the-digital-personal-data-protection-act-2023
- Significant Data Fiduciary (SDF) Under the DPDP Act: https://pricoris.com/blog/significant-data-fiduciary-dpdp-act/