Overland Park's new license plate reader policy is a real step forward. It isn't enough.

What the police department presented to the Public Safety Committee on October 14, what changed, and what's still missing.

Back to Automated Resident Data Collection

On October 14, the Overland Park Police Department presented an updated policy for its automated license plate readers (ALPRs) to the City Council's Public Safety Committee. The new rules took effect the week before, KCUR reported. ALPRs are cameras that photograph license plates and record when and where a vehicle passed. Overland Park has 37 fixed cameras at eight sites, an eight-camera test site for a newer Axon system, and ALPR capability in 110 patrol cars.

These tools help find stolen cars, solve serious crimes, and locate missing people, and the department shared real Overland Park cases where they did exactly that.

The Cases the Department Shared
  • A missing person: another metro agency entered a plate tied to a missing person. An Overland Park camera alerted when the vehicle passed, officers found the driver disoriented, and the person was taken to a hospital and reunited with family.
  • An armed robbery: a seller meeting a buyer from social media was robbed at gunpoint. Plate reader data helped identify the suspect's vehicle, and the suspect was charged.
  • A burglary series: a suspect who hit 11 stores across seven states was identified after a plate read led detectives to his probation officer. He pleaded guilty.

What Changed

  • Retention cut to 30 days. Plate data was kept for two years until 2026, then one year, and now 30 days.
  • No facial recognition.
  • Protected activities are off-limits.
  • Every search needs a reason.
  • Data sharing is paused until formal agreements are written.
  • Monthly audits of searches, checking 1% of those deemed valid.
The Full List of Changes
  • Retention: cut from one year to 30 days. It was two years before 2026.
  • Facial recognition: the policy prohibits integrating it.
  • 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. 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" or "routine patrol" aren't allowed.
  • Data sharing: other agencies need a formal agreement or written request. All sharing is paused until agreements are written. Committee Chair Gregg Riess, a council member, pressed the department on this, citing reports that Kansas City, Kansas license plate data had been searched by agencies in Texas.
  • 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: now required annually.
  • Coming in 2027: a public dashboard summarizing plate reader use, and an alert when the same plate is searched repeatedly. The Chief asked the vendor to build that alert after seeing how misuse cases play out nationally.

Chief Doreen Jokerst and her team deserve real credit. They sought outside input, including from the ACLU of Kansas, which called the policy a significant step forward.

Why It Isn't Enough

The rules can change without a vote. These are internal department rules. Retention changed twice this year, and the Council voted on neither change.

More on How the Rules Were Set

The original two-year retention period was set by department staff based on how much data the city's servers could hold, and it went unchanged for more than a decade. The Chief said the department had to estimate the new 30-day period through conversations with investigators, because the current system makes it hard to pull historical usage data.

When a committee member asked whether the department wants to expand camera coverage, the Chief said there could be room for that discussion, but that her current focus is a more robust system, and that she would never do something without making sure everyone understands what's happening. Asked directly whether she wants to expand coverage, she answered, "I think eventually."

Today's rules are good because today's chief chose them. The next chief could choose differently.

The department audits itself. Outside review was declined, though other states require it.

The Audit Exchange

Council Member Melissa Cheatham asked whether the department would accept an independent audit. The answer was that no process exists and that outside review could violate federal CJIS security rules for criminal justice data. Cheatham followed up by noting that some of the worst misuse cases nationally involved agency heads themselves, and asked how an audit that reports to the chief accounts for that. The answer was that staff can report concerns to the city manager.

Federal CJIS rules already allow outside access under formal agreements, and 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. The department said it can't require partner agencies to follow Overland Park's standards.

Why Data-Sharing Agreements Matter

Cheatham asked whether agencies receiving Overland Park's data would have to meet the same standards on retention, audits, and access. The Chief said she couldn't place stipulations on other departments. Cheatham urged the department to partner only with agencies that have similarly high standards, and Riess said he liked the idea.

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.

Residents can't check for themselves. State law lets police keep plate data closed to the public.

What Residents Can and Can't Do

