Gardner, Kansas Cancels Flock Cameras: What Changed [2026]

Gardner, Kansas turned off its license plate cameras this week. On Monday, August 17, 2026, the Gardner City Council voted to immediately deactivate the city's Flock Safety automated license plate readers (ALPR) and not renew the contract. By Tuesday, some of the units were physically covered to stop them recording. The Gardner Police Department confirmed it had notified Flock that the agreement was canceled.

It's a small-town story with a national pattern behind it. Gardner is one of roughly two dozen city councils that have voted to cancel, reject, or decline to renew a Flock contract since the start of 2026, and the reasons keep repeating: unclear vendor access to scan data, officer misuse, and a public that no longer trusts the "just for public safety" pitch. Gardner's specific trigger was a resident group's discovery that more than 1,200 third parties reportedly had some form of access to the city's plate data — a number the city itself apparently couldn't fully account for.

This piece covers what Gardner's vote actually stops (and doesn't), the vendor-access and misuse concerns driving the broader backlash, the retention and search changes Flock announced days earlier, and what any of this means if you're the one holding a camera that captures other people's plates.

What Did the Gardner City Council Actually Vote to Do?

The council agreed to immediately turn off the city's Flock cameras and to not renew the contract for the automated license plate-reading system. In a statement, the city framed it as "an ongoing evaluation of technology and resources to ensure the Police Department is using tools that provide the utmost value to the community and support its public safety operations" — administrative language for a decision that was clearly political as much as operational.

The Gardner Police Department confirmed it discontinued all Flock cameras and notified the provider the contract was canceled. Cameras began getting physically covered the day after the vote, which matters: a covered lens is a visible, verifiable signal to residents that the system is actually off, not just contractually terminated while still capturing footage on a lapsed agreement.

Why the Vote Happened Now

Bradley Steinmetz, who organizes the No Flock in Gardner movement, told the council that more than 1,200 vendors had access to the city's information through the Flock system, and that he did not know the identities of all those entities. That's the specific number that made this a Gardner story rather than a generic "surveillance is bad" complaint — a concrete, hard-to-defend figure about who could reach a resident's driving history, and nobody on the city's own side offering a clean answer.

Flock's platform is built around network effects: agencies can opt into sharing search access with other law-enforcement customers nationwide by default, which is how a single municipality's camera feed becomes queryable by departments hundreds of miles away, and in documented cases, by federal agencies the city never approved. MIT Technology Review's coverage of Flock's policy response describes this default-sharing architecture as the structural reason vendor-access numbers like Gardner's can balloon without any single council member voting for it.

Does Gardner's Vote Stop All License Plate Cameras in the City?

No — and this is the detail residents most often get wrong. Gardner council member Kelly Johnson said publicly that the council's action only applies to cameras controlled by the city itself. "Gardner can make decisions about the cameras and contract that belong to Gardner," Johnson said. "We cannot, however, turn off cameras that are owned and operated by Johnson County or the State."

That's not a loophole the council created — it's a jurisdictional reality of how ALPR networks are procured. A city council can cancel a purchase order; it cannot cancel a county sheriff's separate contract or a state highway patrol deployment, even if those cameras sit on roads inside city limits. Johnson said the city is still looking into what options it may have regarding cameras operated by other jurisdictions in and around Gardner — which means, as of this vote, the honest answer is that some Flock-style coverage around Gardner continues regardless of what the city council decided.

How Many Vendors Really Had Access to Gardner's Data?

Steinmetz's figure — over 1,200 vendors — is the headline number, and he was explicit that even he, as the person who surfaced it, couldn't name every entity on that list. That's the part worth sitting with: the concern isn't just "the police can see my plate." It's that an unknown, apparently large set of commercial and institutional third parties could query a scan of your car parked outside your own house, and no single public official in Gardner appears to have had a complete accounting of who that was.

This isn't unique to Gardner. Flock's own national retention and audit-log overhaul, announced August 13, 2026 — four days before Gardner's vote — was itself a direct response to reporting on exactly this kind of access sprawl. Flock's own announcement of its updated guardrails confirms the company is now requiring officers to enter a case number before running most searches and defaulting new deployments to a 7-day retention window instead of 30 — a tacit admission that the old defaults let data persist and circulate longer than most agencies, let alone residents, understood.

What Did Flock Change, and Does It Fix the Gardner Problem?

