Tehama County Sheriff | License plate readers
The clearest sharing rule on this site, in the most recently revised policy. Its first sentence reads loosely and its second closes it completely.
At a glance
- Published policy
- Policy 472, inside the 828-page manual the office publishes. Lexipol release of 2 July 2026 [1]
- Sharing
- California state and local agencies only. The policy states that a public agency "does not include out-of-state or federal law enforcement agencies", citing the statute [1]
- Requests from outside California
- Routed to a separate records policy rather than answered under this one [1]
- Suspicion required to run a search
- None. "Reasonable suspicion or probable cause is not required before using" an ALPR [1]
- Public access to the data
- None. "it is not open to public review" [1]
- Retention
- A one-year minimum for data downloaded to the server [1]
- Access control
- A login system "capable of documenting all access of information by name, date and time", with audits "on a regular basis" [1]
- The mechanism the policy describes
- Data "transferred from vehicles to the designated storage" [1]
- What the office operates
- not established. No camera count, vendor, contract or cost appears in anything we read, and the policy has no vocabulary for fixed cameras [1]
- Which body approved it, when, at what cost
- not read. 356 Board of Supervisors documents since 2021 are in our corpus and have not been scanned [1]
How it happened
- Context
Policy 472, as currently released
The most recently revised plate reader policy on this site. No suspicion required, data closed to public review, a one-year minimum retention, access logged by name and time, regular audits, and a sharing clause that limits release to California state and local agencies and expressly excludes out-of-state and federal law enforcement agencies. [1]
Two paragraphs
The Tehama County Sheriff’s Office publishes its policy manual, all 828 pages, on a page titled Policy and Procedures, alongside a custody manual and a declaration about federal surplus equipment. Policy 472 covers licence plate readers, and it was revised on 2 July 2026, which makes it the most current such policy this site has read.
Most of it is what these policies say. No reasonable suspicion or probable cause is needed before running a search. The data “is not open to public review”. Retention is a one-year minimum. Access runs through a login that records who looked, by name and date and time, and audits “should be conducted on a regular basis”. The system it imagines is a patrol car: data “transferred from vehicles to the designated storage”.
The interesting part is section 472.7, and it needs both of its paragraphs.
The first:
The ALPR data may be shared only with public agencies and only as otherwise permitted by law (Civil Code § 1798.90.55).
Read alone that is loose. A public agency is a far wider category than a police department: it takes in every city, county, district and state body there is.
The second paragraph:
For purposes of this section, a public agency is limited to California state or local agencies, including law enforcement agencies, and does not include out-of-state or federal law enforcement agencies (Civil Code § 1798.90.5).
That is the clearest statement of the rule anywhere on this site. It names the category, names the exclusion, and cites the section of the Civil Code that defines it. Requests from public agencies outside California are routed to a different policy rather than answered under this one.
We nearly published the opposite. Reading the first sentence and stopping would have produced a page saying Tehama had the loosest sharing clause of any county documented here, when it has the tightest.
Three counties, one section
Three counties on this site publish the same section of the same family of manual, and they answer the central question three different ways.
Tehama’s names the exclusion of out-of-state and federal agencies outright, with the statute cited.
Santa Barbara’s restricts sharing to other California law enforcement and prosecutorial agencies, which reaches the same place through geography.
Colusa’s permits sharing with other law enforcement or prosecutorial agencies, and says nothing about where those agencies are.
That is a comparison of published texts and nothing else. It does not establish what any of the three agencies does with its data. A department can comply with the statute perfectly while its policy says nothing, or write an admirable clause and never look at it again.
What the comparison does show is which agencies wrote the answer down. That matters because a written rule is the thing a resident can point at, a court can enforce, and an auditor can test against. An unwritten practice is only as durable as the person currently in charge of it.
And it matters here in particular because of what happened further south. Ventura’s sheriff relied on exactly this restriction, switched off a vendor feature specifically to honour it, and then found through an audit that agencies outside California had queried its data hundreds of thousands of times in a single month regardless. A clause is not a wall. It is just the only place the wall is written down.
What is missing
Everything about the equipment.
There is no camera count in anything we read. No vendor. No contract. No cost. No record of the board approving any of it. The policy describes data coming out of patrol cars and has no vocabulary at all for a camera bolted to a pole, which does not tell us whether the office has any.
That last gap is closer to being filled than most on this site: 356 Board of Supervisors documents going back to 2021 are already in our corpus, fetched and unread. The decision is probably in there.
One more thing is reported and unverified, and it would change the shape of this page if it turned out to be true. Reporting describes the Corning Police Department operating both Flock and Motorola readers, and partnering with the Red Bluff Police Department and this Sheriff’s Office on a shared plate reader programme. We have not confirmed it.
If it is true, it raises a question Policy 472 cannot answer by itself. A carefully drafted sharing clause binds the agency that wrote it. In a system three departments share, the data tends to move under whichever of the three rulebooks says the least.
What we do not know
- What the office actually operates. No count, vendor, contract or cost is established anywhere.
- Whether the office runs fixed cameras. The policy describes data transferred from vehicles and has no vocabulary for anything on a pole.
- When the Board of Supervisors approved this and at what cost. The board record is in our corpus and unscanned.
- What the regular audits the policy requires have found.
- Whether a three-agency programme with Corning and Red Bluff police departments exists, and if so whose policy governs the shared data.
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 Tehama County.
What we have documented in Tehama 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.