Kansas ALPR Lawsuit: License Plate as GPS Tracker? [2026]

On July 31, 2026, a Wichita machinist named Mason Grimmett filed a lawsuit in Sedgwick County District Court that could reshape how courts think about automated license plate readers (ALPRs). The claim isn't about a data breach or a leaked database — it's a constitutional argument that Wichita's roughly 190-camera Flock Safety network turns every driver's plate into, in the complaint's own words, "the functional equivalent of affixing a GPS tracking device," and that operating it without a warrant is an unreasonable search.

That theory arrives at the same moment California courts are hearing an entirely different kind of ALPR case: class actions against Flock Safety and Motorola's Vigilant Solutions subsidiary, alleging those companies let out-of-state and federal agencies search millions of plate records without authorization. Together, the two legal tracks — one constitutional, one statutory — represent the broadest legal pushback ALPR technology has faced since it went mainstream.

This piece breaks down what Grimmett v. Wichita actually argues, how it differs from the California suits (and from the separate Bartholomew v. Parking Concepts litigation we covered previously), and what any of this means for the plates that show up in footage you publish yourself — dashcam clips, ride-share content, real estate walkthroughs, and social posts.

What Does the Kansas Lawsuit Actually Argue?

Grimmett v. Wichita argues that continuous, city-wide license plate logging by Wichita's ALPR network amounts to a warrantless search under the Kansas Constitution's search-and-seizure protections. The complaint's central line, reported by Reason, states that when coupled with Wichita's ALPR dragnet, a license plate "is now the functional equivalent of affixing a GPS tracking device, which constitutes a trespassory search."

The lawsuit was filed by the Kansas Justice Institute on behalf of Mason Grimmett, a Wichita machinist and member of the Sunflower Privacy Alliance, with litigation director Sam MacRoberts representing him, according to KCUR. The relief sought is a court declaration that the program is unconstitutional and an injunction stopping Wichita from operating it without a warrant — not statutory damages. That's the first thing that separates this case from nearly every other ALPR lawsuit filed this year: it's not chasing a per-violation payout, it's trying to shut the program down.

The "GPS Tracking Device" Argument, Explained

The theory rests on United States v. Jones, the 2012 Supreme Court case holding that police physically attaching a GPS device to a suspect's car without a warrant was a Fourth Amendment search. Grimmett's complaint argues that a dense network of cameras logging every plate that passes achieves the identical outcome — continuous location tracking of a specific vehicle over time — without ever touching the car. If a warrant is required to bolt a tracker onto a bumper, the argument goes, one should also be required to build the functional equivalent out of cameras and a database.

Why Chatrie v. United States Strengthens the Timing

The complaint leans on the Supreme Court's Chatrie v. United States, decided June 29, 2026 — barely a month before Grimmett was filed. According to Reason's reporting, Chatrie gave privacy advocates their strongest precedent yet for the idea that aggregated location data — even data a third party holds, even without any physical trespass onto a person's property — can trigger Fourth Amendment protection. Grimmett v. Wichita is among the first cases to apply that reasoning squarely to ALPR networks rather than cell-site or geofence data, which is what made it worth filing now.

How Big Is Wichita's Camera Network, and Has It Been Misused?

Wichita operates more than 190 Flock Safety cameras across the city, per KCUR's reporting. Every camera photographs every passing vehicle, timestamps it, geolocates it, and uploads a searchable record — building what the complaint calls a dragnet capable of reconstructing any driver's movements across the city over time, all without judicial oversight or a warrant requirement for individual queries.

The lawsuit doesn't argue this risk is theoretical. It cites two documented misuse cases: former Kechi police lieutenant Victor Heiar was convicted of unlawful computer use after using Flock access to track his estranged wife, and former Sedgwick police chief Lee Nygaard resigned after reportedly using the same system to track his ex-girlfriend and her boyfriend. Neither incident required a warrant, a supervisor's sign-off, or a documented investigative purpose — the officers simply had access and used it.

That's the practical argument sitting underneath the constitutional one: a database built for public safety becomes a stalking tool the moment access controls are looser than the surveillance capability itself. If you're unfamiliar with how Flock's cameras work day-to-day, our Flock Safety camera privacy guide breaks down what the system captures and what rights drivers actually have.

How Does This Differ From the California Flock Safety and Motorola Lawsuits?

The Kansas case and the California cases both target license plate surveillance, but through legally distinct doors, and understanding the difference matters if you're trying to follow where this litigation wave is headed.

Gibbs Mura's class action against Flock Safety, filed in San Francisco Superior Court, alleges that out-of-state and federal agencies queried San Francisco's Flock database more than 1.6 million times over a seven-month period — access the complaint says wasn't authorized under California's ALPR privacy statute, according to Stoll Berne's case coverage. A related class action against Motorola Solutions and its Vigilant Solutions subsidiary, filed in Cook County Circuit Court with an amended complaint July 16, 2026, alleges Motorola-run California systems shared drivers' precise location data with Customs and Border Protection, IRS Criminal Investigation, the U.S. Marshals Service, and other federal agencies, per ClassAction.org's reporting.

Neither California suit argues ALPR surveillance itself is unconstitutional — they argue the data sharing violated a specific state statute, and both seek per-violation statutory damages that could run into the billions given the search volumes alleged. We've also covered a third, related California theory: Bartholomew v. Parking Concepts, where a state Court of Appeal ruled that a business operating an ALPR system without a published privacy policy is itself a statutory violation, separate from any data-sharing claim. Three lawsuits, three distinct theories, one common target: license plate data moving further than the person whose plate it is ever agreed to.

