Flock Safety’s network is the name most people now attach to the fight. The company has on the order of 120,000 cameras across 49 states. The cameras photograph plates, vehicle characteristics, time, and place. Police query that history when they have a case. Florida already uses plate reads for tolling. DeSantis drew a line between that and what he called “actual criminal surveillance” of ordinary travel.
Two professional views collide on the same facts. Neither needs a slogan. Both show up in every procurement, retention schedule, and audit that a privacy office or a sheriff’s command staff will have to write next year.
The chief privacy officer’s brief
A plate read of every car on a public road is not a targeted search. It is a mass log. The Fourth Amendment cases that treat a plate on a highway as “in public” do not answer how long the log may live, who may query it, whether a vendor may pool it across cities, or whether a federal customer may buy the same feed. Those are data-governance questions. They are also the questions state privacy laws and ALPR statutes were written to force into the open.
From a CPO desk the risk stack looks like this.
First, purpose creep. A camera sold as stolen-car recovery becomes a general movement database. Once the archive exists, every new use is a policy choice, not a new collection. Immigration queries, protest monitoring, and “see where this plate went last month” are all the same technical act: a search against innocent travel.
Second, vendor architecture. The interesting system is not one city’s pole. It is a networked product that can share hits across agencies. Sharing agreements, subprocessor lists, and whether the vendor trains models on the video matter as much as the local SOP. If the city cannot name every downstream querier, it cannot claim minimization.
Third, retention. Florida law has allowed plate data to sit for up to two years. Some agencies self-limit to 30 days. Privacy programs treat long retention of unsuspected travel as the injury. A two-year searchable history of a family car is a dossier, even if no officer is watching the feed live.
Fourth, access control and audit. DeSantis’s ex-girlfriend example is the CPO’s nightmare case because it is ordinary. Hot-list queries for a crime are one thing. Curiosity searches against an intimate partner, a neighbor, or a journalist are another. If logs cannot show who searched, why, and whether a supervisor saw it, the program is not governed. Arrests of officers in multiple states for personal lookups are not a PR problem. They are a control failure.
Fifth, sensitive locations. Clinics, schools, houses of worship, courthouses, and shelters turn a plate log into inference about health, faith, and legal trouble. New Hampshire-style rules that keep readers off those sites exist because the plate is a proxy for the person.
Sixth, notice and legitimacy. Residents often learn the cameras exist from a map site, not from the agency. A CPO will ask for public inventories, retention posted in plain language, and a process to challenge a hit. “These are just images” does not describe a queryable, multi-year, multi-agency index.
None of that requires a total ban. It requires treating ALPR like other high-risk processing: documented purpose, short default retention, warrant or documented predicate for historical lookups, no sale of the feed, audits with teeth, and a kill switch when an agency or a vendor cannot keep the rules.
The public-safety brief
Investigators will say the CPO is describing a library card as a spy satellite. The plate was already visible. The camera does what a deputy used to do with a notepad, only faster and with fewer missed recoveries.
The operational case is specific. A missing child. A trafficking victim. A violent felony suspect in a car that just passed a reader. Minutes matter. A query against a regional network can put a last-known direction on a map before the next shift change. Agencies that dropped Flock or similar tools have said, in public, that they lost recoveries they used to get. That is the metric command staff will bring to a county commission.
Accuracy and scope arguments cut both ways. Defenders note the system photographs vehicles, not faces, and that many deployments are not monitored live. They point to case law that photographing a plate on a public road is not, standing alone, an unconstitutional search. They point to transparency portals, audit logs, and agency policies that already limit queries to legitimate investigations.
They will also say phones already produce a tighter location history than a pole camera, and that criminals use the same roads as everyone else. Narrowing the net to “only the worst crimes” after the fact is easy in a hearing and hard at 2 a.m. when the only fact you have is a plate and a time.
Misuse is real, they concede, and should be prosecuted. The fix they prefer is access discipline: named accounts, reason codes, random audits, firing people who run a plate for a personal grudge. They do not accept that a few dirty queries prove the tool itself is illegitimate, any more than a deputy abusing NCIC means you shut NCIC down.
On vendors, the law-enforcement view is procurement and contract, not abolition. Require on-shore storage, no secondary commercial sale, agency ownership of the data, and the right to pull the feed. Treat Flock like CAD or body-worn video: a system of record with a security schedule, not a political symbol.
On legislation, many chiefs will live with shorter retention and a ban on personal lookups if the statute still allows hot-list alerts and historical search when there is an open case. What they will fight is a rule that makes the archive useless before the detective can use it, or that assumes every plate read is a constitutional event requiring a warrant in advance.
Where the two briefs actually meet
They already agree on more than the comments section does. Neither side needs unlimited retention. Neither side defends stalking an ex. Both sides want a human in the loop before an automated ticket or an automated life consequence. Both sides know a vendor network that outruns local policy is the hard problem, not the pole on Main Street.
The live fight is default settings. Privacy officers want the default to be: collect little, keep it briefly, query only with a documented reason, do not federate the feed. Investigators want the default to be: collect enough to reconstruct a route when a crime is already in motion, keep it long enough that last month’s hit is still there, share with partners who have the same case.
DeSantis put that fight on the legislative calendar. He did not call for a statewide ban. He said go after criminals, protect ordinary movement, and write the rules in statute because company policy and local SOP will not hold the line alone. Privacy offices and sheriffs will both testify. The useful hearing is the one that makes them specify retention days, query predicates, audit frequency, and whether a plate at a clinic is in or out, instead of arguing about whether cameras are “just images.”