# Federal LE Quiet Access through Vendor Platforms Federal law-enforcement agencies search the automatic-license-plate-reader data of the Conway, Arkansas police department — a municipal force of roughly 138 sworn officers — thousands of times a month. The public knows this because one Arkansas citizen filed a records request and Conway PD produced a spreadsheet. There is no other disclosure channel. No warrant appears in the loop, no memorandum of understanding is surfaced, and Conway receives no notice at the time any federal search is run. The access is mediated entirely by the vendor's platform: federal agencies are enrolled under Flock Safety's "[Federal]" organizational convention, and once a sharing relationship is configured, federal officers query continuously. This page calls the access "quiet" — not because it is concealed, but because nothing in the system's design surfaces it. It is visible only afterward, only in aggregate, and only on request. **The number.** The [[Federal Searches CSV]] is a Flock platform export of every federal-agency lookup that touched Conway PD's data over a 51-day window, March 1 to April 21, 2026. It contains **5,929 search events** — an average of about 116 federal lookups per day involving one mid-sized Arkansas city's plate-reader data. The searching agency is named in plain text in each row, and the distribution is concentrated. The **US Postal Inspection Service** ran 3,502 of the searches (59 percent). The **Federal Bureau of Investigation** ran 2,385 (40 percent). The **National Park Service**, through its Natchez Trace Parkway unit, ran the remaining 42. The figure is not an estimate or a projection; it is a row count from a vendor-generated record in the agency's own production. **The mechanism: a configured relationship, not a warrant.** The [[Federal LE Data-Sharing Pipeline]] concept page sets out how the access works. A federal agency is onboarded to Flock under the platform's "[Federal]" org-name prefix. Flock's admin interface lets agencies on either side toggle a sharing relationship. Once that relationship exists, every plate read by a Conway camera becomes searchable by the federal agency's authorized users — with no per-query approval from Conway, no notice to Conway, and no judicial process specific to the search. The 5,929 lookups are not 5,929 decisions Conway made or saw. They are the downstream consequence of a relationship configuration. The gate that warrant or subpoena process historically placed between one jurisdiction's records and another agency's access is, in this model, replaced by a setting. This is the federal case of the broader posture set out in [[Surveillance Data Sharing — Default-On Posture]]. **What the reason codes record.** Each row of the [[Federal Searches CSV]] carries a "Reason" field. The FBI's 2,385 searches are, uniformly, logged as "Other - Not Applicable" — the agency entered no case-type predicate at all. The Postal Inspection Service's searches carry the reason "Financial Crime (Embezzlement/Fraud) - Inspections." Two observations follow, and both are narrow. First, the reason field is recorded but not gating: it is an annotation, not a checkpoint that must be satisfied before the search runs. Second, the reasons do not, on their face, explain the scale or the scope. A financial-crime inspection predicate does not obviously require continuous access to a nationwide camera network, and "Other - Not Applicable" explains nothing at all. The corpus does not establish that any individual search was improper — the searching officers and the queried plates are redacted, so the records cannot be assessed at that resolution — but it does establish that the reason field is a label, not a limit. **The reach.** A federal officer querying through this platform is not searching Conway. The [[Federal Searches CSV]] records, for each lookup, how many distinct Flock networks the query swept; the observed values run from roughly 1,076 to 2,690 networks per search. Conway PD's data appears in the export not because Conway was the target of these 5,929 searches but because Conway is one of the thousand-plus networks each federal query swept. The [[SharedNetworks 2025-12-17 Snapshot]] is the other half of the picture: it shows Conway itself sharing with 1,384 organizations. The structure is a mesh, and a federal login positioned in it reaches continentally. The 5,929 lookups are simply the portion of that continental reach that happened, in 51 days, to pass through one Arkansas city's records. **Quiet by design — and getting quieter.** The federal access surfaces through exactly one mechanism: a public-records request, answered after the fact, in aggregate. There is no proactive disclosure — no report to the Conway City Council, no public dashboard, no notice to the residents whose plates were among those searchable. And the records window itself is narrowing. In December 2025 Flock changed its audit system, stripping officer names, specific plates, and vehicle-fingerprint data from the inter-agency "Network Audit Logs," and telling customers the change would stop "those abusing our transparency" ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]]). Those stripped fields are precisely the ones that let a records requester reconstruct who searched what. When Flock later launched an analytics tool over the audit data, it warned customers to evaluate how the aggregated view would be treated under public-records law before enabling it. The one channel by which federal access becomes visible is the audit record released on FOIA — and the vendor, across the corpus, is narrowing what that record reveals. **What is absent.** Several federal agencies named in the original records request do not appear in the [[Federal Searches CSV]]: Immigration and Customs Enforcement, the Department of Homeland Security and Customs and Border Protection, the Drug Enforcement Administration, the Bureau of Alcohol, Tobacco, Firearms and Explosives, and the US Marshals Service are all absent from the March–April 2026 window. Absence in this record is information, but it is not proof of non-access. The export covers 51 days; a different window could differ. It captures logins enrolled under the "[Federal]" prefix; a federal officer operating on a task-force account under a state or local agency's credentials would not appear in the federal bucket at all. And the [[SharedNetworks 2025-12-17 Snapshot]] offers a concrete caution: it lists a federal entity — Wright-Patterson Air Force Base in Ohio — as a configured sharing relationship that shows no activity in the Federal Searches window. A relationship can exist, dormant, and not appear in an activity export. Configured is not the same as used; but configured means available. **The platform as the control point.** The corpus's second jurisdiction shows the same structural fact from the opposite side. The Fayetteville Police Department ran its ALPR program as a vendor trial, and when the trial ended the agency "lost access to all administration, data, hotlists, and logs" — the operational record of a government surveillance program remained on the vendor's platform, beyond the agency's reach ([[Vendor-Controlled ALPR Trial Data]]). In Conway, the vendor platform is what lets federal agencies into a local department's data; in Fayetteville, the vendor platform is what locked a local department out of its own. The common element is the locus of control. The data, the relationships, the activity records, and the exports all live inside a private company's product. Federal access to local surveillance data, and local access to it, are both — in the corpus — functions the vendor administers. **What this is, and is not.** Inter-agency and federal-local law-enforcement data sharing is lawful, and ALPR data sharing through commercial platforms is, at present, sparsely regulated rather than prohibited. This page alleges no illegality and characterizes no individual federal query as wrongful; the redactions in the record would not support such a claim, and none is made. The finding is about visibility and process. A continental-scale federal capability to query a local agency's surveillance data has been established by configuration rather than by warrant; it operates without notice and at a volume — 5,929 searches in 51 days against one city — that the local agency does not see in real time; and it becomes publicly knowable only through a records request, into an audit record the vendor is actively narrowing. Whether federal access to local ALPR data should require process, generate notice, or be disclosed proactively is a question for legislatures and for the public. The record establishes that, for Conway, it currently requires none of the three. ## Evidence - **The volume.** [[Federal Searches CSV]] — 5,929 federal-agency lookups touching Conway PD data over 51 days (2026-03-01 to 2026-04-21); USPIS 3,502 (59%), FBI 2,385 (40%), Natchez Trace Parkway NPS 42 (<1%). - **The mechanism.** Federal agencies enrolled under Flock's "[Federal]" org prefix; sharing established by an admin-interface toggle; no per-query Conway approval, notice, or warrant ([[Federal LE Data-Sharing Pipeline]]). - **The reason codes.** FBI searches uniformly logged "Other - Not Applicable"; USPIS searches "Financial Crime (Embezzlement/Fraud) - Inspections" — recorded, not gating ([[Federal Searches CSV]]). - **The reach.** Each federal query swept roughly 1,076–2,690 Flock networks; Conway is one network within continental-scale queries ([[Federal Searches CSV]], [[SharedNetworks 2025-12-17 Snapshot]]). - **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)]]). - **A configured-but-dormant relationship.** [[SharedNetworks 2025-12-17 Snapshot]] lists Wright-Patterson Air Force Base as a federal sharing relationship with no activity in the Federal Searches window. - **The platform as control point.** At Fayetteville, the agency lost access to its own ALPR trial data when the vendor trial ended ([[Vendor-Controlled ALPR Trial Data]]). ## Caveats - The [[Federal Searches CSV]] is a single 51-day window. It does not establish federal-access levels before or after, and it cannot show a trend. - The absence of ICE, DHS/CBP, DEA, ATF, and the US Marshals from this window is not evidence of non-access; a different window, or a federal officer using a non-"[Federal]"-prefixed login, would not appear in this export. - 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 does federal access to Conway's data look like outside the March–April 2026 window — and would a full-deployment-life export show 5,929 as typical, high, or low? - Do ICE, DHS/CBP, DEA, ATF, or the US Marshals access Conway-area ALPR data through non-"[Federal]"-prefixed logins or task-force credentials this export would not capture? - Is there any Arkansas statute, or any Conway policy, that requires process or notice for federal queries against municipal ALPR data? - Do the other filed jurisdictions — Arkansas State Police, Little Rock PD, Pulaski County SO — have equivalent Federal Searches exports, and do they show the same agencies at similar scale?