Public-records requests

How these emails were obtained

Every document on this site arrived the same way: through a written request under the California Public Records Act. No leak, no source, no litigation. The process is open to anyone, and the portal is public.

Where they were filed

Eleven of the twelve requests went to the City of Benicia through its records portal at beniciaca.justfoia.com. The twelfth went to the San Francisco Police Department through its GovQA portal. JustFOIA is the City’s own intake system — submitting there produces the PR-YYYY-NNN reference numbers used throughout this archive, which is why every document here can be traced to a numbered request.

No account is needed to read the Act, and none of these requests explained who was asking or why.

What the Act actually requires

• A determination within 10 calendar days. An agency must decide within ten days whether it holds records responsive to the request and tell you (Gov. Code §7922.535). This is a determination, not delivery — a common source of confusion, and a distinction agencies rely on.
• An extension of up to 14 more days, in “unusual circumstances”, with written reasons (§7922.535(c)). Benicia invoked this on PR-2026-181, citing voluminous records.
• No identification, no stated purpose. The Act does not permit an agency to condition access on who you are or why you want it (§7921.000 et seq.).
• Records in the format held. Electronic records are generally produced electronically. These arrived as PDF printouts of email threads, with attachments embedded inside them.
• Exemptions must be claimed, and cited. An agency withholding material has to say so and identify the basis. Benicia withheld camera locations under §7923.600(a) and the §7922.000 public-interest balancing test.

What actually happened here

The statutory clock and the delivery time are very different things. Across the nine requests that produced anything, the gap between filing and production ranged from 8 days to 320 days:

Request	Filed → produced	Days
PR-2025-271	2025-12-04 → 2025-12-12	8
PR-2026-180	2026-07-11 → 2026-07-21	10
PR-2026-189	2026-07-18 → 2026-07-28	10
PR-2025-200	2025-09-08 → 2025-10-02	24
PR-2026-155	2026-06-24 → 2026-07-21	27
PR-2025-159	2025-08-16 → 2026-02-14	182
PR-2026-7	2026-01-07 → 2026-07-25	199
PR-2025-199	2025-09-08 → 2026-07-25	320

Several of these remain partial: the City produces in rolling batches and continues to add to requests it has already answered. PR-2026-7 was re-released on 2026-07-25 with 31 documents that had not appeared in the 2026-07-11 production two weeks earlier. A request marked “produced” is not necessarily finished.

Stated fairly: long turnarounds are not by themselves evidence of obstruction. Some of these requests were broad, and the City did keep producing. The Act’s ten-day clock governs the determination, not the delivery, and Benicia generally met it.

The friction worth recording

Benicia does not accept requests submitted through MuckRock. Deadline tracking on this site is therefore maintained by hand rather than by a filing service. The Act does not let an agency dictate the channel a request arrives through, and an agency that rejects otherwise valid requests solely because of the service that transmitted them is on questionable ground.

One request was closed for ambiguity, then reopened. PR-2026-155 was closed on the basis that it was unclear, and reopened on 2026-07-22 after a challenge under §7922.600 — the provision requiring an agency to assist a requester in making a focused, effective request.

One was denied outright. PR-2025-254, for raw ALPR data, was refused. The denial letter is itself part of the record.

One production answered a different question than the one asked. PR-2026-189 returned 29 email printouts matched on the bare token “Leonardo” — 17 of them Leonardo.Ai marketing, Leonardo da Vinci, Leonardo DiCaprio or Leonardo S.p.A. The City also produced its own tasking emails, which state the search terms and show the search was run unscoped across all City mail.

Checking the chain yourself

Provenance only means something if it can be tested. The original request-response .zip files as downloaded from the portal are kept unmodified, and ARCHIVE-CHECKSUMS.txt lists the SHA-256 of every file in the archive. Nothing here is edited to fix a typo or remove a name — redactions are applied at publish time, so the published text and the source can always be compared. See Do this for your city for the full method.

What is still outstanding

The single most valuable record not yet produced is Benicia’s Flock Network Audit export — the log of every external agency search run against Benicia’s cameras. The data owner can run it on demand. If entries from NCRIC, the Western States Information Network, or out-of-state and federal agencies appear there, that answers directly whether Benicia’s data travelled the network involved in San Francisco’s disclosed misuse.