Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Surveillance Technology topic
No spam. Unsubscribe anytime.
City reviews surveillance-technology and military-equipment reports; staff outlines data safeguards
Summary
City staff presented annual reports on surveillance technology and military-equipment inventory required under AB481 and described contractual and technical safeguards (local storage, vendor contract terms) intended to prevent off‑site sharing of data; commissioners asked about fleet counts, rifle assignment, UAS costs and speed trailers.
Get email alerts on the Surveillance Technology topic
No spam. Unsubscribe anytime.
City staff presented the annual surveillance-technology and military-equipment reports required under state law (transcript references to AB481) and explained how the reports will be used in the staff report to city council. The presentation summarized inventory changes, replacement planning and oversight elements for each technology listed for the coming year.
Staff reviewed that surveillance systems must be supported by an approved use policy and that each piece of equipment listed in the annual report requires an impact report and council approval before procurement. The department said it does not use a vendor called Flock and stressed contractual protections when selecting a third-party vendor; staff cited contract terms and audits as reasons the department selected Motorola for certain surveillance solutions.
On data-sharing limits, presenters said California law restricts sharing surveillance data to in-state agencies and that the city audits access logs (who accessed footage, IP addresses and justifications) to detect unauthorized use. Staff emphasized that some devices store footage locally on removable media and that footage is routinely uploaded to servers when officers return to vehicles or to base.
Commissioners asked routine inventory questions: the chief said the department has about 15-18 fully marked patrol vehicles and explained that rifles are issued and sighted to individual officers, which is why the inventory count reflected one rifle per officer. Staff also described the annual cost components for UAS operations (flight-tracking software, replacement parts and training) and estimated the recurring software and maintenance costs.
A resident asked whether solar-powered radar speed-trailers that display vehicle speed are considered surveillance; staff explained those devices do not capture personally identifiable data and therefore are not covered by the surveillance-technology ordinance. Staff also noted that a small number of higher-intermediate less-lethal devices (for example extended-range 40mm sponge rounds) are retained for rare, high-risk incidents and that policy and training specify appropriate distances and circumstances for deployment.
No formal votes were recorded on the surveillance or military-equipment presentations at this meeting; staff said inventory updates and any proposed procurements will return to council through the usual staff-report process.

