Unclaimed Hardware: The Plate Reader Networks of St. Lucie County and the Null-Owner Problem

The permit database for St. Lucie County lists fourteen plate-reading cameras. The county's public safety infrastructure, reviewed against installation records filed between January 2022 and March 2025, accounts for three of them. The St. Lucie County Sheriff's Office claimed those three. The remaining eleven have no owner on file, no installation authorization, and no documented procurement chain. A camera with no owner has no retention schedule. A retention schedule that does not exist cannot be violated.

The servers are lying, but not in the way that makes headlines. The firmware running on the network's aggregation hardware, version 4.2.1, carries a security designation from a patch cycle finalized eighteen months after the hardware beneath it was purchased. The procurement record has not been updated to reflect the gap. The result is a system that describes itself as current while running on a physical substrate the current description was never written for. The gap between what the documentation says and what the hardware can enforce is not theoretical. Fifty documented cases of officer misuse across the United States have already moved through it.

In Pinellas County, two officers were arrested for using the plate reader network to track individuals outside any authorized investigation. The system did not flag either officer during the tracking period, because the audit architecture was not built to detect lateral queries by credentialed users. Flock Safety, the vendor operating the network, has stated that safeguards against misuse are in place. Security researchers who have reviewed the safeguard design describe the same gap the Pinellas arrests walked through. The vendor's description of the system and the system's actual enforcement behavior are not the same document.

In four of the six accessible Floridas, a configuration matching this one was flagged and taken offline during a 2024 audit cycle. The permit discrepancy triggered the review. This is not one of those Floridas. Here, the audit has not started, the permit discrepancy is on record, and the cameras are still running.

Commissioner James Clasby has stated publicly that non-law enforcement entities operating cameras in the county is not acceptable. The statement was made in response to a question about the eleven unclaimed units. The statement does not constitute a shutdown order. The cameras do not require a shutdown order to continue operating. They require one to stop.

The retention question is jurisdictionally unresolved for a specific technical reason. A permitted camera is bound by the data governance policy attached to the permit. An unpermitted camera is bound by nothing on file, because nothing was filed. Thirty days is the standard retention window cited by the Sheriff's Office for the three units it owns. The eleven units with no owner have no window on record, which in practice means the window is open until someone closes it. No one has been assigned to close it, because no one has been assigned to own the cameras that would require a window.

The plate reader hardware logs vehicle identification data, timestamps, and geolocation coordinates for every vehicle that passes a mounted unit. That log exists somewhere. The somewhere is not documented for eleven of the fourteen cameras because the documentation was never created. A database with no audit trail does not lose its memory. It loses the requirement that anyone read the memory.

The field observation from Timeline 3 is relevant here: the plate reader rollout in that county proceeded identically through the permitting phase, then diverged at the audit step. The divergence was not dramatic. One department head filed a secondary inventory request. The request surfaced the discrepancy. The discrepancy triggered a public disclosure. The disclosure produced a list of camera locations, ownership assignments, and retention schedules that residents could read. The cameras stayed up. The null-owner problem was resolved because someone asked, in writing, whether everything that was running was accounted for. In this timeline, that request is not on file.

The technical read on why this matters in IT terms: a database that accepts writes from an unregistered source has no way to attribute those writes during a later audit. The query logs for the eleven unclaimed cameras would show data entering the aggregation server, but the ownership field for those writes is unpopulated. An unpopulated ownership field does not prevent the data from being used. It prevents anyone from being held responsible for how it was used. That is a design outcome, not a clerical gap.

Flock Safety's architecture centralizes plate data through a vendor-managed backend. Law enforcement agencies access the data through a credentialed portal. The credential system tracks which agency account ran which query. It does not track who within the agency ran the query, with sufficient granularity to support the accountability standard the Pinellas case required. That granularity is available at the technical level. It is not turned on by default. Turning it on requires a policy directive from the contracting agency. Agencies that did not know the granularity existed have not issued that directive.

The infrastructure read is clean. Fourteen cameras are running. Three are claimed. The data from all fourteen is flowing into a backend that will retain it for a period no document specifies for eleven of the units. The system is functioning as built. The build does not include an owner requirement as a prerequisite for operation.

Residents traveling through St. Lucie County should understand that their vehicle's plate is being logged, that the log may be held for an unspecified period, that the entity holding eleven of those logs is not on record, and that the access policy for an unregistered data source is whatever the unregistered source decides it is.

Advisory: the cameras are still running. Whoever is reading the plates, the plates are being read. This bulletin was filed before the permit question was resolved, because the permit question has not been resolved.