Flock Safety vs. Rekor, Axon, and Motorola: The Privacy Questions That Matter

Automated license plate recognition is an industry, not one product. Flock Safety’s rapid roadside deployment has made “Flock camera” shorthand for ALPR, but agencies also use Rekor, Axon, Motorola Solutions’ Vigilant products, Genetec, PlateSmart, and other systems.

The comparison that matters is not which logo appears on the pole. It is how a system collects observations, turns them into searchable history, connects to other sensors or jurisdictions, and constrains access. Vendor marketing can help document capabilities, but only a local contract and policy reveal the deployment a resident actually lives under.

ALPR vendor comparison at a glance

This table describes public product positioning as of August 2026, not every configuration. Capabilities, retention, and sharing can be changed by contract, law, customer choice, and software release.

Flock Safety: fast fixed deployment and a broad sharing network

Flock is known for solar-powered, cellular-connected fixed cameras that can be installed without a city building its own network backbone. Its current product pages emphasize plate recognition, visible vehicle characteristics, natural-language search, real-time alerts, and multi-jurisdiction collaboration.

Flock says customers own and control their data, sharing is opt-in, every search is auditable, and 30 days is the default retention period. The company’s scale and sharing architecture are also the focus of its controversy. State and municipal audits have documented cases in which access did not match legal or local expectations. Flock says it has added controls and stronger state-specific safeguards.

Best question: Show us the actual sharing list, audit logs, configured retention, and state/federal controls for this account today—not the platform default.

Rekor: turn existing cameras into plate readers

Rekor Scout is software that can add plate and vehicle recognition to many existing IP traffic or security cameras. Rekor says Scout can run with cloud-hosted or on-premise components and identify plate number, make, model, color, and direction of travel. It supports real-time alerts, shared hotlists, and access to a data-sharing network.

That flexibility changes the visibility problem. Residents may look for a distinctive roadside ALPR pole while a city or private operator enables recognition on infrastructure already present. An inventory should therefore include software-enabled cameras, not only newly installed hardware.

Best question: Which existing cameras now perform ALPR, and does each feed stay on-premise, go to Rekor’s cloud, or enter a sharing network?

Axon: ALPR inside a real-time public-safety ecosystem

Axon expanded from body cameras and digital evidence into fixed ALPR hardware and real-time crime-center software. Axon Outpost supplies fixed plate and vehicle intelligence, while Axon Fusus can display ALPR alerts and searches alongside live video, officer location, dispatch information, and third-party feeds.

Integration can reduce friction in an urgent response. It can also make one platform a powerful window into many data sources. A privacy review that looks only at the ALPR camera misses how plate sightings are correlated, displayed, exported, and retained elsewhere.

Best question: Which systems can receive an ALPR hit, and does data copied into evidence, incident, or real-time intelligence systems inherit a new retention period?

Motorola Solutions and Vigilant: fixed, mobile, and large-scale vehicle intelligence

Motorola Solutions offers fixed, mobile, and in-car plate-reader hardware plus software under names including Vigilant PlateSearch and VehicleManager. Its product materials emphasize AI searches by make, model, color, damage, stickers, and other visible features. VehicleManager adds location history, association analysis, alerts, and access to large detection collections.

Motorola says customers control access, sharing, and retention. The important contract question is which datasets a customer licenses or receives. Some vehicle-location databases historically include detections from private or commercial sources as well as government cameras.

Best question: Does a search cover only agency-owned cameras, shared public agencies, commercial detections, or all of the above?

Ten vendor-neutral questions that matter more than the brand

1. What exact images and metadata are collected?
2. Can the system search by vehicle traits when no plate is known?
3. What is the retention period in the signed contract?
4. What events preserve a record beyond normal deletion?
5. Which agencies, federal entities, private operators, and vendor staff can access the account?
6. Is sharing opt-in per agency, per search, or enabled by a broader network setting?
7. Does the policy require a warrant, case number, suspected offense, or only a text reason?
8. How are false alerts confirmed before a stop or enforcement action?
9. Are audit logs reviewed independently and published?
10. What happens to data when the contract ends or the agency changes vendors?

The Associated Press reported that Border Patrol had, at different times, access to vehicle data from Flock Safety, Rekor, and Vigilant Solutions. That finding is a useful warning against treating a vendor swap as a complete privacy policy.