THE PUBLIC RECORD

What Stockton Bought

Stockton’s Flock relationship grew from 15 license-plate cameras into privately supplied police infrastructure that joins plate records, emergency calls, video search, drones, radar, and outside data networks.

Contract records establish what Stockton authorized or purchased. They do not establish that every contracted product has been deployed, how every setting is configured, or who has searched Stockton data.

Last materially updated: August 12, 2026.

Stated contract maximum
$5,416,700
The March 2026 staff report and amendment state this total after Amendment No. 4. Finance records and executed contract copies should confirm the cost stack.
Extended through
April 14, 2031
Council approved the term extension on March 31, 2026.
Reported by Flock’s portal
147 cameras
Flock’s public Stockton portal reported 147 cameras on August 8, 2026. City contract-history records described 120 readers. Stockton should reconcile the difference through an authoritative equipment inventory.
Approved package
6 drones
The quote lists six drones with docks, two radar units, Flock911, a trailer, FreeForm, and ten integrated video streams. Deployment status remains unknown.

A platform built in stages

The public record shows a sequence of contracts and amendments, not one isolated camera purchase.

Stockton records describe an original 15-camera contract, a Prepared 911 integration, a federal grant and 105-camera Falcon expansion, a later amendment whose underlying document remains missing, and a 2026 package for drones, radar, Flock911, a mobile trailer, FreeForm search, and ten integrated video streams.

The March 2026 staff report states that the new package adds $3.15 million, extends the agreement through April 14, 2031, and raises the stated maximum to $5,416,700.

City contract-history records described 120 license-plate readers. Flock’s public Stockton portal reported 147 cameras on August 8, 2026. The portal figure is vendor-published data preserved by a third party, not a City-certified inventory.

How the system grew

The timeline separates council actions, staff statements, and the one amendment still missing from the reviewed archive.

  1. September 2023

    Original Flock contract

    A later staff report says Stockton executed a contract for 15 Flock cameras. Amendment No. 1 records an original amount of $97,400.

  2. July 9, 2024

    Prepared 911 integration

    Council approved Amendment No. 1 for an amount not to exceed $877,600. The consent agenda passed 6–0 with one member absent.

  3. November 12, 2024

    Federal technology grant

    Council accepted a $963,000 COPS Technology and Equipment Program grant and identified a larger plate-reader program among the proposed uses.

  4. November 19, 2024

    Falcon expansion

    Council approved Amendment No. 2 for $1,196,700 to add 105 Falcon units and related software and APIs. The consent vote passed 7–0.

  5. March 19, 2025

    CEQA notice

    A state environmental record names two camera locations. It is not a complete camera map.

  6. June 26, 2025

    Amendment No. 3

    The March 2026 staff report says the City Manager approved a $95,000 extension. The underlying amendment has not yet been located in the reviewed archive.

    The underlying amendment remains missing.

  7. March 31, 2026

    Drone as First Responder expansion

    Council approved a $3.15 million package and extended the agreement through April 14, 2031. The item passed 7–0 after separate consideration.

What the contracts could cost

Amendment amounts and cumulative totals appear separately so readers do not add the same dollars twice.

Original contract
$97,400
Recorded in the Amendment No. 1 change-order calculator.
Amendment No. 1
$877,600
Prepared 911 integration.
Amendment No. 2
$1,196,700
Falcon expansion with 105 cameras and related APIs.
Amendment No. 3
$95,000
Reported in the 2026 staff report; the underlying amendment remains missing from the reviewed archive.
Amendment No. 4
$3,150,000
Drone as First Responder package.

The clean public statement is that the Drone as First Responder package adds $3.15 million and pushes the stated contract maximum to $5.4167 million. Finance records, invoices, purchase orders, and executed contract copies still need to confirm the full cost stack.

What the package contains

Each capability carries an attribution and a status label.

  • Plate readers: staff described 15 original cameras and an approved 105-camera expansion. Flock’s archived portal later reported 147 cameras. These figures come from different sources and do not establish the current deployed inventory.

  • Prepared 911: city documents describe caller location, transcription, translation, caller-provided media, and dispatch tools.

  • Drone package: the quote lists six drones and docks, two radar units, Flock911, a mobile trailer, FreeForm, and ten compatible video streams.

  • Search scale: the figures for ten billion monthly nationwide reads and 500 million monthly regional reads are vendor and staff claims. They are not evidence of Stockton searches or sharing events.

Public funding and long-term dependence

The record names several grant and city funding paths, but it does not support a dollar-for-dollar promise to transfer the contract amount to another program.

Records name AB109 funds, a federal COPS Technology and Equipment Program grant, Board of State and Community Corrections funds, the Police Department Field Services budget, later grants, and possible city appropriations.

A grant is public money. It may carry legal restrictions, and it may create future subscriptions, staffing duties, training costs, and pressure for replacement funds.

The city cited vendor continuity

The city’s competitive-bidding rationale is reported without declaring the exception lawful or unlawful.

