IS FLOCK CONSTITUTIONAL? SCALE IS THE VARIABLE.

The easiest argument about automated license plate readers is also the least useful: a license plate is visible in public, therefore there is no privacy issue.

That proposition describes one observation. A modern ALPR system is a database of observations that can be searched backward in time, combined across cameras, and used to reconstruct movement. Constitutional analysis increasingly turns on the difference between those two things.

Church did not give Flock a constitutional blank check.

In Commonwealth of Virginia v. Ronnie D. Church, the Virginia Court of Appeals reversed a suppression ruling and held that police did not need a warrant to access Flock data in that case. Norfolk had 172 cameras, the data were retained for 30 days, and the officer obtained three images covering roughly seven minutes of Church's drive.

The court emphasized those facts. It distinguished the case from Carpenter v. United States, where the government obtained a far more comprehensive record of cell-site location history, and from the Fourth Circuit's Leaders of a Beautiful Struggle decision involving persistent aerial surveillance of Baltimore.

That matters because the opinion's logic is not “ALPR can never be a search.” It is closer to: this amount of ALPR evidence, on these facts, did not create the kind of comprehensive chronicle that triggered the cases Church relied on.

Massachusetts already framed the future problem.

In Commonwealth v. McCarthy, Massachusetts' Supreme Judicial Court considered ALPR cameras placed at the two bridges leading to Cape Cod. It concluded that the limited network did not produce a detailed enough mosaic of the defendant's movements to invade a reasonable expectation of privacy.

But the court also said widespread police use of ALPRs could implicate constitutional protections. That is the hinge. The legal object is not merely the camera. It is the surveillance capability produced by the network.

The network changes the constitutional facts.

Suppose a camera records a vehicle at one intersection. That resembles ordinary observation. Add hundreds or thousands of cameras, longer retention, cross-jurisdiction sharing, searchable historical records, and automated pattern analysis, and the system begins to answer a different class of questions:

• Where was this vehicle over a week?
• Which locations recur?
• Which other vehicles appear nearby?
• Can an investigator reconstruct a route after deciding who to investigate?

The Supreme Court's location-privacy cases do not reduce to “public versus private.” They also ask whether technology gives government access to a quantity and persistence of information that changes the nature of surveillance.

Retention is constitutional architecture.

A seven-day database and a multi-year database do not create the same investigative capability. A citywide network and four bridge cameras do not create the same coverage. A local-only system and a network with broad interagency access do not create the same retrospective reach.

That is why constitutional analysis cannot stop at camera specifications. Density, duration, sharing scope, query rules, and aggregation determine what the system can know.

The cleanest policy can be stricter than the constitutional minimum.

Even if a particular use survives Fourth Amendment review, a city can still require warrants, documented investigative predicates, retention caps, audit review, and narrower sharing as policy choices. Constitutional permission is a floor, not an instruction manual for maximum surveillance.

That distinction gets lost constantly. “A court allowed this use” does not mean “the government should deploy every technically possible version of it.”