Surveillance News Roundup

Recent surveillance news that connects directly to what Overland Park is building.

Back to Resident Data Oversight
February 2026 snapshot. This roundup reflects the news as of February 16, 2026. The Real-Time Information Center has since launched, and in October the police department adopted a new plate reader policy that cuts retention to 30 days. See Overland Park's New Plate Reader Rules and our current work, Resident Data Oversight.

It's Been a Busy Week in Surveillance News

A few stories caught our attention because they connect directly to what's happening here in Overland Park. Here's what you should know.

What We Learned from OP's Public Safety Committee

The Overland Park Public Safety Committee recently discussed ALPR (automated license plate reader) policy in a public meeting. We appreciate that the conversation is happening. Here's what came out of it:

  • OPPD retains license plate reader data for one year
  • Local metro agencies on the ALPRWeb platform can access OPPD's reads
  • Federal agencies can request data by contacting an OPPD administrator. The DEA was given as an example
  • The city committed to creating an "ALPR transparency web page"

These are useful starting points, but a "transparency page" isn't governance.

Retention: A one-year retention period for non-investigative data is exceptionally long. Privacy-focused agencies like Providence, RI; Culver City, CA; and Ogden, UT use 30 days. To be clear, our proposal doesn't require detectives to lose evidence. Data tied to an active investigation stays as long as the case needs it. What it doesn't allow is storing every plate read in the city for a year on the off chance it might be useful someday. That's not targeted policing; it's bulk data retention.

Access: The question worth asking is what criteria are applied to federal data requests, and whether any have ever been denied.

Proposal Connection

Cities like Santa Cruz, CA; Evanston, IL; and Oak Park, IL have canceled contracts with vendors specifically because of unauthorized federal access and data sharing concerns.

That's why our proposal takes a harder line: Unflagged LPR data is hard-deleted after 30 days, not one year (Section 18, Tiered Retention). Standing data feeds to federal agencies are explicitly prohibited. Data can only be shared for a specific, active investigation with a criminal predicate (Section 8, Data Firewall).

OPPD Announces New "Transparency First" Body Cam Policy

Feb 9, 2026

Overland Park Police Chief Doreen Jokerst released a new policy regarding body camera footage.

The big change? The department now commits to the automatic release of body cam footage for "officer-involved critical incidents" (like shootings).

Chief Jokerst put it simply: "Trust is the foundation of effective policing... we recognize that in moments of crisis, the community expects and deserves clarity."

Proposal Connection

Advocacy works. This policy shift proves that when the community demands transparency, we can get it. Our governance proposal locks this principle into law for all surveillance tech, not just body cams. It ensures that as new tools like drones and AI are added, they come with the same level of openness: clear rules, automatic transparency reports (Section 19), and no dark corners.

Lenexa Police Used ALPRs to Track a Critic

Next door in Lenexa, a troubling case came to light on Feb 3, 2026: Lenexa Police used their License Plate Reader system to track a resident after he wrote an op-ed critical of the department's cooperation with ICE.

Emails later revealed the Police Chief issued a BOLO ("Be On the Look Out") for the writer, explicitly telling officers to "Make Your Own Case" (MYOC). In plain English: officers were told to find their own reason to stop him. The stated reason for looking for him was that he had put up posters with "damaging glue," a minor ordinance violation.

It shows the risk isn't theoretical. Tools bought to fight violent crime were turned on a resident over a minor ordinance violation, right after he criticized the department in print.

Proposal Connection

Our proposal includes strict First Amendment protections to prevent exactly this kind of abuse. Section 16 (Protection of First Amendment Activity) explicitly forbids using RTIC assets to monitor or identify individuals engaged in protected political speech. It also limits data access to specific criminal investigations involving threats to life or felonies, not minor ordinance violations or personal vendettas.

Source: ACLU

Ring dropped Flock. They didn't drop Axon.

You might have seen the headlines. After Ring aired a Super Bowl ad for its "Search Party" feature, which uses AI and a network of neighborhood cameras to find lost dogs, people immediately pointed out the surveillance implications. That backlash, combined with growing pressure over Flock Safety's connections to ICE (Immigration and Customs Enforcement) and CBP (Customs and Border Protection), pushed Amazon to cancel Ring's planned integration with Flock within days.

Good news, right? Sort of.

What most coverage missed is that Ring's partnership with Axon is completely unaffected. A Ring spokesperson confirmed it the same day. And the same day Ring-Flock was canceled, a sheriff's office in New York announced a brand new Axon-Ring Community Requests partnership.

Why does this matter here? Axon is the company that runs Overland Park's entire RTIC (Real-Time Information Center) system. The $22.4 million contract covers body cameras, license plate readers, drones, the Fusus integration platform (the software that connects all the camera feeds into one interface), and cloud storage. Ring's Community Requests program through Axon still allows law enforcement to send geo-targeted footage requests to every Ring owner in a given area.

The surveillance pipeline people were angry about this week didn't disappear. It runs through a different company. And that company is already here.

Proposal Connection

If officers can just log into a vendor portal to get data, our city rules don't matter. Our proposal explicitly forbids officers from bypassing the RTIC to access surveillance data through third-party vendor portals (Section 11, Parallel Access Prohibition). If they want the data, they have to get it through the governed system, with a case number and an audit trail.

"No Subscription" Doesn't Mean "No Data"

This one is worth understanding even if you don't follow surveillance policy.

In the Nancy Guthrie kidnapping case this week, the FBI recovered video footage from her Google Nest doorbell. She didn't have an active Nest Aware subscription. The power to her home had been cut before the kidnapping. Most people would assume that means no footage exists.

They'd be wrong. Nest doorbells save roughly three hours of event-based video on Google's servers for free, even without a subscription. And when that data is "deleted," it isn't actually erased. It sits on Google's servers until it gets overwritten, the same way a file you drag to the trash on your computer isn't really gone until something else writes over that space.

This matters because a lot of the conversation around surveillance governance comes down to data retention. How long is your information kept? Who can access it? And what does "deleted" actually mean? The answer, in most cases, is that your data sticks around longer than you think, in places you didn't know about, accessible to people you didn't authorize.

Proposal Connection

We define "deletion" differently. Our proposal defines "Hard-Deletion" as the cryptographic destruction of data, not just removing it from a search index (Section 0). It also requires vendors to provide a written certification that data has been physically destroyed from all backups and archives (Section 6(b), Vendor Deletion Verification). We don't take their word for it; we require proof.

Source: Tom's Guide

The Industry Isn't Slowing Down

One more thing. Flock Safety raised $275 million last year at a $7.5 billion valuation, led by Andreessen Horowitz. While over two dozen cities have since canceled or rejected Flock contracts (tracked by EFF and 404 Media), that fundraise provided them with a massive war chest to continue their aggressive expansion. The company is still growing at 70% year over year.

These companies are not going away. Which is exactly why local governance is the most effective lever any community has. We can't control what the industry does. We can control what Overland Park requires.

When we wrote this, the RTIC was set to go live for the FIFA World Cup. It's running now, which makes oversight of how it's used the next job.

What We're Asking For

We've drafted a governance proposal that addresses all of this: data ownership, retention limits, independent oversight, facial recognition prohibition, case-based access, and protections for your First Amendment rights. You can read the full proposal and sign up for updates at opvoice.org.

If you care about how these systems are used in our city, stay connected. Read the proposal, share it, and let your council members know you're paying attention.

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