top of page

Ep 96 - Back Porch Files: The Cameras That Remember

Jul 10
8 min read

There is a decent chance you have driven past one of them and never noticed it. A small black camera box on a pole. Maybe at an intersection. Maybe near a school. Maybe at the edge of town, where the road bends and the streetlights thin out. It does not look dramatic. It does not look like a warning. It looks like municipal clutter, one more little piece of roadside furniture in a world already full of signs, wires, boxes, poles, and things nobody asked about until they were already there.


It’s not the camera that should worry you. It’s the memory.
It’s not the camera that should worry you. It’s the memory.

But that camera may not be there to catch speeders. It may not be there to issue tickets. It may not even be there to record normal security footage in the way most people imagine. It may be an automated license plate reader, scanning passing vehicles, reading plates, recording time and location, and entering that information into a searchable system. One car. One plate. One timestamp. One more tiny breadcrumb in a database that can remember where vehicles have been.


That is where the debate begins. Not with the camera itself, but with the memory behind it. A human being sees your car drive past and forgets. A database sees your car drive past and remembers. And when that memory is searchable, shareable, and connected to other systems, a simple public-safety tool starts becoming something much larger. It becomes infrastructure. It becomes a record. It becomes a map.


To be fair, the sales pitch is not nonsense. Police departments and local officials often justify these cameras with real concerns: stolen vehicles, Amber Alerts, missing people, robberies, burglaries, hit-and-runs, and violent crimes. Those things matter. Victims matter. Public safety matters. Nobody should have to pretend stolen cars are imaginary or missing children are theoretical just to have a serious conversation about civil liberties.


But usefulness is not the end of the conversation. It is the beginning. A tool can be useful and still dangerous without rules. A tool can help solve crimes and still create a surveillance system that sweeps up ordinary people who are not suspected of anything. That is the line we keep tripping over in this country. Someone points to a useful outcome, and suddenly every question about limits, oversight, retention, sharing, and misuse is treated like an attack on safety itself.


The problem is not that police want tools. Police should have tools. The problem is that every tool creates a system, and every system needs rules before we discover what it can do in the wrong hands. “Public safety” cannot be a magic phrase that turns off civil liberties. It cannot mean the government gets to collect first, search later, and ask the public to be grateful for the privilege of being cataloged.


The key issue is aggregation. Your license plate being visible in public is one thing. Your license plate being logged over and over again, across locations and over time, is something else. One sighting is a moment. Many sightings become a pattern. And a pattern can reveal a life: where you work, where you worship, where you seek medical care, where you attend meetings, where you protest, where you organize, where you spend the night, and where you go when nobody has any right to ask.


That is why the “nothing to hide” argument is so lazy. Privacy is not the same as guilt. A free society does not require innocence as the entry fee for basic limits on government power. And the same people who casually say “if you have nothing to hide, why do you care?” would likely combust into patriotic confetti if the government started tracking their guns, church attendance, political donations, or browser history. Privacy matters most when power decides it is inconvenient.


Most of the data collected by these systems is not about criminals. It is about everyone else. People going to work. People going to school. People going to the doctor. People visiting family. People buying groceries. People driving home. The suspect is the needle. But the haystack is us. And the haystack should not be treated like disposable background material in a system built for someone else’s investigation.


The network is what makes this especially serious. One camera in one town is one debate. Thousands of cameras connected through a searchable platform is another. A local police department may buy a tool for stolen car alerts, but that tool can become part of a much larger system depending on sharing settings, agency agreements, retention policies, and future decisions. The town buys a camera. The department joins a network. Suddenly a local public-safety tool starts looking like a national tracking grid with a customer-service number.


That does not mean every officer is abusing the system. It does not mean every department has bad intentions. It does not require a secret villain in a basement stroking a cat and whispering plate numbers into the dark. Systems do not need evil geniuses to become dangerous. Sometimes all they need is weak policy, broad access, poor oversight, and time. That is how mission creep works. Yesterday’s “limited use” becomes tomorrow’s standard operating procedure.


The federal access and immigration enforcement concerns make this even more complicated. Companies may say they do not work with certain agencies. Departments may say access is limited. Settings may be disabled by default. Those claims matter and should be reported accurately. But civil liberties cannot depend on slogans, defaults, or company FAQs. The concern is not only direct access. It is workaround access: one agency searching for another, data shared across jurisdictions, out-of-state requests, informal cooperation, future policy changes, and political pressure that finds the dropdown menu.


That is why rules have to come before abuse, not after it. After abuse, everyone acts shocked. After abuse, there is a review. After abuse, someone says lessons were learned. Wonderful. The barn door is fixed, the horse has a lawyer, and the public gets a PDF. Civil liberties are not protected by vibes. They are protected by enforceable rules, audit logs, public reporting, independent oversight, real penalties, and clear limits on who can search what, when, and why.


Then there is the accountability problem. Many people only learn about these cameras after they are installed. The decision may have happened through a police budget, a grant, a pilot program, a city council contract, a homeowners’ association, a school district, a business district, or some other local process that technically counts as public but practically functions like a civic trapdoor. By the time residents notice the pole, the system may already be running.


That is not good enough. A system that records public movement should not arrive as a quiet line item hiding between road salt and copier maintenance. There should be a public hearing. There should be a vote. There should be plain-language policies. Residents should know what is collected, how long it is kept, who can search it, who can share it, who can request it, what happens when someone misuses it, and whether the whole thing expires unless the public renews it. Local democracy should not be a scavenger hunt.


