Resident Data Collection: The Research
What Overland Park collects, whether the tools work, what can go wrong, and what other cities have done.
What does Overland Park collect about residents, do the tools work, and what can go wrong?
Automated resident data collection means any system that automatically records, identifies, or describes people or vehicles without individual suspicion, and keeps that information searchable. Automated license plate readers (ALPRs) are the clearest example. They are cameras that photograph license plates and record when and where a vehicle passed.
This page carries the full picture. The first six sections are open. The reference sections below them fold shut, with the heading showing, for officials, reporters, and advocates who want the detail. Our proposal says what we're asking for, and the issue page is the short version.
What Overland Park Collects Today
Overland Park police run 37 fixed plate readers and readers in 110 patrol cars, can search privately owned Flock cameras in the city, and operate a Real-Time Information Center (RTIC) that brings camera feeds together.
- 37 fixed readers (Genetec) at eight sites, an eight-camera Axon fixed test site (pre-production; OP owns the data, not the devices), and 110 vehicles with Axon Fleet 3; 25 to 35 patrol cars with readers are on the road at any time. (OPPD deck, transcript, KCUR)
- Using plate readers since 2011. (KCUR)
- Search access to privately owned Flock cameras in the city; the city doesn't own Flock hardware. (KCUR)
- Axon contract: 10 years, $22.4 million, approved 9-0 in September 2025. Covers body cameras, Fleet 3 patrol car cameras, the ALPR beta, Fusus, a dashboard, and unlimited Axon cloud storage. (Johnson County Post)
- RTIC: QuikTrip gave $500,000 (July 2025). It opened in early 2026. Runs on Axon Fusus and includes traffic cameras and plate readers. (Johnson County Post, FOX4, KSHB)
Still open: Axon contract terms on data ownership, retention, and AI training; RTIC operating policy; agreements governing access to private Flock cameras. Each is an open records request (see Open Questions and KORA Requests).
Do These Tools Work?
They help recover stolen cars, find missing people, and generate leads in serious cases. Whether they prevent crime hasn't been shown.
What They Do Well
- OPPD's own cases: a missing person found, an armed robbery suspect charged, a multi-state burglary series solved (suspect pleaded guilty). (deck slides 19 to 21, transcript)
- Austin's City Auditor (three quarters of a pilot): 165 arrests, approximately 133 prosecutions, one missing or endangered person recovered, and zero incorrect or unjustified stops among those reviewed.
- Kansas law enforcement testimony to the Legislature: stolen vehicles, felony arrests, kidnapping and trafficking victims. (KLRD)
The Scale of It
- Austin: an estimated 75 million Flock and Axon scans (the department's estimate; the auditor said the true number can't be verified) produced 13,122 hotlist matches and 165 arrests, about one arrest per 450,000 scans (our arithmetic).
- California State Auditor: 99.9% of the 320 million images LAPD stored were of vehicles not on any hotlist when photographed.
Deterrence
No peer-reviewed study on whether plate readers deter crime turned up in our research, so we make no claim either way.
What Can Go Wrong?
Officers misusing the system for personal reasons, distant agencies searching local data at huge scale, wrongful stops from misread plates, and breaches. Several of these have happened in Kansas or Missouri.
Personal Misuse
- Sedgwick, KS: Police Chief Lee Nygaard resigned after using Flock to track his ex-girlfriend and her new boyfriend more than 200 times over several months. (KCUR)
- Kechi, KS: Lt. Victor Heiar pleaded guilty to computer crime and stalking after using Flock to track his estranged wife. (KCUR)
- Bonner Springs, KS: a detective allegedly used plate readers to track his estranged wife and two men; he was charged in March 2026. (KCUR)
- Joplin, MO: an officer was fired in January 2026 for misusing Flock data; an activist group found one plate had been searched 395 times. (KCUR)
- St. Charles County, MO banned Flock after a former civilian employee abused system data. (STLPR)
- The Institute for Justice maps 275 cases of data abuse in the U.S. since 2018, five of them in Kansas. (KCUR)
Speech and Retaliation Concerns
- Lenexa, KS: police tracked columnist Canyen Ashworth with the city's plate readers after he wrote a column criticizing the department, in a criminal investigation into posters hung on city property. He wasn't the person in the video, and nobody was charged. His plate was recorded about 150 times in less than two years. (KCUR)
Scale of Outside Searching
- Kansas City, KS Flock data was searched 1.1 million times in six months; 198,000 of those by Houston, Dallas, and the California Highway Patrol. (KCUR)
What OP's Own Reporting Will and Won't Show
- The planned 2027 dashboard (sample on deck slide 18, another agency's Axon page) reports retention settings, reads and hits stored, hits by hotlist category, and device counts. Nothing on searches, audit results, outside access, private Flock searches, or Genetec. (slides)
- The sample's fine print says search audit logs are "stored indefinitely." Another agency's page, so it doesn't prove OP's practice, but it raises the question of how long OP keeps its own search records. OP's practice is open.
- The Chief asked Axon to build an alert for an officer searching the same plate repeatedly; targeted for early 2027. (meeting video)
What Outside Reviews Found
- Seattle, Washington, Inspector General: no justification given for about 47% of Seattle police's 2025 searches, on Axon's platform.
- Austin City Auditor: some searches lacked case numbers. The audit gives no percentage.
- California State Auditor: none of four agencies audited their own usage; three shared data with hundreds of entities without checking their right to it.
Wrongful Stops
- Texas: Lindsey Isaacs spent 13 days in jail after a Flock read placed her car near a crime; she testified at the Senate hearing.
Breaches and Security
- Benn Jordan's testimony: no required multifactor authentication; Flock police logins for sale online.
- 404 Media found exposed livestreams for at least 60 Flock cameras (via KCUR).
- Lawmakers asked the FTC to investigate Flock's security.
- Flock's contract terms grant it a perpetual license to "aggregated data." (Austin audit)
What Other Cities Have Done
Cities have gone three directions: ended their programs, paused or tightened them, or set rules in law. Overland Park has tightened its policy but hasn't put anything in law.
Ended Programs
- Gardner, KS turned off its Flock cameras and canceled its Flock contract (August 2026). (Johnson County Post)
- Weston, MO canceled its Flock contract five months after approving it, after residents objected (spring 2026). (KCUR)
- Seattle, Washington, shut off its police plate readers in March 2026 after a new state law.
- The ACLU says dozens of communities have canceled Flock contracts, suspended programs, or switched off cameras. That's an advocacy group's estimate.
Paused or Tightened
- Lee's Summit, Missouri, police now require a memorandum of understanding before sharing plate reader data.
- Austin, TX let its Flock contract lapse in June 2025 after community pushback; it still uses plate readers through Axon. (EFF)
- Parkville, MO suspended its 16-camera Flock program for a review of privacy, data access, and data sharing (September 2026). (KCTV5)
- Overland Park's October 2026 policy.
Set Rules in Law
- Minnesota: 60-day limit, a public log of use, independent audit every two years, suspension for noncompliance.
- Missouri: executive order covering state agencies and state-funded police, 30-day deletion, no vendor sales or sharing for non-law-enforcement purposes, no facial recognition pairing (September 2026). Other local agencies are encouraged to follow it. Critics said much of it was already standard practice.
- CCOPS ordinances (council approval before acquiring or using surveillance tech): about two dozen cities, including St. Louis, Missouri; Madison, Wisconsin; and Detroit, Michigan.
- Chula Vista, CA: council approved a use policy for its Fusus-based real-time crime center.
- Washington State (2026): AG registration, no immigration use.
- Federal: Hawley's Stop Flock Abuse Act (Sept 30, 2026); Ban Flock Act, H.R. 10691 (Oct 2, 2026).
Kansas
No state law on use. The Kansas Justice Institute is suing Wichita over its roughly 200-camera Flock network under the Kansas Constitution (Grimmett v. City of Wichita, filed July 30, 2026, in Sedgwick County District Court; pending as of October 2026). KCUR expects the Legislature to take it up in 2027 (a prediction).
Timeline
- 2021 to 2022 SB 305 (policy and audit requirements) fails; SB 434 (records exemption) passes.
- October 2024 Doreen Jokerst becomes chief.
- 2025 Austin audit (May); Austin lets its Flock contract lapse (June); QuikTrip RTIC grant (July); Axon contract approved (September).
- February 2026 KCUR's Lenexa investigation; we publish our RTIC governance proposal.
- Early 2026 RTIC opens.
- August to October 2026 Gardner ends Flock; Parkville suspends it; Lee's Summit restricts sharing; Missouri executive order; Senate hearing; federal bills.
- October 2026 OPPD's revised policy and the committee presentation.
What We Proposed, What's Now Policy
Our February 2026 governance proposal covered the whole Real-Time Information Center. The department's October policy covers license plate readers, and it puts several of the same protections in place. That's a win for everyone who asked questions, spoke up, and pressed for answers, and for a department that listened. The protections not yet adopted are mostly about who decides, which is what our current proposal asks for.
| February Proposal | October Policy | Status |
|---|---|---|
| Section 13: facial recognition prohibited | Prohibited | Adopted |
| Section 18: plate reader data deleted after 30 days | Kept 30 days, down from a year | Adopted |
| Section 14: every search tied to an incident | A case number and a specific reason on every search | Adopted |
| Section 16: First Amendment activity protected | Free speech and religious activity can't be monitored | Adopted |
| Section 8: no standing data feeds; sharing only on case-by-case written requests | A formal agreement or written request; sharing paused until agreements are written | In part |
| Sections 17 and 23: audit log, discipline for misuse | Searches "audited every 30 days by our Technology Captain"; misuse referred for discipline or to the District Attorney | In part |
| Section 19: annual public report | A public dashboard is planned for 2027 | In part |
| Sections 1, 2, and 4: Council authorization, impact reports, a civilian advisory panel | Not in the policy | Not yet |
| Sections 6 and 10: city data ownership, a public registry of private camera integrations | Not in the policy | Not yet |
Our Case in Full
Why We're Starting With Rules
Residents who aren't suspected of anything shouldn't have their movements recorded and stored by their government. That's where we start.
We also know these systems are already part of how Overland Park keeps people safe, and the department's new policy is a real step toward protecting residents. So we're focused on building on that work with the strongest protections we can put in place now. We don't see them as the finish line.
It's much easier to start collecting data than to stop, and each new camera, data partner, or software feature makes the system harder to change later. That's why rules set by elected officials today should be a floor, not a ceiling, and why the burden should always be on the city to justify the data it keeps.
How We Got Here
We started paying attention as news reports showed how quickly the private sector's ability to track individuals was growing.
Then in July 2025, Overland Park announced plans for a Real-Time Information Center, supported by a grant from QuikTrip. In February 2026, we published a governance proposal focused on it, because a center that brings together camera feeds and data deserves clear rules from the start.
Soon after, the country erupted over Flock, one of the largest plate reader companies. Cities canceled contracts. Reporters documented officers misusing these systems to track people. Closer to home, Lenexa police used the city's plate readers to track a columnist who had criticized the department; nobody was charged. In September 2026, a U.S. Senate subcommittee held a hearing on plate readers, and senators from both parties raised concerns.
In October 2026, the Overland Park Police Department adopted a stronger license plate reader policy, and it's a real step forward. But following all of this closely taught us something: the problem was never one company, one camera, or one building. It's how much data about residents gets collected, how long it's kept, and who decides.
What We Mean
Why the Data Matters More Than the Device
One plate read tells you very little: a car passed a corner at a certain time. Thousands of them, kept and searchable, start to show where someone lives, works, worships, and who they spend time with. Privacy experts call this the mosaic effect. The U.S. Supreme Court relied on similar reasoning in Carpenter v. United States (2018), when it held that police generally need a warrant to get someone's historical cell phone location records.
It's Already More Than License Plates
At the October 2026 Public Safety Committee meeting, Police Major Keith Jenkins explained that one of the department's search tools can look for vehicle details like a roof rack or a window sticker. It doesn't work well at night or after snow, but the capability is there. Some vendors market searches by bumper stickers and other unique features. These systems describe vehicles, not just plates, and the capabilities keep growing.
Software Is What Makes a Camera a Plate Reader
Kansas law defines a license plate reader as cameras combined with software that converts plate images into computer-readable data. In other words, the law itself says the software is what makes it a plate reader. Rules written around specific devices can be sidestepped by running other camera images through new software.
That's why purpose matters. Overland Park's traffic cameras post updating images so residents can check road conditions, and that's a genuine public service. Images collected to manage traffic shouldn't quietly become a tool for identifying people without elected officials deciding that's appropriate.
A Gap in State Law
Kansas law lets police keep the locations of plate readers closed to the public, a protection the police department described as preventing stalking. Meanwhile, the city publishes images from traffic cameras at known intersections. The difference between the two is software.
The state law also governs only what can be disclosed, not how data can be used. No Kansas law sets rules for how plate reader data is collected, kept, or searched. Those rules are left to each department.
Where We Draw the Line
Real-time tools like traffic cameras and the city's Real-Time Information Center help the city respond when something happens. Our concern starts when data is kept and searched long after, or repurposed to identify people it was never collected to track. Those decisions should belong to elected officials.
What This Means for the Real-Time Information Center
The Real-Time Information Center brings camera feeds and data together so staff can coordinate during active incidents. Used that way, it's a valuable tool. It would raise new concerns if it began storing feeds from many sources and making them searchable later, running analysis across stored footage to describe vehicles or people, or connecting private cameras without rules on what's kept. We think it should stay a real-time tool unless elected officials approve more.
Everything That Changed in October
- Retention: cut from one year to 30 days (it was two years before 2026)
- Facial recognition: prohibited
- Protected activities: data can't be used to monitor free speech, religious activity, or other constitutionally protected activity. News reports on the policy say it also bars use for immigration or tax enforcement.
- Camera placement: fixed cameras can't be placed within 100 feet of a place of worship, polling place, or medical facility without the agreement of the owner or operator
- Searches: every search requires a case number and a specific reason; vague reasons like "investigation" aren't allowed
- Data sharing: requires a formal agreement or written request; all sharing is paused until agreements are written
- Audits: searches are "audited every 30 days by our Technology Captain," and the audit will "check 1% of all searches that are deemed valid"
- Misuse: referred for discipline and, if criminal, to the District Attorney
- Training: required annually
- Coming in 2027: a public dashboard and an alert when the same plate is searched repeatedly
The department sought outside input, including from the ACLU of Kansas, which called the policy a significant step forward.
What's Still Missing
The Rules Can Change Without a Vote
The original two-year retention period was set by department staff based on how much data the city's servers could hold. It went unchanged for more than a decade. In 2026 it changed twice, and the City Council voted on neither change.
Asked whether she wants to expand camera coverage, the Chief said, "I think eventually." She added that her current focus is a better system, not more cameras, and that she would never expand without making sure everyone understands what's happening. That's a good commitment. We'd like to see it written into the rules.
Today's rules are good because today's chief chose them. The next chief could choose differently. And today's small footprint is the best time to set the rules, before the system grows.
The Department Audits Itself
Monthly audits are conducted inside the department and reported to the Chief. When a Council member asked about an independent audit, the department said no process exists and that outside review could violate federal security rules for criminal justice data.
Those federal rules already allow outside access under formal agreements. The same rules let the department store this data in its vendor's cloud. Minnesota requires independent audits of police plate reader programs, usually by outside firms, and publishes the results. In Seattle, Washington, the city's Inspector General reviewed police searches on Axon's platform, the same one Overland Park uses. About 47% of Seattle's 2025 searches had no justification given.
An independent reviewer wouldn't need case details. Reviewing the search logs (who searched, when, and whether a valid case number was attached) is enough to catch misuse.
Shared Data May Not Stay Protected
Data sharing is paused until formal agreements are written. But when asked whether partner agencies would have to meet Overland Park's standards, the department said it can't place requirements on other departments.
The city can't control other agencies' policies, but it can decide which agreements it signs. Once our data is shared, our 30-day limit only protects our own copy. A partner that keeps data for years or shares it onward undoes that protection.
Not Every Camera Follows the Same Rules
Police can search privately owned Flock cameras installed by businesses around the city. Where those cameras go and how long their data is kept is up to their owners, not the city.
No Vendor Is the Safe Choice
Flock has drawn most of the national criticism, and many cities have replaced Flock cameras with ones from Axon, which Overland Park uses for body cameras, patrol car cameras, and plate readers. But the core concerns don't depend on the brand. Axon sells cameras that combine plate reading with live video, and it owns a platform built to combine feeds from many sources.
In September 2026 testimony to a U.S. Senate subcommittee, security researcher Benn Jordan urged Congress to apply any rules for Flock to other camera networks, including Axon. We agree. There's no safe vendor, only safe rules.
Collected Data Can Be Breached
Data that's kept can be stolen, not just misused. Researchers have found serious security weaknesses in plate reader systems, including police logins offered for sale online. Shorter retention limits that risk, which is one more reason the 30-day change matters.
Residents Can't Check for Themselves
Kansas law lets police withhold plate data and reader locations from the public. A resident who worries their own plate is being searched, such as by an ex-partner who's an officer, can't find out. Their only option is filing a complaint with the department.
No dashboard can tell one resident whether their plate was searched. The closest protection is the department's planned alert when an officer searches the same plate repeatedly, a feature the Chief asked the vendor to build after seeing how misuse cases play out nationally. Reporting how often that alert fires, and what came of it, would show residents whether the protection works.
The department's planned 2027 dashboard is a welcome step. But the sample shown to the committee reports what the system collects (how many plates it read, how many matched a hotlist) rather than how it's used: how many searches officers ran and why, what the audits found, and who outside the department searched our data. Misuse happens in searches, so that's what residents most need to see.
Reference
For officials, reporters, and advocates. Each section opens to the detail.
Kansas Law
Home rule lets OP act by ordinance; no state law on ALPR use; the Kansas Open Records Act (KORA) exemption covers disclosure only and doesn't prohibit it; SB 305 history, including the ACLU of Kansas opposing it as too weak.
The KORA Inconsistency
State law lets police withhold where their plate readers are, but the city publishes images from traffic cameras at known intersections. The difference is software.
A department technology officer cited the KORA exemption (plate reads and reader locations closed) when Council Member Cheatham asked whether residents can check if their plate was searched, and framed it as anti-stalking.
- The exemption only protects records of public agencies. A private company running its own analysis on public stills isn't bound by it.
- The exemption says an agency "shall not be required to disclose"; it doesn't prohibit disclosure.
- "High-speed cameras" in the definition may not cover updating stills, a possible gap.
- The exemption governs disclosure, not use. A 2021 bill (SB 305) to require agency ALPR policies never became law; the disclosure exemption passed on its own in 2022 (SB 434). Nuance: the ACLU of Kansas opposed SB 305 as too weak, in part because it exempted plate data from open records, so its failure wasn't simply police opposition.
- A 2025 ACLU of Iowa / University of Iowa report said Kansas's secrecy about ALPR locations "does the opposite" of protecting privacy (via St. Louis Public Radio).
- Research found no Kansas ALPR bills 2023 to 2026. KCUR predicts action in the 2027 session.
How the Law Defines a Plate Reader
- Kansas law (K.S.A. 45-217 definition, used by the 45-221(a)(55) exemption from SB 434, 2022) defines an ALPR system as high-speed cameras plus algorithms that convert plate images to computer-readable data. The law itself defines ALPR by its software.
Audits and CJIS
How outside review works (Minnesota firms, the Seattle, Washington, Inspector General, and the Austin and California auditors); management control agreements (MCAs) and the Security Addendum under the FBI's Criminal Justice Information Services (CJIS) rules; no FBI ruling on whether search logs are CJIS data; asking the KBI.
A department reviewing its own audits isn't oversight. We're asking for review of how the tools are used, not of the data itself.
- Monthly audits run internally by the Technology Captain; results go to the Chief.
- Outside audit declined: "no process" and "potential CJIS violation." (staff presenter, repeated by the Chief)
- Council Member Cheatham asked how an audit that reports to the chief accounts for agency heads misusing systems; staff said concerns can be reported to the city manager.
- The deck's "Exceeds the Standards" table is self-graded. (slide 15)
- Middle ground: audit logs (who searched, when, whether a valid case number was attached), anonymized if needed, without case content.
- CJIS already allows outside access under a Management Control Agreement and the FBI Security Addendum, and it lets agencies store data with cloud vendors that work under the Addendum. OPPD's Axon data is stored in Axon's cloud; Genetec data is on city servers (meeting transcript). The FBI's own definition of a criminal justice agency includes "State and federal Inspectors General Offices." (FBI CJIS Security Policy, Appendices A and G.3)
- No FBI statement says whether ALPR search logs are CJIS data. Logs can be reviewed without case content. A written view from the Kansas Bureau of Investigation (KBI) is an open step.
- Minnesota requires independent biennial ALPR audits, published publicly, usually by hired firms (LOGIS, Wildcard); a pattern of noncompliance suspends the program. (Example: Plymouth PD)
- Seattle, Washington's Inspector General reviewed all police users' activity in Axon's Evidence.com, found no unauthorized access, and found no justification given for about 47% of 2025 searches. (Seattle OIG, September 2026)
- Sen. Hawley criticized ALPR makers for relying on agencies to self-police; Benn Jordan called for independent security testing. (Nextgov, September 2026)
Vendors
Flock vs. Axon, the real differences: Flock's national lookup network vs. Axon's agency cloud and Fusus integration. Jordan's "no vendor switch fixes it."
Axon is no safer than Flock. The two have similar capabilities and different customer bases, and Axon draws more innate trust despite still being private.
- OP has a 10-year, $22.4 million Axon contract (body cameras, Fleet 3, ALPR beta, cloud storage, dashboard, Fusus), approved 9-0 in September 2025. The Chief wants an "Axon-integrated approach" (meeting video). Consolidating everything into one ecosystem is itself data aggregation.
- Cities dropping Flock often install Axon on the same poles; Axon gets less backlash because it isn't a household name. (Mother Jones, American Prospect)
- Experts: whether Axon is as bad as Flock is "temporal." (American Prospect)
- Axon bought Fusus (2024), which aggregates live video and data feeds from many sources.
- Benn Jordan urged Congress to apply any Flock rules to other networks, including Axon (Senate Judiciary subcommittee, September 23, 2026), and said replacing Flock with another vendor wouldn't resolve the security concerns. (Atlanta News First, Fox Carolina, Police1)
- Axon, Flock, Motorola, and Verkada CEOs were invited to testify and did not attend. (Nextgov, The Hill)
- A real difference exists: Flock runs a national lookup network; Axon says it doesn't operate one. Denver, Colorado's mayor cited this when the city moved from Flock to Axon in February 2026. (9News)
Software and Traffic Cameras
Kansas defines ALPR by its software; Minnesota bars traffic enforcement cameras from ALPR use; Axon Lightpost turns streetlights into readers.
Traffic Cameras Today
OP's public traffic cameras (Public Works) publish updating still images at known intersections. OPPD's deck says ALPR locations are exempt from disclosure under Kansas law. KSHB reported the RTIC "will include traffic cameras and license plate readers."
- Axon's Lightpost converts streetlights into combined video and ALPR cameras. (Jalopnik)
- OP's public feeds are updating stills, likely not readable for plates today. They could become so.
Traffic Cameras and Purpose
Traffic cameras are a genuine public service and should stay public. The line is purpose: images collected to manage traffic shouldn't be repurposed to identify or track people without elected officials approving it.
No ALPR policy touches this. It sits with Public Works, not OPPD.
- The framework should cover city-generated data from any department, not just policing.
- Minnesota bars using traffic safety cameras as ALPRs (Minn. Stat. § 13.824, Subd. 2a).
Retention Comparison
| Place | Limit | Type |
|---|---|---|
| Austin, TX | 7 days | Council resolution |
| Overland Park | 30 days (was 1 year) | Police policy |
| Missouri | 30 days | Executive order (state agencies and state-funded police) |
| Minnesota | 60 days | State law |
| Austin's 6 peer cities | 30 to 730 days | Various |
| Kansas | None | No state law (failed SB 305 proposed up to 5 years) |
Open Questions and KORA Requests
- Full Axon agreement and order forms: data ownership, retention, secondary use, AI training, sharing.
- All OPPD ALPR policy versions, 2011 to October 2026 (confirms the retention history).
- Monthly audit reports since October 2026, including sampling method.
- Any written analysis behind the "potential CJIS violation" statement, and KBI communications.
- All data-sharing agreements and requests, including federal.
- Agreements for access to private Flock cameras and Fusus private-camera terms.
- Records of Council votes on Genetec fixed-site purchases.
- RTIC operating policy: feed retention, viewers, analytics enabled.