Header Ideas

Students’ Right to Data Privacy– Guidance for Drafting Legislation and Policy

Student data privacy is by no means a new policy concept, nor is it a new concern. There is often strong bipartisan support for measures to strengthen privacy protections and ensure students, and their valuable information, are safe and secure. However, education technology is quickly evolving. With the expanded use of artificial intelligence (AI) and other cutting-edge technologies used in remote and hybrid learning models, the ways that students’ private information can be compromised are growing rapidly.

Neither All4Ed nor state policymakers have access to a crystal ball to see what threats to student data privacy might arise in the future, but there are measures state policymakers and advocates can adopt now to strengthen existing laws that protect student data. Adopting laws that are adaptable to emerging technologies and scenarios is critical to meeting the future uses of education technology in a way that is innovative and effective, while still protecting students.

Below, All4Ed offers drafting guidance for state policymakers, highlighting promising policies coming out of states that can be used to strengthen existing student privacy state laws and to make them more able to meet current and emerging education technologies and tools.

For an individual consultation on how these suggestions can be incorporated into your specific state, please contact our Director of State Government Relations, Jenn Ellis, jellis@all4ed.org.

States should consider modernizing their privacy policy definitions

Before adopting new requirements, lawmakers should consider improving existing statutory and regulatory definitions to ensure that student data privacy requirements reflect the current education landscape, including positioning them to address emerging education technologies like artificial intelligence. A few key definitions to evaluate for possible amendment in state law include:

“De-identified Data”. While properly de-identified data generally need not be subject to privacy protections, advances in computing power and the widespread availability of large datasets have made it increasingly difficult to ensure that data remains truly anonymous. To safeguard privacy in this evolving landscape, it is essential for states to modernize their definitions of “de-identified data” to account for the growing risk of re-identification. The below definition builds on the high bar set by federal law for de-identified data. For more information on how the federal law utilizes this term, guidance is available from the Department of Education.

Proposed language:

“De-identified Data” means records and information that have had all personally identifiable information removed or sufficiently obscured, such that the remaining information does not reasonably identify a specific individual, including, but not limited to, any information that, alone or in combination, whether through single or multiple releases, and taking into account other reasonably available information is linkable to a specific student and provided that the educational agency or institution has made a reasonable determination that a student’s identity is not personally identifiable, taking into account reasonably available information. For data to be truly de-identified, the de-identification must be irreversible.

“Disclose or Disclosure”. Clearly defining what it means to “disclose” data under a student privacy law—including which categories of student information are covered and under what circumstances—is essential to protecting student privacy while enabling the appropriate, efficient, and lawful use of data for educational purposes. If this term is currently undefined in the state law or the definition is dated, state leaders should consider adopting a definition of “disclose” or “disclosure” that reflects the ways that schools share data for legitimate educational purposes.

Such a definition should adhere closely to the one found in the Family Educational Rights and Privacy Act (FERPA) which focuses on student’s personally identifiable information as showcased in the proposed language below. Another example is found in Illinois’ definition of “breach”, which gets to the same conclusion through a different means, specifically, defining when a disclosure is illegal.

Proposed language:

“Disclose” or “Disclosure” means to permit access to or the release, transfer, or other communication of personally identifiable information contained in education records by any means, including oral, written or electronic means, to any party except the party identified as the party that provided or created the student data.

“Educational technology”. As new technologies, like AI, continue to evolve and expand in education, it is essential for states to adopt a definition of educational technology that encompasses current tools, emerging innovations, and potential future applications in learning environments. As an exemplar, New Mexico’s Digital Equity in Education Act provides an open definition of education technology designed to be flexible and grow with the field. For more information on New Mexico’s work on digital equity, see All4Ed’s interview with Representative Brian Baca.

Proposed language:

“Educational technology” means all applications of technology in the learning process, including internet connectivity, digital information, electronic devices and evidence-based software applications used to facilitate and enhance teaching and learning.

“Operator.” Technology companies deliver critical administrative, instructional, and other services to schools—services that often involve access to students’ personally identifiable information. To safeguard this data, laws and regulations must clearly limit how these companies—commonly referred to as “operators” under state law—can use and disclose it. A clear and precise definition of “operator” and the related concept of “PreK–12 school purpose” is essential to ensuring these protections are effective.

