Oregon
Oregon License Plate Reader Laws (2026)
Independently fact-checked against primary sources (last audited September 30, 2026). · 5 primary sources cited on this page. How we verify our legal content

Oregon has a specific license plate reader statute. Sections 3 to 9 of enrolled Senate Bill 1516 (Oregon Laws 2026, chapter 77) bar a law enforcement agency from using an ALPR system or captured plate data except for listed purposes, cap most retention at 30 days, limit sharing, and put rules on vendors. The prohibition in section 4 of the enrolled bill is addressed to law enforcement agencies.
Information reviewed September 30, 2026.
For related pages, see the Oregon entry in the state comparison, the ALPR laws hub, Are Flock cameras legal?, What are Flock cameras?, and our Oregon surveillance camera laws guide.
Is there an Oregon law on license plate readers?
Yes. Enrolled SB 1516-A, listed by the legislature's tracking system as chapter 77 of the 2026 session laws, contains the ALPR rules in its sections 3 to 9. Section 4(1) reads: "Except as provided under sections 3 to 9 of this 2026 Act, a law enforcement agency may not use an automated license plate recognition system or captured license plate data."
The bill has 14 sections. Sections 1 and 2 and sections 12 and 13 deal with other subjects. Section 10 requires any plate reader bought with Organized Retail Theft Grant Program money to comply with sections 3 to 9, and section 11 amends the public records law. Section 14 is an emergency clause saying the act "takes effect on its passage." The legislature's bill history records that the Governor signed the bill on March 31, 2026, and lists March 31, 2026 as its effective date. We also did not confirm whether the ALPR sections were compiled into a chapter of the Oregon Revised Statutes, which is why we cite the session law and section numbers.

