Virginia — Va. Code §22.1-289.01 (school service providers)
Virginia's SOPIPA-family statute, binding school service providers and school technology providers directly: no sale of student personal information, no targeted advertising from it, no non-school-purpose profiling; security, deletion-on-request, and (unusually) a duty to provide students/parents an electronic copy of their data in a machine-readable format on contract terms.
Contents
| Document | Covers |
|---|---|
| SSP-DUTIES.md | §22.1-289.01 in full |
Scope note: §22.1-287 (records access) and §22.1-79.3 (local policies) from the TODO working cite are school-side provisions — add on demand.
Licence
The reproduced text is Va. Code §22.1-289.01, enacted by the General Assembly of Virginia and served by the Division of Legislative Automated Systems on law.lis.virginia.gov. No copyright subsists in this text. In Georgia v. Public.Resource.Org, Inc., 590 U.S. 255 (2020), the Supreme Court held: "Under what has been dubbed the government edicts doctrine, officials empowered to speak with the force of law cannot be the authors of—and therefore cannot copyright—the works they create in the course of their official duties." It went on: "judges—and, we now confirm, legislators—may not be considered the 'authors' of the works they produce in the course of their official duties as judges and legislators. That rule applies regardless of whether a given material carries the force of law." (slip opinion, pp. 1 and 5–6, read 2026-10-01.)
The site footer reads "© Copyright Commonwealth of Virginia, . All rights reserved." (read 2026-10-01). That is a site-wide notice; under the holding above it cannot reach the statute text, which is the work of the General Assembly in the course of its official duties. It may cover the site's own design, which the corpus does not reproduce.
Public-domain text carries no conditions. The corpus attributes it all the same: the {.meta} provenance line on each section names the publisher, the Sources section links the official text, and the Meta section describes what the builder changed (markup and anchors only). Nothing here suggests that the General Assembly of Virginia endorses the corpus.