St. Paul City Council Committee on Public Safety Technology - June 24, 2026
St. Paul City Council Committee on Public Safety Technology - June 24, 2026
The City Council’s Committee on Public Safety Technology convened on June 24, 2026, to discuss two agenda items related to evolving technology in public safety: the St. Paul Police Department’s (SPPD) use of drones, automated license plate readers (ALPRs), and a real-time information center; and a presentation by the ACLU of Minnesota on municipal regulations for ALPRs. The meeting featured presentations from Deputy Chief Kurt Holstrom and Senior Commander Murphy of SPPD, and John Baylor, Policy Director of the ACLU of Minnesota. No votes were taken; the committee agreed to send follow-up written questions to SPPD, the ACLU, and the Ramsey County Sheriff’s Office (which declined to attend).
Discussion Items
- SPPD Presentation on Public Safety Technology (SR 26-132)
- Deputy Chief Holstrom outlined SPPD’s technology framework, emphasizing constitutional policing, lawful purpose, limited use, trained operators, documented actions, auditability, transparency, and corrective action. Technologies discussed include:
- Dock Drone Program: Launched May 30, 2026, with three drones on rooftops (one per district), each with a ~2-mile radius and 20-30 minute battery life. Drones are not used for general surveillance; cameras point to horizon during transit. As of the meeting, nearly 500 flights had been completed, with drones arriving on scene before squad cars 51% of the time. Response time is 60-90 seconds for drones vs. 7-10 minutes for squad cars. Drones are deployed only under 11 warrant exceptions in state statute. No internal affairs complaints have been filed regarding drone operators in three years.
- License Plate Readers (LPR): SPPD uses ALPRs in squad cars and two fixed Flock cameras (at Kellogg and Smith). Data retention: 60 days for squad-car LPR data (per state statute), 30 days for Flock data. Data is not shared outside Minnesota or with federal agencies. Queries require a case number and criminal investigation reason. A biannual third-party audit (conducted October 2025 by Logis) found SPPD in compliance with state law.
- Real-Time Information Center (Arctic): Also launched May 30, 2026, staffed by trained officers and analysts to provide real-time situational awareness to officers in the field. Operates under the same legal and policy constraints.
- Council members asked about:
- Data sharing with the BCA (state Bureau of Criminal Apprehension) and Minnesota Fusion Center: SPPD confirmed BCA has access, but no out-of-state sharing.
- Distinguishing drone response times from officer response times: SPPD agreed to provide disaggregated data.
- Video retention for active investigations: Video becomes public after case closure; if another jurisdiction has an active investigation, SPPD may share.
- Potential use of drone footage to review officer conduct: Confirmed that such footage would be retained as part of any misconduct investigation.
- Deputy Chief Holstrom outlined SPPD’s technology framework, emphasizing constitutional policing, lawful purpose, limited use, trained operators, documented actions, auditability, transparency, and corrective action. Technologies discussed include:
- ACLU of Minnesota Presentation on ALPRs and Municipal Regulations (SR 26-133)
- John Baylor provided context on Flock cameras, noting that Flock is a data company. SPPD’s two fixed cameras generate about 5,000 searches per month (January data). Baylor recommended:
- Implementing a public-facing transparency portal (as used by Roseville and St. Louis Park) to show aggregate search statistics.
- Restricting access from agencies with 287(g) agreements (federal immigration enforcement cooperation). SPPD already restricts out-of-state access, but in-state agencies with 287(g) agreements—such as Mille Lacs, Crow Wing, Itasca, and others—have run searches on St. Paul’s cameras for civil immigration enforcement (based on search logs from other cities). Baylor clarified that 287(g) agreements do not override state privacy law.
- Increasing the frequency of internal audits (beyond the biannual third-party requirement).
- Baylor raised concerns about potential misuse of drone capabilities (e.g., facial recognition, carrying devices like stingrays), but noted SPPD’s program appears to use drones only for situational awareness. He emphasized ongoing public engagement to avoid over-policing minority neighborhoods.
- Council members discussed the county’s 11 LPR cameras (operated by Ramsey County) and the lack of coordination. Questions were raised about St. Paul’s ability to control data once shared with in-state agencies, even if those agencies are bound by state law.
- John Baylor provided context on Flock cameras, noting that Flock is a data company. SPPD’s two fixed cameras generate about 5,000 searches per month (January data). Baylor recommended:
Key Outcomes
- No formal votes or resolutions were adopted.
- The Committee will compile follow-up written questions for SPPD, the ACLU, and the Ramsey County Sheriff’s Office. Questions will cover:
- SPPD’s response to ACLU concerns about redacted search reasons in audit logs.
- SPPD’s collaboration with Ramsey County on LPR placement and data sharing.
- The Ramsey County Sheriff’s Office (invited but declined) will respond in writing.
- The chair noted that presentations and the ACLU’s paper on drone limits will be distributed to council members.
Meeting Transcript
Thank you. I will say to everybody in the room, if you're sensing a lot of nervous energy from me, it's my first time chairing a committee meeting, so apologies in advance for everything I get wrong. And to my colleagues, please correct me if I'm doing something illegal. With that, we will proceed directly to today's agenda. We have two items before us, both relate to the topic of changing technology use in our public safety arena. We are delighted to have two speakers with us today. And to kick things off, I would like to invite Deputy Chief Kurt Holstrom of the St. Paul Police Department to present on SUPD and public safety technology. Item number one is SR twenty six-132. Excellent. And I'm sorry, before you get started, I will just note for my colleagues. We'll have 30 minutes for each of our presentations. So I will do my best to track as those come up. Ready? Good afternoon, Chair, Council members, and community members. Thank you for the opportunity to discuss the Saint Paul Police Department's use of public safety technology and more importantly, the safeguards that govern in its use. People have a right to ask, ask how these tools are used, who has access to them, how the information is protected, and what prevents its misuse. Those questions are not obstacles to this discussion. They are a reason for this discussion, and why we're here today. Technology does not supersede, nor does it replace constitutional policing. Technology must operate inside constitutional policing. Throughout this presentation, you will hear a reoccurring theme: lawful purpose, limited use, trained operators, documented actions, audibility, public transparency, and corrective action when necessary. When we discuss drones and our doctor drone program, it's important to understand what the program is and what it is not. It's designed to help train pilots respond more quickly on a high priority call for service. A drone can often arrive in minutes and provide information that helps officers make safer, more informed decisions before arriving on scene. However, faster response does not mean lower standards. Minnesota law, federal aviation regulations, department policy, training requirements, flight logs, audit controls, and reporting requirements all remain in place. These drones are not deployed for general surveillance. Their use must be lawful, documented, and reviewable. You will also hear about license plate reading technology. SPPD LPR use is only for specific public safety, and investigative purposes such as locating missing persons, recovering stolen vehicles, supporting criminal investigations, and identifying wanted vehicles. SPPD LPR technology does not identify drivers, it does not use facial recognition, it is not used to issue speeding tickets or red light citations. Queries require trained and authorized users, a documented reason and a case number. Access is logged, reviewed, and auditable. Again, our answer is not trust the technology. Our answer is constitutional policing, lawful purpose, documented use, audits, transparency, and accountability. A key component of that accountability is independent review, public reporting, audit requirements, data practices controls, compliance reviews, retention requirements, and access controls are designed to ensure that these systems can be examined, verified, and evaluated. Trust should be supported by evidence, not assumptions. You will hear about a real-time information center, or Arctic is what we call it. Arctic officers provide real-time information, situational awareness during active incidents. Their role is to improve officer and community safety, reduce uncertainty, and to provide actionable information during rapidly deploying events. Arctic operates under the same legal policy training, documentation, and audit requirements that govern technologies it uses. Finally, we will share examples where these tools have helped already to locate missing persons, interview and violent incidents, identify suspects, in serious crimes, respond to public safety threats, and assist people in crisis. The common threat in each example is not a broad monitoring system. It is a specific public safety purpose, a documented deployment and a defined legal basis for its use. Public safety and constitutional rights are not competing values. They must exist together. The standard we apply is simple. If a technology cannot be used lawfully, transparently and accountably, we should not be using it. As we move through this presentation, we will welcome questions and scrutiny, as that is part of accountability.
openpublica.com