In 2019 Maryland policymakers convened a Student Data Privacy Council to study emerging technologies, exemplar policies, and best practices, and to make recommendations for strengthening the state’s Student Data Privacy Act. The Council recommended changes to the definition of “Operator” and found that the state’s definition of “PreK-12 school purposes” was already strong. Both are offered as models below.

Proposed language – Operator:

Proposed language – PreK–12 School Purpose:

“Covered Information.” Federally, FERPA creates minimum standards for protecting a student’s personally identifiable information, but states have expanded the definition of what constitutes student data to capture a broad and emerging list of information and identifiers that can put students at risk. The definition below is modeled after the language in California’s Student Online Personal Information Protection Act, but other state examples include Maryland, and Illinois’ definition for “covered information.”

Proposed language:

“Covered information” means personally identifiable information or materials, in any media or format that meets any of the following:

“Targeted Advertising”. Many states have enacted laws that prohibit companies serving schools from using student information for advertising or marketing purposes. For example, California’s Student Online Personal Information Protection Act includes a specific prohibition on targeted advertising using student information. Hawaii’s Student Personal Information Protection law also offers a definition of targeted advertising, modeled below.

Proposed language:

“Targeted advertising” means presenting advertisements to a student where the advertisement is selected based on information obtained or inferred over time related to that student’s online behavior, usage of applications, or student data. “Targeted advertising” does not include advertising to a student at an online location based upon that student’s current visit to that location, or in response to that student’s request for information or feedback, without the retention of that student’s online activities or requests over time for the purpose of targeting subsequent advertisements.

Every state should adopt and cultivate strong state privacy governance structures and practices

In addition to reviewing and considering updates to the definitions found in their student privacy policies, states should carefully review their laws and regulations to ensure they reflect robust governance structures that provide oversight, support, and the capacity to adjust and grow with technological changes.

State Chief Privacy Officer and State Student Privacy Council. Even when robust student data and privacy laws are present, states need systems designed to build state and local capacity to support proper implementation, compliance, evaluation, and improvement. To build robust governance systems, states should consider the creation or enhancement of a Chief Privacy Officer role and/or a Student Data Privacy Council.

Chief Privacy Officer positions play a valuable role in centralizing the implementation and enforcement of privacy policies, ensuring compliance with applicable laws and regulations, providing technical assistance, and reviewing privacy agreements in real time. A Privacy Council would be concurrently tasked with reviewing existing laws in light of new technological and educational developments, examining the work of other states, and making recommendations for improvements in both laws and regulations. 

One powerful state example of a law creating a Chief Privacy Officer is New York’s Section 2-d. An example of a law governing a Student Data Privacy Council is Maryland House Bill 245.  Both examples were used as models for the proposed language featured below.

Proposed language:

STATE CHIEF PRIVACY OFFICER. The [STATE] Department of Education shall appoint a Chief Privacy Officer responsible for overseeing and enforcing data privacy compliance when using websites, applications, and platforms for K-12 school purposes within the state. The Chief Privacy Officer shall have the following responsibilities:

STATE STUDENT DATA PRIVACY COUNCIL. There shall be established a Student Data Privacy Council (hereafter “The Council”).

States should consider expanding privacy requirements applicable to schools and their private sector partners

Responsibilities of Education Agencies or Institutions.  If they have not already done so, states should establish stronger data use limitations and protection requirements on the companies that work with schools (the “Operators” defined earlier). States should also expand the privacy obligations of education agencies or institutions subject to FERPA. For education agencies and institutions, state laws should also consider strategic and targeted expansion of the protections offered by FERPA.

