# Federal LE Quiet Access through Vendor Platforms *Erratum, 2026-07-30: this page formerly treated every row as a search that touched Conway data and treated absent warrant, agreement, approval, and notice columns as proof that those processes did not exist. The CSV establishes federal-tagged search activity and the fields it carries. It does not name the networks searched, identify returned data, or establish every process outside the export.* Conway PD produced a Flock file named `Federal Searches March 2026 to April 2026.csv`. Its 5,929 rows run from March 14 through April 13, 2026 and identify a searching organization, a `Total Networks Searched` count, a reason label, timestamp, and search type. The file is important because it documents large-scale federal-tagged activity inside the vendor platform. It is also narrower than this page previously claimed: no column names Conway, enumerates the searched networks, or records which network returned a match. **The number.** The [[Federal Searches CSV]] contains **5,929 lookup rows** across 31 calendar dates. The **US Postal Inspection Service** accounts for 3,502 rows (59 percent), the **Federal Bureau of Investigation** for 2,385 (40 percent), and the National Park Service's Natchez Trace Parkway unit for 42. This is a full-file row count from `raw/conway-pd/PD-2026-354/Federal Searches March 2026 to April 2026.csv`, not an estimate. **The recorded reach.** `Total Networks Searched` ranges from 586 to 2,878. That field establishes that each logged query was broad. It does not list those networks or say which returned data. The separate [[SharedNetworks 2025-12-17 Snapshot]] documents a 1,384-row Conway relationship topology, including two federal-tagged organizations. The two files show platform topology and federal-tagged activity, but they lack a row-level join. They cannot establish that all 5,929 searches touched, viewed, or returned a Conway record. **What the reason codes record.** The FBI rows carry “Other - Not Applicable”; the Postal Inspection Service rows carry “Financial Crime (Embezzlement/Fraud) - Inspections.” Those labels are fields in completed rows. The export does not expose the interface's validation rules, the underlying case facts, or whether another predicate was documented elsewhere. **What the export does not show.** It has no per-row network-name, result, match, warrant, subpoena, MOU, approval, notice, or judicial-process field. That is a limitation of this file, not proof that no such record or process existed. The production reviewed for this synthesis also does not supply documentation joining a particular row to a Conway result. **Why “quiet” remains a useful but limited frame.** The activity became visible here through a public-records production, while the file itself leaves the participating networks and results opaque. Flock separately announced that Network Audit Logs would omit officer names, specific plates, and vehicle-fingerprint data and said the change would stop “those abusing our transparency” ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]], `Flock Safety Announces Improvements to Your Audit Logs.msg`, body). That is a records-visibility finding, not a conclusion about the legality of any query. **What this is, and is not.** The record supports a finding of federal-tagged Flock activity at scale and a finding that Conway produced the export. It does not support calling USPIS or the FBI a demonstrated consumer of Conway data in every row, characterizing an individual query as wrongful, or concluding that platform configuration replaced legal process. Those questions require network identities, results, access-path records, and governing documentation that the CSV does not contain. ## Evidence - **The volume and organization labels.** `Federal Searches March 2026 to April 2026.csv`, header plus full-file parse: 5,929 rows; USPIS 3,502, FBI 2,385, Natchez Trace Parkway NPS 42 ([[Federal Searches CSV]]). - **The available fields.** `ID, Name, Org Name, Total Networks Searched, License Plate, Reason, Case #, Filters, Search Time, Search Type`; no network-name or result column appears in the header. - **The reach.** The same file's `Total Networks Searched` values span 586–2,878. [[SharedNetworks 2025-12-17 Snapshot]] separately records Conway's relationship topology; the files do not contain a row-level join. - **The narrowing records window.** Flock's December 2025 removal of officer names, plates, and vehicle-fingerprint data from Network Audit Logs, and its FOIA-exposure warning on the Audit Assistance tool ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]]). ## Caveats - The [[Federal Searches CSV]] is a single 31-calendar-date window. It cannot show a trend or a row's relationship to Conway data. - Flock's current public statement describes National Lookup as opt-in, exact-full-plate only, reason-required, and audited; it also describes agency-controlled sharing choices (vendor primary/self-description, [Flock network-sharing statement](../../web%20archive/2026-07-20/flocksafety.com/statement-network-sharing-use-cases-federal-cooperation.md)). The Conway export does not identify every access path or prove whether each event was National Lookup, another sharing mode, or a delegated identity. Actual tenant configuration and identity records are needed. - Separate national reporting describes federal-pilot and unauthorized-access disputes that led Flock or local agencies to pause access elsewhere (web research 2026-07-20, [Associated Press 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)). Those accounts supply context only; they do not establish Conway's configuration or the route behind any row in this export. - ICE, DHS/CBP, DEA, ATF, and the US Marshals do not appear in this window. Their absence is not evidence of non-access outside it or under a differently classified login. - The searching officers and the queried plates are redacted in the record. This page therefore makes no claim about any individual search; it addresses volume, mechanism, and visibility only. - The corpus does not surface what prompted Flock to generate this export, or whether equivalent exports exist for other periods or other Arkansas agencies. - This page is the author's analytical synthesis, demarcated as such per the wiki's editorial posture. Every factual claim above is anchored to a source page and, through it, to a raw FOIA document. ## Open questions - What report filter produced this file, and what makes a search eligible for inclusion? - Which named networks were searched or returned results in each row? - What does the federal-search export look like outside the March–April 2026 window? - What authorization, access-path, or identity records can be joined to a particular search?