A parking enforcement supervisor for a mid-sized Virginia city spent part of January briefing his director on a bill working its way through the General Assembly. House Bill 1437 would have done something Virginia law has never done: put an actual statutory number on how long license plate reader data can sit in a database before it has to be purged. For an enforcement division running plate-based permit and meter compliance out of a handful of LPR-equipped vehicles, that mattered less as an abstraction and more as a planning question — retention schedules affect data storage contracts, vendor agreements, and what happens when someone files a records request. The supervisor’s director told him to hold off updating any internal policy until the bill actually passed.

That caution turned out to be justified for reasons nobody expected in January. HB 1437 and its Senate companion, SB 1165, moved through committee with unusually broad, bipartisan-adjacent support — only to collapse within about 48 hours of each other in the final days of the General Assembly’s short session, after a coalition of civil liberties groups intervened late and hard. As of this week, Virginia remains a state with no statutory limit on how long a license plate reader can retain the data it collects, and no statewide law defining who can access it or for what purpose. The bills that would have changed that are dead for this session.

For an editorial audience that spends most of its attention on states like California, where SB 34 has required ALPR operators to post a privacy policy since 2016, Virginia’s near-miss is worth a closer look — not because the state passed anything, but because of what its failure reveals about the specific fault line where these bills tend to break, and about the vacuum that persists when they do.

What HB 1437 and SB 1165 Would Have Actually Done

Both bills were carried by lawmakers who framed the legislation around a fairly narrow set of high-stakes law enforcement uses: locating stolen vehicles, supporting child abduction and human trafficking investigations, and giving agencies a lawful basis for using a technology many already had in the field without much statutory guidance. Del. Bill Wiley (R-Winchester) patroned the House version; Sen. Lynwood Lewis (D-Accomack) patroned the Senate companion.

The operative provisions were straightforward. Video and image data captured by license plate reader devices used for public safety purposes would have had to be erased after 30 days unless it was actively tied to an ongoing investigation. The bills also drew a bright line around traffic enforcement specifically: agencies would have been barred from using reader data to enforce speed limits, general traffic regulations, tolling requirements, or high-occupancy-vehicle lane restrictions. A further provision would have given the Commonwealth Transportation Board authority to regulate reader systems mounted on state and local roadways.

The bill’s subcommittee hearing drew support from the Virginia Sheriffs’ Association and the Virginia State Police Association, along with representatives of two companies that sell the underlying camera systems, Flock Safety and Altumin. Flock Safety in particular has become one of the most visible vendors in this space nationally, and reporting around the bill described more than 1,000 of its cameras already deployed across Virginia jurisdictions — installed under existing local contracts, ahead of any statewide rule about what happens to the data they generate. That gap between deployment and regulation is the condition HB 1437 was written to close.

A House transportation subcommittee voted unanimously to advance the bill on January 31. At that point, the legislation looked like it had a real path to passage.

The Ruling That Created the Vacuum These Bills Were Trying to Fill

To understand why a 30-day retention rule was newsworthy in Virginia specifically, it helps to know what the law currently does — which is very little. In 2020, the Supreme Court of Virginia issued its decision in Neal v. Fairfax County Police Department, resolving a challenge to the Fairfax County Police Department’s practice of retaining license plate reader captures — plate, timestamp, and location — for 364 days regardless of whether any individual plate was ever linked to a crime. A circuit court had initially sided with the plaintiff, finding that passive, undifferentiated retention of that kind violated Virginia’s Government Data Collection and Dissemination Practices Act. The Supreme Court of Virginia reversed, holding that an ALPR database of plate numbers, timestamps, and locations does not meet the statutory definition of a regulated “information system” because it isn’t cross-referenced with a driver’s name, address, or other personally identifying information at the point of collection.

That ruling didn’t approve of long-term bulk retention so much as it found that the specific state law being invoked didn’t reach it. The practical effect has been a legal vacuum: absent county-by-county policy choices, Virginia law enforcement agencies operating license plate readers are not bound by any statewide statute governing how long they keep the data, who can query it, or what it can be used for. HB 1437 and SB 1165 were the first serious legislative attempt since that ruling to fill the gap the court declined to fill itself.

Why the Bills Fell Apart in 48 Hours

The collapse was fast enough that people who had been tracking the bills for weeks were caught off guard by how quickly the tone shifted. A coalition of civil liberties and defense organizations — including the ACLU of Virginia, Justice Forward Virginia, and the Virginia Association of Criminal Defense Lawyers — sent a joint letter in the final days before the floor votes, describing the legislation as effectively codifying a mass surveillance capability with insufficient oversight. Their objections centered on three things: the absence of a warrant requirement or comparable judicial checkpoint before data could be queried, no meaningful independent audit mechanism, and concern that reader placement and enforcement patterns tend to concentrate in and disproportionately affect communities of color.

One Virginia state senator involved in the process described the shift in blunter terms than legislators typically use about their own bills, characterizing it as an “unraveling” of support unlike anything he’d seen move through in that short a window. A last-minute floor amendment proposing a study work group on law enforcement recording devices, offered as a compromise to buy more time, wasn’t enough to save either bill. HB 1437 died in the House; SB 1165 died in the Senate a day later.

It’s worth noting what didn’t kill the bills: opposition from the vendor side, cost concerns, or a competing bill with stronger protections that lawmakers preferred instead. What sank HB 1437 and SB 1165 was a fast-moving, well-organized argument that the retention limit and use restrictions on offer, while real, still left the core surveillance capability unchecked by any warrant or independent audit requirement — a bar the bill’s supporters hadn’t tried to clear because their framing was about limiting misuse, not about restricting collection or access in the first place.