Cheatham asked whether a resident could find out if their own plate had been searched. A department technology officer answered that under Kansas open records law, plate data and camera locations can be withheld. If someone suspects misuse, such as an ex-partner who's an officer searching their plate, the only option is filing a complaint with the department.

The 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.

Private cameras play by their own rules. Police can search privately owned Flock cameras across the city.

The Flock Question

Council Member Richard Borlaza asked why Flock, a vendor whose cameras here are owned by private businesses, draws more criticism than the city's own systems. The Chief said she couldn't speak in detail about a system the city doesn't own or operate. She said she judges the department's own systems by their governance, safeguards, and accountability, in a way that's "almost vendor agnostic," and stressed that "we own our own data." Police can still search the Flock cameras. Where they go and how long their data is kept is up to their owners.

The concerns don't depend on the brand, either. 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, which Overland Park uses (Atlanta News First). There's no safe vendor, only safe rules.

The camera is the least of it. The real issue is how much data about residents gets collected and kept.

Beyond License Plates

Borlaza also asked what the "additional details" field in the search tool can look for. Police Major Keith Jenkins said it can search for things like a roof rack or a window sticker. It doesn't work well at night or after snow, but the capability is there.

Under Kansas law, what makes a camera a plate reader is the software running on it. As software improves, the line between ordinary cameras and plate readers gets thinner. That's why we think the rules should follow the data, not the device.

What We're Asking For

Residents who aren't suspected of anything shouldn't have their movements recorded and stored by their government. These tools are already part of how Overland Park keeps people safe, so we're starting with the strongest protections we can put in place now: rules for automated resident data collection set by elected officials, independent review of how the data is searched, minimum standards for any agency we share data with, the same standards for every camera the police can access, and regular public reporting on how these systems are used. Those rules should be a floor, not a ceiling.

Read our full proposal

Watch the Oct. 14 Public Safety Committee meeting
View the department's presentation slides

Sources & Research

The October 14 Meeting
KCUR, October 13, 2026
City of Overland Park, October 14, 2026
Public Safety Committee, October 14, 2026
Audits and CJIS
Minnesota Legislative Reference Library
Seattle Office of Inspector General, September 2026
Vendors and the Senate Hearing
Atlanta News First, September 23, 2026

Privacy Policy

Last updated: October 14, 2026

Overland Park Voice ("we") runs opvoice.org. This explains what the site collects and why.

Information We Collect

We collect as little as we can. We don't use cookies, ad trackers, or tracking pixels, and we don't build profiles of visitors. The only personal information we get is what you choose to send us.

Sign-Up Form

If you use the sign-up form on our site, we receive:

  • Your name
  • Your email address
  • Your message, if you add one

We use these only to reply to you and to send the updates you asked for.

Site Analytics

We count visits with GoatCounter, an open-source analytics service built for privacy. It's fully anonymized. It records which page was viewed, the referring site, your browser and screen size, and your country. It doesn't use cookies or store your IP address, and it can't identify you or follow you across other sites. We use these counts only to see which pages people read.

Our Web Host

Like any website, our host keeps standard server logs under its own policy. We don't use them to identify visitors.

How We Use Information

  • Replying to you: we use what you send through the form to answer you.
  • Improving the site: anonymous visit counts tell us what's useful and what's broken.

We never sell, rent, or share your personal information for marketing.

Third-Party Services

  • GoatCounter (gc.zgo.at): the anonymized visit counts described above.
  • Formspree (formspree.io): handles the sign-up form and forwards submissions to our email. We don't store form data on the website.
  • Google Fonts (fonts.googleapis.com): serves the site's typeface. Your browser contacts Google to load it.
  • Tailwind CSS (cdn.tailwindcss.com): serves the site's styling.
  • Chart.js (cdn.jsdelivr.net): draws the charts on our housing research page.

Social Media

We link to our accounts on Facebook, Instagram (@op.voice), Reddit (r/OverlandParkVoice) and YouTube (@VOICEofOP). Those platforms have their own privacy practices, which we don't control.

Data Security