What Would It Mean If Kansas Courts Adopt the GPS-Tracker Theory?

If a Kansas court accepts that city-wide ALPR logging is the functional equivalent of a GPS tracking device, the practical effect would be requiring a warrant — or at minimum individualized suspicion — before a city like Wichita can operate a network like this at all, not just before officers query a specific plate. That's a materially higher bar than most ALPR deployments currently clear, and it would put Kansas courts in tension with jurisdictions that have allowed similar systems to operate under a lower "no reasonable expectation of privacy on public roads" standard.

A ruling in Grimmett's favor wouldn't be binding outside Kansas, but constitutional theories like this tend to travel. Litigation groups tracking ALPR pushback nationally will likely cite a favorable Wichita ruling in future filings elsewhere, the same way California's statutory ALPR cases have already spawned copycat filings in other states with similar privacy statutes on the books.

Who Should Be Paying Attention to This Litigation Wave?

City and county governments operating or considering ALPR networks are the most direct audience — a favorable ruling for Grimmett would put warrant requirements on the table for any similarly dense deployment, regardless of state.

Privacy and civil liberties advocates now have a live test case applying Chatrie's aggregated-location-data reasoning outside the cell-site and geofence context it originated in, which matters well beyond Kansas.

ALPR vendors like Flock Safety and Motorola/Vigilant face compounding legal pressure from two directions at once: constitutional challenges to how their customers deploy the technology, and statutory claims about how the data gets shared afterward.

Everyday drivers, dashcam owners, and content creators aren't parties to any of these suits, but the underlying pattern — plate data collected for one purpose ending up searched, shared, or exposed for another — is exactly the risk you take on voluntarily every time you publish footage showing someone else's plate without redacting it.

What This Means for Footage You Publish Yourself

None of these lawsuits target individual creators, dashcam owners, or ride-share drivers — they target governments and vendors. But the underlying concern driving all three cases is the same one that should shape how you publish your own footage: license plate data, once it's public and searchable, moves in directions nobody who owns that plate agreed to and can't easily be pulled back.

Every dashcam clip, ride-share dropoff video, real estate walkthrough, or "day in the life" social post that shows a readable license plate contributes a small piece to that same searchable data trail — just voluntarily, and outside any government database's access controls entirely. A plate visible in a public YouTube video or TikTok clip can be scraped, indexed, and associated with a person's identity by anyone, with none of the oversight (however thin) that even a government ALPR system nominally has.

That's a gap you control directly, unlike the litigation above. A few scenarios where it shows up most often:

• Dashcam footage: Daily commute or road-incident clips routinely catch dozens of other people's plates in frame, especially in stop-and-go traffic or parking lots.
• Ride-share and delivery content: Drivers filming pickups, drop-offs, or "day in the life" vlogs capture surrounding vehicles' plates as a byproduct of the shot.
• Real estate video: Walkthroughs and drone flyovers of driveways and street parking often include neighbors' or clients' visible plates.
• General social content: Street scenes, car meets, parking lot b-roll, and travel vlogs routinely include plates nobody consented to have published.

Read our deeper breakdown on why license plate redaction matters for the legal and practical reasoning behind treating this as a standard publishing step, not an edge case.

How to Blur License Plates Before Publishing: A Step-by-Step Approach

1. Upload your clip to BGBlur. Processing happens entirely in your browser — footage is never sent to a third-party server to be analyzed, and files are deleted within 24 hours.
2. Let AI detect every plate automatically. BGBlur's motion-tracked detection follows plates across frames as vehicles move, turn, or change distance from the camera — no manual frame-by-frame masking required.
3. Add face blur in the same pass if needed. Bystanders caught in dashcam or street footage can be anonymized alongside plates using the same workflow — see our guide on blurring faces and license plates together in dashcam video for the combined process.
4. Review before exporting. Confirm every plate in frame — including partially visible or angled ones — is fully obscured.
5. Export up to 4K. Output supports MP4, MOV, and WebM, ready for social platforms, client delivery, or archival without extra conversion steps.

This workflow applies whether the source is a dashcam, a real estate walkthrough, or general social content — the point is the same: strip identifying plate data before footage becomes permanently searchable on the public web.

Pro Tips for Reducing Your Own Plate-Data Footprint

1. Default to blurring every plate in frame, not just the ones central to the shot — background vehicles count too.
2. Batch-process backlog footage. If you have months of dashcam or ride-share clips sitting unpublished, run them through redaction before you post any of them.
3. Treat parked cars the same as moving ones. A plate in a driveway shot is just as identifiable as one caught mid-drive.
4. Pair plate blur with face blur whenever bystanders appear in the same footage — the two categories of identifying data usually show up together.
5. Watch how this litigation develops. If Kansas courts side with Grimmett, expect more state-level challenges to ALPR programs — and more scrutiny generally on how license plate data gets collected, shared, and published.

The Bottom Line

Grimmett v. Wichita is the most direct constitutional challenge ALPR technology has faced yet, arguing that a dense enough camera network turns a license plate into a GPS tracker in every way that matters under the Fourth Amendment. It's running alongside, not instead of, the California statutory class actions against Flock Safety and Motorola/Vigilant over unauthorized data sharing, and a separate California case over missing privacy policies. Three different legal theories, one consistent throughline: license plate data is a lot more exposed, searchable, and misusable than most drivers ever assumed.

You can't control how a city deploys its ALPR network or who a vendor shares data with — but you can control what you publish. BGBlur's automatic, motion-tracked license plate blur strips readable plates from dashcam footage, ride-share content, real estate video, and social posts before they add another data point to a system nobody fully oversees. Try BGBlur's license plate blur tool on your next clip before it goes public.