Staff cited proprietary integration, continuity with existing Flock infrastructure, a limited market, and the risk of duplication or incompatibility. That rationale shows how an embedded platform can make later expansion appear easier than choosing a different course.

Who owns the hardware and operational data

The vendor terms reserve control over hardware and a broad category of operational and derived information.

The drone addendum says Flock owns the hardware and places stated risk of loss on the customer after delivery. It defines a broad category of “Flock Drone IP” that includes operational and derived information.

This record does not prove that Stockton lost control of protected records. It shows that public operations depend on private technology, permissions, and contract terms.

Sharing settings are not access history

The archived portal documents configured recipients and public search labels. Native City records are still needed to establish actual access and disclosure.

The August 8 portal archive listed 320 outbound-sharing recipients, including NCRIC, El Cajon Police Department, Stanford University CA PD, University of San Francisco CA PD, University of the Pacific, and “Decommissioned Org.” ICE, CBP, DHS, and USMS were not listed as direct recipients. A listed recipient is a sharing configuration, not proof of a search or disclosure.

The same 1,774-row public audit contained 40 rows labeled “USMS case,” and every public user ID was masked. USMS is a separate Department of Justice agency, not ICE. The label does not identify who requested the search, who had credentials, what information was returned, or whether the search was lawful.

A City response to PRA 10325372 says an SPD Flock administrator authorized UOP through the portal and that no written agreement was located. This raises an audit and compliance question. It does not prove UOP searched or received Stockton data or establish a legal violation.

NCRIC’s structure and generic data-sharing agreement create a possible indirect pathway worth auditing. The public materials do not prove Stockton executed that agreement, contributed Flock data under it, or that a federal or immigration agency accessed Stockton records.

What the record does not prove

Unanswered questions receive the same prominence as verified facts.

  • The reviewed record does not prove that Stockton shared data with ICE or any other federal immigration agency.

  • It does not prove that USMS directly accessed Stockton data or that NCRIC gave ICE access.

  • It does not prove that UOP searched or received Stockton data.

  • It does not prove that Stockton violated state law or misused the system.

  • It does not establish that every contracted camera, drone, radar unit, search tool, or video integration is deployed.

  • It does not provide a complete camera map, active hotlist list, sharing history, search log, or outside-agency access record.

  • It does not establish that the competitive-bidding exception was unlawful.

Records Stockton still owes the public

The final section turns research gaps into concrete public questions.

  • The executed Amendment No. 3 and its procurement, invoice, purchase-order, and authorization records.

  • A current inventory and deployment status for cameras, drones, docks, radar, the trailer, Flock911, FreeForm, and video streams.

  • The owners, locations, feeds, retention rules, and permissions for the ten compatible video streams.

  • Current and historical sharing settings, stable recipient identifiers, administrator approvals, native search and access logs, outside requests, re-sharing records, and the identity of “Decommissioned Org.”

  • Native records for every “USMS case” row, including the local user, requester, case number, query scope, networks searched, results returned, authorization, and supervisory review.

  • Executed agreements, authorization records, legal reviews, and actual access records for UOP, NCRIC, El Cajon, university-associated entities, and every other outbound recipient.

  • CAD fields, data flows, policies, integrations, funding records, and termination or deletion procedures.

SOURCE REGISTER

Sources and notes

Sources are numbered by first appearance. Return links lead back to the exact cited claim.

  1. Stockton recordFile 26-0269 staff report
  2. Stockton recordFile 26-0269 Amendment A—Agreement and Quote
  3. Stockton recordStockton City Council agenda and draft minutes, March 31, 2026
  4. Archived Flock portalStockton CA PD public transparency portal data

    Vendor-published portal data preserved by a third party; not a City-certified audit

  5. Stockton recordFile 24-1097 legislation text
  6. Stockton recordFlock Amendment No. 2
  7. Stockton recordFile 24-0561 legislation text
  8. Stockton recordFile 24-1067 legislation text
  9. Stockton recordFlock Amendment No. 1
  10. Stockton recordStockton City Council minutes, July 9, 2024
  11. Stockton recordStockton City Council minutes, November 12, 2024
  12. Stockton recordCOPS Technology and Equipment Program award package
  13. Stockton recordResolution 2024-11-12-1210
  14. Stockton recordStockton City Council minutes, November 19, 2024
  15. Official legal/policy sourceStockton Police Department Flock ALPR Camera Installation Project
  16. Official legal/policy sourceAbout the U.S. Marshals Service
  17. Stockton recordPRA 10325372 concerning UOP authorization
  18. Official legal/policy sourceCalifornia Civil Code sections 1798.90.5–1798.90.55
  19. Official legal/policy sourceAttorney General Bulletin 2023-DLE-06
  20. Official legal/policy sourceNC HIDTA Executive Board
  21. Official legal/policy sourceGeneric Data Sharing Memorandum of Understanding

    The generic form is not evidence that Stockton executed it or contributed Flock data under it