The site uses HTTPS encryption, and form submissions go to Formspree's secure servers. No method of sending data over the internet is completely secure, but we keep what we hold to a minimum.

Data Retention

  • Form messages: we delete them when they're no longer needed to reply to you or send the updates you asked for.
  • Visit counts: kept as anonymous totals.

Your Rights

You can ask what personal information we hold about you, and ask us to correct it, delete it, or stop contacting you. Email us and we'll take care of it.

Contact Us

  • Email: overlandpark.voice@gmail.com

We aim to reply within 5 business days.

OP Voice Transparency

AI Use Policy

How We Use AI in Our Research and Writing

Updated: October 2026

Scope: All OP Voice research, policy drafting, and community projects

Objective: Ensuring human judgment remains the foundation of civic advocacy

Part I

Why This Exists

As a one-person organization juggling a full-time job and serious policy work, efficiency is a necessity. However, if we demand transparency from the City on their AI use, we owe you the same.

Core Principles:

  • 1.
    Authenticity Over Polish: AI helps me be more thorough, but it never replaces the reading or the judgment.
  • 2.
    Transparency as Default: If AI contributed significantly to a piece of work, we disclose it.
  • 3.
    Human-in-the-Loop: AI can surface patterns, but humans make the call on what matters.

Part II

How the Work Actually Happens

Step 1: Human Research & Analysis

Every project starts with reading actual documents: city contracts, vendor policies, ordinances, and investigative reporting. I form my own hypotheses and arguments from this research foundation. AI never sees a blank slate; it sees work I've already started.

Step 2: Using AI to Cover Gaps

AI tools are used to find sources I might have missed, identify logical holes, and synthesize patterns across multiple documents. All AI-surfaced sources get verified independently. We use multiple AI systems to avoid vendor lock-in.

Step 3: Red-Teaming & Stress-Testing

Before committing to a position publicly, I use AI to find the strongest counter-arguments. This helps identify vulnerabilities before they reach the City Attorney or Council. If red-teaming reveals a weak position, I change or abandon it.

Part III

The Red-Teaming Practice

Red-teaming is the most valuable way I use AI. It's brutally honest feedback without social pressure.

The Red-Team Protocol: What We Ask

"What's the strongest case against this?"

Finding the counter-perspectives early.

"What am I assuming that I shouldn't?"

Exposing blind spots in our logic.

"Where is this most vulnerable to criticism?"

Strengthening the evidentiary base.

"How would city staff oppose this?"

Preparing for the real-world debate.

Part IV

Verification & Disclosure

Section 1: The Human Verification Standard

This mirrors our February 2026 RTIC governance proposal. Just as OPPD shouldn't take enforcement action based solely on an AI alert, OP Voice doesn't publish AI analysis without human verification.

Claims verified vs original sources
Tested against lived experience
Judgment on community needs
Tone edited for authenticity

Section 2: Clear Disclosure Requirements

Disclosure is required for research posts where AI helped find sources, policy documents with AI assisted structure, or any content where AI contribution was substantial.

"Research conducted by OP Voice, gaps filled and verified with AI assistance. Draft organized with AI tools, substantially edited for accuracy and voice."

Part V

Accountability When AI Gets It Wrong

No verification process is perfect. If AI-assisted research leads to an error in published work, our response is human-centered:

Public Correction

We correct it with the same visibility as the original post, explaining what went wrong (bad source, flawed synthesis, verification gap).

Human Accountability

We don't hide behind "the AI got it wrong." The human verified it. The human published it. The accountability is 100% human.

What This Means for Readers

When you read an OP Voice research post, the sourcing is real. I've read the contracts, the ordinances, and the vendor policies myself.

Where AI shows up is in the gaps: flagging a case I hadn't found, catching a logical inconsistency, or helping organize 30 pages of research into something readable. The positions, the framing, and the decision to publish are mine.

If something seems off or you want to see the underlying sources, ask. That's the whole point.

This policy is a living document, evolved through community feedback and technical changes.

© 2026 Overland Park Voice

Visit opvoice.org for more information