Americans are increasingly aware, if not entirely comfortable, that they are being watched. That is the opening premise of a new Q&A from UCLA Luskin with Zachary Steinert-Threlkeld, which asks what comes next for Flock cameras. The published excerpt is brief, so this post does not attempt to summarize the interview itself. Instead, it uses the conversation as a prompt to explain how Flock cameras license plate surveillance works, where a VPN fits (and doesn't), and what ordinary residents can do about it.

How Flock cameras track vehicle movements

Flock Safety's cameras are automated license plate readers (ALPRs). Rather than watching for a specific suspect, they capture passing vehicles and turn them into searchable records. One search result describes the output as a searchable, time-stamped database of vehicles. A city page from Columbia, Missouri says the cameras record plate numbers and vehicle details such as make, model and color. Another critic-run site, Stop Flock, argues the systems go further, using features like bumper stickers and dents to build databases.

Those descriptions differ in tone, and that is worth noting. Cities tend to emphasize that the cameras do not capture identifiable images of people, while critics focus on the aggregate picture. A single plate read is not very revealing. Thousands of reads across a network of cameras can show when a vehicle leaves home, where it parks, and what routes it takes. One search result puts the number of ALPRs installed nationwide at over 100,000, which helps explain why researchers are asking about the next phase of the technology.

The core privacy question is not whether one camera sees one car. It is what happens when those sightings are linked, stored and searched.

Data retention and sharing: what the rules allow

The rules governing ALPR data are set largely at the local and state level, so there is no single answer. One headline in search results refers to Flock cameras tracking everyone for 30 days, but retention periods depend on the agency's contract, policy and applicable law. That is exactly why residents should look at their own city's documents rather than rely on national summaries.

Three questions matter most:

  • How long is data kept? Shorter retention limits how much history can be searched.
  • Who can search it? Access by other agencies widens the circle of people who can look up a vehicle.
  • Is every search logged? Audit logs are how the public learns whether the system is used as promised. One growing website, per a search result, now lets drivers see whether their plates have been searched in Flock camera databases, a sign that audit data is becoming a point of public interest.

The broader trend is familiar. Identity and location data collection expands, and public debate often trails behind. We saw a similar pattern in the rollout of mobile driver's licenses across more than 20 states.

What a VPN can and can't do against street-level surveillance

This is where readers of a VPN site deserve a plain answer: a VPN does not protect you from license plate readers. A VPN encrypts your internet traffic and masks your IP address from the sites you visit. A camera on a pole reads the plate on your car, which is a physical identifier that has nothing to do with your network connection. Turning on a VPN changes nothing about what that camera records.

Where a VPN does help is with online location signals. IP-based location is one of the ways sites guess where you are, as we explain in our look at how geo-blocking detects VPNs. That is a different problem from ALPR tracking, and it is worth keeping the two separate. Treating a VPN as a fix for street-level surveillance would give a false sense of security.

Other data sources, like location sharing on phones and social media tracking, are also part of the picture the UCLA Q&A describes. Those can be reduced through device settings and app permissions, but a plate on a public road remains visible.

How residents can audit and push back on local deployments

The most effective tools here are civic, not technical. Local governments typically decide whether to buy and how to configure these systems, which means residents have real leverage.

  • Request the contract. Public records requests can often surface the agreement with Flock, including pricing, data terms and sharing provisions.
  • Ask for the retention policy. Find out how many days data is stored and whether anyone can extend it.
  • Request audit logs. Logs show who searched the database and for what stated reason.
  • Attend council or commission meetings. Ask whether there is an oversight process, a public report on usage, or a sunset clause requiring renewal votes.
  • Check for independent tools. Some sites, as noted above, let drivers see whether their plate has been searched, though you should evaluate any such service carefully before entering personal information.

Proponents argue the cameras help police solve serious crimes, and that claim deserves a fair hearing alongside the concerns. Public records and open meetings are how a community weighs those tradeoffs with real facts.

What This Means For You

If you drive in the United States, your vehicle may already be logged by a networked camera, and a VPN will not change that. The practical impact depends on your local policies: how long records are kept, who can search them, and whether searches are audited. Those details are knowable, and they are often within reach of a simple records request.

Key takeaways

  • Flock cameras license plate surveillance works by building searchable, time-stamped records of passing vehicles.
  • Retention and sharing rules vary by place, so check your own city's documents.
  • A VPN protects your internet traffic, not your license plate.
  • Request your city's Flock contract, retention policy and audit logs, and raise questions at public meetings.
  • For another example of identity and location data collection growing with little public debate, read our piece on mobile driver's licenses and their privacy risks.