What may Oregon law enforcement use plate readers for?
Section 4(2) lists the purposes for which a law enforcement agency may use an ALPR system or captured data. Among them:
- Identifying a vehicle used to facilitate the commission of a crime or to avoid apprehension for one.
- Non-traffic violations under ORS 153.008.
- Identifying a vehicle registered to a person with an outstanding criminal arrest warrant.
- Missing or endangered persons, including Amber and Silver Alerts.
- An uninsured vehicle, an unregistered vehicle, parking facilities and secured areas.
The crime and warrant purposes reach out-of-state crimes that are substantially equivalent to Oregon crimes. They also reach federal crimes and federal judicial arrest warrants, but only where the use is "not contrary to the public policies set forth in ORS 24.500 or any law of this state restricting the use of public resources for prohibited enforcement activities, including ORS 181A.250, 181A.820 and 181A.826." The text of section 4 does not use the word immigration. Separately, two Oregon sanctuary statutes that do not mention plate readers limit using public resources for immigration enforcement, subject to exceptions they list: ORS 181A.820 bars a law enforcement agency from using agency moneys, equipment or personnel to detect or apprehend people for the purpose of enforcing federal immigration laws, and ORS 181A.826 bars using public equipment, technology or personnel to investigate, detect, apprehend, arrest, detain or hold people for immigration enforcement, which it says includes providing information to a federal agency except as ORS 181A.823 allows. Any person may sue an agency to enjoin a violation of either.
Other operating rules in section 4 include the following. A hot-list entry must state its purpose and identify the employee who added it (section 4(4)(c)). Before a traffic stop based on an alert, the officer must visually confirm the plate number, the issuing state and the vehicle characteristics (section 4(6)). An agency may also request data held by private entities for a law enforcement purpose (section 4(7)).
How long can Oregon agencies keep plate data?
Section 4(3) sets the default at 30 days. Captured data not related to a court proceeding or ongoing criminal investigation "may be retained for no more than 30 days after the captured license plate data is collected." Data related to a court proceeding or an ongoing investigation may be kept as long as evidence is kept in the normal course of the court's business. The retention limits do not apply to audit information.
Who can get access to Oregon plate data?
Section 5 governs sharing. Another Oregon law enforcement agency may query an agency's data. Access for any government entity not created under Oregon law is barred except for a law enforcement purpose, must be limited to relevant data, and "may not include unrestricted or ongoing access to captured license plate data." The search log must name the requesting entity and the cameras used. Section 5(3) carves out judicial subpoenas and other compulsory court process.
What audit and policy rules apply?
Section 4(5) requires a search log that records the user ID, the agency, the search inputs, the date and time, the case number and the law enforcement purpose. For an investigation it also records the type of crime or violation.
Section 7 requires an agency to establish and publish a policy before deploying a system. The policy must cover security, hot-list accuracy, training, retention and destruction, and audit processes. It must also include vendor contract terms providing that the agency owns the captured data, that vendor requests are directed to the agency, that data is end-to-end encrypted, that the vendor complies with the FBI's CJIS Security Policy, and that the vendor is liable for misuse.
Section 6 requires vendors under contract to give the agency a searchable monthly audit and a quarterly audit of searches run for outside agencies. The monthly audit covers installed cameras, fixed-camera locations, searches, agencies with access, users, unique vehicles, alerts and, for each search, the user, date and purpose. The agency must publish the results on its website within two days or require direct public access, redacted as provided in ORS 192.345(44)(a).
Are private companies and vendors covered?
The prohibition in section 4 is addressed to law enforcement agencies, and the sections we read otherwise regulate the vendors that work for them. Under section 9, a vendor may not "access, disclose, sell, share or otherwise use" captured data, with exceptions for technical support the agency consents to and for providing the section 6 audits. Section 8 lets vendor contracts entered before the effective date run to their end, but they cannot be extended, renewed or replaced except in compliance, and section 4 applies regardless.
We did not find in the sections we read a rule addressed to a business or homeowners association that runs its own plate reader. We did not review every other Oregon statute for one. One general privacy law may matter for companies that sell location data: since January 1, 2026, the Oregon Consumer Privacy Act bars a covered business from selling personal data that identifies a consumer's or a linked device's present or past location within 1,750 feet (ORS 646A.578). We did not confirm how it applies to plate reader data.
Can I sue over a violation?
Section 9(2) gives an individual a civil action against a vendor for an intentional or grossly negligent violation, for "economic and noneconomic damages and equitable relief," with attorney fees at the court's discretion. Any person may sue a vendor to enjoin a violation of section 9(1)(a). The text makes these the exclusive remedies for a violation of section 9(1)(a). In the enrolled text we read, we did not find a direct private action against an agency or a criminal penalty for misuse. Oregon's sanctuary statutes, ORS 181A.820(6) and 181A.826(5), separately let any person sue an agency to enjoin using its equipment or technology for federal immigration enforcement.
Can I request Oregon plate reader data as a public record?
Section 11 adds subsection (44) to ORS 192.345. Captured license plate data collected by a system deployed or used by a law enforcement agency is exempt from disclosure unless the public interest requires disclosure in the particular instance, because ORS 192.345 lists conditional exemptions. The contents of the section 6 vendor audits must be disclosed after plates and vehicle characteristics are removed. The subsection also sets conditional-disclosure rules, including a request tailored to a date and time, blurred faces, and sealed data staying sealed, and it preserves criminal discovery rights. Requesters seeking audits should ask the agency that contracts with the vendor, since the agency publishes them.
What have Oregon courts said about plate readers?
We found no Oregon appellate decision on plate reader use. Our searches of the Oregon courts site, CourtListener and Justia returned only unrelated cases about obstructed plates, so this is a statement about our search and not proof that none exists.
Which Oregon agencies have ended plate reader programs?
This list is not complete. The City of Eugene posted a notice, and our records mark the Eugene Police Department deployment as ended as of December 5, 2025. The City of Springfield announced removal of Flock cameras, and our records mark the Springfield Police Department deployment as ended as of January 21, 2026. We did not tie either decision to the statute.
How can I check my local system?
Under section 7, an agency must publish its ALPR policy, and under section 6 it must publish vendor audit results on its website. Start there, then ask the agency for its retention setting and its vendor contract terms. For the technology itself, see What are Flock cameras?.
Frequently Asked Questions
Does Oregon have a license plate reader law?
Yes. Sections 3 to 9 of enrolled SB 1516 (Oregon Laws 2026, chapter 77) bar law enforcement agencies from using ALPR systems or captured data except for listed purposes, and add retention, sharing, audit and vendor rules.
How long can Oregon police keep license plate reader data?
Data not related to a court proceeding or an ongoing criminal investigation may be kept no more than 30 days after collection under section 4(3). Data tied to a court proceeding or investigation may be kept as long as evidence is kept in the normal course of the court's business.
Can other agencies or the federal government search Oregon plate data?
Another Oregon law enforcement agency may query the data. A government entity not created under Oregon law may have access only for a law enforcement purpose, limited to relevant data and without unrestricted or ongoing access. Federal crimes and federal judicial warrants count as purposes only where the use is not contrary to the public policies in ORS 24.500 and the state laws the statute lists.
Can I get plate reader data through an Oregon public records request?
Captured plate data from an agency-deployed system is conditionally exempt under ORS 192.345(44), so it is withheld unless the public interest requires disclosure in the particular instance. The vendor audits the statute requires must be disclosed with plates and vehicle characteristics removed.
Can I sue over misuse of plate data in Oregon?
Section 9 lets an individual sue a vendor for an intentional or grossly negligent violation. We did not find a direct private lawsuit against an agency in the enrolled text. Separately, Oregon's sanctuary statutes, ORS 181A.820 and 181A.826, let any person sue an agency to stop the use of public resources for immigration enforcement.
Have Oregon courts ruled on plate readers?
We found no Oregon decision on the subject in our searches of the state courts site, CourtListener and Justia.
Updates
Independently fact-checked against the cited primary sources
The Law Behind This Article
This article rests on the statutory provisions below, held in our own legal record and retrieved from the official source. Tap a section to read the operative text.
Oregon Revised Statutes, Chapter 153: Violations and Fines
§ 153.008Violations describedIn force
(1) Except as provided in subsection (2) of this section, an offense is a violation if any of the following apply: (a) The offense is designated as a violation in the statute defining the offense. (b) The statute prescribing the penalty for the offense provides that the offense is punishable by a fine but does not provide that the offense is punishable by a term of imprisonment. The statute may provide for punishment in addition to a fine as long as the punishment does not include a term of imprisonment. (c) The offense is created by an ordinance of a county, city, district or other political subdivision of this state with authority to create offenses, and the ordinance provides that violation of the ordinance is punishable by a fine but does not provide that the offense is punishable by a term of imprisonment. The ordinance may provide for punishment in addition to a fine as long as the punishment does not include a term of imprisonment. (d) The prosecuting attorney has elected to treat the offense as a violation for purposes of a particular case in the manner provided by ORS 161.566.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at oregonlegislature.gov
Cited in 57 court opinions in our collectionLatest citing opinion in our collection: 2026
Opinions citing this section in our collection:
- State v. Litscher (Court of Appeals of Oregon 2006, 207 Or. App. 565)“…s described in ORS 161.515, or a violation, as described in ORS 153.008.” The latter statute defines a “violati…”
- Harris v. Department of Public Safety Standards & Training (Court of Appeals of Oregon 2017, 287 Or. App. 111)“…ontext and conflicts as well as conflicts with another law, ORS 153.008(2). For the reasons that follow, we dis…”
- State v. Coughlin (Court of Appeals of Oregon 2013, 258 Or. App. 882)“…s described in ORS 161.515, or a violation, as described in ORS 153.008.” Contempt is not a crime, defendant ar…”
Identified automatically from the court opinions citing this section — not a ranking of which case controls.
Oregon Revised Statutes, Chapter 181A: State Police; Crime Reporting and Records; Public Safety Standards and Training; Private Security
§ 181A.250Specific information not to be collected or maintainedIn forcecited in 2 of our articles
No law enforcement agency, as defined in ORS 181A.010, may collect or maintain information about the political, religious or social views, associations or activities of any individual, group, association, organization, corporation, business or partnership unless such information directly relates to an investigation of criminal activities, and there are reasonable grounds to suspect the subject of the information is or may be involved in criminal conduct. [Formerly 181.575] Note: 181A.250 was made a part of 181A.160 to 181A.250 by legislative action but was not added to 181A.010 to 181A.350. See Preface to Oregon Revised Statutes for further explanation.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at oregonlegislature.gov
Cited in 1 court opinions in our collectionLatest citing opinion in our collection: 2025
Opinions citing this section in our collection:
- ACLU of Oregon v. City of Portland (Court of Appeals of Oregon 2025, 338 Or. App. 750)“…t least portions” of the livestreams in this case “violated ORS 181A.250” and “breached [the PPB’s] obligations”…”
Identified automatically from the court opinions citing this section — not a ranking of which case controls.
Also relied on in: Oregon Laws on Recording Police: Your Rights and Legal Limits
§ 181A.820Enforcement of federal immigration laws; civil action for violationIn force
(1) As used in this section: (a) “Federal immigration authority” has the meaning given that term in ORS 180.805. (b) “Warrant of arrest” has the meaning given that term in ORS 131.005. (2) A law enforcement agency may not use agency moneys, equipment or personnel for the purpose of detecting or apprehending persons for the purpose of enforcing federal immigration laws. (3) A law enforcement agency may not enter into a formal or informal agreement with a federal immigration authority relating to the detention of a person described in subsection (2) of this section. (4) Notwithstanding subsection (2) of this section, a law enforcement agency may exchange information with a federal immigration authority in order to request criminal investigation information with reference to persons named in records of the federal immigration authority. (5) Notwithstanding subsection (2) of this section, a law enforcement agency may arrest any person who: (a) Is charged by the United States with a criminal violation of federal immigration laws under Title II of the Immigration and Nationality Act or 18 U.S.C.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at oregonlegislature.gov
Cited in 7 court opinions in our collectionLatest citing opinion in our collection: 2022
Opinions citing this section in our collection:
- Cruz v. Multnomah County (Multnomah County Circuit Court, Oregon 2016, 279 Or. App. 1)“…im for false imprisonment and a claim based on violation of ORS 181A.820C1). 1 On cross-motions for summary jud…”
- City & County of San Francisco v. Merrick Garland (Court of Appeals for the Ninth Circuit 2022, 42 F.4th 1078)“…eignty injuries. But far from limiting information sharing, ORS 181A.820 explicitly permits state law enforcemen…”
- Tovar Hernandez Jr. v. Washington County (District Court, D. Oregon 2022)“…a negligence claim based on a non-physical injury or that ORS 181A.820 can be used to establish negligence p…”
Identified automatically from the court opinions citing this section — not a ranking of which case controls.
§ 181A.823Prohibitions related to immigration enforcement; explanation of rights and consequences; civil actionIn force
(1) A law enforcement agency or public body may not: (a) Except as required by state or federal law, deny services, benefits, privileges or opportunities to an individual in custody, or on parole, probation or post-prison supervision, on the basis of known or suspected immigration status, the existence of an immigration detainer, hold, notification or other related federal immigration request or a civil immigration warrant; (b) Inquire into or collect information about an individual’s immigration or citizenship status or country of birth unless: (A) The information is required to advance an investigation into a violation of state or local criminal law; (B) The information is submitted to a court of this state, whether orally or in writing, in connection with a proceeding in that court; or (C) As necessary to determine the individual’s eligibility for a benefit that the individual is seeking; or (c) Provide information, or enter into an agreement to provide information, about an individual in the custody of the public body or law enforcement agency to a federal immigration authority for the purpose of civil immigration enforcement, except: (A) As may…
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at oregonlegislature.gov
§ 181A.826Prohibition on use of public resources for immigration enforcement; documentation; submission to Oregon Criminal Justice Commission; website; disclosure to Department of Justice; reporting requirements; civil actionIn force
(1) Public facilities, property, moneys, equipment, technology or personnel may not be used for the purpose of investigating, detecting, apprehending, arresting, detaining or holding individuals for immigration enforcement. (2) Actions with a purpose described in subsection (1) of this section include, but are not limited to, the following: (a) Granting a federal immigration agency access to an area of a facility that is not normally open to the public. (b) Supporting or assisting a federal agency in immigration enforcement, including but not limited to any of the following: (A) Providing information, including but not limited to an individual’s contact information, country of birth, custody status, release date, parole, probation or post-prison supervision appointment dates or times, or home or work address, except as provided in ORS 181A.823; (B) Investigating or interrogating individuals for immigration enforcement; or (C) Establishing traffic perimeters for the purpose of supporting or facilitating immigration enforcement.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at oregonlegislature.gov
Oregon Revised Statutes, Chapter 192: Records; Public Reports and Meetings
§ 192.345Public records conditionally exempt from disclosureIn forcecited in 6 of our articles
192.345 Public records conditionally exempt from disclosure. The following public records are exempt from disclosure under ORS 192.311 to 192.478 unless the public interest requires disclosure in the particular instance: (1) Records of a public body pertaining to litigation to which the public body is a party if the complaint has been filed, or if the complaint has not been filed, if the public body shows that such litigation is reasonably likely to occur. This exemption does not apply to litigation which has been concluded, and nothing in this subsection shall limit any right or opportunity granted by discovery or deposition statutes to a party to litigation or potential litigation. (2) Trade secrets. “Trade secrets,” as used in this section, may include, but are not limited
Official text (excerpt) · last checked 2026-09-02 · Read the full text in our law library · Verify at oregonlegislature.gov
Also relied on in: Oregon Police Reports: How to Get a Crash or Incident Report, Are Autopsies Public Records? Vital Records Explained, Oregon Police Bodycam Laws: Retention, Access & Facial Recognition Ban
Oregon Revised Statutes, Chapter 646A: Trade Regulation
§ 646A.578Duties of controller; prohibitions; privacy notice to consumerIn forcecited in 8 of our articles
(1) A controller shall: (a) Specify in the privacy notice described in subsection (4) of this section the express purposes for which the controller is collecting and processing personal data; (b) Limit the controller’s collection of personal data to only the personal data that is adequate, relevant and reasonably necessary to serve the purposes the controller specified in paragraph (a) of this subsection; (c) Establish, implement and maintain for personal data the same safeguards described in ORS 646A.622 that are required for protecting personal information, as defined in ORS 646A.602, such that the controller’s safeguards protect the confidentiality, integrity and accessibility of the personal data to the extent appropriate for the volume and nature of the personal data; and (d) Provide an effective means by which a consumer may revoke consent a consumer gave under ORS 646A.570 to 646A.589 to the controller’s processing of the consumer’s personal data. The means must be at least as easy as the means by which the consumer provided consent.
Official text (excerpt) · last checked 2026-08-28 · Read the full text in our law library · Verify at oregonlegislature.gov
Also relied on in: OCPA Compliance Checklist for Oregon Businesses, OCPA Consumer Rights: Oregon Data Privacy Act, What Is the OCPA? Oregon Consumer Privacy Act
Search our full record of US law — 2.1 million sections, every state + federal →
Sources and References
- Oregon SB 1516 (2026), enrolled (Oregon Laws 2026, ch. 77)(olis.oregonlegislature.gov).gov
- City of Eugene notice on Flock cameras(www.eugene-or.gov).gov
- City of Springfield, Flock removal notice(springfield-or.gov).gov
- ORS chapter 181A (incl. 181A.820, 181A.826)(oregonlegislature.gov).gov
- Oregon HB 2008 (2025), enrolled(olis.oregonlegislature.gov).gov