What Benicia's own records say about its surveillance cameras
What the City of Benicia's own public records show about its Flock Safety surveillance camera program. Every claim below links to the document it came from.
1 public-records request is past the statutory deadline.
California law requires a determination within 10 days (Gov. Code §7922.535).
PR-2026-155 — City of Benicia — due .
See the request tracker →
The findings
Each one rests on documents the City produced itself. Where the record is ambiguous or a claim can't yet be proven, the finding says so plainly.
-
01
Flock wrote the city's no-bid justification
The sole-source letter that justified skipping competitive bidding was drafted by the vendor who won the contract.
-
02
The city was billed for a camera the state refused to allow
Benicia's five-year term was co-terminous from the "first camera" — including one Caltrans would not permit.
-
03
The public "transparency" page showed "system down" — and the city could edit it
Flock concluded the outage notice on Benicia's public audit page had been posted by the agency itself.
-
04
Public search-auditing is a switch the vendor flips
Whether residents can audit police searches at all is a toggle in the vendor's console, not a policy.
-
05
A years-long state-permit fight the public never saw
Caltrans encroachment permit 0424-NSV-0053 ran unresolved for years, with at least one denial.
-
06
Data shared with outside agencies by letter, with "no formal MOU"
The instrument is a one-page self-certification signed by the receiving agency — not an agreement Benicia executes.
-
07
When scrutiny arrived, Flock coached staff on the messaging
As residents raised the 2025 security exposure, the vendor supplied city staff with talking points for Council.
-
08
Every comprehensive audit found violations. Every ten-item sample found none.
18 audits, Nov 2021 to Apr 2026. The three that reviewed every inquiry found 33 violations. The fourteen that sampled 10 found zero — including one quarter where both methods ran on the same data.
-
09
The public list of sharing partners was switched off at the Chief's request — in three minutesnew
On the day the transparency portal went up in 2021, the Chief asked Flock to hide which agencies get the data. It was done before the hour was out.
-
10
For weeks the City published a superseded policy with no mandatory audit requirementnew
A resident, not the City, noticed that the ALPR policy on the website had no quarterly-audit section. The Chief confirmed it was the old version.
-
11
Officers were told to log only a case number — because the public reads the logsnew
The department removed the case-number field and barred explanatory words, citing "groups looking at our public search logs daily."
-
12
The network grows by vendor email with an "Accept All" buttonnew
59 agencies asked for access in five months. 56 have no acknowledgment letter on file, and 15 asked for video rather than just plates. Updated 2026-08-28: the portal roster shows those requests were not granted — all 75 organizations with access hold a letter.
-
13
Fifty of fifty-one camera sites are built — one is still stuck in permittingnew
The deployment is 98% complete, with a single location held in "permitting" — consistent with the unresolved Caltrans dispute.
-
14
Residents were told a "Signed MOU" is required. The City's own records say there is none.new
The November 2025 community-meeting deck states the requirement plainly. The sharing instrument is a one-page letter, and the department said in 2022 it had no formal MOU.
-
15
The City published a camera map in 2025, then called the same information a security risk in 2026new
In October 2025 it released a public placement map and a per-device inventory. In July 2026 it withheld the same category under a broader law-enforcement exemption, without explaining what changed.
-
16
The City produced the record of its own search — and it shows the search was run on a bare keywordnew
Asked about SignalTrace device-identifier correlation, the City ran an unqualified keyword search that returned Leonardo.Ai marketing, Leonardo da Vinci and Leonardo DiCaprio. Its own tasking emails were produced along with the results.
-
17
The Chief confirmed NCRIC has Benicia's data, and said nobody knew where it went nextnew
Asked by the Mayor the day after SFPD cut NCRIC off, Chief Menesini answered “Yes, for NCRIC.. No to WISN” and said the Department would need to research whether NCRIC had passed Benicia's cameras onward. NCRIC has since said that research cannot be finished: queries are logged, but no report can show whose cameras answered one.
-
18
Flock was inside the city nine months before it sold the city anythingnew
In May 2020 the vendor offered Benicia PD free access to a private homeowners association's camera network. The sole-source letter came nine months later. By the time Council voted, the Department had been using a Flock system in its own city for a year.
-
19
The community meetings were the vendor's plan, and their stated goal was Council approvalnew
Ten weeks before the vote, Flock's territory manager set out the community-engagement format and its purpose in his own words: "Engage the community so Benicia PD's project will be approved when it goes to Council." The same chain carries the sole-source letter, the agreement, and two other cities' staff reports as models.
-
20
The "California only" rule held. The data reached the DEA anyway.new
Benicia told residents it shares only with California agencies, and the sharing roster published on its own portal bears that out: 75 organizations, every one of them Californian. Benicia camera data still ended up in searches run for out-of-state and federal agencies, because the rule governs who Benicia hands data to and says nothing about what those agencies do next.
-
21
Asked whether outside agencies could reach Benicia's cameras, staff answered with a 50-mile setting. The roster runs 500 miles.new
In February 2026 the Mayor asked whether Flock's statewide and nationwide settings had been used on Benicia's data. Records staff answered with screenshots showing discoverability capped at 50 miles. That answer was accurate. It also described a different thing: the roster of agencies actually granted access includes nine Southern California departments 350 to 500 miles away.
-
22
To get another agency's data, Benicia signed up to 60-day audits. It has produced none.new
Every sharing instrument in this archive so far runs outward: a one-page letter the receiving agency signs itself, imposing nothing on Benicia. Roseville's runs the other way. To obtain access to Roseville's Flock cameras in November 2024, Benicia accepted named-user logging, a mandatory case number on every search, a ban on onward sharing without written consent, and an audit of its own searches at least every sixty days. Deputy Chief Edward Criado signed it twice, the second time as the Agency's LPR Manager, the officer the agreement makes responsible for those audits.
Start here
Search the documents →
717 files, full text, as produced. Nothing summarised away.
Who gets the data →
83 agencies hold a signed letter. 59 more asked in five months.
The timeline →
2018-12-20 to 2026-08-21, built from the documents' own dates.
Do this for your city →
The request language, the pipeline, and what to ask for. Flock is in hundreds of towns.
Questions for candidates →
5 questions on the Flock program and City use of AI, going to every candidate in the Benicia City Council — November 2026 race. 5 of 5 answered so far.