Albany's 4-2 cancellation vote ended one contract. The next source-backed question is how far the City can regulate ALPR use, private plate data, audits, deletion, and future exceptions.
Updated July 9, 2026
Source review completed May 28, 2026
The legal analysis Councilor McLeod requested arrived July 8, 2026 as a verbal-only briefing. The City Attorney told the council a citywide ban would face state-preemption, Equal Protection, and Fifth Amendment takings problems; said the city's insurer advised against it; and declined a councilor's request to put the analysis in writing, citing attorney-client privilege. No vote was taken. The council directed staff to explore a narrower signage or disclosure ordinance at a work session in late August. Two record facts matter going forward: no ALPR chapter exists anywhere in the Albany Municipal Code, so the existing public-property posture is a contract termination plus council direction rather than codified law — and the city already regulates privately owned technology on private commercial property through its cryptocurrency-kiosk rules (AMC Chapter 7.06), a local precedent for the placement-and-disclosure path now under discussion. Details continue in the companion article, The July 8 Line: Banning ALPRs.
Albany neighbors did something concrete on May 27, 2026: they showed up, waited through a long council meeting, followed the public comment rules even when applause and signs were shut down, and put enough source-checkable concern into the record that the City Council cancelled the City's Flock Safety contract. The final vote was 4–2 on a motion to cancel the contract effective immediately.
The June 10 packet's draft May 27 minutes record Councilors Newton, Thomson, Van Drimmelen, and McLeod voting yes, with Councilors Smith and McGhee voting no. Approved minutes should remain the controlling vote record once adopted.
This article does not treat every public comment claim as established fact. It treats the meeting itself as the record — a room full of neighbors asking whether Albany should normalize routine license plate capture by a private vendor, and a Council majority deciding public trust mattered more than finishing the remaining seven months of the contract.
This is a Councilor McLeod follow-up packet, not a personal packet against City Attorney Sean Kidd. Council asked a serious question; neighbors can help build the public records, and staff needs to answer it. This is not an anti-police project. It is a public trust, privacy, cybersecurity, and local government project. Albany now has a chance to decide whether automated public movement databases belong inside city limits at all — and if so, under what rules?
The May 27 agenda packet listed Flock as Action Item 7a: a verbal automated-license-plate-reader discussion and Public Safety Commission recommendation from Police Chief Marcia Harnden. The packet did not include a written ALPR staff memo for the vote. The June 10 packet now adds draft minutes, but the meeting video, APD public materials, contract records, termination records, and written public comments remain especially important.
The cancellation vote ends Albany's own Flock contract. It does not, by itself, ban private ALPR systems, camera systems owned by other public agencies, Oregon State Police vehicle-mounted ALPR, Benton County activity in North Albany, or future council attempts to regulate surveillance technology.
APD's public case for the system was that Flock captures still images of vehicles and license plates, not continuous video or facial recognition; that Albany would use a 30-day retention period; that sharing would be limited to Oregon law enforcement; and that prohibited uses, reason codes, audit logs, and reporting would create local guardrails.
Most public testimony pushed the other way. Neighbors raised concerns about vehicle-location data, private vendor control, cybersecurity, federal or out-of-state access, surveillance creep, contract incentives, and the harder civic question: whether residents can trust a system once the data leaves local hands.
Albany neighbors used the process, stayed in the room, spoke from many angles, and changed the outcome of a public safety technology decision. That is not adversarial citizenship; that is what a working city is supposed to look like.
During public testimony, the mayor enforced decorum rules against clapping and signs. Yet neighbors still found a way to be visible without turning the meeting into disorder. Councilor Van Drimmelen later thanked the public for the unusually large turnout and for shifting into quiet, unobtrusive support inside the rules. City Manager Peter Troedsson also closed by describing the audience as orderly and respectful. Here is the applause the chamber did not allow: they used the process, stayed in the room, and changed the outcome of a public technology decision.
After the vote, Councilor McLeod pushed for a broader ordinance addressing ALPR systems inside Albany city limits, including public and private systems. The City Attorney flagged legal complications and committed to research before ordinance drafting. Source review places the return date at July 8, 2026 and records that the City's review would take at least four weeks, depending on scope.
The local record gives staff a real assignment. The agenda listed the item as 'Flock Automated License Plate Reader Camera Discussion and recommendation from the Public Safety Commission.' Councilor McLeod described public comment as highly influential and treated the issue as a larger public-trust problem, not just a camera-placement problem. Her proposed direction asked staff to explore an ordinance addressing ALPR technology within city limits, including City agencies, contractors, private organizations, businesses, individuals, and private property, with definitions, enforcement mechanisms, and exceptions only as required by law.
So the question is not whether Albany should dislike Flock. The legal assignment is narrower and more useful: what ordinance can survive review?
Whether the City of Albany may adopt a civil ordinance prohibiting or regulating automated license plate reader systems within city limits, including private ALPR systems on private property when those systems capture public streets, public rights-of-way, public parking areas, or places open to the public, and whether any narrower fallback ordinance would be more legally defensible.
That issue statement forces the right analysis: not is Flock good or bad, but what ordinance can survive review. The written feasibility memo should answer eight questions: whether SB 1516 preempts stricter local rules; whether Albany can ban City/APD ALPR use; whether APD can be barred from private ALPR data except by warrant, court order, subpoena, or documented emergency; whether private ALPR systems capturing public-facing traffic can be regulated or banned; whether zoning, business licensing, nuisance, privacy, public-safety, or data-governance authority can support the ordinance; what exceptions are legally required; what enforcement mechanism is safest; and what fallback language should be used if a total private-property ban is vulnerable.
The legal review should answer whether SB 1516 is a statewide ceiling or a statewide floor. The enrolled bill's ALPR material is concentrated in Sections 3 to 9, with related amendments to organized-retail-theft grant rules and public-records law.
Section 3 supplies the definitions Albany should not ignore. An automated license plate recognition system is one or more high-speed cameras combined with algorithms that convert license plates or other vehicle characteristics into computer-readable data. Captured license plate data includes GPS coordinates, date and time, video, photograph, license plate number, vehicle characteristics, and related data. The definition expressly excludes photo red light cameras and photo radar when used for the listed traffic-enforcement statutes.
Section 4 is the main law-enforcement use section. It says a law-enforcement agency may not use an ALPR system or captured plate data except under Sections 3 to 9, then lists authorized uses including crimes, nontraffic violations, criminal warrants, missing or endangered persons, uninsured vehicles, unregistered vehicles, parking facilities, and secured-area access. It sets a 30-day retention limit for captured plate data not tied to a court proceeding or ongoing criminal investigation, requires visual confirmation before a traffic stop based on an alert, and requires search-entry logs with user, agency, search inputs, date/time, case number, law-enforcement purpose, and crime or violation type when applicable.
The private-data sentence is Section 4(7), and it matters. SB 1516 expressly recognizes that a law-enforcement agency may request access to captured license plate data collected by a private person or entity or non-law-enforcement agency, provided the agency uses the data for a law-enforcement purpose. That proves the private-to-police pipeline exists. It does not by itself answer whether Albany can locally prohibit or narrow that pipeline.
Section 5 limits sharing. Oregon law-enforcement agencies may allow queries by another law-enforcement agency, but captured plate data provided to a government entity or agency outside Oregon must be limited to data relevant to a law-enforcement purpose and may not include unrestricted or ongoing access. The section also preserves disclosure required by judicial subpoena or other compulsory court-issued legal process.
Section 6 is the audit and publication engine. Vendors contracting with law enforcement must provide searchable monthly audits covering systems, camera/device locations, searches, agencies with access, authorized users, unique vehicles captured, alerts, cameras/devices accessed, user identifiers, search times, and search purposes. Quarterly audits must cover searches conducted on behalf of outside government agencies. The agency must publish audit results within two days of receiving them, or require vendor public access within two days, with the ORS 192.345(44) redactions.
Sections 7 to 9 carry the policy, contract, existing-contract, and vendor-liability rules. Section 7 requires public policies before deployment and contract terms saying law-enforcement-captured data belongs to the agency, vendor requests must be routed to the agency, captured data must be encrypted at least end-to-end, vendors must comply with current FBI CJIS security policy where applicable, and vendors may be liable for misuse or improper release. Section 8 protects preexisting vendor contracts from immediate full contract rewrite, but still requires Section 4 compliance after the effective date. Section 9 bars vendors from accessing, disclosing, selling, sharing, or otherwise using captured plate data, with narrow technical-support and audit exceptions, and creates civil-action remedies for improper vendor access or disclosure.
Section 10 matters if any organized-retail-theft grant funds touch ALPR equipment: ALPR systems purchased under that program must comply with Sections 3 to 9. Section 11 adds ORS 192.345(44), conditionally exempting law-enforcement captured plate data while requiring redacted audit disclosure. Section 14 declares an emergency and says the Act takes effect on passage. Those timing and funding pieces should be checked against Albany's contract and any grant file.
Key question: Does SB 1516 preempt stricter local ALPR regulation, or does it leave room for stronger local privacy rules?
Albany's charter gives the City broad municipal authority, and the City's own council page describes Council as the legislative branch that adopts ordinances, resolutions, policies, budgets, taxes, and conducts public meetings. The League of Oregon Cities frames the main limit on Oregon home rule as preemption: state or federal law may displace local lawmaking on the same subject.
The clean legal theory to test is this: Albany is not trying to rewrite Oregon criminal law. Albany is regulating local surveillance infrastructure, local public trust, use of city resources, and capture of public-right-of-way movement data inside city limits.
The legal review should address whether Albany may prohibit its own departments, officers, contractors, and agents from deploying, using, requesting, buying, or relying on ALPR data. This should be the least vulnerable ordinance layer because the City controls its own agencies and resource use.
The next clean layer is APD access to privately collected ALPR data. The memo should answer whether Albany may prohibit APD from accessing private ALPR data except by warrant, court order, judicial subpoena, or documented emergency involving imminent risk of death or serious physical injury.
This matters because even if private cameras remain, the police-use pipeline can be cut or narrowed by local policy.
The hard part is separating ordinary private security cameras from networked ALPR surveillance infrastructure. The ordinance should not say no private security cameras. It should focus on automated plate extraction, public-right-of-way capture, storage, sharing, sale, upload, third-party searchability, and law-enforcement access.
A stronger private-system rule to test is: No person may operate an ALPR system that captures license plate data from public streets, public sidewalks, public rights-of-way, public parking areas, or places open to the public, and stores, shares, sells, uploads, or makes searchable that data through a third-party ALPR network, except as expressly authorized by City ordinance or required by state or federal law.
The private-property analysis should include property rights, takings, due process, vagueness, and First Amendment issues. The definitions need to make clear that Albany is regulating automated data extraction and surveillance databases, not ordinary photography or speech.
The legal review should also include the federal Driver's Privacy Protection Act because plate scans can become more sensitive when paired with motor-vehicle-record data, and ORS 181A.250 because Oregon law already limits law-enforcement collection or maintenance of political, religious, or social association information unless tied to a criminal investigation. ALPR cameras near protests, churches, clinics, courts, shelters, unions, or political events can become association-tracking tools if the data pipeline is not tightly controlled.
SB 1516 is the anchor, but it should not be the whole memo. The enrolled bill defines ALPR systems and captured license plate data, restricts law-enforcement use, sets a 30-day ordinary retention limit for non-investigative data, requires search logs, requires policies and vendor audits, limits sharing, requires audit publication, and expressly recognizes law-enforcement requests for ALPR data collected by private people, private entities, or non-law-enforcement agencies. That sentence proves the private-to-police pipeline exists; it does not clearly prove that cities are preempted from regulating it.
The SB 1516 text makes the constitutional question stronger, not weaker. Oregon already treats ALPR data as sensitive enough to define, limit, audit, redact, publish in sanitized form, restrict by contract, and regulate through civil remedies. The legislature has already recognized that ALPR data is not ordinary camera footage. Albany's question is whether those state minimums are enough locally.
The Oregon home-rule cases are the backbone. Schwartz v. Washington County is the strongest current case because the Oregon Supreme Court held in 2026 that statewide licensing/regulation did not preempt a stricter local flavored-tobacco ordinance when the statute did not unambiguously make state law exclusive and the local ordinance could operate concurrently. Rogue Valley Sewer Services v. City of Phoenix, Owen v. City of Portland, and Thunderbird Mobile Club v. City of Wilsonville reinforce the same high bar for preempting local civil regulation. City of Portland v. Jackson is the caution case: draft this as a civil privacy, public-safety, licensing, nuisance, or data-governance ordinance, not as a local crime that rewrites Oregon criminal law.
The Oregon surveillance and public-resource statutes should be part of the legal review. ORS 181A.250 matters because ALPR cameras near churches, political meetings, protests, courthouses, clinics, shelters, unions, legal-aid offices, or public-comment events can become association-tracking infrastructure. ORS 181A.820 and ORS 181A.826 matter because SB 1516 itself cross-references Oregon limits on using public resources for prohibited enforcement activities. Any ordinance should test a no-federal-immigration-enforcement clause and a no-DHS/ICE/CBP data-sharing clause except where a judicial subpoena or other compulsory court-issued process legally requires disclosure.
The public-records hook is ORS 192.345(44), as amended by SB 1516. Captured plate data may be conditionally exempt, but SB 1516 requires audit results to be published after removing personally identifying information. Albany should treat those statutory audit categories as a floor for public monthly audits, redacted logs, camera locations, search counts, outside-agency access, authorized-user counts, alerts, deletion certification, and data-sharing records.
The constitutional question is not whether a license plate can be seen in public. The question is whether government or private vendors may convert ordinary public travel into a searchable, time-stamped, location-stamped movement history.
The Oregon Constitution should come before the U.S. Constitution in the legal memo. State v. Kennedy explains that Oregon constitutional guarantees are independent of federal constitutional doctrine. Under Article I, section 9, State v. Campbell is the strongest Oregon privacy hook because technology-aided tracking of a vehicle on public roads can be a search when it significantly impairs the people's freedom from scrutiny. Campbell maps directly onto ALPR because one plate view is observation, while thousands of plate reads, GPS coordinates, timestamps, images, vehicle characteristics, search logs, alerts, databases, and multi-agency access become surveillance infrastructure.
State v. Mansor adds the digital-data point: constitutional privacy rules must account for modern repositories of searchable information. SB 1516's own definition of captured license plate data helps prove that ALPR is not merely a camera pointed at traffic; it is GPS coordinates, date and time, video, photographs, plate numbers, vehicle characteristics, and related data made computer-readable and searchable.
Oregon Article I, sections 8 and 26 also matter. ALPR systems near City Hall, courthouses, legal-aid offices, churches, clinics, shelters, protests, council meetings, campaign events, or union activity can chill speech, association, assembly, and petitions for redress. Albany should not permit infrastructure that lets a government agency, vendor, landlord, shopping center, HOA, or private network reconstruct who attended a council meeting, protest, court hearing, clinic, church, legal-aid appointment, or political event.
At the same time, vendors and private operators may raise free-expression arguments. State v. Robertson is the drafting warning: regulate automated surveillance infrastructure and captured license-plate data, not speech, opinion, journalism, ordinary photography, recording public officials, or ordinary security cameras that do not perform automated plate recognition.
Oregon Article I, section 18 and the federal Takings Clause are opponent-risk issues. The safer ordinance regulates operation and data use; it does not confiscate equipment. Due process and vagueness risks are addressed by precise definitions for ALPR system, captured license plate data, public right-of-way, place open to the public, operate, deploy, request, access, search, share, third-party ALPR network, law-enforcement purpose, emergency exception, and ordinary security camera.
The federal constitutional cases should be used carefully. Carpenter v. United States and United States v. Jones do not automatically ban ALPRs, but they support the concern that persistent, searchable location history is constitutionally different from a single officer seeing a single car in public. United States v. Yang is useful because the Ninth Circuit describes private ALPR databases, GPS-linked plate scans, years of storage, and law-enforcement subscription access, even though the defendant did not win suppression and the court did not squarely decide the Fourth Amendment ALPR question. The DPPA, including 18 U.S.C. 2721 and 2722, should be reviewed because plate scans become more sensitive when matched to DMV or motor-vehicle-record data.
The strongest framing is this: the legal issue is not whether SB 1516 permits some ALPR use. It does. The issue is whether SB 1516 unambiguously preempts Albany from adopting stricter local civil rules. Schwartz is the key Oregon preemption case for this point: state regulation is not the same thing as an affirmative right to do the regulated activity free from stricter local rules. A state law regulating ALPRs is not a state law giving Flock, private businesses, landlords, HOAs, shopping centers, vendors, or public agencies an affirmative right to operate networked ALPR surveillance systems inside Albany.
The July 8 question should therefore be precise: If state law recognizes that private ALPR data can flow into law enforcement, can Albany locally restrict or prohibit that pipeline to protect public trust, assembly, privacy, and local civil liberties?
Council should ask for ranked options by litigation risk, not a yes-or-no memo.
A draft ordinance core to test could say: No person, business, homeowners' association, landlord, property manager, or private entity may install, operate, contract for, or maintain an automated license plate recognition system within the City where the system captures license plate data from a public street, public sidewalk, public parking area, public right-of-way, or other place open to the public, unless expressly authorized by City ordinance and subject to public notice, data-retention limits, audit logs, cybersecurity review, and restrictions on disclosure to law enforcement or third parties.
The companion City-use rule matters even more: The City of Albany, Albany Police Department, and all City employees should be prohibited from accessing, requesting, receiving, purchasing, searching, or relying on ALPR data collected by a private person or entity, except under a judicial warrant, judicial subpoena, court order, or a narrowly documented emergency. Even if a private-camera regulation is challenged, Albany can still decide that its own government will not use the private surveillance feed.
The clean public frame is simple: private security cameras are not the issue. Automated public-movement databases are the issue.
Do not overstate this point. The careful sentence is: federal vulnerability records identify Flock-related vulnerabilities that should be reviewed before any deployment or future ordinance exception.
NVD lists CVE-2025-59403 for the Flock Safety Android Collins application, describing unauthenticated administrative API endpoints with possible denial of service, information disclosure, and remote code execution impacts. NVD also lists CVE-2025-47822 for Flock Safety LPR devices with firmware through 2.2, describing improper access control on an on-chip debug interface.
Flock's own public response says the company is improving security, has pledged to CISA Secure by Design principles, continues engaging with CISA, and does not believe the disclosed vulnerabilities affect customers' ability to carry out public-safety objectives. That response belongs in the same source review. The City's job is not to ignore the vendor's answer; it is to avoid treating vendor assurance as a substitute for independent verification.
Senator Ron Wyden's October 2025 letter to Flock should also be in the legal-review folder because it places federal/out-of-state access, search-reason, vendor-audit, immigration-enforcement, and abortion-enforcement concerns into the public record. Albany does not need to adopt every conclusion in that letter to treat it as a source for review.
The July 8 analysis should be paired with a preservation and review list.
This ordinance is not anti-police. It is a test of Albany's own stated commitment to transparent, data-driven, community-accountable government. The FY2026-2030 Strategic Plan includes Safe and Resilient Community work on cybersecurity, community policing reporting, and neighborhood safety, and High-Performing Government work on data-driven decisions, technology modernization, and department metrics. It also includes citywide artificial-intelligence governance standards by June 30, 2027 and an AI integration plan by June 30, 2030. ALPR is exactly the kind of AI/data-governance issue Albany says it intends to manage. The Flock vote gives the City a live test case for whether transparent, accountable, AI-governed government means anything before the next vendor arrives.
Do not ask only whether Albany can ban private Flock. That lets the answer collapse into maybe complicated. Ask this instead: Please identify the strongest enforceable ordinance Albany can pass, and provide fallback language if a full private-property ALPR ban is not recommended.
Residents can help by keeping the record specific: submit written comments, identify where private ALPR systems may capture public-facing traffic, ask for records rather than rumors, and request that the July 8 memo publish the legal source trail as well as the conclusion. Albany does not need to choose between safety and civil liberties. It needs rules strong enough to protect both.
Albany does not have to wait for a constitutional lawsuit to decide that searchable public-movement databases are wrong for the city. SB 1516 sets the floor; Albany can ask whether local constitutional values require a higher ceiling.
The next public records are concrete: the Flock termination notice, final invoices or grant closeout, data deletion or retention confirmation, audit logs, sharing-partner records, written public comments, public-comment sign-up records, and the July 8 City Attorney analysis. If Albany wants neighbors to trust the next answer, the memo should publish the legal source trail, not just the conclusion.
This article is supported by public records, source review, and neighbor-funded records work. Source gaps stay visible until the next record closes them.