Colusa Police | License plate readers
Nine sworn officers, one camera on a thirteen-foot pole, and a published policy that describes data coming out of patrol cars. Its sharing clause is missing one word.
At a glance
- What the state has a record of
- One Flock ALPR camera on "a 13' X SQRD REDITORQUE pole with a camera and solar panel", filed 4 March 2026 [2]
- The department
- Nine sworn officers, serving a city of about six thousand [3]
- Published policy
- Policy 430, inside the full 736-page manual the department publishes. Lexipol release of 19 March 2025 [1]
- Suspicion required to run a search
- None. "Reasonable suspicion or probable cause is not required before using" an ALPR [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]
- Sharing
- "only with other law enforcement or prosecutorial agencies", on a written request approved by a lieutenant and kept on file. The clause carries no geographic limit [1]
- What the policy says about fixed cameras
- nothing. Its collection section describes data "transferred from vehicles to the designated storage", and the camera in the state record is bolted to a pole [1] [2]
- Who approved the camera, when, at what cost
- not established. The city's agenda platform was not identified during discovery, so no council record was reached [2]
- How many cameras there are
- not established. The state notice describes one camera on one pole [2]
How it happened
- Context
The policy, as currently released
The department's published plate reader policy: no suspicion required, data closed to public review, a one-year minimum retention, access logged by name and time, regular audits, and a release clause permitting sharing with "other law enforcement or prosecutorial agencies". [1]
- Deployment
The state records a camera on a pole
A Notice of Exemption filed with the state describes the installation of one Flock Safety ALPR camera on a thirteen-foot pole with a solar panel, on behalf of the Colusa Police Department, with "minimal ground disturbance". [2]
Nine officers and a pole
The Colusa Police Department has nine sworn officers. The city has about six thousand people. It is the smallest agency documented anywhere on this site, and in March 2026 the state received a notice that it was installing a licence plate reader.
The notice describes the whole project:
The project consists of the installation of a Flock Safety automated license plate reading (ALPR) camera to be installed on behalf of the Colusa Police Department. The installation consists of a 13’ X SQRD REDITORQUE pole with a camera and solar panel (to power the camera) mounted to the pole with minimal ground disturbance consisting of the 3” by 48” pole anchor.
A pole, a camera, and a solar panel to run it. That is the entire physical footprint, and it is enough to record every vehicle that passes it.
The department publishes its rulebook, properly
Give Colusa this: the department puts its whole policy manual on its website. All 736 pages, no request, no portal, no login. Policy 430 covers plate readers and it is a real policy.
It says the data “is not open to public review”. It sets retention at a minimum of one year. It requires that access run through “a login/password-protected system capable of documenting all access of information by name, date and time”, limits access to legitimate law enforcement purposes, and says audits “should be conducted on a regular basis”. It cites the sections of California’s Civil Code that govern plate readers.
It also says, as most of these policies do, that “Reasonable suspicion or probable cause is not required before using” the system.
And then there is the section on where the data lives:
The Administration Lieutenant is responsible for ensuring systems and processes are in place for the proper collection and retention of ALPR data. Data will be transferred from vehicles to the designated storage in accordance with department procedures.
Data transferred from vehicles.
The camera in the state’s record is bolted to a pole.
That is not a violation and this page does not call it one. The manual was released in March 2025 and the notice was filed a year later. Policies lag purchases in every agency in the country, and a Lexipol manual gets revised on the vendor’s schedule rather than the department’s. What it means is narrower and still worth knowing: the rulebook a Colusa resident would find, if they went looking for the rules about the camera on their street, describes a different kind of system.
One word
There is a second thing in Policy 430, and it only becomes visible when you have read the same section in another county.
Colusa’s release clause:
The ALPR data may be shared only with other law enforcement or prosecutorial agencies for official law enforcement purposes or as otherwise permitted by law, using the following procedures:
The Santa Barbara County Sheriff’s manual has the same section, in the same family of manual, in the same position, with the same sentence structure. Its version restricts sharing to other California law enforcement or prosecutorial agencies.
One word, and it is the word that matters most in this whole subject. California law prohibits sharing plate data with out-of-state and federal agencies. It is the restriction Ventura’s sheriff relied on, switched a feature off to honour, and then discovered through an audit had failed anyway, after agencies outside the state queried its data hundreds of thousands of times in a month.
Santa Barbara’s manual writes that limit into the sentence. Colusa’s does not.
We are not saying Colusa shares data outside California. We have read a policy, not a log. These manuals are assembled from a vendor’s template with per-agency choices, and this difference might be nothing more than which optional clause somebody kept in 2025. A department of nine officers is not running an interstate data operation.
What is publishable is that the two sentences exist, that they differ by that word, and that the word is not decorative.
What nobody wrote down
The decision. The state has a record of the camera going up, and we could find no record of anyone deciding to put it there: not a cost, not a contract, not a vote, not a minute of public discussion.
That gap is ours rather than the city’s. We did not identify the city council’s agenda system during this sweep, so we never looked in the one place the answer would be. It is first on this county’s retrieval list, and for a city this size it is probably a single agenda item somebody could find in ten minutes.
What we do not know
- Who approved the camera, when, and at what cost. The state has a record of the installation and we found no record of the decision.
- How many cameras there are or are planned. The state notice describes one.
- Whether Policy 430 has been revised since March 2025 to cover a fixed, pole-mounted camera.
- Who the department has actually shared data with, and whether any of it left California.
- Whether the department's data is searchable by other agencies through a vendor-hosted network.
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 Colusa County.
What we have documented in Colusa 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. City of Colusa, Police Department page · Primary document · accessed
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.