City contract
Canceled 4-2
Draft minutes now in the June 10 packet
Councilor McLeod Follow-up Workspace
The Flock vote opened a bigger Albany question.
On May 27, 2026, the Albany City Council voted 4-2 to cancel its Flock Safety contract. The June 10 agenda packet now carries draft May 27 minutes for approval, including the cancellation vote, the heavy public-comment record, and Councilor McLeod's follow-up request for legal analysis of citywide automated license plate reader rules.
The July 8 legal review has now happened — as a verbal-only briefing. The City Attorney described state-preemption, Equal Protection, and takings obstacles to a total ban, declined a councilor's request to put the analysis in writing, and the council directed staff to explore a narrower signage/disclosure ordinance at a work session in late August. This workspace pairs the official packet record with SB 1516, source records, and a model ordinance path so residents can separate what has happened from what still needs written analysis, closeout records, and data-deletion proof.
Legal briefing
Delivered July 8
Verbal only — written memo declined on privilege grounds
State law
SB 1516
Definitions, retention, audits, policies, vendors
Next step
~Aug 24
Work session on a signage/disclosure ordinance — the city's first actual ALPR ordinance if adopted
Plain-language guide
License plate readers, explained in two minutes.
You do not need to read SB 1516 or a model ordinance to follow this issue. Start with what the technology actually does, then dig into the records and drafting detail below as far as you want.
What an ALPR is
An automated license plate reader is a camera paired with software that reads every passing plate and logs the plate number, a photo, the time, the location, and vehicle details in a searchable database.
What it is not
It is not a red-light camera, a speed camera, or an ordinary security camera. Oregon law treats those separately. The question on the table is automated, networked, searchable plate databases.
Why a network is different from one camera
One camera sees a moment. A networked database can answer “where has this car been for the last month” — a map of daily life: home, work, school, worship, medical visits, meetings, and protests.
Where Albany stands today
The Council voted 4-2 on May 27, 2026 to cancel the city's Flock Safety contract. No city-run ALPR network operates today — and no ALPR chapter exists anywhere in the Albany Municipal Code, so the current "ban" is a contract termination plus council direction, not codified law. The council has directed staff to explore a signage/disclosure ordinance at a late-August work session.
Words you will see on this page
- Captured plate data
- The plate number plus the photo, time, location, and vehicle details an ALPR records.
- Hot list
- A list of plates that triggers an automatic alert whenever a camera sees a match.
- Retention
- How long the data is kept. SB 1516 sets 30 days for routine law-enforcement reads.
- Audit log
- The record of who searched the data, when, and for what stated reason.
- Preemption
- Whether state law blocks stricter local rules or only sets a statewide floor.
- Home rule
- Oregon cities' authority to legislate on local matters unless state law clearly displaces it.
Flock timeline
How Albany got from one contract to a citywide surveillance question.
Follow the public record in order: what happened, what the June 10 packet now documents, what ARP drafted, and where residents can participate next.
01 / Before May 27
Flock record builds up
Albany's Flock Safety question had already moved through public safety materials, vendor claims, community concern, and a long suspension before the Council took it up again.
02 / May 27, 2026
Neighbors fill the public record
Public testimony focused on vehicle-location data, private vendor control, cybersecurity, federal access, and whether routine plate capture belongs in city life.
03 / May 27, 2026
Council cancels the contract
The Council voted 4-2 to cancel Albany's Flock Safety contract effective immediately. The closeout records, deletion proof, and audit trail still matter.
04 / After the vote
Councilor McLeod asks the bigger question
Councilor McLeod asked City Attorney Sean Kidd to review what Albany can lawfully do about public and private ALPR systems inside city limits.
05 / June 10, 2026 packet
Draft minutes enter the next agenda packet
The June 10 agenda packet includes draft May 27 minutes for approval, documenting the 4-2 Flock cancellation vote, the public-comment volume, and the request for ALPR legal analysis.
06 / July 8, 2026
Briefing delivered — verbally only
The City Attorney briefed the council on ban feasibility (preemption, Equal Protection, takings) but declined a councilor's request to put the analysis in writing, citing privilege. The council directed staff to explore a signage/disclosure ordinance instead.
07 / ~Aug 24, 2026
Work session: signage ordinance
The council's chosen next step. If adopted, it would be Albany's first actual ALPR ordinance — no ALPR chapter exists in the Municipal Code today. The ask: written options materials in the record before any further direction.
The Ask & Public-Trust Inquiry
Detailing Councilor McLeod's request to City Attorney Sean Kidd.
Following high public engagement and a clear call for surveillance guardrails, Councilor McLeod requested that the City Attorney analyze the lawful options Albany has to regulate ALPR data and networks. That analysis arrived July 8 as a verbal-only briefing: a total ban was framed as facing preemption, Equal Protection, and takings obstacles; a councilor's request for the analysis in writing was declined on privilege grounds; and the council directed staff to explore a signage/disclosure ordinance at a late-August work session. The five questions below remain the ones a written record still needs to answer.
Does SB 1516 preempt stricter Albany ALPR rules, or does it set a statewide floor?
Can Albany ban City/APD deployment, operation, contracting, and use of ALPR systems?
Can Albany prohibit APD access to private ALPR data except by warrant, court order, subpoena, or documented emergency?
Can Albany regulate or ban private ALPR systems that capture public streets, parking areas, rights-of-way, or places open to the public?
Which enforcement tool is strongest: civil penalty, permit denial, nuisance abatement, contract bar, exclusion of city use, or complaint right?
Our Draft Ordinance
A structured, defensible model ordinance for local privacy.
Our draft ordinance maps out options systematically: it bans public agency deployment, prevents private data workarounds that bypass court processes, regulates private networks scanning public rights-of-way, and embeds a robust fallback registration model to preserve maximum legal protection even if specific provisions face challenges.
Sections 4-5
City ALPR use and access to public or private ALPR data are barred.
Sections 6-8
Court process, crime-victim reports, real emergencies, secured-area access control, and parking management are narrowly preserved.
Sections 9-14
Private public-road ALPR systems, notice, cure, hearings, transparency, complaints, and proportionate enforcement are defined.
Section 18(D)
If the private-system ban is narrowed, the ordinance falls back to registration, notice, retention, audit, no-sharing, and deletion rules.
Ordinance stack
A constitutional-safe path for Albany.
Regulate automated extraction, retention, public-right-of-way capture, searchability, and sharing, not ordinary cameras or speech.
Layer 1
City/APD use ban
Safest
No City agency, contractor, employee, or officer may deploy, operate, contract for, or use ALPR systems.
Layer 2
Private-data access ban
Very strong
No Albany official or APD employee may request, receive, buy, search, access, rely on, or act on private ALPR data except by narrow legal process or emergency.
Layer 3
Private public-road rule
Contested
Regulate ALPR systems that capture public-facing traffic and upload, store, sell, share, or make the data searchable through a third-party network.
Layer 4
Speech carveout
Required guardrail
Protect ordinary photography, journalism, recording public officials, and security cameras that do not perform automated plate recognition.
Layer 5
Takings protection
Drafting shield
Regulate operation and data use; do not confiscate equipment.
Constitutional frame
Public visibility is not the same as searchable movement history.
One plate view is observation. Plate reads plus GPS coordinates, timestamps, images, vehicle characteristics, alerts, search logs, databases, and multi-agency access are surveillance infrastructure.
Oregon Article I, section 9
State v. Campbell supports treating technology-aided vehicle tracking as constitutionally significant scrutiny.
Article I, sections 8 and 26
ALPR near civic, legal, religious, medical, union, or protest activity can chill participation and association.
Federal analogy
Jones and Carpenter do not ban ALPRs, but they support the line between one observation and persistent location history.
SB 1516 map
Oregon already treats ALPR data as regulated movement data.
Section 3
Definitions
ALPR systems, captured plate data, alerts, hot lists, secured areas, and photo red-light/photo-radar carveouts.
Section 4
Law-enforcement use
Authorized uses, 30-day ordinary retention, search logs, visual confirmation before stops, and the private-data access sentence.
Section 5
Sharing limits
Outside-government access must be purpose-limited and cannot become unrestricted or ongoing access.
Section 6
Audits
Monthly and quarterly searchable audits, camera locations, searches, access lists, alerts, and two-day publication.
Sections 7-9
Policies and vendor duties
Public policies, ownership, encryption, CJIS terms, existing contracts, vendor misuse limits, and civil actions.
Sections 10-11
Grants and public records
Organized-retail-theft grant compliance and ORS 192.345(44) redacted audit disclosure.
For City staff and the City Attorney's office
A working crosswalk from SB 1516 to the model ordinance.
This page is offered as civic assistance for the ~August 24 work session, not as a demand letter. The July 8 briefing was delivered verbally and no written analysis was produced, so this crosswalk is currently the most complete written record on the question. It shows where the model draft tracks the state floor and where it goes further, so each drafting choice can be accepted, narrowed, or rejected on its own terms. Every provision links back to a public source, and the full draft is printable from the ordinance page.
| State floor (SB 1516) | Model ordinance response |
|---|---|
| SB 1516 §3 — Definitions | Model §3 adopts definitions that read together with the state terms, then adds terms the statute does not reach: private networks, shared databases, and third-party access. |
| SB 1516 §4 — Law-enforcement use, 30-day retention, search logs | Model §§4–5 go past the floor: a City deployment-and-use ban plus a data-access ban, with §§6–7 preserving warrants, court orders, subpoenas, and documented emergencies. |
| SB 1516 §5 — Sharing limits | Model §5 closes the indirect route: no access through vendors, subscriptions, mutual-aid requests, or other agencies that the City could not obtain directly. |
| SB 1516 §6 — Audits and publication | Model §12 sets public-records and audit duties; §16 adds an annual Council review so compliance stays on the public calendar. |
| SB 1516 §§7–9 — Policies, vendor duties, civil actions | Model §§10–11 and §14 cover notice-and-cure with hearing rights for private operators, closeout of existing contracts, devices, and data, and proportionate civil enforcement. |
| Beyond the statutory floor | Model §9 regulates private public-road systems while preserving parking management and crime-victim incident reports, §10 gives existing operators a 90-day compliance window, §15 bars retaliation, and §18 falls back to registration-and-audit rules if the private-system ban is narrowed. |
Challenge matrix
Stress-test the ordinance before opponents do.
The July 8 briefing named several of these risks verbally but produced no written analysis. A written options memo for the work session should name the likely attacks — with the standard of review for each — and answer them in the ordinance structure.
| Challenge | Answer needed |
|---|---|
| State preemption | Does SB 1516 leave room for stricter local rules? |
| Private property | Can Albany regulate private devices when they scan public travel? |
| Speech | Is the ordinance regulating automated data extraction rather than expression? |
| Takings | Is this a use regulation rather than equipment seizure? |
| Public safety | Which warrant, subpoena, court-order, and emergency exceptions are needed? |
| Immigration access | How does Albany prevent public resources from supporting prohibited enforcement? |
| Cybersecurity | What independent review is required before any future exception? |
| Local precedent | How does an ALPR placement or disclosure rule differ legally from the cryptocurrency-kiosk rules Albany already enforces (AMC 7.06: placement limits and seizure authority over private equipment on private commercial property)? |
Records checklist
The record still needs a preservation trail.
The July 8 briefing left no written record. Without these documents, residents are left guessing about closeout, data deletion, access, audits, security, private pipelines — and the legal analysis the next ordinance direction rests on.
Cancellation notice and termination-fee analysis
Deployment, demo, activation, suspension, and reactivation records
Any collected data and deletion or return certificate
Access logs, search logs, sharing logs, hot-list entries, and support-access logs
Monthly and quarterly SB 1516 audit records and publication timestamps
APD ALPR policy drafts and vendor contract/security terms
IT/security review, CVE responses, DHS/ICE/CBP statements, retention and deletion claims
The written ALPR options memo the July 8 briefing did not produce (requested by a councilor; declined on privilege grounds — the privilege is the council's to waive)
The insurance carrier's (CIS) written response on ALPR liability, with a privilege log for anything withheld
The law-enforcement list of the ~30 Albany businesses said to operate ALPRs (unsourced at the briefing; conflicts with a councilor's list of ~6)
Frequently asked questions
The five questions the July 8 briefing left open.
These answers reflect Albany Records Project research positions, not legal advice. The City Attorney's July 8 review was delivered verbally and not reduced to writing, so these questions remain without an official written answer. This page will be updated if one is produced for the late-August work session.
Does SB 1516 preempt stricter Albany ALPR rules, or does it set a statewide floor?
SB 1516 regulates law-enforcement ALPR use and monthly audits, setting a statewide statutory floor while leaving room for local municipalities to explore more protective local policies.
Can Albany ban City/APD deployment, operation, contracting, and use of ALPR systems?
Yes, municipalities have direct authority over their own agency operations, contracting, and public resource allocations, making a City/APD deployment ban a legally straightforward regulatory choice.
Can Albany prohibit APD access to private ALPR data except by warrant, court order, subpoena, or documented emergency?
Yes, local ordinances can establish strict procedural safeguards to prevent city agencies and law enforcement from bypassing public rules through unchecked private-sector data pipelines.
Can Albany regulate or ban private ALPR systems that capture public streets, parking areas, rights-of-way, or places open to the public?
Regulating private systems scanning public rights-of-way is legally contested. While the city can regulate automated data extraction and public-road captures, a strict permit system or registration fallback is often drafted alongside a ban to protect constitutionally protected photography and personal privacy.
Which enforcement tool is strongest: civil penalty, permit denial, nuisance abatement, contract bar, exclusion of city use, or complaint right?
A multi-layered enforcement structure utilizing notice-and-cure periods, civil penalties, permit denial for non-compliant private operators, and explicit complaint rights provides the most balanced and resilient framework.
Source dashboard
35 reviewed public sources support the packet.
12
Case law
5
State law
4
Meeting records
3
Legal authority
2
Cybersecurity
2
Federal law
State law
Oregon SB 1516 enrolled ALPR provisions
Enrolled Senate Bill 1516 from the 2026 regular session. Sections 3 to 9 define ALPR systems and captured license plate data, restrict law-enforcement use, recognize law-enforcement requests for private or non-law-enforcement ALPR data, limit ordinary retention to 30 days for non-investigative data, require visual confirmation before ALPR-based stops, limit sharing, require monthly and quarterly searchable audits, require public policies and vendor-contract terms, address existing contracts, and create civil remedies for improper vendor access or disclosure. Related sections require organized-retail-theft grant ALPR purchases to comply with Sections 3 to 9, amend ORS 192.345 with ALPR audit-disclosure rules, and include an emergency clause.
Public sourceCase law
State v. Campbell, 306 Or 157 (1988)
Oregon Supreme Court Article I, section 9 decision holding that police use of a radio transmitter to locate a vehicle was a search, rejecting a federal-style reasonable-expectation-of-privacy formula for Oregon searches, and explaining that technology-aided government practices can significantly impair the people's freedom from scrutiny.
Public sourceCase law
Schwartz v. Washington County, 375 Or 227 (2026)
Oregon Supreme Court home-rule/preemption decision holding that a county flavored-tobacco ban was not preempted by statewide tobacco licensing law because the statute did not unambiguously show legislative intent to make state law exclusive and the local ordinance could operate concurrently.
Public sourceState constitutional authority
Oregon Constitution Article I rights
Official Oregon Constitution text, including Article I, section 8 free expression, section 9 search and seizure, section 18 takings, and section 26 peaceable assembly, instruction of representatives, and petition for redress.
Public sourceCase law
Carpenter v. United States, 585 U.S. ___ (2018)
United States Supreme Court decision holding that government acquisition of historical cell-site location records was a Fourth Amendment search and describing long-term location data as a detailed chronicle of a person's physical presence. Used as a location-privacy analogy for searchable ALPR movement databases, not as a direct ALPR holding.
Public sourceCase law
United States v. Yang, 958 F.3d 851 (9th Cir. 2020)
Ninth Circuit decision involving ALPR database evidence. Useful for explaining the architecture of private ALPR databases and law-enforcement access even though the court did not squarely decide the broader Fourth Amendment ALPR search question.
Public sourceHow to participate
This project provides the research, but official public comments belong with the City. We encourage all Albany neighbors to submit formal written testimony to the City Council to ensure your voice is officially on the record.