Not entirely, and the timing tells you why. Four days before Gardner's council voted, Flock Safety announced it would reduce its recommended default retention period from 30 days to 7, add mandatory case-number entry for searches, and roll out an "Evidence Mode" that keeps data tied to an active case in separate cold storage rather than letting it decay under the standard clock. Police1's coverage of the changes notes that most of these reforms become mandatory for law-enforcement customers on January 1, 2027 — existing customers keep their current retention settings unless they proactively adopt the new 7-day default before then.

That's the gap. A shorter retention window and a case-number requirement address how long data sits and whether a search leaves an auditable trail — they do nothing about how many external vendors a city's live feed is shared with in the meantime, which was Gardner's specific complaint. Retention policy controls the past; vendor-sharing settings control the present. Flock's August 13 changes are a real response to the misuse scandal, but they're a different lever from the one Gardner's residents were pulling.

Have Police Actually Misused This Data — Is This Just Theoretical?

No, it's documented and it's the reason the retention overhaul happened at all. A Washington Post investigation found that at least 69 police officials have been accused, charged with, or convicted of misusing Flock's system or other license-plate readers for unauthorized purposes. In at least 15 of those cases, someone outside the department — a victim, an activist, or a journalist — was the one who first identified the misuse, not an internal audit. The Post's reporting also found that departments across the country do not regularly audit their officers' Flock use, despite that being a practice the company itself recommends, and that some agencies have no formal training or written policy on how the technology should be used at all.

Earlier Post reporting documented the specific pattern behind those numbers: in at least 26 identified cases, officers used license-plate tracking to spy on wives, girlfriends, exes, an ex's new partner, or women they wanted to meet — using a public-safety tool as a personal surveillance system with no court order and, in most cases, no one checking the search log until it was too late. We go deeper on the mechanics of that abuse — including the Milwaukee officer who ran 179 unauthorized searches on his partner — in our breakdown of Flock camera vandalism and police data misuse.

Is Gardner Part of a Bigger Trend, or an Isolated Case?

Bigger trend. City-level trackers following Flock contract activity count roughly two dozen councils that have voted to cancel, reject, or decline to renew ALPR agreements since the start of 2026, spanning Rhode Island, Oklahoma, Nebraska, Arkansas, and now Kansas. The specific pressures vary by city — some cite officer misuse, some cite unauthorized out-of-state or federal data sharing, some cite budget scrutiny once the political cost outweighs the operational case — but the shape of the vote is consistent: a council that approved a contract with little public debate reverses course once residents surface exactly what the data-sharing terms actually allow.

If your own city just canceled, or is debating it, the part most coverage skips is what happens to the scans already taken. Cancellation stops future collection; it does not delete data that was already exported into a case file or shared with another agency before the vote. We cover that gap — and the much larger world of HOA, retail, and dashcam cameras that keep operating with zero ALPR statute governing them — in our guide to what happens to plate data after a Flock contract is cancelled.

For the legal theory courts are actually testing on whether this kind of tracking requires a warrant, our analysis of the Kansas ALPR lawsuit treating plate tracking as GPS-style surveillance and the parallel California ALPR lawsuit over license plate privacy walk through the Fourth Amendment arguments — both filed in the same state where Gardner just voted, which is not a coincidence.

If My City Cancels Flock, Am I Still Being Scanned?

Almost certainly, yes — for three separate reasons, all confirmed by Gardner's own council member.

1. County and state cameras aren't covered. As Johnson said explicitly, Gardner's vote reaches only city-owned equipment. Johnson County or Kansas state-operated readers, if deployed nearby, are untouched.
2. Neighboring cities that kept their contracts still cover the roads you drive. A single canceled contract doesn't create a gap-free zone; it creates one town's worth of missing coverage inside a regional network that mostly stayed intact.
3. Private cameras were never part of the debate. HOA gate cameras, retail parking-lot systems, storefront cameras, and consumer dashcams capture readable plates continuously and are, in most states, subject to essentially no ALPR-specific regulation at all.

That last category is the one most residents overlook after a win like Gardner's. The council vote addresses the government side of plate capture. It says nothing about the private cameras — including the ones your own household might run — that keep recording, and increasingly, keep getting posted.

What Should I Do If I'm the One Holding a Camera?

Whether you run a dashcam, a storefront security system, or a doorbell camera, the Gardner story is a reminder that the privacy conversation cuts both ways: it's not only about being scanned, it's about what you do with footage you capture of someone else's plate before you post it.

