An edtech vendor meets FERPA through the school official exception, the studies exception or a de-identified release.
This page reads the rules as of 2026-11-17 for student records in AI training data licensing, with the Protection of Pupil Rights Amendment (PPRA) and California's K-12 student law.
Five FERPA Routes for a Student Records Deal at a Glance
Beside written consent, FERPA gives five routes by which student records or data derived from them reach an outside party, and each carries its own purpose limit. The table compares consent plus the five routes without it, as of 2026-11-17.
| Route | Citation | What the text lets the recipient do | What the text requires | Source |
|---|---|---|---|---|
| Written consent (default) | 34 CFR 99.30 | receive the identified records for the stated purpose | signed and dated; names records, purpose and party or class | ecfr.gov |
| School official (outsourced service) | 34 CFR 99.31(a)(1)(i)(B); 99.33(a) | use records for the school's institutional service | service the school would use employees for; direct control; use only for the disclosed purposes; Department guidance: no sharing or selling | ecfr.gov; studentprivacy.ed.gov |
| Studies for the school | 34 CFR 99.31(a)(6); 20 U.S.C. 1232g(b)(1)(F) | study to develop or validate predictive tests, administer student aid or improve instruction | written agreement; no personal identification outside the organization; destruction | ecfr.gov; govinfo.gov |
| Directory information | 34 CFR 99.3, 99.37 | receive designated directory items | public notice and opt-out; school may limit parties or purposes | ecfr.gov |
| De-identified release | 34 CFR 99.31(b)(1) | receive records after all personally identifiable information is removed | reasonable determination of non-identifiability across releases | ecfr.gov |
| Coded de-identified data | 34 CFR 99.31(b)(2) | receive record-coded student-level data for education research | code used for no other purpose; not based on a Social Security number or personal information | ecfr.gov |
The sections below follow the table order.
Which Records and Institutions FERPA Covers
FERPA applies to an educational agency or institution that receives funds under a program the Secretary of Education administers (34 CFR 99.1(a)), and it protects "education records": records directly related to a student and maintained by the agency or institution or a party acting for it (34 CFR 99.3).
Non-monetary benefits to students alone do not bring an institution in (99.1(b)). Three points matter for a data holder:
- Employee records kept exclusively as employee records are excluded, but records of a person employed because of student status are education records (34 CFR 99.3).
- Personally identifiable information (PII) includes name, address, student number, indirect identifiers such as date and place of birth, and information "linked or linkable" that lets a reasonable person in the school community, without personal knowledge of the circumstances, identify the student with reasonable certainty (34 CFR 99.3).
- A biometric record is a record of measurable biological or behavioral characteristics usable for automated recognition, such as fingerprints, voiceprints, facial characteristics and handwriting, and it counts as a personal identifier (34 CFR 99.3).
Rights pass to an "eligible student" at 18 or on attending a postsecondary institution (34 CFR 99.3). Voice, face and handwriting data from students enter the PII definition directly, which the page on biometric data in AI training compared across laws sets beside other regimes.
Written Consent as the Default Route
Absent an exception, a school may disclose personally identifiable information from education records only with a signed and dated written consent from the parent or eligible student (34 CFR 99.30(a), as of 2026-11-17).
The consent must specify the records to be disclosed, state the purpose and identify the party or class of parties receiving them (99.30(b)).
The text sets no blanket consent for later or unstated uses, and each consent is tied to a stated purpose and a named party or class. The steps a seller takes before any such license are on the page about consent and confidentiality clauses before licensing data.
The School Official Exception and Edtech Vendors
A school may disclose records without consent to a contractor to which it has outsourced an institutional service, treating that party as a school official, only if the party meets three conditions (34 CFR 99.31(a)(1)(i)(B), as of 2026-11-17). The conditions are:
- the party performs a service for which the school would otherwise use employees;
- the party is under the school's direct control for the use and maintenance of the records;
- the party is subject to 34 CFR 99.33(a), the use and redisclosure limits.
Under 34 CFR 99.33(a)(2) the recipient may use the information "only for the purposes for which the disclosure was made", and 99.33(a)(1) bars disclosure to another party without consent.
The Department's Privacy Technical Assistance Center (PTAC), in guidance of February 2014, says a provider under this exception "may not share (or sell)" FERPA-protected information or re-use it for other purposes except as the school directs and FERPA permits.
The same document says properly de-identified information is "not protected by FERPA", and that a provider can use de-identified metadata to develop new products "unless the district's agreement with the provider precludes this use".
The school's contract therefore decides what a vendor may do with de-identified usage data, and the PTAC text predates generative AI and says nothing about training. The page on field of use and scope limits in AI data licenses covers purpose limits.
The Studies Exception and Model Training
A school may disclose records to an organization conducting studies for or on behalf of the school only to develop, validate or administer predictive tests, administer student aid programs, or improve instruction (34 CFR 99.31(a)(6)(i); 20 U.S.C. 1232g(b)(1)(F), as of 2026-11-17). Three requirements follow in 99.31(a)(6)(iii):
- no personal identification of students by anyone other than the organization's representatives;
- destruction of the information when no longer needed;
- a written agreement stating purpose, scope, duration and information, limiting use to the stated purposes.
The three purposes do not name training a general model. No Department reading on AI training under this exception was found on studentprivacy.ed.gov as of 2026-11-17, and this page concludes nothing for a developer.
Directory Information as a Limited Route
FERPA lets a school disclose "directory information", information that would not generally be considered harmful or an invasion of privacy if disclosed, after public notice and an opportunity to opt out (34 CFR 99.3, 99.37(a), as of 2026-11-17). Examples in 99.3 include name, address, email address, photograph, dates of attendance and degrees.
The notice may limit the parties or purposes for which directory information is released (99.37(d)). The redisclosure limit of 99.33(a) does not apply to directory disclosures (99.33(c)). FERPA alone therefore sets the notice and the school's own limits, and state law may be narrower.
De-identified Release Under 34 CFR 99.31(b)
A school, or "a party that has received education records or information from education records under this part", may release them without consent after removing all personally identifiable information, provided it "has made a reasonable determination that a student's identity is not personally identifiable, whether through single or multiple releases, and taking into account other reasonably available information" (34 CFR 99.31(b)(1), as of 2026-11-17).
The determination looks beyond the file itself, because the PII definition turns on what a reasonable person in the school community could infer, and voice, face and handwriting data are biometric records.
The coded route in 99.31(b)(2) serves education research only, and the code cannot rest on a Social Security number or other personal information. A coded set is therefore not a general training license, which is a reading of the text, not a Department statement.
Technique is covered on the page about PII removal and de-identification before licensing data. A contract can still bar a vendor's use of de-identified data, as the PTAC text notes.
PPRA and California's K-12 Student Law Beside FERPA
FERPA is not the only student privacy rule: PPRA, 20 U.S.C. 1232h(c)(1)(E), requires a local educational agency that receives federal funds to adopt policies on collecting, disclosing or using student personal information for marketing or for selling it, with an exception for the exclusive purpose of developing, evaluating or providing educational products or services (1232h(c)(4)(A), as of 2026-11-17).
California's Business and Professions Code 22584 bars an operator of a site, service or app used primarily for K-12 school purposes from selling a pupil's information, including covered information (22584(b)(3)). The section also bars targeted advertising, requires deletion on a school's request and excludes general audience services.
Carve-outs in subdivisions (c), (f) and (g) allow use to improve the operator's own educational products and use of deidentified or aggregated deidentified information, and none names training a general model.
The amended text took effect on January 1, 2025 (AB 801) and was read from an archive capture dated 2026-01-08; other states' student laws were not read. The California student data law beside the CCPA page covers the state's general privacy layer.
How the Department of Education Enforces FERPA
FERPA is enforced through federal funding, not a statutory fine: the Secretary may withhold payments, issue a complaint to compel compliance by cease and desist order or terminate eligibility, and may terminate assistance only if voluntary compliance fails (20 U.S.C. 1232g(f); 34 CFR 99.67(a)). The table lists the provisions, as of 2026-11-17.
| Provision | Who acts | What the text provides | Source |
|---|---|---|---|
| 20 U.S.C. 1232g(f) | Secretary of Education | appropriate enforcement; terminate assistance only if compliance cannot be secured by voluntary means | govinfo.gov |
| 34 CFR 99.67(a) | Secretary | withhold payments, issue a complaint to compel compliance by cease and desist order, or terminate eligibility | ecfr.gov |
| 34 CFR 99.67(c), (e) | the school of origin | may not allow a third party found to have violated 99.31(a)(6)(iii)(B), or to have improperly redisclosed in violation of 99.33, access to PII for at least five years | ecfr.gov |
| 34 CFR 99.60, 99.64 | the Department's designated office | investigates a timely complaint from a parent or eligible student, or acts on its own initiative | ecfr.gov |
The sections read name no penalty amount, and a third party's exposure runs through the school's five-year access bar. Case law was not checked.
Benefits, Risks, Downsides and Alternatives for a School or Edtech Seller, Including Not Licensing
FERPA leaves a school or edtech company a few lawful routes to move student-derived data to an AI developer, and each trades reach for conditions, so licensing only de-identified data, a research arrangement or no licensing at all are valid choices.
Benefits
- De-identified release needs no consent once the 99.31(b)(1) determination is made.
- Coded data can serve education research under 99.31(b)(2).
- California's carve-outs allow use to improve the operator's own educational products.
- A consent route exists for identified records.
Risks
- School official data cannot be reused or sold outside the school's purposes.
- A studies agreement requires destruction.
- Improper redisclosure costs a third party access for five years.
- Re-identification across releases undermines a de-identification claim.
Downsides
- Consent is needed per student or parent and names a purpose and a party.
- The determination must account for other reasonably available information.
- A school's contract may bar even de-identified use.
- A state layer, such as California's, sits on top of FERPA.
Alternatives
- Licensing de-identified or aggregated data only.
- A research agreement under the studies exception.
- Licensing content that holds no student records.
- Waiting for a Department reading, without assuming its result.
- Not licensing at all, as the page on alternatives to selling data to AI labs sets out.
Beyond FERPA: Children's Data, Universities, Education Content and the Seller Process
FERPA is one federal layer, and the seller pages turn these rules into steps. The United States AI training data law page sets it beside the other sector statutes.
- AI training data law outside the US: copyright, privacy, employee and contract rules by jurisdiction.
- COPPA and children's data in AI training: separate parental consent for children under 13.
- Universities and research groups licensing data to AI companies: the university as licensor.
- Anonymization vs pseudonymization for AI training data: what anonymized records achieve legally.
- What company data cannot be licensed for AI training: data barred by law.
- Privacy law and AI training data compared: student privacy beside other privacy laws.
- Should you sell or license your data to AI companies: the decision before any records deal.
- Sell or license company data to AI companies: the steps of a sale.
- Education companies licensing content to AI: edtech and school content.
- Course and education content as AI training data: course content as a data type.
How This Page Is Sourced and Dated
Every rule here cites a section of 20 U.S.C. 1232g or 1232h, 34 CFR Part 99, a Department of Education document or a California code section, with the date it was read. The method for sourcing and dating each figure is public. This page is general information, not legal advice for any specific deal.
Frequently Asked Questions
Can a school sell student records to an AI company?
Not without written consent from the parent or eligible student unless an exception in 34 CFR 99.31 applies, and none names licensing records to a developer.
Can an edtech vendor train AI on student data?
Under the school official exception a vendor may use records only for the purposes the school disclosed them for, and Department guidance says it may not share or sell them. The guidance dates from February 2014.
Does FERPA apply to employees?
Records kept exclusively about a person as an employee are not education records, but records of a person employed because of student status are. The rule is in 34 CFR 99.3.
Does FERPA apply to private schools?
FERPA covers an agency or institution that receives funds under a Department program, and non-monetary benefits to students alone do not bring it in. The rule is in 34 CFR 99.1(a) and (b).