Statements are compared conservatively
A record conflict means a released document materially conflicts with the wording of a meeting statement. It does not establish intent, dishonesty, or misconduct. Where a platform capability may have been disabled by ACSO configuration, that possibility is stated. Legal sections identify possible compliance issues and are not court findings or legal advice.
Executive summary
- Strongest factual conflict: the statement that Flock has no stolen/wanted-vehicle notification capability conflicts with the signed product description and released hot-list alert reports.
- Camera siting does not match a perimeter-only description: several disclosed sites are on internal Amador County corridors, making the Martell grocery-shopping example too categorical.
- Pre-contract use was operational: searches began in August 2023 and continued through 2024, well before County-owned cameras were installed.
- Retention remains unresolved: 30-day Flock cloud retention and Policy 473’s one-year server language were already recognized as a conflict before the 2025 approval.
- The February 2025 approval process raises a public-comment compliance question: the transcript shows only a non-agenda public-comment period before the Board immediately approved the consent calendar.
What happened on August 11
The Sheriff presented the program and answered Board questions. Public comment followed. Supervisor Brian Oneto later moved to cancel the Flock contract; Supervisor Logan Carnell seconded. The motion failed 2–3. A later motion to bring the program back as a regular agenda item near renewal passed 5–0.
During that deliberation, Chairman Patrick Crew said the Board could “probably” agree the program should not have been on consent when originally approved. The transcript records an audible agreement immediately afterward. That statement is relevant process context, but it is not itself a legal finding that the 2025 approval violated the Brown Act or another statute.
Sheriff’s statements compared with the records
| Topic | Meeting statement | What the records show | Assessment |
|---|---|---|---|
| 2023 “demoing” vs. operational use | The Sheriff described 2023 as a period when ACSO was “demoing” Flock and had no County cameras. | Records show the Flock organization and administrator accounts were created in August 2023, shared-camera access was confirmed, training was underway, and ACSO conducted 219 searches from August–December 2023 and 1,527 in 2024. | Accurate if “demoing” means Amador had not yet installed its own cameras; incomplete if it suggests operational use did not begin until the 2025 contract. Sources: 06 transcript, 23:27–24:04; pre-contract access report; monthly search records. |
| Stolen/wanted vehicles and “zero notifications” | The Sheriff said ACSO receives “zero notifications,” the system cannot tell ACSO if a vehicle is stolen or wanted, and “has none of those capabilities”; he said it must be searched. | The signed product description lists real-time NCIC alerts, custom hot-list alerts, and vehicle-description notifications. Released data also include “Hotlist report by source type” and “Hotlist total alerts by topic,” including stolen-vehicle and stolen-plate categories. | The categorical capability claim conflicts with the contract and released alert reports. A possible reconciliation is that Amador has alert delivery disabled, but the production reviewed to date does not establish that configuration. Sources: 06 transcript, approx. 27:50–28:45; contract product description; usage-data report. |
| County-entry rationale and the Martell example | The Sheriff said the goal was “really to get the people that are coming into and out of Amador County” and later said a person going to the grocery store in Martell would not even be on a Flock camera. | The eight disclosed installations include two at Ridge Road/Highway 49, two on Airport Road, and one on Ridge Road near Highway 88, in addition to Lake Camanche and Shenandoah Road locations. Several are internal travel corridors rather than county-boundary sites. | The disclosed network is not limited to the county perimeter. Ordinary intra-county travel can encounter cameras depending on route, so the Martell example is too categorical. Sources: 06 transcript, approx. 25:15–25:50 and 31:20–32:00; camera-location response and camera map. |
| 30-day deletion vs. Policy 473 | The Sheriff said ordinary Flock images are deleted on day 31 unless downloaded for a case. | The contract states a 30-day rolling retention period. Policy 473.5 separately says ALPR data downloaded to “the server” should be stored for a minimum of one year. A February 2025 email shows ACSO identified the conflict before Board approval and Flock said one-year cloud retention would cost extra. | The 30-day statement matches Flock cloud retention but does not resolve the one-year policy language or define “the server.” Sources: 06 transcript, approx. 38:40–40:25; Policy 473.5; Feb. 2025 retention email; policy-and-retention report. |
| “It’s not tracking people” | The Sheriff repeatedly distinguished Flock from “tracking” and described searches as something done only after there is a law-enforcement reason. | The system records vehicle sightings at known locations and times and allows historical searches. That is not continuous GPS tracking, but multiple sightings can reveal portions of a vehicle’s movement history. | “Not live or continuous tracking” is a narrower, more supportable description than a categorical statement that the system is not tracking. Sources: 06 transcript, approx. 28:00 and 31:30; contract/search records. |
| “Cheapest / economy version” and available capabilities | The Sheriff repeatedly described Amador’s purchase as the cheapest or economy version and said the camera could not do the broader functions discussed. | The order form identifies FlockOS Essentials, an Enhanced LPR Upgrade and 10 Falcon cameras. The product description lists network search, real-time NCIC alerts, custom hot lists, vehicle-description alerts, Community Network Access and state/nationwide lookup features. | The records support that Amador bought Falcon LPR rather than the vendor’s broader live-video/facial-recognition products, but they do not support the broader claim that the contracted platform lacks alert and network-search capabilities. Sources: 06 transcript, approx. 26:50–28:45 and 42:00–42:45; signed contract. |
| California-only / federal sharing statements | The Sheriff said ACSO does not share outside California or with federal agencies and confirmed that no one outside California can access Amador cameras. | The available outgoing snapshot supports in-state outgoing sharing at that time. Separate incoming reports list 187 organizations/networks and include clearly out-of-state organizations; invitations also came from agencies outside California. Those records do not prove the invitations were accepted or used. | “We do not share Amador camera data out of state” is supported by the outgoing snapshot. That is different from saying the platform cannot support out-of-state access or that ACSO has never been offered incoming out-of-state data. Sources: 06 transcript, approx. 34:00–38:30; data-sharing report; unified-response findings. |
| “We review and audit everything” | The Sheriff said command staff audits the system and “we review and we audit everything.” | Policy 473 calls for regular audits, and California law requires access records with date/time, query data, user and purpose. The released administrative event log documents configuration/account activity, not a complete search-use compliance audit. No report demonstrating review of every search was produced. | The records show logging and audit requirements, but the production does not independently demonstrate the categorical claim that every use is reviewed by command staff. Sources: 06 transcript, approx. 29:20–30:10; Policy 473; Civil Code §1798.90.52; unified-response findings. |
| Eight installed / ten total | The Sheriff said eight cameras were installed and the program was slated for ten total, not ten additional cameras. | The contract is for 10 Falcon cameras; the released installation sheet contains eight installation entries, and later deployment correspondence refers to two remaining locations. | Consistent with the released records. Sources: 06 transcript, approx. 25:00 and 53:00; contract and deployment records. |
| “15,000-plus hits per day” | The Sheriff said ACSO averages about 15,000-plus “hits” per day. | The released May 17–June 15, 2026 vehicle-volume CSV totals 700,047 reads over 30 days, an average of about 23,335 per day. | The figures cover different moments and “hits” may have been used loosely, so this is not treated as a contradiction. The meeting figure should not be substituted for the released 30-day dataset. Sources: 06 transcript, approx. 51:20; usage-data report and vehicle-volume CSV. |
| “Unequivocally” zero Fourth Amendment issue | The Sheriff said there is “zero Fourth Amendment violation,” told critics to take him to federal court, and said case law supports his position. | In United States v. Yang (9th Cir. 2020), the court affirmed denial of suppression on the facts before it but the majority did not resolve the broader warrantless-ALPR privacy question because the defendant lacked a reasonable expectation of privacy in the overdue rental vehicle. | Visible license plates generally receive limited privacy protection, but the Ninth Circuit decision does not establish that every possible aggregated ALPR search, retention period, sharing arrangement or scale of location history is categorically constitutional. Sources: 06 transcript, approx. 24:20–25:20 and 48:00; United States v. Yang, 958 F.3d 851 (9th Cir. 2020). |
| Data “owned and stored by the company” | The Sheriff said the data is “owned and stored by the company.” | The records support Flock-hosted storage under the contracted cloud service. Legal ownership is a separate proposition governed by the incorporated agreement/terms and should be verified against the controlling contract language. | Treat storage and ownership as separate questions rather than repeating the meeting statement as an established fact. Sources: 06 transcript, approx. 33:30–34:30; executed contract and incorporated terms. |
February 25, 2025 approval: public-comment question
The transcript does not show agenda-item public comment before the consent vote
The February transcript shows the Chair opening public comment expressly for matters not on the agenda. After that period closes, the Board approves the day’s agenda and immediately approves the consent calendar 5–0. No separate invitation for comment on the consent calendar appears in the transcript between those votes.
California Government Code § 54954.3 requires an opportunity for the public to address a local legislative body on agenda items before or during consideration, subject to statutory exceptions. Civil Code § 1798.90.55(a) separately requires a public agency that operates or intends to operate an ALPR system to provide an opportunity for public comment at a regularly scheduled meeting before implementing the program.
The archived transcript therefore raises a concrete compliance question, but the archive is not labeling the 2025 vote unlawful. A definitive conclusion would require review of the full agenda language, any separate comment procedures, any qualifying earlier public meeting or committee consideration, and the precise point at which ACSO’s “program” was implemented for purposes of the ALPR statute.
Earlier policy timing question: 2023 Flock use
Records show ACSO searches beginning in August 2023. A September 2023 email refers to preparing to “push out” the ALPR policy and directs personnel to complete Flock training. Civil Code § 1798.90.53 requires an ALPR end-user to implement and publicly post a usage/privacy policy covering authorized uses, training, monitoring/audits, sharing, accuracy, and retention. The key unresolved question is whether a compliant policy was already in force and publicly posted when operational searches began. The currently released records do not answer that.
Fourth Amendment context
The report does not treat the Sheriff’s constitutional position as automatically wrong. It does distinguish the narrower proposition that a visible license plate is exposed to public view from the broader question of warrantless searches across aggregated historical ALPR location data. In United States v. Yang, the Ninth Circuit majority did not resolve that broader privacy question on the merits because of the defendant’s lack of a reasonable expectation of privacy in the overdue rental vehicle.
Open questions for records follow-up
- Are NCIC, hot-list, stolen-vehicle, or vehicle-description alert deliveries disabled for ACSO? If so, what configuration record proves that?
- What is the documented siting rationale for each of the 10 contracted cameras, and how does each site relate to the stated “coming into and out of Amador County” goal?
- What exactly does “the server” mean in Policy 473.5, and what data are retained locally for one year?
- What audit record demonstrates command-staff review of search activity, as distinguished from the administrative event log?
- Was a compliant ALPR policy in force and publicly posted before searches began in August 2023?
- What public-comment opportunity, if any, preceded implementation of the 2023 Flock access or the 2025 County-camera deployment?
Transcript provenance
The meeting transcripts used here were generated from the public YouTube captions and manually reviewed to add speaker names where reasonably clear and correct obvious caption/spelling errors. They are working transcripts, not certified verbatim records. Readers can compare them directly with the original videos.
Revision history
- Initial publication using the manually reviewed transcript bundle and previously archived CPRA records.