Passed · 12–0
Final action on 2025-480: Add Code to establish a City Data and Privacy Office (add Code Chapter 3.39)
Each stop is a meeting in the official record, with the City’s own words for what happened.
Not applicable.
Official community impact statementThis legislation does not require changes to current FTE or budgets and does not result in new financial obligations. Instead, staff are directed to establish a Data and Privacy Office and create a transition plan, detailing what staff is necessary for the office. After functions and staffing are identified, a plan for resourcing both data governance and privacy work will be produced to be taken up in the budget.
Official financial impact statementAn Economic and Real Estate Development Impact Analysis was not submitted for this proposed action. Pursuant to City Council Resolution 37664, Prosper Portland staff has reviewed the action and agree that it does not require an Economic and Real Estate Development Impact Analysis.
Economic and real estate development analysis, provided by Prosper PortlandThis ordinance would establish a City Data and Privacy Office in Chapter 3 of Portland City Code, creating a new bureau. The creation of a new bureau would likely require creating new positions, specifically the creation of a Chief Data Officer, which would likely add costs, as the City does not currently have a Chief Data Officer classification. Additionally, budgeting a new organizational unit would require either realigning resources from existing programs or adding resources. If existing positions are identified for realignment, resources supporting those positions may or may not be able to move with them depending on whether they are restricted fund sources. In summary, standing up a new operating bureau that completes the work outlined in this resolution would require either reprioritizing existing work or adding costs for new positions.
Financial and budget analysis, provided by City Budget OfficeFinal action on 2025-480: Add Code to establish a City Data and Privacy Office (add Code Chapter 3.39)
Official title: Add Code to establish a City Data and Privacy Office (add Code Chapter 3.39)
Ordinance 192143Final official action · Portland.govThe City of Portland ordains.Section 1. The Council finds:The City of Portland has built a legacy of privacy protections through prior Council actions, including Resolution 37437 (adopted June 19, 2019) establishing Privacy and Information Protection Principles; Ordinances 190113 and 190114 (adopted September 9, 2020) prohibiting the use of face recognition technologies by City bureaus and in public accommodations; and Resolution 37608 (adopted February 1, 2023) establishing a Citywide Surveillance Technology Inventory and privacy review processes; andThe City of Portland has a core value of transparency to support accountability and democracy and has adopted the Open Data Resolution 36735 (adopted September 30, 2009) and established an Open Data Policy (Ordinance 188356, May 2017); and Since these policies were adopted, new generations of surveillance technologies, AI enabled camera networks, automated license plate reader (ALPR) systems connected to nationwide sharing platforms and interconnected "smart city" sensors embedded in traffic systems and public spaces, have expanded the scope and precision of government and commercial monitoring. These systems generate continuous streams of data, often analyzed in real time, and combine disparate sources, from geolocation and license plate scans to facial recognition, enabling the creation of detailed patterns of movement, association, and identity across entire communities; andData brokers play a central role in this evolving surveillance ecosystem by aggregating and selling personal information from multiple sources, including public records and state and local data streams. These brokers increasingly provide services to federal law enforcement agencies and other entities seeking to circumvent local privacy and sanctuary safeguards, allowing sensitive data originally collected for municipal purposes to be repurposed for unrelated enforcement or profiling activities; andFederal law enforcement agencies exploit these brokered datasets and also access state and national information sharing systems, creating indirect pathways to City originating data that bypass local oversight and frustrate the intent of Portland's privacy principles and sanctuary policy; andSensitive data most at risk including but not limited to categories defined by the Oregon Consumer Privacy Act, personally identifiable information, biometric identifiers, and geolocation or utility data, which, when aggregated or deanonymized, enable comprehensive surveillance of individuals and households well beyond the original context of collection; andThese risks fall disproportionately on marginalized communities, including Black, Indigenous, and other people of color; immigrants; unhoused Portlanders; people living with mental health conditions; and individuals engaged in protest or civic activity, exacerbating inequities and eroding public trust in government; andEnterprise data governance enables organizations to make decisions about data and hold those that work with data accountable to data policies; and Effective data governance requires knowledge and experience with business needs and strategy, data collection and analysis, data management, data culture change management, and is distinct from information technology expertise; and To address these emerging threats and close gaps in current protections, Council seeks to establish a City Data and Privacy Office to enable data minimization, strengthen contractual controls, improve data security and advance data governance maturity, while enhancing public transparency and community oversight to prevent the misuse of City originating data and reaffirm Portland's sanctuary and privacy commitments.NOW, THEREFORE, the Council directs:Add City Code Chapter 3.39 as shown in Exhibit A.
Motion to amend Exhibit A as shown in Novick 1: Moved by Kanal and seconded by Koyama Lane. (Aye (11): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Dunphy; Absent (1): Zimmerman) Passed to second reading as amended February 5, 2026 at 2:00 p.m.
Motion to amend Exhibit A to remove the second sentence in Subsection 3.39.020 B.1.: Moved by Zimmerman and seconded by Smith (Aye (1): Zimmerman; Nay (4): Smith, Morillo, Novick, Kanal). Motion failed to pass. Motion to refer the Ordinance, Document Number 2025-480, to City Council with the recommendation it be passed: Moved by Morillo and seconded by Novick. (Aye (4): Zimmerman, Morillo, Novick, Kanal; Nay (1): Smith)
Motion to amend Exhibit A as shown in Novick 1: Moved by Kanal and seconded by Koyama Lane. (Aye (11): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Dunphy; Absent (1): Zimmerman) Passed to second reading as amended February 5, 2026 at 2:00 p.m.
Motion to amend Exhibit A to remove the second sentence in Subsection 3.39.020 B.1.: Moved by Zimmerman and seconded by Smith (Aye (1): Zimmerman; Nay (4): Smith, Morillo, Novick, Kanal). Motion failed to pass.
Motion to refer the Ordinance, Document Number 2025-480, to City Council with the recommendation it be passed: Moved by Morillo and seconded by Novick. (Aye (4): Zimmerman, Morillo, Novick, Kanal; Nay (1): Smith)
Motion to amend Exhibit A as shown in Novick 1: Moved by Kanal and seconded by Koyama Lane. (Aye (11): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Dunphy; Absent (1): Zimmerman) Passed to second reading as amended February 5, 2026 at 2:00 p.m.
Motion to amend Exhibit A to remove the second sentence in Subsection 3.39.020 B.1.: Moved by Zimmerman and seconded by Smith (Aye (1): Zimmerman; Nay (4): Smith, Morillo, Novick, Kanal). Motion failed to pass.
Motion to refer the Ordinance, Document Number 2025-480, to City Council with the recommendation it be passed: Moved by Morillo and seconded by Novick. (Aye (4): Zimmerman, Morillo, Novick, Kanal; Nay (1): Smith)
0 human-reviewed findings are linked to this record. Unreviewed machine-extracted fragments are not presented as findings.
This checks whether decision-relevant categories appear in the published packet. It does not recommend approval or opposition.
The official title and operative text identify the requested action.
Official text was found. This check does not certify that every referenced exhibit is complete.
The official impact statement includes financial information.
The impact statement identifies funding information without an explicit unresolved-source qualifier.
No linked attachments were found on the official page.
The text references exhibits. This guide has not yet automatically verified that each referenced exhibit is present, populated, and internally consistent.
The reviewed action is not expressly identified as a non-binding agreement.
A direction, reporting requirement, or deadline appears in the official text.
Stability requires at least two observed snapshots; the system will update this after another ingestion.
Passed as amended by council
Observed in the official source.
Passed as amended
Passed to second reading as amended
Referred to City Council
Independent guide by Portland Civic Lab. Official City records are authoritative. Votes alone do not establish a Councilor’s reasons.