Sutter County Sheriff | License plate readers
A detailed order with real safeguards, read from an archive because the county's servers refuse us. It sets a two-year cap, and it never mentions California.
At a glance
- Published policy
- An "Automated License Plate Reader Program" General Order, on the Sheriff's website. Read as it stood on 20 January 2026 [1]
- Retention
- Two years, stated as a maximum. "shall be retained for a maximum of two (2) years" [1]
- On acting on a hit
- "A positive Hit under the ALPR Program does not establish probable cause", and absent exigent circumstances it must be confirmed first [1]
- Sharing
- Detection data "will be shared with requesting law enforcement agencies who utilize" the LEARN network. Agencies not on it go to a commander [1]
- Oversight the order requires
- A monthly report of total detections and hits by the 5th, periodic audits of user queries, and quarterly equipment inspection [1]
- Operators
- Directed to maintain a National Vehicle Location Services account, a commercial plate database [1]
- Mentions of California in the order
- None [1]
- Any limit on sharing outside California
- none on the face of the order. It cites no California plate reader statute and never refers to out-of-state or federal agencies. What happens in practice is not established [1]
- How many readers there are
- not established. The order describes external cameras on patrol cars; no count exists in any document we could reach [1]
- Which body approved it, when, at what cost
- unknown. The county website answers automated requests with a bot wall, so no decision record was reachable [1]
How it happened
- Context
The order, as captured
The Sheriff's published ALPR General Order sets a two-year maximum retention, requires a monthly detections-and-hits report and periodic query audits, states that a hit does not establish probable cause, directs that detection data be shared with requesting agencies on the LEARN network, and tells operators to maintain a National Vehicle Location Services account. It contains no reference to California or to the state's plate reader statute. [1]
Read from an archive
Sutter County’s servers do not talk to us. Both the Sheriff’s website and the county’s own answer automated requests with a bot wall, a 403 and a support reference, while letting any person with a browser straight through.
This project treats that as a hard stop rather than a puzzle. So the Sheriff’s “Automated License Plate Reader Program” page was read from a copy the Internet Archive captured on 20 January 2026, and everything on this page describes the order as it stood on that date. Whether it still reads this way is a question we cannot answer.
The parts that are good
It is a real General Order, not a paragraph of reassurance, and several of its provisions are firmer than what neighbouring counties publish.
A positive Hit under the ALPR Program does not establish probable cause. With the absence of exigent circumstances, the Hit information/data must be confirmed prior to taking any related law enforcement action.
Other agencies on this site tell officers to verify a hit “if practicable”. This one states flatly that the hit is not probable cause. That distinction is the difference between a suggestion and a rule, and it is the difference between a bad match being caught and a person being stopped at gunpoint over a misread plate.
The order also builds in oversight that produces documents. A monthly report to division commanders, due by the fifth, including “total detections and hits generated from the ALPR equipment”. Periodic audits of who has been querying the database, with access pruned to those showing “a continued need for it”. Quarterly equipment inspections. Hot plates entered by users expiring within thirty days.
And retention is stated the useful way round:
ALPR data that is not considered intelligence and investigative information shall be retained for a maximum of two (2) years.
Two years is a long time. But it is a maximum, and a maximum is the number a resident actually needs. San Luis Obispo and Santa Barbara both state a one-year minimum, which is a floor with no ceiling above it.
The word that is not there
Read the order from beginning to end and the word “California” does not appear in it.
Neither does any reference to Civil Code § 1798.90, the state law that governs licence plate readers, nor to SB 34, the bill that put it there. The only statute the order cites anywhere is a records retention provision. There is no clause restricting sharing to California agencies. There is no mention of out-of-state or federal agencies at all.
What the order does say about sharing is this:
All detection data generated from Sheriff’s ALPR systems will be shared with requesting law enforcement agencies who utilize the Law Enforcement Archival Reporting Network (LEARN).
LEARN is a commercial plate reader platform. The default here is that the data goes to agencies on that network when they ask for it. Agencies not on the network get escalated to a commander rather than refused.
Operators are separately directed to “maintain a National Vehicle Location Services (NVLS) account”, which is a commercial vehicle location database.
What that does and does not mean
It does not mean this office shares plate data unlawfully. It does not mean it violates SB 34. It does not mean its actual practice lacks the limits its order omits. We have read one web page, captured on one day in January, and a document’s silence is not evidence of an agency’s conduct.
What is worth putting side by side is the documents.
Kern County’s sheriff wrote an explicit prohibition on sharing with out-of-state and federal agencies into its own published policy. Santa Barbara’s restricts sharing to California law enforcement and prosecutorial agencies, and names the statute it is complying with. Ventura’s switched off a national lookup feature for the same reason, and later discovered that agencies outside California had queried its data 364,000 times in a month anyway. Each of those counties has its own page on this site, carrying its own documents.
Every one of them treated the question of whether the data leaves California as central to a plate reader programme. Sutter’s order, on its face, does not raise it.
Whether that gap matters is exactly what a records request is for, and this county’s request asks for the sharing records, the monthly reports and the query audits by name.
What we cannot tell you
How many readers there are. Whether any of them are fixed cameras rather than the external cameras on patrol cars the order describes. What the system cost. When the Board of Supervisors approved it, or whether it ever did in public.
The county’s website will not answer us, so there is no decision record here at all. That is a fact about our access, not about the county’s conduct, and a person with a browser could resolve most of it in an afternoon.
What we do not know
- Whether the order still reads this way. Our copy is from January 2026 and the live page cannot be checked while the host refuses us.
- Whether detection data has gone to agencies outside California. The order's sharing clause has no geographic limit on its face; what happens in practice is a different question.
- What the monthly detection and hit reports show. The order requires one by the fifth of every month.
- What the periodic query audits have found.
- How many readers the office operates, and whether any are fixed rather than mounted on cars.
- When the Board of Supervisors approved this, at what cost, and whether the public was heard.
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 Sutter County.
What we have documented in Sutter 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.
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.