TL;DR: Virginia's SB 1515 has been law since July 1, 2023 [2]. A commercial entity that knowingly or intentionally publishes material harmful to minors from a website where that material makes up "more than 33 and one-third percent of total material" has to "verify that any person attempting to access such material harmful to minors is 18 years of age or older" [1]. The statute allows two routes: "a commercially available database that is regularly used by businesses or governmental entities for the purpose of age and identity verification" or "another commercially reasonable method of age and identity verification" [1]. It does not require a photo of your ID, and it says nothing at all about what happens to your data after the check. There is no retention rule, no deletion rule and no penalty for keeping what the check collected. The consequence the law does create is a civil claim for "damages resulting from a minor's access to such material harmful to a minor and reasonable attorney fees and costs" [1]. No court ruling on the statute could be verified on November 19, 2026 [7].
What the Statute Actually Requires
Virginia put its age-check law in the civil remedies code, not the criminal code. The whole law is Section 8.01-40.5, four subsections, added by Chapter 811 of the 2023 Acts of Assembly [1]. Read it once and you will find no screen to click past, no health warning to scroll, and no officer to knock on the door.
Who it covers. The duty falls on any commercial entity that "knowingly or intentionally publishes or distributes material harmful to minors on the Internet from a website that contains a substantial portion of such material" [1]. The trigger is a threshold, and the statute sets it exactly: a "substantial portion" means "more than 33 and one-third percent of total material on a website that meets the definition of material harmful to minors" [1]. A site with less than that is outside the law. So is the plumbing. The statute says "Nothing in this section shall be construed to impose an obligation or liability on a provider or user of an interactive computer service on the Internet" [1]. The liability sits with the site that publishes the material, not with the network that carries it.
What counts as harmful material. The definition is the familiar three-part test: "any description or representation of nudity, sexual conduct, sexual excitement, or sadomasochistic abuse when it (i) appeals to the prurient, shameful, or morbid interest of minors; (ii) is patently offensive to prevailing standards in the adult community as a whole with respect to what is suitable material for minors; and (iii) is, when taken as a whole, lacking in serious literary, artistic, political, or scientific value for minors" [1]. The statute defines the term "sexual conduct" by pointing to § 18.2-390 [1].
How the check has to be done. Subsection B gives two options and no more. A covered site must use "a commercially available database that is regularly used by businesses or governmental entities for the purpose of age and identity verification" or "another commercially reasonable method of age and identity verification" [1]. That is the entire privacy bargain Virginia struck. The statute never says you must hand over a government ID, never says a camera has to scan your face, and never names a vendor. It leaves the method to the site.
One detail worth keeping in mind. The duty attaches to the site, not to a single page, because the covered entity must verify "any person attempting to access such material harmful to minors" [1]. The same shape showed up in Texas, where the check covers every visitor "by collecting age-verifying personal information from all visitors" even when the visitor wanted material that is not adult content at all [5].
The Part the Statute Leaves Out
Here is the privacy finding, and it is worth stating plainly. Section 8.01-40.5 contains no rule about data. It does not require an age-check company to delete what it collected. It does not prohibit keeping it. It sets no deadline and attaches no penalty for holding on to it [1].
Compare that with Texas, where the statute the Supreme Court upheld does exactly what Virginia's does not. Section 129B.002(b) of the Texas law provides that a site, or a third party running the check, "may not retain any identifying information of the individual", and the penalty for breaking that rule is up to "$10,000 per instance when the entity retains identifying information in violation of Section 129B.002(b)" [3]. Virginia's law has no equivalent sentence and no equivalent penalty [1].
The only consequence Virginia's statute creates is a civil claim. A covered entity that violates the section "shall be subject to civil liability for damages resulting from a minor's access to such material harmful to a minor and reasonable attorney fees and costs" [1]. The bill's own summary describes it the same way: it "Creates a civil cause of action for any commercial entity that knowingly or intentionally publishes or distributes on the Internet material harmful to minors, as defined in the bill, and that does not take reasonable steps to verify that the age of a person attempting to access such material harmful to minors is 18 years of age or older" [2].
Read the section end to end and you will not find the attorney general's name in it, a criminal charge, a fine per violation or a health warning screen. The enforcement mechanism is a family with a lawyer. That is a meaningful difference from Texas, where the statute lets the attorney general sue and sets civil penalties for violations [3].
The Electronic Frontier Foundation's warning about what an age check really is applies here with full force: "every age-verification system is, at its core, a surveillance system" [4]. EFF is also blunt about deletion promises: "Online, there’s no way for users to verify that their private information has been deleted, or to ensure that it won’t be copied, sold, or stolen" [4]. Virginia's law does not require a deletion promise. It does not forbid one either. Which means the only protection you get is whatever the company running the check decided to offer you on its own.
How It Became Law, Over the Governor's Changes
The governor tried to change this bill before signing it. Virginia's Senate passed it on February 7, 2023 by "Passed Senate (37-Y 3-N)" and the House passed it on February 23 with a "Passed House with amendments BLOCK VOTE (96-Y 0-N)" [2]. The sponsor was Senator William M. Stanley, Jr. [2]. The bill was "Enrolled Bill Communicated to Governor on March 13, 2023", with a "Governor's Action Deadline 11:59 p.m., March 27, 2023" [2].
On March 27 the governor sent back his own substitute, printed as "23107762D-S3" [2]. The Senate rejected it. On April 12, 2023 the Senate "Senate rejected Governor's recommendation (18-Y 22-N)" [2], and on May 12 the governor "Approved by Governor-Chapter 811 (effective 7/1/23)" [2]. The Acts of Assembly record for that session carries the same number, CHAP0811 [2].
So the law has been in force since July 1, 2023 [2], and the current Code text cites only Chapter 811 of 2023 as its source [1].
The Court Status, Checked November 19, 2026
No ruling on Section 8.01-40.5 could be verified as of November 19, 2026. The Free Speech Coalition's age-verification lawsuit tracker, checked the same day, lists challenges to age-check laws in other states and no Virginia case [7]. That is the honest state of the record: the statute is on the books, and no challenge to it appears on that tracker.
Texas, by contrast, took its age-check law to the Supreme Court, and the Court affirmed on June 27, 2025 by a 6 to 3 vote in an opinion by Clarence Thomas, with Justice Kagan's dissent joined by Justices Sotomayor and Jackson [6]. The holding was narrow: "A Texas law requiring certain commercial websites publishing sexually explicit content that is obscene to minors to verify that visitors are 18 or older only incidentally burdens the protected speech of adults and survives intermediate scrutiny under the First Amendment’s Free Speech Clause" [6].
EFF reads that decision narrowly too: "Importantly, the Court’s reasoning applies only to age-verification rules for certain sexual material, and not to age limits in general" [5]. Virginia's statute works on the same basic plan: a content threshold, an age check before access, a court remedy. The difference is who brings the case, and there is nobody in the statute who brings it for the state.
What You Actually Face if You Are in Virginia
Two outcomes, and which one you get depends on the site. Either it puts a check in front of you, or it stops serving Virginia. The law pushes sites toward the second option. EFF expects it: "Many sites that cannot reasonably implement age verification measures for reasons such as cost or technical requirements will likely block users living in Texas and other states with similar laws wholesale" [5]. A site that refuses to serve you is not the same as a site that protected you.
If you do get a check, the commonest method is not gentle. EFF describes it as "uploading a photo of your government ID along with a “live” selfie or video", a method it calls "far more invasive than an in-person ID check" [4]. Virginia's statute does not require that method. It requires a commercially reasonable one [1], so a site has room to pick something narrower. Not every site will use that room.
The people most likely to be caught by a badly built check are the people the law claims to protect. EFF notes that ID-based systems "exclude those who either don’t have ID or whose appearance doesn’t match their current documents" [4], and that facial-recognition systems "commonly misjudge age based on skin tone, gender, and disability" [4]. On the Texas ruling, EFF noted that "Many others do not have a driver’s license or photo ID to complete the age verification process" [5]. There is no method on the market that is "entirely privacy-protective, fully accurate, and that guarantees complete coverage of the population" [4].
What to Do
- Ask what the check is before you hand anything over. Virginia's statute lets the site choose between a commercial verification database and any other commercially reasonable method [1]. Those two options are not interchangeable, and you are the only one who can pick the narrower one if both are offered.
- Give the least you can. Virginia's statute does not require a government ID upload, so a site that demands one is making that choice on its own [1]. If a document-free estimate is offered, take it.
- Assume nothing gets deleted. The statute says nothing about deleting your data [1], and EFF's point stands: "Online, there’s no way for users to verify that their private information has been deleted" [4].
- Keep a record. Which site, which vendor, which document, which date. If you ever want to know what was collected in your name, that is the only place the answer starts.
- Expect to be blocked rather than checked. EFF expects many sites to refuse service to states like Virginia wholesale [5], and Virginia's law has no state enforcement to push them the other way.
- Shrink the rest of the surface. Age verification is one channel. Your browser, your apps and your phone leak more without a single court order involved. See browser privacy and app permissions.
Sources
- Code of Virginia: Section 8.01-40.5, Publishing or distributing material harmful to minors on the Internet (current text, historical citation 2023, c. 811).
- Virginia General Assembly, Legislative Information System: Bill Tracking, SB 1515, 2023 session (summary as passed and full history, capture dated November 2, 2026).
- Texas Legislature Online: 88(R) HB 1181, Enrolled version, Bill Text (new Chapter 129B, Civil Practice and Remedies Code).
- Electronic Frontier Foundation: Age Verification Systems Are Surveillance Systems.
- Electronic Frontier Foundation: The Supreme Court's Decision on Age Verification Tramples Free Speech and Undermines Privacy.
- SCOTUSblog: Free Speech Coalition, Inc. v. Paxton (23-1122) (case page with the vote, opinion author, dissent lineup and holding).
- Free Speech Coalition: Lawsuit Status, Age Verification Resources (checked November 19, 2026).
Published: November 19, 2026