# Private-Business Camera Sharing into LE Networks The pattern by which **private commercial entities (retailers, banks, HOAs, hospital systems, school districts)** that own Flock cameras share search and alert access to their cameras with municipal/county/federal LE agencies. The arrangement operates entirely through the Flock platform: no MOU, no warrant, no per-share legislative oversight, no public disclosure. The Conway production documents one concrete example — The Home Depot's spring 2026 state-wide rollout — and the broader topology (the [[SharedNetworks 2025-12-17 Snapshot]] lists private entities among its 1,384 organizations). ## How it appears in the corpus **The Home Depot rollout (spring 2026):** - 2026-03-12 — Flock Onboarding Specialist Danica Pierce emails Chief Harris (cc Burningham) announcing a "process, in coordination with The Home Depot (THD), to provide agencies with state access to THD cameras for both search and hotlist capabilities as a part of their rollout." - Six Conway-area Home Depots' camera shares completed 2026-03-12 → 2026-04-08: stores #1401, #1402, #1405, #1407, #1412, #8919. - THD's template language to LE recipients: "The Home Depot would like to provide your agency with state-wide access to The Home Depot owned Flock safety systems … should only be used for bona fide investigations, which are documented within your department and via audit trail within the Flock Safety platform. … The Home Depot reserves the right to terminate the department's access to The Home Depot owned Flock safety systems." **Topology context (SharedNetworks 2025-12-17):** - Conway PD's sharing list of 1,384 organizations includes private entities; not all 1,384 are LE. Examples in the visible sample include school-district PDs (Galena Park ISD TX PD), but private-business names like "Home Depot - #NNNN" appear in inbound-only relationships as well (the Conway-targeted store-share notifications confirm at least six). - The 12/17/2025 snapshot predates the spring 2026 THD rollout, so the snapshot understates current private-business sharing. ### In PDFOI-2026-1874 (LRPD Flock emails) The Little Rock Police Department production corroborates that the Home Depot share is not a single-agency arrangement but a corporate state-wide rollout reaching multiple Arkansas agencies. The **same six Arkansas Home Depot store numbers documented at Conway — stores #1401, #1402, #1405, #1407, #1412, and #8919 — each shared their private Flock Safety cameras into LRPD's searchable network in February 2026**, granting LRPD the ability to search footage from those private-business cameras ([[Home Depot Camera Sharing into LRPD]], Emails 36-63.pdf p. 591-614; share-notification emails dated 2026-02-05). The notification template is identical to the Conway language: "Great News! Home Depot - #1401 (AR) has just shared their cameras with Little Rock AR PD, granting you and your organization the ability to search footage from their Flock Safety cameras" ([[Home Depot Camera Sharing into LRPD]], Emails 36-63.pdf p. 591). The recurrence of the identical store roster across two unrelated Arkansas agencies confirms a single corporate (The Home Depot) state-wide camera-sharing program executed through the Flock platform rather than ad hoc local agreements (see [[2026-02 Home Depot Shares Cameras with Little Rock PD]]). The LRPD emails also show the share is administered agency-side via Flock's "Organization Management" > "Roles" > "Networks" controls, i.e. role-based access to the inbound private network. ### In the Benton County SO SharedNetworks export The 2026-07-22 BCSO export adds private/community-labeled topology evidence without establishing registrant identity or physical camera location. `Rogers AR - Creekwood HOA` appears as an inbound-only relationship, and the Jonesboro row carries the compound inbound label `Bridger Place (AR)` alongside Jonesboro PD networks ([[SharedNetworks 2026-07-22 Snapshot]], `SharedNetworks_2026_July_22.csv`, lines 417 and 278). These labels support the existence of private/community-named network relationships; they do not by themselves prove ownership, live access, camera count, or what BCSO could view at a particular moment. ## Stakeholders - **Private-camera owner** (THD, retailers, banks, HOAs) — initiates the share. Motivation: outsourcing loss-prevention investigation to LE; LE pressure to obtain access; vendor sales pressure. - **LE agency** — receives access; gains a non-public-records camera footprint. - **Vendor (Flock)** — runs the platform; mediates the rollout; collects the data revenue from both sides. - **The public** — surveillance subjects who pass through private property on which Flock cameras operate. No notice; no opt-out; no FOIA pathway against the private camera-owner directly (FOIA doesn't apply to private companies). ## Notes - The pattern's **policy significance** is that it routes around the FOIA / open-records ecosystem. The cameras are privately owned, so the private owner is not subject to public-records law; the LE agency receives access through a Flock-platform toggle that produces no public-records-bearing paper trail; the resulting search activity is logged in audit logs that *are* public-records-bearing — but only insofar as the receiving agency cooperates with FOIA. The asymmetry favors opacity. - The **terms-of-use language** ("bona fide investigations … via audit trail") is the only ostensible accountability mechanism. The receiving agency's audit log is the only check on whether the cameras are being used as the template specifies. Whether agencies enforce that limit, and whether THD periodically audits it, are open questions. - The pattern is reproducible across vendors and product categories. Further work on this concept could pull in: - 404 Media coverage of Flock-private partnerships (Tier 3). - EFF Atlas of Surveillance — Flock camera deployments (Tier 3). - Any THD public statements on the program (Tier 2 / 3). - Comparable patterns in Ring (Amazon), Verkada, Axon, etc. (Tier 3). - For Conway specifically, the open question is whether the spring 2026 rollout triggered any City Council inquiry beyond the April 2026 information-security questions surfaced in [[Flock Cameras Apr 2026 City Council QA Thread]].