Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Privacy topic
No spam. Unsubscribe anytime.
Council defers vote on $150,000 Paragrin police‑data subscription after privacy, security concerns
Summary
A public commenter urged the council to remove a $150,000 appropriation to subscribe to Paragrin, a vendor product intended to integrate police data. The police chief described the system as CJIS‑compliant and said it would help analysts; council asked for legal and cybersecurity details and deferred action to a future meeting.
A public commenter and several council members raised privacy and civil‑liberties concerns about a proposed $150,000 appropriation to purchase a one‑year subscription to Paragrin, a private data‑integration product intended to unify separate police and public‑safety data systems.
At public comment, a resident identified as Mo asked council to remove the Paragrin appropriation from the consent agenda and called the product “a panopticon,” arguing it centralizes law‑enforcement data, entrenches surveillance practices and creates substantial risks if accessed by outside parties. “If Seville police want to improve data efficiency, they should hire someone to do that in‑house, not offload all storage, management and analytics to a private company in another state that is literally trying to build the future from Minority Report,” Mo said.
A police representative explained the operational case for the product: Paragrin would integrate disparate systems (records management, computer‑aided dispatch, body‑worn camera storage and other analytic feeds) to make data queries feasible across sources and to support community‑stat analysis. The chief described Paragrin as CJIS‑compliant (criminal‑justice information systems security standards) and said data would be stored locally and in the cloud on the same AWS services the department already uses for body‑camera storage. The chief said authorized users must complete required CJIS training to gain access.
Council members expressed both openness to improved data analytic capacity and concern about centralizing sensitive data with a third‑party vendor. Members requested detailed answers about (1) data ownership and vendor rights, (2) where data would be hosted and how it would be protected from unauthorized access, (3) what access other agencies or the vendor would have, and (4) the legal framework for responding to requests (FOIA, warrants, or federal demands). Staff said they would return with vendor and technical detail and recommended having the city attorney review contract and privacy terms.
The appropriation remained on the calendar but council deferred final action, asking staff to bring back legal, cybersecurity and contractual protections and, if needed, a vendor representative to answer technical questions at a future meeting.
