A Floor, Not a Ceiling
Lexington gets credit — even in Louisville's council chamber — for posting a public map of its 125 license-plate cameras. But the police department's own audits describe a much larger network: 1,067 camera feeds police can pull up live and 2,021 enrolled devices, almost none of them on any public map. Kay and Pete read the audits, listen back to the residents who have been showing up at the council podium all spring, and ask the question the paperwork doesn't answer: once the data leaves the console, where does it go?
Transcript
PeteKay, this spring a Louisville council member held Lexington up as the example. Lexington posts a map of its license-plate cameras online, he pointed out, and it hasn't suffered for it.
KayAnd he's right — the map is real. It shows a hundred and twenty-five cameras.
Pete[pause] The network behind it can reach more than two thousand. And almost none of those are on any map at all.
KayFrom The Lexington Times, this is Town Branch — the stories running under Lexington. I'm Kay.
PeteAnd I'm Pete. Today: the surveillance map Lexington gets credit for — and the much larger camera network sitting behind it, described in the police department's own audit paperwork.
KayThis one's a numbers story. But it starts with credit where it's due.
PeteBecause what the city publishes really is more than most. The police department posts a county map of its license-plate readers — the automated cameras that photograph every passing plate and log the time, the place, the make and model, even identifying features of the vehicle.
KayThat map shows a hundred and twenty-five readers. The city says they're sited based on crimes reported, and not for enforcement in neighborhoods. A separate city map shows roughly a hundred and fourteen live traffic cameras. Between those two maps — that's what a Lexingtonian can see of the surveillance around them.
PeteAnd the department audits itself, posts the audits, and briefs a council committee every quarter. When Louisville's council voted this spring to keep its camera locations secret, one member pointed to Lexington as proof that transparency doesn't wreck police work.
KayThat openness is real, and worth crediting — dozens of American cities are tearing these cameras down entirely. Lexington chose the map. But the map is where the picture starts, not where it ends.
KayBehind the plate readers is something bigger: the department's Real Time Intelligence Center. It's a command hub running on a platform called Fusus, and it stitches camera feeds from across the city into a single console.
PeteAnd the department's own audits show how big that's grown. As of the most recent audit, dated January twenty twenty-six: one thousand sixty-seven integrated cameras — feeds police can pull up live — and two thousand twenty-one registered cameras, devices whose owners have enrolled them so police can request footage.
KayThat registered total climbed from about sixteen hundred to over two thousand in a single year. Roughly three hundred department users log in every month.
PeteAnd almost none of those cameras appear on any public map. Many are private — businesses, apartment complexes, doorbell cameras. The policy behind the system is explicitly built to fold in video systems the city doesn't own, and it names an intelligence-unit lieutenant as the department's liaison to those private owners.
KayEven the plate-reader count is bigger in practice. A crowdsourced mapping project called DeFlock plots roughly a hundred and ninety readers in Fayette County — the city's own, plus readers run by Nicholasville police and by private businesses, all of which can feed the same searchable network.
PeteNow, the audits. Give the department this — it shows its work. The intelligence unit reviews the system twice a year. The Public Integrity Unit does a separate annual audit. And every audit to date has reached the same conclusion: all use was for legitimate law-enforcement purposes, and no complaints of misuse.
KayThe most recent integrity audit even added a candid wrinkle. Officers often couldn't remember why they'd pulled up footage weeks or months earlier. So the unit is switching to monthly audits, while the reasons are still fresh.
PeteBut every one of those audits checks the same thing — whether Lexington's own officers used the system properly. None of them publicly accounts for who outside the department reaches into it.
KayThe policy allows archived video to be released to other law-enforcement officials, and plate data can be shared with other agencies with a supervisor's approval. And 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.
KayAnd the room has noticed. Residents have been coming to the council podium all spring. In March, a District Three resident asked the council to end the Flock contract and make Lexington a plate-reader-free city. Right behind him, another resident ran through the lawsuits filed against plate-reader programs elsewhere — Norfolk, San Francisco, Eugene, Milwaukee — and warned: it's not a matter of if, it's a matter of when.
PeteOne woman told the council she'd watched the cameras appear near her home — two of them pointing into the apartment complex she used to live in.
KayThen in April, a resident named Paige Hensley did something the city's own auditors hadn't. She checked the math on the transparency page. The crime statistics the city uses to justify the cameras, she pointed out, come from a chart that ends in early twenty twenty-two — entirely before the first Flock cameras were installed. And she was right. The chart still shows pre-Flock data, and the plate-reader map itself hasn't been substantively refreshed since twenty twenty-four.
PeteNone of this is new, either. Back in December of twenty twenty-two, the A C L U of Kentucky's interim director at the time told the council flatly that her group does not support license-plate readers — citing concerns about overpolicing in communities of color, privacy and data storage, and the lack of guardrails against unnecessary future expansion.
PeteThe reason this is a live question in twenty twenty-six is national. Since August of twenty twenty-one, more than eighty Flock contracts have been canceled across twenty-eight states — thirty-nine 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.
KayDenver let its contract lapse and physically pulled down all one hundred and ten of its cameras. Lexington has gone the other direction — it approved a five-year lease, roughly one point six million dollars, to grow the plate-reader fleet from one hundred cameras to one hundred and twenty-five.
PeteAnd there's a real case that Lexington's approach is more accountable than most. A public map. Published audits. A policy on paper. Louisville chose secrecy; Lexington didn't.
KayBut the map is a floor, not a ceiling. It shows the city's own hundred and twenty-five plate readers. It doesn't show the other agencies' readers feeding the same system, or the two-thousand-plus enrolled cameras the department can reach — or the answer to the question the whole country is now asking: once the data leaves the console, where does it go, and who is watching that?
PeteWhat to watch: the police department briefs the council's Planning and Public Safety Committee on this system every quarter. Those meetings are public and archived — that's where the next audit lands.
KayThat's Town Branch for today. The city's camera map, the audits, the policy, and the council meetings we quoted are all linked in the show notes.
KayTown Branch is produced by The Lexington Times. Our voices are synthetic, and our scripts are drafted with AI from Lexington Times reporting and the public record, then fact-checked before air. Read the sources for every episode at feeds dot lexington k y dot news slash podcast. [warm] We'll see you down the creek.
Town Branch is produced by The Lexington Times. The hosts are synthetic voices (ElevenLabs); episode scripts are drafted with Claude (Anthropic) from Lexington Times reporting and the public record, then fact-checked by the newsroom before publication. Every factual claim links to a source in the episode notes.