That Camera at the Intersection Is Building a Searchable Map of Your Life

You drive to church on Sunday. A clinic on Tuesday. A late-night pharmacy on Thursday.

You probably did not consent to turning those trips into a searchable record. Yet a small camera near an intersection may have captured your license plate, vehicle details, location, and time. Multiply that by cameras across a city, then connect the searches across jurisdictions, and an ordinary drive stops looking ordinary. It becomes a trail.

This is why automated license plate readers, especially the network operated by Flock Safety, have become one of the sharpest privacy fights in American technology. The cameras can help police find stolen vehicles and missing people. They can also make it cheap and easy to reconstruct where innocent people have been.

The uncomfortable part is that both things can be true.

A traffic camera that works like a search engine

An automated license plate reader, or ALPR, does more than photograph a plate. According to the Electronic Frontier Foundation, ALPR systems collect the plate number along with the date, time, and location. Fixed cameras can scan every vehicle that passes, whether or not the driver is suspected of a crime.

Flock's own representative told PBS News that its cameras identify a vehicle's make, model, color, plate, and issuing state. The system can also record visible details such as bumper stickers and dents. Police can compare those observations with lists for stolen vehicles, outstanding warrants, hit-and-runs, or missing persons.

That is the useful version of the story. A camera notices a wanted vehicle, sends an alert, and gives officers a lead they might otherwise miss.

But the same infrastructure does not forget the other cars. PBS reported that Flock data is stored in a searchable cloud database for 30 days. A single scan says where one vehicle was at one moment. Thousands of scans can reveal routines: where someone sleeps, works, worships, receives medical care, attends a protest, or visits another person.

You do not need facial recognition to learn a lot about a life.

The debate has moved beyond hypothetical risk

Privacy advocates have warned about ALPR databases for years. In July 2026, the argument gained new attention as the ACLU published a campaign against the expansion of networked plate readers and documented disputes involving Flock's public claims and its customers' access to data.

One dispute concerns immigration enforcement. Flock says it does not work with U.S. Immigration and Customs Enforcement and that ICE does not have direct access to its cameras, systems, or data unless an agency that controls the data deliberately permits access. That distinction matters, but it does not settle the issue. The ACLU points to reporting that local officers and departments shared searches or results with federal immigration agencies even without a direct federal contract.

So the privacy question is not simply, "Does one federal agency have a login?" It is also, "Who can ask a local agency to run a search, and who audits that request afterward?"

The ACLU also cited audits in which officers entered vague reasons for searches. In one Oregon department, the recorded reasons reportedly included "investigation" 111 times and "hehehe" 20 times during September 2025. A required text box is not meaningful oversight if almost anything can be typed into it.

That example is almost absurd. It is also a useful lesson for software developers: a compliance field is not a control. A control needs validation, review, consequences, and evidence that someone actually checks it.

Why the convenience is so persuasive

Police departments do not buy these systems because they want a philosophical debate. They buy them because searching a camera network is faster than asking officers to watch roads manually.

In its July 2026 report, PBS presented both sides. Flock said its technology contributes to solving hundreds of thousands of crimes each year. Police officials described plate-reader alerts as practical investigative leads. Critics described broad collection, weak oversight, and the risk of abuse.

Faster investigations are a legitimate public benefit. But the company's crime-solving figures are company claims, not a reason to skip independent evaluation. Cities should ask how often an alert directly led to an arrest, how many alerts were false, how often stored data was searched without a warrant, and whether a less invasive method would have worked.

Technology procurement often collapses these questions into a sales presentation. A dashboard shows alerts, matches, and success stories. The people who were scanned but never suspected of anything do not appear on the dashboard at all.

The database is the product that matters

The camera gets the attention because people can see it on a pole. The database deserves more attention.

A camera limited to one police department and a short retention period creates one level of risk. A searchable network shared across agencies creates another. The value grows when more cameras and jurisdictions join. So does the damage possible from a careless search, compromised account, insider misuse, incorrect plate match, or policy change.

This is a familiar engineering problem. Centralization makes a system more useful and more dangerous at the same time. The larger the dataset, the more tempting it becomes to reuse it for purposes that were not part of the original pitch.

"We only keep it for 30 days" sounds reassuring until you ask how many trips one vehicle makes in a month, how many users can query the record, whether query results can be exported, and what happens when another agency requests help.

What responsible guardrails would look like

A city does not have to choose between unlimited surveillance and abandoning every investigative tool. It can impose limits before signing a contract.

Delete scans that do not match a legitimate hot list as quickly as technically possible.
Require a specific case number and a documented legal purpose for every historical search.
Ban searches related to constitutionally protected activity, immigration enforcement, reproductive health care, or religious attendance unless a court order clearly authorizes them.
Restrict data sharing to named agencies and publish those relationships.
Use independent audits instead of relying only on vendor dashboards and internal reviews.
Notify the public before cameras are installed and require elected officials to renew approval regularly.
Publish accuracy data, misuse incidents, search counts, and measurable case outcomes.
Include contract terms that let the city obtain logs, enforce deletion, and leave the network without losing access to its own audit records.

EFF recommends strict retention limits and access controls, and argues that one of the strongest protections is to retain nothing when a passing vehicle does not match a hot list. That approach preserves the real-time alert while reducing the creation of a month-long movement database for everyone else.

What you can ask in your own city

You do not need to be a privacy lawyer to ask useful questions. Search your city council's agenda and procurement records for "Flock Safety," "ALPR," "license plate reader," or "LPR." If the cameras are already installed, ask for the written policy, contract, retention period, approved sharing partners, search audit logs, and any reports about false alerts or misuse.

Then ask the question that procurement documents often avoid: how many people had their movements recorded for every case the system helped solve?

A city may decide that carefully limited plate readers are worth using. But that decision should be public, measurable, and reversible. It should not begin with a camera quietly appearing on a pole and end with residents discovering that their daily movements became searchable.

The most powerful surveillance systems rarely look dramatic. Sometimes they look like a small black box at an intersection, waiting for your next ordinary drive.

References

Originally published at https://blog.jenuel.dev/blog/that-camera-is-building-a-searchable-map-of-your-life

Thanks for reading! If you enjoyed this article and like this kind of content, you're always welcome to buy me a little coffee, but only if you'd like to. No pressure at all, and either way I'm truly grateful you stopped by. ☕️