New or expanded requirements on these entities should include:

  • language that requires written agreements specifying the scope of allowable data uses and outlining related protections before educational agencies or institutions disclose any personally identifiable data to Operators;
  • requirements to limit the collection and disclosure of student data to the minimum required by agencies or institutions and the Operators they hire;
  • adoption and implementation of robust physical, administrative, and technical data security measures in consultation with experts on cybersecurity and education (e.g, the NIST Cybersecurity Framework);
  • clear and accessible notification procedures for parents and students regarding what data is collected, how it will be used, and how it will be protected;
  • requirements to delete and destroy data that is no longer needed for the legitimate educational purposes for which it was collected or disclosed; and
  • designation by school districts of a Student Data Manager to serve as the primary contact for the State Privacy Officer and ensure data requirements, procedures, and rules are consistently followed.

The featured language below includes a section on contract transparency modeled on Colorado’s Student Data and Transparency Law and the designation of a Student Data Manager modeled on Utah law.

Proposed language:

Responsibilities of Operators. In addition to the responsibilities of educational agencies and institutions, it is critical that state laws specify rules and responsibilities for Operators who collect and use student data when working with schools, as well as, in some permitted circumstances, share access to said data with other third-party vendors for legitimate education purposes. 

These responsibilities should include:

  • prohibiting the use of student data for advertising or other commercial purposes;
  • prohibiting the re-disclosure of data except as permitted or required by state and federal law; and prohibiting the use of student data for any purpose not authorized by a written agreement with an educational agency or institution and not serving a legitimate educational interest;
  • provisions requiring Operators to implement reasonable and robust security measures for all student data consistent with a nationally recognized standard such as the NIST Cybersecurity Framework;
  • timely notification of education agencies and institutions of any breach of student data;
  • allowing the education agency or institution to conduct privacy audits and allowing access of data for parents and students as requested; and
  • deleting and destroying data when it is no longer needed for the legitimate educational purpose for which it was collected.

The proposed language below includes provisions to ensure state laws comply and incorporate best practices from the federal Children’s Online Privacy Protection Rule (COPPA). Iowa’s Student Personal Information Protection law was used for the provisions related to accepted commercial uses of student data, while language requiring adequate training on state and federal privacy laws was modeled on New York’s section 2-d.

Proposed language:

States should ensure any new privacy obligations accommodate legitimate educational or other appropriate data uses

The proposed language below offers some additional provisions that can be added to state law or regulation to ensure privacy protections do not have unintended consequences, such as limiting legitimate educational uses of student data.

Proposed language:

States should consider cybersecurity improvements designed to protect student and personnel data

Ransomware and other cyberattacks are among the greatest threats to K-12 student data privacy. States should evaluate the cybersecurity threats faced by their schools and consider adopting policies designed to strengthen their overall cyber-defenses.  Key strategies could include the following:

School Device Standards and Parental Engagement

State policymakers should direct the state board of education to adopt standards for permissible electronic devices and software applications used by schools. In adopting the standards, the district must ensure that parents are provided the resources necessary to understand cybersecurity risks and online safety and assign a party to receive cybersecurity concerns. The below language is modeled on Texas Code Section 32.1021.

Proposed language:

REQUIREMENTS FOR TRANSFER. Before transferring data processing equipment or an electronic device to a student, a school district or open-enrollment charter school must: adopt rules establishing programs promoting parents as partners in cybersecurity and online safety that involve parents in students’ use of transferred equipment or electronic devices.

Promoting Cyberattack Information Sharing and Collaborative Response

States should encourage or require their educational agencies and institutions to collaborate in identifying and responding to cyberattacks.  States should also establish a statewide cybersecurity center, include representatives from the Department of Education in the center’s leadership, and ensure all school districts are among entities that benefit from the center’s work, including coordinating information sharing and cyber threat information. California Government Code Section 8586.5 provides a good model for ways to incorporate these structures in state law.

Proposed language:

States should ensure educators, students, and families are privacy literate

States should consider adopting a student data privacy education and capacity-building strategy to provide educators, students, and families with tools to assist in navigating an increasingly digital learning environment. As schools rely more heavily on technology tools and data-driven practices, it is essential that all stakeholders understand how to protect student information and comply with applicable privacy and cybersecurity laws.

Proposed language:

For more policy resources and recommendations on ways to strengthen digital equity in your state, enhance college and career pathways, and develop next-generation accountability system, explore the rest of All4Ed’s State Policy Center.

Click here to return to the home page of our State Policy Center.
Click here to return to our Digital Equity Page.