What Are Flock Cameras? What They See, Store, and Share

Flock Safety sells ALPR cameras and related public-safety software to police departments, neighborhoods, schools, and businesses. The cameras have become easy to spot on roadsides, often on a slim pole with a small solar panel, but the hardware is only the front end. The consequential part is the record created after a vehicle passes.

This distinction explains why the same system can be described as a useful lead generator by police and as mass location surveillance by civil-liberties groups. Both sides are talking about more than a photograph. They are talking about what can happen when many ordinary vehicle sightings become searchable across time and geography.

How a Flock camera turns a passing car into a searchable record

Flock’s current License Plate Reader Usage and Privacy Policy says its system stores the plate image, vehicle image, plate number and state, vehicle characteristics, date, time, and camera location. Flock also markets natural-language vehicle searches, allowing an investigator to look for visible features even when a complete plate is unavailable.

An alert is different from a historical search. A plate or vehicle on an authorized hotlist can generate a notification when it passes a camera. A retroactive search asks where a vehicle matching certain criteria was previously seen. The second use can reveal movement patterns when enough cameras and dates are available.

What Flock cameras collect—and what the company says they do not

According to Flock’s policy and product materials, a standard license-plate reader collects vehicle-facing data rather than driver identity: plate characters, plate state, vehicle make or type, color, visible features, timestamp, and location. Flock says the ALPR product does not use facial recognition and does not collect biometric data or driver information.

That limit matters, but it does not make a sighting anonymous. A license plate is designed to connect a vehicle to a registration record in authorized government systems. Repeated sightings can also expose sensitive inferences—where a car spends the night, which medical office it visits, which religious service or political event it attends—even when the camera never identifies a face.

How long is the data kept, and who can search it?

Flock states that its default retention period is 30 days and that data is automatically deleted after the period configured for the customer. Its June 2026 explanation of deletion controls says customers can have shorter or longer schedules depending on contracts, policy, and law, and that records preserved as evidence or under a legal hold may last longer.

The answer for a particular city is therefore not simply “30 days.” Residents need the signed contract, local ALPR policy, evidence-retention rules, and any state statute. Flock’s own guidance tells residents to confirm the setting with the local agency or governing body.

Access is similarly local in theory and networked in practice. Flock says customers own their data, choose their sharing relationships, and can change them. Search and access logs are designed to record the user, date, purpose, and query. Yet audits in Illinois and California found access that local agencies or state officials said should not have occurred. Those incidents turned configuration, vendor controls, and audit frequency into central policy questions.

Why Flock cameras are at the center of a privacy debate

Police departments point to stolen-vehicle recovery, missing-person alerts, and faster investigations. Those are concrete benefits. The controversy is whether the same infrastructure creates a nationwide movement database whose reach exceeds the rules set by any one city.

In August 2025, the Illinois Secretary of State reported that Customs and Border Protection had gained access to Illinois ALPR data in violation of state law and ordered that access shut off. In February 2026, the Oxnard Police Department suspended its fixed Flock cameras after an audit found nationwide queries could include local data despite California-only settings.

Flock has responded with new controls, standardized search-purpose fields, state-specific restrictions, transparency portals, and public explanations of its safeguards. Civil-liberties organizations argue that controls do not resolve the structural risk of collecting every passing vehicle first and justifying searches later. Read our sourced 2025–2026 controversy timeline for the sequence of audits, policy changes, and suspensions.

Seven questions to ask about cameras in your community

1. What is captured? Ask for the exact fields, images, and search capabilities—not only the phrase “license plate reader.”
2. What is the configured retention period? Confirm it in the contract and policy, including saved-evidence exceptions.
3. Who can search? Request the current list of local, out-of-state, federal, and private sharing relationships.
4. Is a warrant required? Many agency policies allow searches based on an entered reason rather than a warrant.
5. Who audits the logs? Ask how often, by whom, and whether findings are published.
6. What happens after misuse? Look for access revocation, discipline, notification, and public reporting procedures.
7. Who approved deployment? Determine whether elected officials debated the system, including pilots and donated equipment.

Those questions apply to every ALPR vendor. Flock is currently the most visible name, but Rekor, Axon, Motorola Solutions’ Vigilant products, and other systems can create similar location records. Our ALPR company comparison focuses on the policy questions that remain relevant when a city changes vendors.