Direct the City Administrator to establish a City Data and Privacy Office to advance privacy protections, steward data assets, and minimize risks from data brokers,…
After the decisionFollow-through is not tracked yetA final vote is not the same as the work being done.
In brief
From the official impact statement
Rapid advances in AI and surveillance tools have transformed ordinary data (transit records, utility data, traffic cameras, geolocation data, purchase records) into inputs for advanced behavioral and pattern-of-life analysis. Across the country, federal agencies and private contractors use multi-source datasets to identify, track, and monitor a wide range of communities and individuals, including but not limited to immigrants. As these tools become more sophisticated and more widely used, the City must adopt a unified, city-wide approach to data governance and privacy to ensure that Portland's systems are not repurposed for broad, population-level surveillance or…
This 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.
An 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.
Final action on 2025-481: Direct the City Administrator to establish a City Data and Privacy Office to advance privacy protections, steward data assets, and minimize risks from data brokers, uncontrolled sharing of personal information, and secondary data use
Official title: Direct the City Administrator to establish a City Data and Privacy Office to advance privacy protections, steward data assets, and minimize risks from data brokers, uncontrolled sharing of personal information, and secondary data use
WHEREAS, 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; andWHEREAS, the City of Portland has a core value of transparency to support accountability and democracy and has adopted the Open Data Resolution 36735 (adopted 2009) and established an Open Data Policy (Ordinance 188356, adopted May 2017), which, alongside the work of the Data Governance Planning and Analysis Team, led to the Citywide Data Governance Committee coordinated by BPS; and WHEREAS, since these policies were adopted, new generations of surveillance technologies, artificial intelligence (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 data, from geolocation and license plate scans to facial recognition, enabling the creation of detailed patterns of movement, association, and identity across entire communities; andWHEREAS, data 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. Data 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; andWHEREAS, federal law enforcement agencies exploit brokered datasets and 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; andWHEREAS, sensitive 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, upon aggregation or deanonymization, enable comprehensive surveillance of individuals and households well beyond the original context of collection; andWHEREAS, such 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; andWHEREAS, enterprise data governance enables organizations to make decisions about data and hold those that work with data accountable to data and privacy policies, including ordinances, resolutions, and City values; and WHEREAS, effective data governance requires knowledge and experience with business needs and strategy, data collection and analysis, data management, data culture change management; and WHEREAS, to address these emerging threats and close gaps in current protections, Council seeks 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, BE IT RESOLVED the City Council directs the City Administrator to establish a City Data and Privacy Office as shown in Exhibit A.BE IT FURTHER RESOLVED, this Resolution is binding City policy.
Meeting history3 meetings · 7 votes
Adopted as amendedAgenda item 14
Motion to amend Exhibit A as shown in Novick 3: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
Motion to amend Exhibit A as shown in Novick 3: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
Motion to amend Exhibit A as shown in Kanal 1: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
ContinuedAgenda item 12
Continued to February 5, 2026 at 2:00 p.m.
Referred to City Council as amendedAgenda item 4
Motion to amend the Resolution as shown in Novick 1: Moved by Novick and seconded by Morillo (Aye (4): Zimmerman, Morillo, Novick, Kanal; Nay (1): Smith)
Motion to table the Resolution, Document Number 2025-481: Moved by Zimmerman and seconded by Smith (Aye (2): Zimmerman, Smith; Nay (3): Morillo, Novick, Kanal). Motion failed to pass.
Motion to call the question: Moved by Morillo and seconded by Kanal. Motion approved by unanimous consent.
Motion to refer the Resolution, Document Number 2025-481, as amended to City Council with the recommendation it be adopted: Moved by Morillo and seconded by Novick (Aye (3): Morillo, Novick, Kanal; Nay (2): Zimmerman, Smith)
Read all 6 exact motions
Feb 5, 2026 · Amendment · Recorded
Motion to amend Exhibit A as shown in Novick 3: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
Feb 5, 2026 · Amendment · Recorded
Motion to amend Exhibit A as shown in Kanal 1: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
Dec 9, 2025 · Amendment · Recorded
Motion to amend the Resolution as shown in Novick 1: Moved by Novick and seconded by Morillo (Aye (4): Zimmerman, Morillo, Novick, Kanal; Nay (1): Smith)
Dec 9, 2025 · Main · Failed
Motion to table the Resolution, Document Number 2025-481: Moved by Zimmerman and seconded by Smith (Aye (2): Zimmerman, Smith; Nay (3): Morillo, Novick, Kanal). Motion failed to pass.
Dec 9, 2025 · Main · Passed
Motion to call the question: Moved by Morillo and seconded by Kanal. Motion approved by unanimous consent.
Dec 9, 2025 · Main · Passed
Motion to refer the Resolution, Document Number 2025-481, as amended to City Council with the recommendation it be adopted: Moved by Morillo and seconded by Novick (Aye (3): Morillo, Novick, Kanal; Nay (2): Zimmerman, Smith)
Motion to amend Exhibit A as shown in Novick 3: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
Meeting-level motion or recommendation · Feb 5, 202612 yes
Motion to amend Exhibit A as shown in Kanal 1: Moved by Novick and seconded by Kanal. (Aye (12): Avalos, Smith, Kanal, Pirtle-Guiney, Ryan, Koyama Lane, Morillo, Novick, Clark, Green, Zimmerman, Dunphy)
Meeting-level motion or recommendation · Dec 9, 20254 yes · 1 no
Motion to amend the Resolution as shown in Novick 1: Moved by Novick and seconded by Morillo (Aye (4): Zimmerman, Morillo, Novick, Kanal; Nay (1): Smith)
Meeting-level motion or recommendation · Dec 9, 20252 yes · 3 no
Motion to table the Resolution, Document Number 2025-481: Moved by Zimmerman and seconded by Smith (Aye (2): Zimmerman, Smith; Nay (3): Morillo, Novick, Kanal). Motion failed to pass.
Meeting-level motion or recommendation · Dec 9, 2025
Motion to call the question: Moved by Morillo and seconded by Kanal. Motion approved by unanimous consent.
Meeting-level motion or recommendation · Dec 9, 20253 yes · 2 no
Motion to refer the Resolution, Document Number 2025-481, as amended to City Council with the recommendation it be adopted: Moved by Morillo and seconded by Novick (Aye (3): Morillo, Novick, Kanal; Nay (2): Zimmerman, Smith)
0 human-reviewed findings are linked to this record. Unreviewed machine-extracted fragments are not presented as findings.
Technical information-completeness check · Ready With Caveats · Rules v2
This checks whether decision-relevant categories appear in the published packet. It does not recommend approval or opposition.
Decision definition
The official title and operative text identify the requested action.
Complete
Official legal text
Official text was found. This check does not certify that every referenced exhibit is complete.
Complete
Financial impact
The official impact statement includes financial information.
Complete
Funding source
The impact statement identifies funding information without an explicit unresolved-source qualifier.
Complete
Supporting documents
No linked attachments were found on the official page.
Unknown
Referenced exhibit integrity
The text references exhibits. This guide has not yet automatically verified that each referenced exhibit is present, populated, and internally consistent.
Unknown
Counterparty acceptance
The reviewed action is not expressly identified as a non-binding agreement.
Not Applicable
Implementation
A direction, reporting requirement, or deadline appears in the official text.
Complete
Document stability
Stability requires at least two observed snapshots; the system will update this after another ingestion.
Unknown
Source record
First discovered
Aug 13, 2026, 1:07 PM PDT
Last checked
Nov 13, 2026, 1:29 AM PST
Evidence hash
6c5907c7a6145d46
Guide status
Deterministic baseline
Append-only timeline
SOURCE UPDATED
Adopted as amended by council
DOCUMENT PUBLISHED
Observed in the official source.
Council Action
Adopted as amended
Council Action
Continued
Council Action
Referred to City Council as amended
Independent guide by Portland Civic Lab. Official City records are authoritative. Votes alone do not establish a Councilor’s reasons.