Ed tech privacy compliance: FERPA, COPPA, GDPR and when a DPO comes in
US ed tech companies deal mainly with FERPA (student education records)[2]and the COPPA Rule (children under 13).[5] Neither creates a GDPR-style data protection officer role, although the COPPA Rule requires an operator to designate one or more employees to coordinate its information security program.[10] A DPO becomes relevant only if the GDPR applies, for example because you offer the product to schools or students in the EU, and an Article 37(1) trigger is met.[11]
This page gives an overview of the three regimes as they apply to a US ed tech company, and where a DPO fits. For the GDPR side of your own case, try the DPO self-check for EU users.
FERPA: student education records
The Family Educational Rights and Privacy Act (FERPA) protects the privacy of student education records. The US Department of Education's Student Privacy Policy Office administers it and publishes guidance for schools and vendors.[1]
The regulations are in 34 CFR Part 99. They apply to educational agencies and institutions that receive funds under programs administered by the US Department of Education (99.1).[3] Section 99.3 defines education records as records that are:
- directly related to a student; and
- maintained by an educational agency or institution or by a party acting for the agency or institution.
FERPA's rules are addressed to educational agencies and institutions. A vendor that receives education records is affected through the school. Section 99.31(a)(1)(i)(A) allows a school to disclose education records without prior consent to school officials "whom the agency or institution has determined to have legitimate educational interests". Within that exception, 99.31(a)(1)(i)(B) lets a school treat a contractor or other outside party as a "school official" if the party performs a service the school would otherwise use its own staff for, is under the school's direct control over the use and maintenance of the records, and is subject to the requirements of 99.33(a) governing the use and redisclosure of personally identifiable information from education records.[4]
COPPA: children under 13
The Children's Online Privacy Protection Rule is 16 CFR Part 312. It defines a child as "an individual under the age of 13" (312.2).[5]
Under 312.3, it is unlawful for an operator of a website or online service directed to children, or any operator with actual knowledge that it is collecting personal information from a child, to collect it in a way that violates the rule.[5] The operator must, among other things:
- give notice of its information practices (312.4);[6]
- obtain verifiable parental consent before collecting, using or disclosing a child's personal information (312.5);[7]
- let parents review the information collected, refuse further use, and direct the operator to delete the child's personal information (312.6);[8]
- not condition a child's participation in a game, the offering of a prize, or another activity on the child's disclosing more personal information than is reasonably necessary to participate in that activity (312.7);[9] and
- protect the confidentiality, security and integrity of the information (312.8(a)). At a minimum, this means a written information security program (312.8(b)), including designating one or more employees to coordinate it (312.8(b)(1)) and assessing risks at least annually (312.8(b)(2)).[10]
GDPR: EU schools, students and children
If you offer your product to schools, students or parents in the EU, or monitor their behavior there, the GDPR can apply even without an EU office (Art. 3(2)).[11] Points specific to children:
- Article 8, child's consent. Where processing is based on consent and an information society service is offered directly to a child, the processing is lawful if the child is at least 16. Below that age, consent must be given or authorized by the holder of parental responsibility. Member states may set a lower age, but not below 13. The controller must make reasonable efforts to verify that consent was given or authorized (Art. 8(2)).[11]
- Recital 38. Children merit specific protection with regard to their personal data, as they may be less aware of the risks.[11]
- Controller or processor. When a school uses your product to process its students' data on its behalf, the school is the controller and you are the processor for that data, which brings in an Article 28 contract and Article 30(2) records. The SaaS GDPR compliance guide explains those duties.
- EU representative. A US ed tech company with no EU establishment that comes under Article 3(2) usually needs an EU representative under Article 27, unless the 27(2) exemption applies.[11] See the guide to EU representatives and their cost.
When is a DPO relevant for an ed tech company?
Neither FERPA nor COPPA creates a GDPR-style DPO role. COPPA does require an operator to designate one or more employees to coordinate its information security program (312.8(b)(1)).[10] The DPO is a GDPR concept, and it applies in two different ways in education:
- The school. Public authorities and bodies must designate a DPO under Article 37(1)(a).[11] Public schools in the EU can fall into that category, so your EU public school customers may already have their own DPO. That obligation is the school's, not yours.
- The vendor. Article 37(1) applies to processors as well as controllers. An ed tech company needs its own DPO if its core activities consist of large-scale regular and systematic monitoring of people (37(1)(b)), or large-scale processing of special category or criminal offense data (37(1)(c)), or if national law requires one.[11] The EDPB-endorsed DPO guidelines explain "core activities", "large scale" and "regular and systematic monitoring", and recommend documenting the assessment.[12]
If you need a DPO, Article 37(6) allows one under a service contract. Read what DPO as a service involves and the index of published DPO prices. If you want privacy advice without designating a DPO, see DPO consultant vs. DPO.
Frequently asked questions
Does FERPA or COPPA require an ed tech company to appoint a DPO?
No. Neither FERPA nor the COPPA Rule creates a GDPR-style data protection officer role. The COPPA Rule does require an operator to designate one or more employees to coordinate its information security program (16 CFR 312.8(b)(1)). The DPO is a GDPR role, and it becomes relevant to an ed tech company only if the GDPR applies and an Article 37(1) trigger is met, or national law requires one.[10][11]
What counts as an education record under FERPA?
Under 34 CFR 99.3, education records are records that are directly related to a student and maintained by an educational agency or institution or by a party acting for the agency or institution.[2]
Who is a child under COPPA?
The COPPA Rule defines a child as an individual under the age of 13 (16 CFR 312.2).[5]
At what age can a child consent under GDPR?
For information society services offered directly to a child, Article 8 sets the age at 16 where processing is based on consent. Member states may set a lower age, but not below 13. Below that age, a holder of parental responsibility must give or authorize consent.[11]
Do EU schools need a DPO?
Public authorities and bodies must designate a DPO under Article 37(1)(a), and public schools in the EU can fall into that category. That duty sits with the school. A vendor needs its own DPO only if a trigger applies to its own processing.[11]
Next steps
- Check whether GDPR may require a DPO for your EU users.
- Read the GDPR rules for US companies.
- Compare published DPO prices.
Sources
- US Department of Education, Student Privacy Policy Office: FERPA (accessed )
- 34 CFR Part 99, Family Educational Rights and Privacy (eCFR) (accessed )
- 34 CFR 99.1, FERPA: to which educational agencies or institutions the regulations apply (eCFR) (accessed )
- 34 CFR 99.31, FERPA: when prior consent is not required to disclose information (eCFR) (accessed )
- 16 CFR Part 312, Children's Online Privacy Protection Rule (eCFR) (accessed )
- 16 CFR 312.4, COPPA Rule: Notice (eCFR) (accessed )
- 16 CFR 312.5, COPPA Rule: Parental consent (eCFR) (accessed )
- 16 CFR 312.6, COPPA Rule: Right of parent to review personal information provided by a child (eCFR) (accessed )
- 16 CFR 312.7, COPPA Rule: Prohibition against conditioning a child's participation on collection of personal information (eCFR) (accessed )
- 16 CFR 312.8, COPPA Rule: Confidentiality, security, and integrity of personal information collected from children (eCFR) (accessed )
- Regulation (EU) 2016/679 (General Data Protection Regulation), official text on EUR-Lex (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), endorsed by the EDPB (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), full text (PDF) (accessed )