And because many of these systems are routed through private technology companies, the accountability problem gets murkier. This is public power delivered through private infrastructure. That means contracts, dashboards, retention settings, sharing defaults, corporate terms, cybersecurity, renewal clauses, and legal language that reads like a caffeinated squid got hired as county solicitor. When government surveillance travels through a vendor platform, democracy suddenly has to read the terms of service.


Government power does not become harmless just because it comes with a user dashboard. If police use the system, if public agencies search the data, if the information can affect real people, then this is not merely a private product. It is public power with a private interface. And the public deserves public rules, not just marketing language, vendor assurances, or promises that the “customer controls the data” while the people being scanned are nowhere in the chain of consent.


The answer does not have to be banning every license plate reader everywhere. That is not the argument. The argument is that the default should not be a permanent, shared, searchable record of ordinary people’s movements. If communities decide they want these tools, then the rules should be strict: short retention periods, strong approval standards for historical searches, limits on sharing, no immigration-enforcement workarounds, public reporting, independent audits, real penalties for misuse, open votes, public hearings, and sunset clauses.


If the tool is as reasonable as officials say it is, then it should survive reasonable rules. If it cannot survive transparency, oversight, short retention, and democratic approval, then maybe the problem is not the critics. Maybe the problem is the tool. A free society does not measure liberty by how politely power promises to behave. It measures liberty by how well power is restrained before temptation gets comfortable.


This is not only about Flock. Flock is the doorway. The larger room is surveillance itself: how it arrives, how it grows, and how it becomes normal before most people know it exists. Modern surveillance does not always kick down the door. Sometimes it gets approved unanimously at a Tuesday night meeting while three people are in the audience and one of them is there about a pothole.


That is the danger. Not always a grand conspiracy. Not always a villainous announcement. Often it is convenience, safety language, grants, pilot programs, “limited use,” emergency exceptions, and contracts nobody reads until the camera is already on the pole and the database is already humming. The future does not always arrive wearing chrome armor. Sometimes it shows up with a procurement code and a cheerful promise that this is only for serious crimes.


Public safety and civil liberties are not enemies. The enemy is unaccountable power. We should not have to choose between solving crimes and living in a country where the government cannot casually reconstruct our movements. That is a false choice, and a lazy one. A democratic society can demand both safety and limits. It can demand both tools and rules. It can demand both justice for victims and privacy for ordinary people.


So, yes, crime matters. Victims matter. Police tools matter. But so does the right to move through daily life without being quietly entered into a searchable movement database. So does the right to know when your town is building surveillance infrastructure. So does the right to ask who controls the data, who searches it, who shares it, and who pays a price when it is abused.


The camera may be small. The pole may be ordinary. The sales pitch may sound harmless. But a democracy should be very careful about building machines that remember where everyone has been.


SOURCES

Flock Safety official license plate reader product page - https://www.flocksafety.com/products/license-plate-readers

Flock Safety statement on ICE and federal data sharing - https://www.flocksafety.com/blog/does-flock-share-data-with-ice

Flock Safety statement on local compliance and federal user categories - https://www.flocksafety.com/blog/ensuring-local-compliance

ACLU article on license plate readings and public data concerns - https://www.aclu.org/news/privacy-technology/tracking-alpr-cameras/alpr-as-public-data

ACLU of Massachusetts report on Flock data-sharing and law enforcement access - https://data.aclum.org/2025/10/07/flock-gives-law-enforcement-all-over-the-country-access-to-your-location/

University of Washington Center for Human Rights report on Flock access pathways and immigration enforcement concerns - https://jsis.washington.edu/humanrights/2025/10/21/leaving-the-door-wide-open/

University of Washington Center for Human Rights report on ALPR dangers to immigrant and reproductive rights - https://jsis.washington.edu/humanrights/2022/12/07/whos-watching-washington/

Institute for Justice case page on Norfolk, Virginia’s Flock camera lawsuit - https://ij.org/case/norfolk-virginia-camera-surveillance/

Institute for Justice press release on Norfolk Flock camera lawsuit moving forward - https://ij.org/press-release/judge-rules-lawsuit-challenging-norfolks-use-of-flock-cameras-can-proceed/

Institute for Justice press release on federal court rejecting Flock’s attempt to intervene in Norfolk lawsuit - https://ij.org/press-release/federal-court-rejects-flock-safetys-late-bid-to-join-and-block-ijs-lawsuit-challenging-norfolks-mass-surveillance-cameras/

Courthouse News report on federal judge ruling Norfolk’s Flock camera use constitutional - https://courthousenews.com/judge-holds-norfolks-license-plate-reader-use-constitutional/

Business Insider report on cities pushing back against Flock license plate readers - https://www.businessinsider.com/cities-putting-trash-bags-over-flock-license-plate-readers-2026-6

San Francisco Chronicle report on improper Flock searches for federal and out-of-state agencies - https://www.sfchronicle.com/bayarea/article/sfpd-flock-license-plate-reader-data-searches-22310416.php

Houston Chronicle report on vandalized Flock license-plate cameras and local backlash - https://www.houstonchronicle.com/news/houston-texas/trending/article/license-plate-cameras-vandalized-22335432.php

Car and Driver explainer on automated license plate readers and Flock cameras - https://www.caranddriver.com/news/a70792616/automated-license-plate-reader-explainer/

Axios report on earlier ICE use of license plate reader data - https://www.axios.com/2019/03/14/aclu-ice-using-license-plate-database-target-immigrants

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating

© 2023 by Train of Thoughts. Proudly created with Wix.com

bottom of page