# Flock Network Sharing / Hot Lists The umbrella concept for **all data-flow mechanisms Flock's platform enables across organizational boundaries**. Encompasses (a) network sharing — granting another org search access to your camera reads; (b) hot list sharing — pushing a custom plate-of-interest list to another org's alert feed; (c) federal-prefix sharing — the special case of federal-LE access via the `[Federal]` org convention. The Conway production documents all three at scale. ## How it appears in the corpus - **[[SharedNetworks 2025-12-17 Snapshot]]** — 1,384 organizations in Conway's sharing topology as of 12/17/2025. Bidirectional: 486. Inbound-only: 471. Outbound-only: 427. Geographic spread across 38+ states. - **[[Escambia County FL SO Hot List Share]]** — A custom hot list pushed from Florida to Conway via the platform alone (no MOU, no countersignature). - **[[Home Depot Camera Sharing Series]]** — A corporate-coordinated, state-wide rollout of private-business camera sharing into Arkansas LE agencies, executed in spring 2026 across six Conway-area stores (more nationally). - **[[Federal Searches CSV]]** — 5,929 federal-LE lookups against Conway's data in March–April 2026. - The **"Flock Network Sharing Tool" PDF series** (`pg1`, `pg2`, `pg3`, `pg5`, `7`, `8`, `9`, `11`, `13` files in the production) is the vendor's customer-facing documentation of the sharing UI — captures the admin-UI workflow agencies use to configure sharing. Per-file ingest deferred to second pass. - **[[PCSO ALPR Six-Month Practice and Usage Report]]** — the activity-side data for the [[Pulaski County Sheriff's Office]] Flock deployment. Of 2,092 alerts in Jan 1 – May 19 2026, **1,645 (79%)** came from "Other Custom Hotlist Alerts on Your Networks" — alerts triggered by custom hot lists other agencies own and share into PCSO's networks. PCSO is itself enumerated in Conway PD's [[SharedNetworks 2025-12-17 Snapshot]] (row 279); the two productions describe the same network from two operating ends. ## Stakeholders - **Agency administrators** — toggle relationships in the platform admin UI. At Conway, this is overwhelmingly [[Lt. Andrew Burningham]] (330 of 389 .msg headers per [[2026-05 Bounce-Scope Diagnostic]]). - **Counterparty administrators** — toggle on their end. - **Flock** — defines the abstraction (network, hot list, federal prefix) and operates the platform infrastructure. ## Timeline The Conway-specific sharing arrangements develop over the deployment's lifetime; the [[SharedNetworks 2025-12-17 Snapshot]] is the only point-in-time view available. Notable events: - 2025-01-23 — Project kickoff; "Faulkner Co Emergency Comms Center - might give them access" candidate noted in [[AR - Conway PD - Welcome to Flock! (3) - Flock Kickoff Slide Deck]]. - 2025-12-17 — SharedNetworks snapshot generated. - 2026-01-22 — [[Escambia County FL SO Hot List Share]] notification. - 2026-03-12 — Home Depot state-wide rollout announcement. - 2026-03-12 → 2026-04-08 — Six Home Depot store shares completed for Conway. ### In PDFOI-2026-1874 (LRPD Flock emails) The Little Rock Police Department production documents the same sharing mechanisms from a second Arkansas jurisdiction, this time observed through hundreds of **[[Flock Deconfliction Advisory|Flock Deconfliction Advisories]]** — the named, automated notifications Flock generates when a hot-list search by one organization overlaps another organization's alert-owner entry for the same plate ([[Flock Deconfliction Advisories and the LRPD Sharing Network]]). Each advisory enumerates the overlapping Alert Owners' contact details and states that "the sharing of information involving this LPR overlap is the responsibility of each individual Alert Owner," making the advisory itself a sharing-coordination instrument rather than a constraint (Emails 1-24.pdf p. 416, p. 540). - **Regional Arkansas network** — Advisories show LRPD's hot-list searches overlapping a cluster of in-state agencies: [[North Little Rock Police Department]], [[Sherwood Police Department]], Springdale, Morrilton, and Pine Bluff PDs, plus Arkansas State Police alert owners at `asp.arkansas.gov` (Emails 1-24.pdf pp. 17-64; Emails 36-63.pdf pp. 622-623, 634-635, 660-661). A January 2026 advisory captures cross-agency interplay in which the originating search was run by North Little Rock PD with overlap owners spanning LRPD and ASP (Emails 36-63.pdf pp. 634-635). - **Out-of-state and fusion-center reach** — Beyond active overlaps, the production records pending Search-access requests to LRPD's Flock network from ten-plus out-of-state agencies (e.g., TN ROCIC, Riverside County CA DA, Michigan Dept. of Attorney General) and from the Missouri Information Analysis Center, a state fusion center (Emails 1-24.pdf pp. 37-40; Emails 36-63.pdf p. 658). Hot-list alerts had auto-activated with Fulton County GA SO, St. Francois County MO, Boone County AR SO, and Van Buren AR PD; LRPD sought search-only access without the bundled hotlist/VMS feed (Emails 1-24.pdf p. 186, p. 260). ## Notes ### Vendor-stated current controls versus tenant evidence Flock's public statement distinguishes 1:1/radius/state sharing from **National Lookup**, which it describes as an opt-in network limited to a full, exact plate; it also says every search requires a reason and that searches are auditable (vendor primary/self-description, [Flock statement on network sharing and federal cooperation](../../web%20archive/2026-07-20/flocksafety.com/statement-network-sharing-use-cases-federal-cooperation.md)). Those controls are vendor representations, not proof of the configuration, identity path, or purpose entered in a particular tenant. That distinction matters because Arkansas Tier-1 records establish actual behavior: Conway's 1,384-organization topology and 5,929 federal queries, PCSO's externally authored hot-list alerts, and LRPD's deconfliction advisories. Those records control over a generic policy page when describing Arkansas agency conduct. Two reported incidents further show why tenant and access records are needed. The Associated Press reported that Flock paused federal pilot access following unauthorized-access concerns, and the San Francisco Chronicle reported that Mountain View disabled its cameras after reported unauthorized federal use (web research 2026-07-20, [AP report](../../web%20archive/2026-07-20/apnews.com/flock-federal-pilots-paused-2025-08-25.md); [San Francisco Chronicle report](../../web%20archive/2026-07-20/sfchronicle.com/mountain-view-flock-cameras-disabled-2026-02-03.md)). These are incident-specific secondary reports, not evidence every tenant permitted unauthorized access. - The vocabulary distinction matters: - **Network sharing** = peer access to another agency's *search index* (you can run queries that touch their reads). - **Hot list sharing** = peer subscription to another agency's *alerts* (their plates of interest cause your cameras to alert). - **Federal-prefix sharing** = a relationship configured under Flock's `[Federal]` org naming convention, exposed to federal-officer logins on a national scope. - The corpus does not surface any per-relationship MOU, warrant, or even agency-leadership notification email. The relationships are administrative toggles. - The single fact that **a configured relationship enables thousands of cross-jurisdictional queries per month** without any per-query process is the central policy-design finding of the investigation.