Santa Barbara County Sheriff | License plate readers

An office that did the things we usually have to ask for

Most pages on this site are assembled out of documents an agency did not particularly want to hand over. This one is not.

The Santa Barbara County Sheriff’s Office publishes its policy manual. All 764 pages of it, on its own website, with no request required. Policy 467 covers automated licence plate readers, and it says what a plate reader policy is supposed to say. Data goes only to California law enforcement and prosecutorial agencies. Each release needs a written request naming the agency, the person asking and the purpose. A division commander has to approve it, and the approved request is kept. Access to the data runs through a login that records who looked, on what date, at what time. Audits “should be conducted on a regular basis”.

And when the office set the system up, it turned off Flock Safety’s “National Lookup”, the feature that opens a local camera network to searches from across the country. It said why: Senate Bill 54, and a state law that prohibits sharing this data with federal or out-of-state agencies.

And before any of that, the Board of Supervisors held a hearing about it.

An hour set aside

On 16 August 2022 the county’s plate reader programme came to the Board of Supervisors as item 3. Not on the consent calendar. As a HEARING, with an hour of the board’s time set aside for it, and with this written into the item itself:

b) Consistent with the requirements of California Civil Code Section 1798.90.55(a), during a regularly scheduled meeting of the Board, provide members of the public and the Board with an opportunity to comment upon and provide suggestions relating to the Sheriff’s Office’s: i) Participation in the National Policing Institute’s study on the effectiveness of Automated License Plate Reader technology; and ii) Operation of Automated License Plate Reader technology within Santa Barbara County, to include policies, procedures, privacy concerns and transparency toward concerned community members and policy makers;

That Civil Code section is the part of California’s plate reader law that says the public gets to be heard before an agency starts operating this technology. Santa Barbara’s board named the statute on the agenda and scheduled a hearing to satisfy it.

The Action Summary records how long it took:

HEARING TIME: 1:00 PM - 1:35 PM (35 MIN.)

Thirty-five minutes. Then a motion, a second, and five ayes to approve execution of the agreement with Flock Group, Inc.

Thirty-five minutes is not a long time to decide that every car passing a set of cameras will have its plate recorded. It is also thirty-five minutes more than several other counties on this site gave the same decision, and it happened because a statute required it and this board followed the statute.

Hold all of that in mind, because of what happened next.

The sentence

In March 2026 the Sheriff’s Office published an update. This is the middle of it:

Recently, Flock Safety notified law enforcement agencies of a system issue that, in some jurisdictions, resulted in nationwide information-sharing settings being activated without the agency’s knowledge. The Sheriff’s Office conducted a review of its system settings and audit logs and confirmed that Santa Barbara County’s National Lookup function remained disabled and that our data was not shared outside of California.

Santa Barbara was fine. It checked, and it says so, and we have no reason to doubt it.

But read what the agency is describing. A California sheriff’s compliance with a California statute rested on a switch inside a private company’s software. The company’s system turned that switch on somewhere, for some agencies, without those agencies knowing. They found out when the company told them.

The office also notes that it was “not among the approximately 75% of agencies nationwide that enabled nationwide data sharing.” That figure is theirs, and it carries no citation in the statement, so treat it as their characterisation rather than an established number. Taken at their word, it means roughly three in four agencies running these cameras had already chosen to make their local plate data searchable from anywhere in the country, before any system issue arose.

Where the proof lives

There is one more sentence in Policy 467 worth reading closely:

All data and images gathered by the ALPR are for the official use of this office. Because such data may contain confidential information, it is not open to public review. However, we will make our policy, aggregated usage and audit data available via the Flock Transparency Portal.

That is a genuine transparency commitment. The office promises to publish how much the system is used and what the audits show.

It publishes them on a website run by the company that sells the cameras.

So the arrangement, described plainly and without accusing anyone of anything, is this. The restriction is a vendor setting. The evidence that the restriction held is a vendor log. The place the public goes to check is a vendor page. When the vendor’s system changed that setting somewhere without telling anyone, the way an agency confirmed it had not happened to them was by reviewing logs the vendor also holds.

That page, incidentally, refuses automated requests, so we cannot read it either. A person with a browser can, and it is first on this county’s retrieval list.

The number that is not there

Policy 467 does address retention, and it is easy to read it as more than it is:

All ALPR data that is downloaded to the server should be stored for a minimum of one year (Government Code § 34090.6) and in accordance with the established records retention schedule.

A minimum, not a maximum, and it applies to data the office has pulled onto its own servers, which the policy says happens only when the data is relevant to an investigation. That is a records retention floor, and it is a sensible one.

What it is not is an answer to the question an ordinary driver would ask. If your plate was read on a Tuesday and you were not relevant to any investigation, that read sits with the vendor, and how long it sits there is not written down anywhere in this policy. We do not know the number. Neither, from this document alone, would a resident.

What else this office has

Very little, and that is worth saying because accuracy runs both directions. The Sheriff’s AB 481 report for 2024 lists three drones. Two DJI Matrice units assigned to Search and Rescue, “Donated by a local business”. One Brinc Lemur S, “purchased with privately donated funds”. In the whole of 2024 the Brinc had no operational uses at all, and Search and Rescue flew drones for about eighteen hours.

Eighteen hours of search-and-rescue flying is not a surveillance programme, and this page is not going to pretend otherwise.