Overland Park, Kansas, did not shut off its license plate readers when residents raised questions about privacy. It took a different approach: keep the technology, but write much stricter rules for what police can do with the information it collects.

In October 2026, Police Chief Doreen Jokerst’s department shortened routine retention from one year to 30 days, restricted searches and sharing, and added more regular reviews of officers’ activity. The change matters because Overland Park has used license plate readers since 2011. This was not a small experiment being discontinued. It was an established police program changing how it operates.

According to KCUR’s October 13 reporting, the department had 37 stationary readers and 110 cameras mounted on police vehicles. The equipment was supplied by Genetec and Axon, not by Flock Safety, the vendor at the center of many other cities’ debates.

What changed for an ordinary driver’s plate record?

Start with storage. Previously, the department could keep routine license plate records for a year. The revised policy cuts the normal period to 30 days. Once that period passes, records not being preserved for a qualifying investigation are supposed to be removed.

Thirty days is not the same as recording nothing. A license plate reader can still capture thousands of ordinary trips in that period, and officers can still investigate crimes using recent sightings. But it narrows how far back routine searches can reach.

The policy also limits where fixed cameras may be placed. KCUR reported a restriction on installations within 100 feet of places of worship, polling places and medical facilities. That is a practical boundary rather than a broad statement that privacy is important. People visiting those places may be especially concerned about their movements being recorded.

The new rules prohibit using plate reader data solely to track protected speech, political or religious activity. They also prohibit personal use and use for enforcing tax or immigration laws outside the department’s jurisdiction. The department separately barred integrating artificial intelligence facial recognition into the plate reader system.

What must an officer do before searching?

One of the most useful changes is easy to understand: a police officer must enter a real case number and a specific reason for a database search. As the Kansas City Star’s October 14 coverage explained, vague explanations such as a general investigation or routine patrol do not satisfy the new rule.

That detail matters long after a search is made. If a supervisor wants to know why someone checked a vehicle at a particular time, a case number offers a place to start. Without it, a search history may tell investigators who clicked the button but very little about why.

Overland Park will also conduct monthly reviews of database searches. If a questionable search is found, the department’s Office of Professional Standards can investigate. The policy contemplates referring substantiated misuse to prosecutors, rather than treating every violation as an issue for internal training alone.

Alerts from a camera are not a verdict, either. The updated rules require an officer to visually verify a plate before taking action on a suggested match. A wrong plate reading can send police toward the wrong vehicle, so that human check is more than paperwork.

Can police in other cities still look up the data?

The revised policy requires formal agreements before routine sharing with another law enforcement agency. Where no agreement exists, an agency seeking information must submit a documented request with its case number and intended purpose.

That distinction helps explain why license plate reader discussions can become confusing. Sharing a particular record in response to an investigation is not identical to giving outside officers standing access to search a whole database. KCUR’s report said the department was changing how those arrangements were controlled.

The department does not operate a Flock camera fleet, but it has access to some privately owned Flock data within Overland Park. That means the absence of city owned Flock equipment should not be mistaken for a complete absence of access to any Flock records.

Did critics support the change?

The American Civil Liberties Union of Kansas did not reverse its overall opposition to broad license plate surveillance. But executive director Micah Kubic described the department’s willingness to engage and adopt meaningful restrictions as a positive development. KCTV’s October 14 account reported that police had sought input from residents and civil liberties advocates while revising the policy.

That is an important middle position. A critic can believe the technology creates unreasonable privacy risks while recognizing that shorter retention, clearer rules and actual audits are improvements over a weaker policy.

Police officials emphasize the other side. Plate sightings can help identify stolen vehicles, find missing people and connect vehicles to serious investigations. The department’s position is that better governance can preserve those benefits while reducing the risk of unauthorized searches.

Neither side’s argument proves that the rules are always followed. An adopted policy shows what officers are supposed to do. Audit results, incident reporting and independent review would help establish whether the safeguards actually work.

What should residents watch for?

The first question is whether monthly audits lead to public accountability, not merely an internal checklist. The next is whether other agencies’ access is documented and updated. Finally, because these are department rules rather than a newly enacted citywide ban, future police leaders may have some ability to revise them.

Readers who want a comparison can see our report on Chicago’s review of searches made through outside plate reader networks. Chicago is focusing on who searches other agencies’ records. Overland Park is tightening the rules for access to records under its own police program. Both illustrate why a policy without a usable search history leaves important questions unanswered.

Sources

KCUR, October 13, 2026: revised policy, equipment and privacy restrictions; Kansas City Star, October 14, 2026: case numbers, audits, retention and verification rules; KCTV, October 14, 2026: police and ACLU responses.