The Question the Bills Never Really Answered: Where Does Parking Enforcement Fit?

Neither HB 1437 nor SB 1165, as reported, drew a clear statutory line around civilian municipal parking enforcement — the divisions that operate LPR-equipped vehicles for permit compliance, meter enforcement, and towing eligibility, typically staffed by civilian personnel rather than sworn officers. Both bills were framed and discussed almost entirely around criminal-justice use cases: stolen vehicles, missing persons, human trafficking. The traffic-enforcement carve-out was explicit and specific — no speed enforcement, no HOV enforcement, no toll enforcement — but parking enforcement, as a civilian municipal function distinct from “law enforcement” in the way the bills likely intended that term, was not directly addressed in the reporting on either bill’s text.

That’s not a small ambiguity for the audience this publication serves. A municipal parking authority or a university transportation department running its own LPR-equipped enforcement fleet has to ask a question state legislators in Richmond weren’t visibly asking on its behalf: if and when Virginia does pass an ALPR statute, will “law enforcement agency” as defined in that statute sweep in a civilian parking enforcement division, or will it leave that function in the same undefined space it currently occupies under Neal? A definition that tracks sworn law-enforcement status specifically could leave parking programs with neither the statutory permissions the bill would have granted police agencies, nor the boundaries designed to constrain them — an outcome that cuts against operators in both directions at once. Programs in this position should not assume a future Virginia ALPR statute will automatically apply to them just because their equipment and use case look similar to a police department’s.

Watching for the Next Attempt

Bills like this rarely disappear for good after one failed session; sponsors on both sides of this debate treated the collapse as a setback rather than a final word, and previous ALPR fights in other states have often taken more than one legislative cycle to resolve into an actual statute. For Virginia specifically, the near-miss establishes a template worth tracking heading into next year’s session: a retention limit and a narrow permitted-use list can attract real bipartisan and law-enforcement support, but that same framing is vulnerable to a late, well-coordinated privacy coalition if it doesn’t also address warrant requirements, independent audits, and — for this industry specifically — where civilian enforcement functions sit relative to the statute’s core definitions.

Virginia’s pattern also isn’t unique to Virginia. The National Conference of State Legislatures maintains a running summary of state ALPR statutes that’s worth bookmarking for exactly this reason — state activity in this area moves in both directions, with new statutes and failed attempts happening in the same legislative season, sometimes in the same state in consecutive years.

What Parking Operators in Ambiguous-Law States Should Do Now

A failed bill doesn’t create a new obligation, but it’s a useful prompt to check a few things regardless of which state a program operates in:

Confirm what your current retention and access practice actually is, on paper, regardless of what state law does or doesn’t require. In a state without a statutory limit, an operator’s own written policy — however informal — is the only documented standard that exists, and it’s the first thing a records request or a lawsuit will ask about.

Don’t assume “law enforcement” definitions in a future statute will automatically include or exclude your program. Civilian parking enforcement occupies an ambiguous space in exactly the kind of legislation Virginia just failed to pass, and that ambiguity should be raised directly with legislative staff or a state parking association during the drafting process, not discovered after the fact.

Track legislative activity in every state where you operate, not just the states with an ALPR-specific statute already on the books. A bill that fails one session can return substantially rewritten the next, and vendors selling into a jurisdiction with live legislative activity should expect contract terms — particularly around data retention and third-party access — to need revision on short notice.

Ask your camera and software vendor directly what their default retention setting is, and whether it’s configurable per contract. Vendor defaults, not statutory minimums, are what most programs are actually running on in states without a governing statute, and that default is frequently more permissive than what a proposed bill like HB 1437 would have required.

Frequently Asked Questions

Did Virginia pass a license plate reader privacy law in 2023?

No. Both HB 1437 and its Senate companion, SB 1165, died in the final days of the 2023 General Assembly session after passing initial committee votes with broad support. Virginia currently has no statewide statute governing license plate reader data retention, access, or permitted use, and the failure of these bills leaves that status unchanged for now.

What does current Virginia law say about how long license plate reader data can be kept?

There is no statutory retention limit. The Supreme Court of Virginia’s 2020 ruling in Neal v. Fairfax County Police Department found that a database of plate numbers, timestamps, and locations doesn’t meet the definition of a regulated “information system” under the state’s Data Act, so the retention practices of individual agencies are governed by local policy choice, not state law.

Why did a bill with law enforcement and bipartisan support collapse so quickly?

A coalition including the ACLU of Virginia and Justice Forward Virginia sent a joint letter shortly before floor votes, arguing the bills lacked a warrant requirement or independent audit mechanism and risked codifying a surveillance capability with insufficient checks. That intervention shifted legislative sentiment within days, and a last-minute compromise amendment wasn’t enough to save either bill.

Would HB 1437 have applied to municipal parking enforcement, not just police departments?

It’s unclear from the bill’s reported provisions. HB 1437 and SB 1165 were framed around law-enforcement use cases like stolen vehicles and trafficking investigations, and included specific carve-outs barring use for traffic and toll enforcement, but neither bill was described as directly addressing civilian municipal parking enforcement divisions, which typically operate outside sworn law-enforcement chains of command.

Should parking operators in other states pay attention to a Virginia bill that didn’t pass?

Yes, as a pattern rather than as binding precedent. The specific coalition objections that sank HB 1437 and SB 1165 — missing warrant requirements, no independent audit provision — are recurring themes in ALPR legislative fights nationally, and operators can reasonably expect similar bills in other states to face the same objections unless drafted around them from the start.

Further Reading from Authoritative Sources