# Federal Data-Sharing Controls and Federal-Access Posture This page collects what the PDFOI-2026-1874 production states about the federal-access dimension of [[Little Rock Police Department]]'s Flock deployment: the federal data-sharing controls [[Flock Safety, Inc.]] rolled out in late 2025 and early 2026, the public denials Flock issued about federal-agency access, and the disclaimers and litigation Flock surfaced touching immigration and reproductive-care enforcement. It also records a documentary absence: the production contains none of the Flock "Federal Searches" CSV or "SharedNetworks" CSV artifacts named in the underlying FOIA request, so it does not establish how LRPD has its own federal-access toggle set. The only direct federal-agency touchpoint in the production is a private citizen who copied the FBI on his own complaint to LRPD. ## What's inside The federal-access material in this production is almost entirely Flock vendor communications swept into the production rather than LRPD policy records. Three strands appear: 1. Flock newsletter announcements (Feb-Mar 2026) describing a new "Agency-Level Control for Federal Data Sharing" and a year-end "Federal Opt-In capability." 2. Flock vendor messaging and a forwarded trade-press article (Fortune) addressing whether federal agencies, including ICE, access the Flock platform; a CJIS login disclaimer referencing immigration and reproductive-care laws; and the California episode in which Flock's architecture allowed out-of-state searching of California data. 3. The absence of the two federal/sharing data exports the FOIA request specifically named, plus a single citizen-initiated FBI cc. ## Key takeaways ### A new agency-level federal-sharing control, and a year-end "Federal Opt-In" A Flock newsletter reproduced in the production announces an agency-level toggle governing whether an agency receives federal partners' data-sharing requests. The verbatim text (Emails 25-35.pdf p. 565, "Agency-Level Control for Federal Data Sharing ... Agencies can now decide, at the agency level, whether they receive data-sharing requests from federal partners.") The same announcement appears again later in the production (Emails 36-63.pdf p. 283, "Agencies can now decide, at the agency level, whether they receive data-sharing requests from federal partners."). A separate Flock message frames a further control as still forthcoming at year-end (Emails 25-35.pdf p. 656, "Before year-end, we will also be releasing a Federal Opt-In capability, giving agencies additional control and flexibility when working with federal partners."). The record states only that Flock announced these controls; it does not state how LRPD configured them. That an "Opt-In capability" is described as a future release implies the prior posture was not opt-in, but the production does not contain LRPD's own setting, so this remains a question the record raises rather than answers. ### Flock's own framing favors cross-jurisdictional and multi-state sharing In the same period, Flock promoted cross-jurisdictional sharing as a feature using a high-profile investigation (Emails 25-35.pdf p. 655, "the Brown / MIT shooter investigation was aided by Flock as Rhode Island and New Hampshire seamlessly shared data across a multi-state network, demonstrating exactly why secure, cross-jurisdictional sharing matters"). This is Flock's characterization, not an LRPD statement. ### Vendor denials about federal-agency access The production preserves Flock's public denials that federal agencies use or contract for the platform. A forwarded Fortune article in LRPD's files records Flock's denial of federal-agency contracts (Emails 36-63.pdf p. 407, "We do not have any contracts with any of them, which means they cannot directly access data on the platform."). Per the digest of this production, a Flock newsletter also relayed a local-official statement on the ICE question (Emails 25-35.pdf p. 523, "East Palo Alto Vice Mayor Mark Dinan recently shared how Flock is used in his community, including confirming ICE does not use Flock for immigration enforcement."). Both statements are attributable to Flock (or to officials whom Flock quoted); neither is corroborated by any LRPD record in this production. ### A CJIS disclaimer and a California episode complicate the denials The same vendor communications acknowledge that ALPR use intersects immigration and reproductive-care enforcement. Per the digest of this production, a Flock newsletter notes a CJIS login disclaimer (Emails 36-63.pdf p. 521, "A new login disclaimer reinforces CJIS compliance and clearly outlines authorized use requirements, including immigration and reproductive care laws in certain states."). The forwarded Fortune article documents that Flock's architecture had, before remediation, allowed agencies outside California to search California agencies' data (Emails 36-63.pdf p. 406, "two state bills 'that unintentionally allowed law enforcement agencies outside of California to search data from agencies across the country, including Santa Cruz.'"). The same article records Flock's described remediation, including "deactivating the National Search Tool for California agencies, revoking the ability for California agencies to create one-on-one data-sharing relationships with agencies outside of California, and adding filters to block searches related to ICE, Border Patrol, immigration, or similar terms" (Emails 36-63.pdf p. 406). The two state bills are identified in the article as SB34 and SB54 (Emails 36-63.pdf p. 406, "The bills, SB34 and SB54, relate to the security and privacy procedures of automatic license plate reader operators in the state"). ### What this production does NOT contain The FOIA request driving this production specifically named two platform exports relevant to federal access and network sharing (Emails 36-63.pdf p. 1475, "any 'Federal Searches' CSV exports (the Flock platform export listing searches by [Federal]-prefixed agencies); any SharedNetworks CSV snapshots (the platform export listing LRPD's data-sharing relationships with other Flock-customer organizations)"). Neither export appears anywhere in this production. There is therefore no quantitative federal-lookup record here comparable to artifacts produced by other Arkansas agencies, and no platform-generated inventory of LRPD's sharing relationships. The absence is the finding: the record does not establish whether federal-prefixed searches of LRPD's network occurred, or how LRPD's federal-sharing control is set. See [[T004 - Item-3 No-Records vs Deconfliction Audit Trail]]. ### The only direct federal touchpoint is citizen-initiated The sole appearance of a federal law-enforcement agency as an actual correspondent in this production is a private citizen copying the FBI on his own complaint to LRPD, not any LRPD-to-FBI data exchange. The complainant cc'd a Little Rock FBI address on a March 2025 FOIA/complaint email. This is a citizen drawing in federal LE, not an LRPD federal data-sharing channel, and the underlying complaint document carries significant reliability problems addressed elsewhere (the names and substance of any private individuals in that complaint are not reproduced here). It does not bear on the platform-level federal-access question. ## People and orgs mentioned - [[Flock Safety, Inc.]] — vendor; source of the federal-sharing control announcements, the federal-contract denial, and the CJIS/California disclosures. - [[Little Rock Police Department]] — the Flock customer agency; the production contains no LRPD record stating its federal-sharing configuration. - [[Federal Bureau of Investigation]] — appears only as a cc recipient on a citizen's own complaint email, not as an LRPD correspondent or data partner. - [[Garrett Langley]] — Flock CEO, signatory/author of Flock command-level communications in this production (federal-sharing and legal-momentum messaging). - Mark Dinan — East Palo Alto, CA Vice Mayor, quoted by Flock on the ICE question (named per Flock's newsletter; a non-Arkansas elected official). ## Concepts invoked - [[Federal LE Data-Sharing Pipeline]] — the central concept; the production documents the vendor controls and denials but not LRPD's actual federal-access posture. - [[Surveillance Data Sharing — Default-On Posture]] — the "Federal Opt-In capability" framing and the California out-of-state-search episode both speak to whether sharing was on by default before remediation. - [[CJIS Compliance]] — invoked by the Flock login disclaimer referencing authorized use including immigration and reproductive-care laws. - [[ALPR-Favorable Case Law as Vendor Messaging]] — adjacent vendor legal messaging surfaced in the same newsletters. ## Events documented - Flock's Feb 2026 announcement of "Agency-Level Control for Federal Data Sharing" (Emails 25-35.pdf p. 565; Emails 36-63.pdf p. 283). - Flock's announcement of a forthcoming year-end "Federal Opt-In capability" (Emails 25-35.pdf p. 656). - Flock's described remediation of the California (Santa Cruz / SB34-SB54) out-of-state-search episode, with violations stated to have stopped Feb. 11 (Emails 36-63.pdf p. 406). ## Cross-references - [[Flock Audit and Compliance Controls and Gaps]] — the audit-redaction and out-of-state-search-filter features announced alongside these federal controls. - [[Flock Deconfliction Advisories and the LRPD Sharing Network]] — the cross-agency sharing actually documented in the production (state and regional, not federal). - [[LRPD FOIA Handling and Disclosure Posture]] — context for the no-records dispositions and withheld categories. - [[Federal Data-Sharing Controls and Federal-Access Posture]] is the federal counterpart to those network and audit pages. - Tension: [[T004 - Item-3 No-Records vs Deconfliction Audit Trail]]. ## Open questions / follow-ups - How is LRPD's "Agency-Level Control for Federal Data Sharing" toggle set, and was a "Federal Opt-In" ever enabled? The production does not say. A targeted follow-up for the configuration record and any "Federal Searches" CSV is warranted. - The named "Federal Searches" CSV and "SharedNetworks" CSV were requested but are absent from this production. Whether they were withheld, not located, or not generated is not stated in the record reviewed here. - Flock's denial of federal-agency contracts ("they cannot directly access data on the platform") is a vendor statement; it does not address whether federal agencies receive LRPD data indirectly via partner agencies on shared networks. Nothing in this production resolves that. - The East Palo Alto/ICE statement and the CJIS immigration/reproductive-care disclaimer were verified against the production digest's quote index (pages 523 and 521) but not re-read in the two analysis chunks opened for this page; confirm the verbatim text against the source PDF before relying on them in synthesis.