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 targeted monitoring of vulnerable groups.The purpose of this resolution, in conjunction with the accompanying ordinance, is to direct the creation of the City Data and Privacy Office, located in the City Operations service area, and to establish the role of Chief Data Officer (CDO). This office will be tasked with improving privacy protections, stewarding data assets, and minimizing risks from data brokers, uncontrolled sharing of sensitive personal information, and secondary data use, including Large Language Models (LLMs) for the use and development of artificial intelligence, and assessing other privacy and data governance issues as outlined in this resolution.Establishing this office will create for a more centralized authority on data governance and privacy in the city, allowing for a more unified approach to data and privacy protection. Upon establishment, data governance work will be consolidated within the City Data and Privacy Office, with the Office functioning as the City authority. The City Data and Privacy Office will continue to collaborate with the Office of Equity and Human Rights to ensure appropriate consideration of equity impacts and will work closely with the Bureau of Technology Services to ensure data governance needs guide information technology decisions and information technology planning supports long-term stewardship of City data assets.
Official proposal and impact statementShould Portland direct the City Administrator to establish a City Data and Privacy Office to advance privacy protections, steward data assets, and minimize risks from…
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 targeted monitoring of vulnerable groups.The purpose of this resolution, in conjunction with the accompanying ordinance, is to direct the creation of the City Data and Privacy Office, located in the City Operations service area, and to establish the role of Chief Data Officer (CDO). This office will be tasked with improving privacy protections, stewarding data assets, and minimizing risks from data brokers, uncontrolled sharing of sensitive personal information, and secondary data use, including Large Language Models (LLMs) for the use and development of artificial intelligence, and assessing other privacy and data governance issues as outlined in this resolution.Establishing this office will create for a more centralized authority on data governance and privacy in the city, allowing for a more unified approach to data and privacy protection. Upon establishment, data governance work will be consolidated within the City Data and Privacy Office, with the Office functioning as the City authority. The City Data and Privacy Office will continue to collaborate with the Office of Equity and Human Rights to ensure appropriate consideration of equity impacts and will work closely with the Bureau of Technology Services to ensure data governance needs guide information technology decisions and information technology planning supports long-term stewardship of City data assets.
Official impact statementSee the official legal 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
Can Portland turn broad privacy principles into enforceable, funded controls over City data, vendors, surveillance tools, and AI?
What this proposal would actually do.
Plain-language orientation first. Every substantive statement below links to its official basis.
The reviewed sources do not clearly identify every existing policy, service, contract, or obligation that would remain unchanged.
Official matter recordThis proposal concerns government & democracy and requires action through Portland’s public legislative process.
Official matter classification and recordNot applicable
Official community impact statementWhat the record establishes and what it does not.
Votes show choices. They do not, by themselves, prove why a member made that choice.
Passed · 12–0
Read the exact motion or vote question
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
We will not turn the roll call into invented arguments.
The vote above establishes who supported or opposed that exact motion. A source-validated account of the competing reasons will appear only after human review of the meeting transcript and documents.
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.
Official financial impact statement- The source-linked record has not yet received a human review of competing arguments. A yes or no vote alone does not establish a Councilor’s rationale.
- What implementation evidence will show whether the intended result occurred?
Official testimony on this decision has closed. Residents can still contact their district Councilors about implementation and follow-up.
Official Council agendaInspect the complete research record.
Official text, source files, exact motions, roll calls, provenance, and the technical completeness check remain available without crowding the explanation above.
Official documents1 sources
The operative official record after Council action.
Open at Portland.govRead the full official text
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.
Meetings, motions, amendments, and votes3 meetings · 7 votes
Recorded amendments
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)
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 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
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)
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)
Meeting-level motion or recommendation · Feb 5, 202612 yes
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)
Final Council action · Feb 5, 202612 yes · 0 no
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
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)
Data quality, timeline, and provenanceRules v2
Unreviewed keyword matches and machine-extracted fragments are not presented as authoritative findings. Only 0 human-reviewed findings are available for this matter.
Technical information-completeness check · Ready With Caveats
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.
- First discovered
- Aug 13, 2026, 1:07 PM PDT
- Last checked
- Sep 13, 2026, 2:26 AM PDT
- Evidence hash
- 559d118790e04e8c
- Guide status
- Deterministic baseline
- 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