Committee advances plan for city data and privacy office after debate over scope and timelines

The Community and Public Safety Committee on Dec. 9 advanced an ordinance to establish a City Data and Privacy Office and referred a companion resolution with amendments to the full City Council after extensive public testimony and debate about timing, scope and resourcing.

Co‑sponsors and presenters said the office would centralize data governance, develop a unified privacy framework across bureaus, steward sensitive information, reduce vendor and secondary‑use risks, and improve public trust. Presenters identified the proposed ordinance as a city‑operations‑housed office led by a chief data officer with rule‑making authority and described the office’s work as covering data governance, privacy reviews, vendor contract language and public‑facing transparency. Zack Ward (Councilor Novick’s policy aide) and Susie Duister (Councilor Murillo’s policy adviser) framed the proposal as responding to evolving technology risks including AI, third‑party data brokers and examples of federal access to municipal data.

Speakers repeatedly cited concerns about automated license‑plate readers and vendor reuse of municipal data. Community witnesses who spoke in support included Sean Patrick of PDX Privacy, who called privacy a "fundamental human right," Jesse Dearing (a tech privacy advocate), independent researcher Kate Kaye and other privacy and cybersecurity professionals; they urged centralized authority and transparency and asked for strong staffing and funding.

Council debate focused on two interrelated questions: whether the ordinance should enshrine detailed implementation steps (for example, requiring privacy impact assessments — PIAs — before deployment of surveillance or AI systems) or leave those operational timelines to a companion resolution and subsequent work by the city administrator; and whether the proposed office could be stood up by realigning existing staff or would require new, resourced hires. An amendment to remove the ordinance sentence requiring pre‑deployment PIAs was put to a roll call vote and failed. Councilors then adopted a separate amendment to the resolution requiring that a city staff member be appointed or hired as an interim or ongoing chief data officer prior to submission of the written transition plan to council; that amendment passed 4–1.

On the committee votes: the ordinance to create the City Data and Privacy Office was referred to full council with a due‑pass recommendation (committee vote recorded 4–1). The companion resolution, as amended to require an interim chief data officer and set target deadlines for reporting, was referred to full council with a recommendation it be adopted (committee vote recorded 3–2).

Administration and staff clarified several points on the record: Smart City/Planning & Sustainability staff (Hector Dominguez) described the city’s existing privacy impact assessment work tied to the 2021 surveillance inventory resolution and noted it has been implemented in pilot contexts; Deputy City Administrator Tracy Warren and DCA Donnie Olivera said staff have been engaged in developing the proposal, that existing work is under‑resourced, and that centralization aims to create consistent standards and accountability across bureaus.

Next steps: both the ordinance and the amended resolution will be considered by full City Council; committee sponsors and staff indicated additional refinement of timelines and administrative impact statements will be part of that transition work.