Step 1: Pull the Relevant Clip, Not the Full Recording

Export just the incident window from your dashcam, NVR, or camera app rather than an entire day's footage. Shorter clips process faster and limit how many uninvolved plates and faces you're handling at all.

Step 2: Run AI Motion-Tracked Detection Before You Publish

Upload the clip to BGBlur in your browser. Its AI detects plates and faces and tracks each one frame-by-frame as the vehicle moves, so a car crossing the frame stays covered the whole time instead of drifting out from under a static blur box — the failure mode that exposes plates in manually-edited clips.

Step 3: Use a Strength That's Actually Irreversible

A light pixelation square is often reversible with modern AI upscaling, because a license plate's character set is small and constrained — a reconstruction model has very few guesses to make. Use a high-strength blur that fully covers the plate region in every frame, not a light filter that "looks blurry enough."

✅ Motion-Tracked Plate and Face Blur

• Tracks each detected plate or face as its own object through the clip, so overlapping vehicles don't swap coverage
• Handles angle and scale changes as a car turns into or across frame
• Covers pedestrians and drivers visible through a windshield in the same pass
• Runs in a browser with no software installed, and uploaded footage is deleted within 24 hours

If you're a dashcam owner specifically, our universal dashcam blur guide covers export steps for most major brands before you get to the blurring step at all.

Honest Limitations

BGBlur isn't a substitute for the policy fight Gardner just had — it doesn't stop county or state cameras from scanning your plate on public roads, and it can't retroactively pull data that's already been shared with another agency. What it does is give you control over the one part of this you actually own: footage you capture and choose to publish. If you're processing thousands of hours of archived body-cam or fleet footage rather than individual clips, an enterprise redaction platform built for that scale, like Axon's evidence-management tools, will likely be more cost-effective than a browser-based consumer tool. For individual dashcam clips, security incidents, or social posts, BGBlur's free tier and browser workflow cover the common case without a software install or a subscription commitment.

Frequently Asked Questions

Why did Gardner, Kansas turn off its Flock cameras? The city council voted August 17, 2026 to immediately shut down city-owned Flock license plate readers and cancel the contract, after a resident campaign flagged that over 1,200 vendors reportedly had some access to the city's data and the council could not fully account for who they were.

Does the vote stop all plate cameras near Gardner? No. Council member Kelly Johnson confirmed the vote only reaches cameras Gardner itself owns — county- and state-operated readers, plus private cameras, are unaffected and continue operating.

What did Flock change in its national policy? On August 13, 2026, Flock cut its recommended default retention from 30 days to 7 and added a case-number requirement for searches, with most changes mandatory for law-enforcement customers by January 1, 2027.

Is officer misuse of this data a real, documented problem? Yes. A Washington Post investigation identified at least 69 police officials accused, charged, or convicted of misusing Flock or similar ALPR systems, including cases of officers tracking current or former partners.

How many other cities have canceled Flock contracts in 2026? Roughly two dozen city councils nationwide have voted to cancel, reject, or decline to renew Flock agreements since the start of 2026, making Gardner part of an accelerating pattern rather than an outlier.

If my town cancels Flock, does old scan data get deleted too? Not automatically. Cancellation stops future collection on that system, but data already exported into a case file or shared with another agency before the vote isn't recalled by the cancellation itself.

How do I blur license plates in my own footage before posting it? Upload the clip to BGBlur, let AI detection find and track plates and faces across frames, then export — the whole process runs in a browser with no software install and the source file is deleted within 24 hours.

The Bottom Line

Gardner's vote is a real, immediate win for the residents who pushed for it — the city's own Flock cameras are off, covered, and the contract is canceled. But the story underneath the headline is that a single municipal vote reaches exactly one layer of a much larger surveillance stack: it doesn't touch county or state readers, it doesn't touch neighboring cities that kept their contracts, and it doesn't touch the private cameras — HOA gates, storefronts, dashcams — that were never part of the debate in the first place.

Flock's own August 13 policy changes — shorter retention, case-number-gated searches — respond to the misuse scandal driving votes like Gardner's, but they don't address the vendor-access sprawl that was Gardner's specific complaint. If you're on the other side of a camera — recording footage that happens to capture someone else's plate — that's the layer you actually control. BGBlur blurs plates and faces in a browser with motion-tracked AI detection before you publish, so protecting the people in your footage doesn't depend on the outcome of the next council vote.