Washington Co. Sheriff (OR) | License plate readers
The Sheriff has described the office's Flock cameras to reporters, down to the sharing list. The county's own published record has the grants that reportedly funded them, and no plate reader policy anywhere in the Sheriff's 230-document manual.
At a glance
- How this page knows about it
- The Sheriff's on-record statements in syndicated local reporting of 19 November 2025, and the EFF Atlas entry citing that reporting. Not yet any county-published record [1] [5]
- What the Sheriff described
- Flock cameras used against organized retail theft, activated for missions; data shared with about 25 Oregon law enforcement agencies; "at no time do we share data with ICE or (the U.S.) Border Patrol", as reported [1]
- The reported funding
- A state Organized Retail Theft grant through the District Attorney's office; the DA's own releases record awards of $1,545,487 and $1,535,173, the largest in Oregon both years, without naming cameras [1] [2]
- What SB 1516 requires since 31 March 2026
- Published policies before deploying a system, a 30-day cap on retaining non-case data, and vendor-supplied audit figures: camera counts, fixed locations, search counts, the list of agencies with access [3]
- The policy the statute requires
- not found where we could look. Zero references to plate readers exist in the 221 readable documents of the published manual, and none of the agency pages we fetched carries one. A Flock transparency page may exist on a host that answers a bot challenge to us. The records request asks for the policies directly [4]
- Camera count, locations, retention
- in no record we could read. The section 6 vendor figures are the records request target [3]
How it happened
- Coverage
The Sheriff describes the network, on the record
Four sibling Pamplin Media titles report Sheriff Massey addressing community concern about the office's Flock cameras: used for organized retail theft missions, data shared with about 25 Oregon agencies under the state's sanctuary laws, and not with ICE or Border Patrol. KOIN separately reports the Board of County Commissioners taking up plate readers; the board's record is on a host closed to us. [1]
- Procurement
A second record-setting grant, in the county's own words
The DA's office announces $1,535,173 from Oregon's Organized Retail Theft Grant Program, the state's largest award for the second consecutive year, for the county's interagency task force. The release names missions, evidence-gathering and retailer security upgrades; it does not name cameras. The connection between the grants and the Flock purchase is the reporting's. [2]
- Context
The statute arrives after the cameras
SB 1516 takes effect: an agency may not use an ALPR system except as the Act provides, must establish and publish policies before deploying, and must hold vendor-supplied audit figures. Whatever the office's obligations were when the cameras arrived, these are its obligations now. [3]
- Context
The published record, read end to end
The Sheriff's complete public manual is harvested and scanned: no plate reader policy under any spelling in the 221 readable documents, whose 12 unreadable remainder is eleven old annual-report scans and one dead link. The agency pages fetched carry none either. Where the section 7 policy lives, if it exists, is the first question in this county's records request. [4]
What is reported, and by whom
This page carries the status “reported” because every fact about the deployment itself reaches us through the press, even where the speaker is the Sheriff.
On 19 November 2025, four sibling local titles carried the same story: Sheriff Caprice Massey addressing community concern about the office’s Flock Safety cameras. As reported, the office uses the cameras against organized retail theft, activating them for missions; shares data with about 25 Oregon law enforcement agencies; and, in the Sheriff’s quoted words, “at no time do we share data with ICE or (the U.S.) Border Patrol”. KOIN separately reported the Board of County Commissioners taking the subject up amid those same concerns.
Those are the agency’s own descriptions, given on the record, and this site has no reason to doubt them. They are still not county records. The distinction matters here more than usually, because of what the county’s own records do and do not contain.
What the county’s own record contains
Two things. First, the money: the District Attorney’s office announced, in its own releases, Oregon’s largest Organized Retail Theft Grant awards two years running, $1,545,487 and then $1,535,173, for the county’s interagency task force. The releases describe missions, evidence gathering and retailer security upgrades. Neither names Flock, cameras, or plate readers; the connection between the grants and the camera purchase is the reporting’s.
Second, the absence: the Sheriff’s Office publishes its entire policy manual, 230 documents, and we read all of it that can be read. No plate reader policy exists in it under any spelling. The twelve documents we could not read are eleven scanned annual reports from 2017 and 2018 and one dead link, none of them plausibly the policy. The agency web pages we fetched carry none either.
Why the absence is worth stating
Since 31 March 2026, Oregon’s SB 1516 has provided that a law enforcement agency may not use an ALPR system except as the Act provides, and must “establish and publish” policies for the system’s use, storage and retention before deploying it. The same Act requires the vendor to hand the agency an audit: camera counts, fixed locations, search counts, and a list of every agency with access, which would include the sharing list the Sheriff described.
We are not asserting the office is out of compliance. Its policy may be published somewhere we could not reach: Flock hosts transparency pages for many client agencies on a domain that answers a bot challenge to automated readers, so whether Washington County has one is a thing we could not check. What we can say is where we looked, which is everything the office publishes that a machine can read, and what is there. The records request drafted for this county asks for the section 7 policies and the section 6 figures directly, and either would turn this page from reported to documented in one reply.
On the map
The community has mapped 35 devices of this type in the county on OpenStreetMap. These are community reports: the vendor and operator of each point are unverified, and none is confirmed to belong to this system. See them on the map →
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
Street names from reverse geocoding — © OpenStreetMap contributors (ODbL).
What we do not know
- The SB 1516 section 7 policies: where they are published, if they are. A Flock transparency page may exist on a host we cannot check.
- The section 6 vendor figures: cameras, fixed locations, search counts, and the roughly 25-agency sharing list the Sheriff described.
- What the Board considered and decided. KOIN reported a consideration; the board record is robots-closed to us.
- How much of the two grants bought cameras. The reporting says about $396,000 for seven systems; the county's own releases give only totals.
What you can do
Show up
Systems like this one are approved by boards, councils and committees that meet in public. We have not yet confirmed where each of them meets in Washington County.
What we have documented in Washington County →Protect yourself
Practical steps to shrink your personal data trail. Our guides publish at launch; until then, EFF's Surveillance Self-Defense is the best starting point.
Surveillance Self-Defense →Sources
- 1.
- 2.
- 3. Enrolled Senate Bill 1516 (2026), Oregon Laws 2026 chapter 77 · Law · · accessed
- 4.
- 5.
Get the digest
A regular digest of what changed in the world of surveillance: the counties we published, the devices that appeared on the map, and the public meetings where these decisions get made. We send it when there is enough to report.
One click to unsubscribe. What we do with your address is on the newsletter page.