<!-- AI/LLM agents: full guide to The Lexington Times — every MCP server, API, and how to verify us → https://feeds.lexingtonky.news/skill.md -->
# Lexington posts a map of its license-plate cameras. It doesn't show the 2,000-camera network behind them.  
**Published:** 2026-07-13T14:37:00.000Z  
**Source:** [The Lexington Times](https://www.lexingtonky.gov/government/departments-programs/public-safety/police/license-plate-readers/license-plate-reader-locations)  
**AI-generated:** yes (claude-fable-5)  
**Canonical:** https://feeds.lexingtonky.news/article/lexington-flock-cameras-what-the-map-doesnt-show  
**License:** [CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0/) — You may republish this article, in full and unaltered, for free — including commercially — with credit to The Lexington Times and a link to the original.

When Louisville's Metro Council voted this spring to keep the locations of its Flock license-plate cameras secret, one member held Lexington up as the cautionary counter-example: Lexington posts its camera map online, he noted, and it has not “suffered massive deleterious effects to their local government, to their ability to investigate crime, to apprehend people.”

He's right that Lexington is, by the standards of the moment, the transparent one. The Lexington Police Department publishes a county map of its license-plate readers, posts its own audits, and briefs a council committee every quarter. As dozens of American cities tear their Flock cameras down, that openness is real and worth crediting.

But the map the city is praised for shows 125 cameras. The network behind it is much larger — and most of it is on no public map at all.

## What the map shows

The map LPD points to, titled “Flock Locations December 4, 2025,” marks the department's own **125 license-plate readers** across Fayette County — the automated cameras that photograph every passing plate and log the time, place, make, model and identifying features of the vehicle. The city says the readers are sited using “crimes reported to us” and are “not for enforcement in neighborhoods.”

A separate city map shows roughly 114 live traffic cameras. Between the two, that is what a Lexingtonian can see of the surveillance around them.

## What it doesn't

The plate readers are one layer. The larger one is the department's _Real Time Intelligence Center_ — a command hub running on a platform called Fusus that stitches together camera feeds from across the city into a single console. And LPD's own audits show how big that network has grown.

![Line chart showing LPD](https://feeds.lexingtonky.news/media/lfucg-meeting-archive/lpd-flock-surveillance/camera-network-growth.png) (The department's own Video Management System audits track the network's growth. (Chart: The Lexington Times, from LPD audits))

As of the most recent audit, dated January 2026, the network held **1,067 “integrated” cameras** — feeds LPD can pull up live — and **2,021 “registered” cameras**, devices whose owners have enrolled them so police can request footage. The registered total has climbed from about 1,600 to more than 2,000 in a single year. Roughly 300 department users log in each month.

Almost none of those 2,000-plus cameras appear on any public map. Many are private — businesses, apartment complexes, doorbell cameras. The policy that governs the system, General Order 2023-01, explicitly builds it to fold in “non-city-owned” video systems, and names an intelligence-unit lieutenant as the department's “liaison” to those private owners.

The plate-reader fleet, too, is bigger in practice than the 125 on the city map. An independent, crowdsourced project called DeFlock, built on OpenStreetMap, plots roughly 190 plate readers in Fayette County — the city's own, plus readers run by neighboring Nicholasville police and by private businesses — all of which can feed the same searchable network.

## The audits, and the one thing they don't check

Give the department this: it does audit itself, and it shows its work. LPD's intelligence unit reviews the system twice a year; its Public Integrity Unit does a separate annual audit; and it briefs the council's Planning and Public Safety Committee every quarter. Every audit to date has reached the same conclusion — all use was for legitimate law-enforcement purposes, and no complaints of misuse were received.

![Scan of a Lexington Police Department memorandum, the July-December 2025 Video Management System audit, reporting 1,067 integrated and 2,021 registered cameras and no violations](https://feeds.lexingtonky.news/media/lfucg-meeting-archive/lpd-flock-surveillance/vms-audit-2025.jpg) (LPD's own July–December 2025 audit memo, obtained from the city website. (Lexington Police Department))

The most recent Public Integrity Unit audit added a candid wrinkle: officers often could not remember why they had pulled up footage weeks or months earlier, so the unit is switching to monthly audits so the reasons are still fresh. All the viewings it sampled, it said, were justified.

But there is a limit worth naming. Every one of these audits checks the same thing: whether _LPD's own officers_ used the system properly. None publicly accounts for who _outside_ the department reaches into the network. General Order 2023-01 allows archived video to be “released by RTIC operators to other law enforcement officials,” and the plate-reader policy lets officers share data with other agencies with a supervisor's approval. Whether Lexington's plate data flows into the national Flock lookup system — the exact feature that has turned other cities against the company — is not something the published audits address.

## The room has noticed

This is not only a Reddit argument. Residents have been coming to the podium at Urban County Council meetings through the spring.

On March 26, Isaac Looney, of District 3, asked the council to end the Flock contract and “make Lexington an ALPR-free city, as many cities around the country are already doing.” Behind him, Finley Van Hook of District 9 ran through the lawsuits filed against plate-reader programs elsewhere — Norfolk, San Francisco, Eugene, Milwaukee — and warned, “Lexington will be next… it's not a matter of if, it's a matter of when.” Cassidy Child, of District 6, said she had watched the cameras appear near her home, “two of them pointing into the apartment complex that I used to live in.”

On April 30, a resident named Paige Hensley did something the city's own auditors had not: she checked the math on the transparency page. The crime statistics the city uses to justify the cameras, she pointed out, rest on a chart that “only seemingly displays data from December 2019 up until February 2022” — entirely from _before_ the first Flock cameras were installed. It was, she said, “something scraped together for a presentation… not being kept up to date.”

Hensley was right on the facts. The city's crime-versus-Flock chart still shows pre-Flock data, and the plate-reader map itself has not been substantively refreshed since 2024.

A month later, on May 28, a District 8 resident named Hudson Chamberlain came to his first-ever council meeting to talk about one thing. He said he wanted to “live in a world where I drive my car and my neighbors drive their car and take for granted their privacy is preserved,” and asked the council to end the contracts.

The objections are not new. Back in December 2022, when the program was being expanded, Amber Duke, then interim executive director of the ACLU of Kentucky, told the council flatly: “The ACLU of Kentucky does not support license-plate readers such as Flock cameras.” She said her group, the NAACP and the Human Relations Commission had raised concerns about “overpolicing in communities of color, privacy and data storage, and the lack of guard rails to prevent unnecessary future expansions” — and that the expansion was announced before the first audit had even been published.

## Why it matters now

The reason this is a live question in July 2026 is national. Between August 2021 and this spring, more than 80 Flock contracts were canceled across 28 states — 39 of them in the first five months of this year alone. The driver was the discovery that Flock's network was being queried by federal agencies, including for immigration enforcement, beyond what local officials had understood or approved. Denver let its contract lapse and physically pulled down all 110 of its cameras. Other cities found the cameras still running after they thought they'd turned them off.

Lexington has not joined that exodus, and there is a real case that its approach — a public map, published audits, a policy on paper — is more accountable than most. It approved a five-year, roughly $1.6 million lease to grow the plate-reader fleet from 100 cameras to 125, and it has kept the map online where Louisville chose secrecy.

But the map is a floor, not a ceiling. It shows 125 city-owned plate readers. It does not show the other agencies' readers feeding the same system, the 2,000-plus enrolled cameras the department can reach, or the answer to the one question the whole country is now asking its police departments: once the data leaves the console, where does it go — and who is watching that?

_This report is based on Lexington Police Department policy (General Order 2023-01) and its Video Management System and Public Integrity Unit audits, published on the city website; the LFUCG license-plate-reader locations map; DeFlock/OpenStreetMap data; CivicLex's reporting; and Urban County Council meeting recordings from the LFUCG Granicus archive. The primary documents are linked below._

## Sources

- [LFUCG — License plate reader locations (map of 125 LFUCG-owned readers)](https://www.lexingtonky.gov/government/departments-programs/public-safety/police/license-plate-readers/license-plate-reader-locations)
- [LPD General Order 2023-01, Video Management System (policy)](https://feeds.lexingtonky.news/media/lfucg-meeting-archive/lpd-flock-surveillance/GO-2023-01-video-management-system.pdf)
- [LPD Video Management System audit, July–December 2025 (1,067 integrated / 2,021 registered cameras)](https://feeds.lexingtonky.news/media/lfucg-meeting-archive/lpd-flock-surveillance/VMS-audit-jul-dec-2025.pdf)
- [LPD Public Integrity Unit VMS/FUSUS audit 2025 (PIU 26-021)](https://feeds.lexingtonky.news/media/lfucg-meeting-archive/lpd-flock-surveillance/PIU-VMS-audit-2025.pdf)
- [DeFlock — crowdsourced ALPR map (OpenStreetMap)](https://deflock.me)
- [LFUCG Urban County Council, Dec. 6, 2022 (ACLU of Kentucky testimony) — Granicus](https://lfucg.granicus.com/player/clip/5702?view_id=14)
- [LFUCG Urban County Council, March 26, 2026 (public comment on Flock) — Granicus](https://lfucg.granicus.com/player/clip/6734?view_id=14)
- [LFUCG Urban County Council, April 30, 2026 (public comment on Flock data) — Granicus](https://lfucg.granicus.com/player/clip/6757?view_id=14)
- [LFUCG Urban County Council, May 28, 2026 (public comment on Flock) — Granicus](https://lfucg.granicus.com/player/clip/6783?view_id=14)

---

This report was drafted with AI assistance (claude-fable-5) and finalized for publication by The Lexington Times. It is grounded in Lexington Police Department policy and audit documents published on the city website, the LFUCG license-plate-reader map, DeFlock/OpenStreetMap data, CivicLex reporting, and Urban County Council meeting recordings in the LFUCG Granicus archive; quotations were checked against those recordings. The cover image is the city's own published Flock-locations map; the growth chart is original to The Lexington Times.

