San Luis Obispo County Sheriff | License plate readers
The rulebook governing plate readers here describes cameras mounted on patrol cars. It has described cameras mounted on patrol cars, in materially the same words, since 2016.
At a glance
- Published policy
- Policy 466, inside the 728-page manual the office publishes, released 12 March 2026 [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]
- The mechanism the policy describes
- Data "stored in department vehicles" transferred to a secure server at intervals "not to exceed 30 days" [1]
- Retention
- A minimum of one year for data downloaded to the server, under a records retention statute [1]
- Changes since the 2016 printing
- Three. The responsible bureau is renamed, a Civil Code citation and a CLETS training requirement are added, and "the department server" becomes "a secure server" [1] [2]
- What the policy says about vendors, fixed cameras or interstate sharing
- nothing. Read end to end, Policy 466 contains no reference to a vendor platform, a transparency portal, pole-mounted cameras, a national lookup capability, or query audit logs [1]
- What the office actually operates
- not established. The Atlas of Surveillance records Motorola Solutions, formerly Vigilant; a local campaign site counts Flock cameras countywide. Neither is verified here [1]
- Which body approved it, when, at what cost
- unknown. The Board of Supervisors publishes through a portal whose robots.txt permits four named search crawlers and refuses everyone else [1]
How it happened
- Context
Policy 466, as printed then
Twenty-one sentences governing vehicle-mounted plate readers: no suspicion required, data closed to public review, transfers from department vehicles at intervals not exceeding thirty days, and a one-year minimum retention under a records retention statute. [2]
- Context
Policy 466, as printed now
The same twenty-one sentences. The bureau responsible is renamed, a Civil Code citation and a CLETS training requirement are added, and "the department server" becomes "a secure server". Every other provision is word for word what it was a decade earlier. [1]
The same twenty-one sentences
The San Luis Obispo County Sheriff’s Office publishes its policy manual, and Policy 466 covers automated licence plate readers. The current printing is dated 12 March 2026.
The Electronic Frontier Foundation collected the same Policy 466 a decade ago, as part of a project gathering plate reader policies from California agencies. That copy survives on a hostname the office no longer uses. Its printed date is 23 March 2016.
We read both, end to end, and compared them sentence by sentence. Both are twenty-one sentences.
In ten years, three things changed. The responsible bureau was renamed from Support Services to Investigative Services. A statutory citation was added, and paragraphs (a) and (d) were tightened to require CLETS authorisation and CLETS-approved training. And “the department server” became “a secure server”.
Everything else is word for word.
What stayed
An ALPR may be used in conjunction with any routine patrol operation or criminal investigation. Reasonable suspicion or probable cause is not required before using an ALPR.
That sentence is in both printings. So is this one:
All data and images gathered by an ALPR are for the official use of the San Luis Obispo County Sheriff’s Office and because such data may contain confidential CLETS information, it is not open to public review.
And so is the passage that describes how the system is imagined to work:
The Investigative Services Bureau Chief or designee is responsible to ensure proper collection and retention of ALPR data, and for transferring ALPR data stored in department vehicles to a secure server on a regular basis, not to exceed 30 days between transfers.
Data stored in department vehicles. Carried back. Transferred to a server, at intervals of up to a month.
That is a patrol car with a camera on the roof. In 2016 it was a fair description of how most police plate readers worked.
What is not in it
Read Policy 466 in its 2026 printing from beginning to end and it contains no reference to any of the following: a vendor, or a platform hosted by one. A transparency portal. A fixed or pole-mounted camera. A national or interstate lookup capability. A log of who searched the data and why. Or any restriction on sharing outside California beyond the words “only as permitted by law”.
That is a statement about one document, and we made it by reading the document.
It matters because of what sits on either side of this county. In Ventura, the sheriff audited its own plate data and found that a vendor’s error had let agencies outside California query it just over 364,000 times in a single month. In Santa Barbara, the sheriff had to review a vendor’s audit logs to confirm that the same thing had not happened there. Neither of those events involves a camera on a car. They happen inside a company’s cloud, through a nationwide search network, and they are detectable only through query logs.
Policy 466 has no vocabulary for any of that.
What we are not saying
We are not saying this policy is inadequate, ignored, or out of date, because we have not established what this office operates.
Three different sources point three different ways. Policy 466 describes vehicle-mounted readers. The Atlas of Surveillance records Motorola Solutions, formerly Vigilant, for this office. A local campaign site counts Flock cameras across the county. Those are not the same system, and none of the three is a document we have verified.
We also cannot tell you what the county decided, or when, or for how much. The Board of Supervisors publishes its agendas through a portal whose robots file permits four named search engines and refuses every other automated client, so the record of what this county bought is not something we can currently read. The county seat’s own website answers us with a 403.
So this page is about a rulebook, and only about a rulebook. The rulebook governing licence plate readers in San Luis Obispo County describes cameras on cars, and it has said the same thing, in materially the same words, for ten years.
What we do not know
- What the office actually operates. Policy 466 describes vehicle-mounted readers; the Atlas records a different vendor; a campaign site counts a third kind of camera. These are not the same system.
- Whether plate data collected here is held by a vendor, and under what retention.
- Whether the office participates in any inter-agency or interstate search network. The policy contains no provision about one, in either printing.
- Whether anyone has ever audited who searched this data. The policy requires no query audit.
- When the Board of Supervisors approved plate readers, at what cost, and whether the public was ever 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 San Luis Obispo County.
What we have documented in San Luis Obispo 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.
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.