{"resourceId":"aclu-alpr-data-federal-hidta-aggregation-20261014","versions":[{"version":"external-3fc85d4d56285328beb428eebc46bec7c63f849c6d21d3802af737b8e108ab4b","resource":{"id":"aclu-alpr-data-federal-hidta-aggregation-20261014","title":"ACLU: local Flock, Axon and other ALPR data may be flowing to federal servers through HIDTA drug-task-force programs","organization":"American Civil Liberties Union","sector":"Policing / ALPR data sharing","geography":"United States","publishedAt":"Oct. 14, 2026","publicationDate":"2026-10-14","eventDate":null,"sourceName":"American Civil Liberties Union","sourceLabel":"ACLU: local Flock, Axon and other ALPR data may be flowing to federal servers th","sourceUrl":"https://www.aclu.org/news/privacy-technology/federal-alpr-database","evidenceClass":"independent-research","outcomeClass":"cautionary","topics":["data-security","governance-procurement"],"finding":"The ACLU, citing documents reported by 404 Media and the creator of HaveIBeenFlocked, says the High Intensity Drug Trafficking Area program, run under the White House drug policy office with 33 regional programs covering all 50 states, aggregates local Flock, Axon and other ALPR data on federal servers accessible to other agencies. Georgia cities must sign an MOU to send data to a HIDTA before placing ALPRs on state rights of way. The DEA has argued HIDTA records are not subject to open records laws. It is unclear how many jurisdictions contribute.","sledRelevance":"Adds a sharing channel that local data-sharing policies and state immigration-sharing limits may not cover, so councils and agencies need to ask whether their ALPR data feeds a HIDTA and under what agreement.","evidence":"Opened original source from American Civil Liberties Union and drew findings from its text. Advocacy commentary relying on secondary reporting and documents that were not opened here; it gives no count of contributing agencies, data volumes or specific misuse cases. The ACLU's recommended remedy is ending ALPR use.","architectureImplications":"Inventory vendor-side outbound integrations and bulk feeds alongside agency-configured sharing.","governanceImplications":"Interpretation: Build and maintain an ALPR data-flow register and present keep-or-stop decisions to leadership.","securityPrivacyImplications":"Log or disable outbound bulk feeds not covered by policy, and document legal basis for each remaining flow.","caveats":"Advocacy piece; underlying documents not inspected.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: the ACLU is giving residents a new question for councils: does our plate-reader data go to a federal drug program database? Agencies and councils that cannot answer will need a data-flow inventory. A bounded engagement is mapping every ALPR sharing path, including task-force agreements. The source cannot support claims about how many agencies participate or that any specific city's data has been misused.","engineering":"Engineering framing: if HIDTA feeds are configured at the vendor or task-force level, a department's own sharing screen may not show them. Pre-sales engineering should ask vendors for a complete list of outbound integrations, including bulk feeds, and confirm whether each can be disabled or logged. State laws limiting immigration-related sharing make this inventory a compliance check, not just a privacy one.","delivery":"Delivery framing: the practical task is a data-flow inventory covering vendor integrations, MOUs and task-force memberships, followed by decisions about which flows to keep. Delivery needs the agency's legal advisor and IT to work together because agreements and technical feeds may be held in different places. Results should be reportable to elected officials who will be asked this question publicly."},"roleDetails":{"sales":{"customerProblem":"Agencies and councils may not know whether their ALPR data is aggregated into federal HIDTA databases.","stakeholders":["Police chiefs and sheriffs","City or county councils","HIDTA task-force liaisons","Vendors such as Flock and Axon","State attorneys general enforcing sharing limits"],"discoveryQuestions":["Does the agency belong to a HIDTA or have an ALPR MOU?","What outbound feeds does the vendor run?","Can each feed be logged or disabled?","Do state sharing limits apply to HIDTA flows?"],"valueHypothesis":"A data-flow inventory could let agencies answer public questions and check compliance; it does not establish misuse.","potentialEngagement":"ALPR data-flow inventory covering vendor integrations, MOUs and task-force agreements.","unsupportedClaims":["A specific agency's data reached ICE","Number of contributing jurisdictions","HIDTA sharing is unlawful"]},"engineering":{"fit":"Agencies using commercial ALPR platforms that participate in regional task forces.","architectureIntegration":"Inventory vendor-side outbound integrations and bulk feeds alongside agency-configured sharing.","prerequisites":["Vendor integration list","Task-force agreements","Sharing configuration exports"],"constraints":["HIDTA records may be withheld from open records requests","Feeds may be set outside agency view","State laws vary"],"security":"Log or disable outbound bulk feeds not covered by policy, and document legal basis for each remaining flow.","proofOfValue":["Obtain written vendor list of all outbound feeds","Reconcile feeds with signed agreements","Verify a disabled feed stops sending data"]},"delivery":{"work":"Build and maintain an ALPR data-flow register and present keep-or-stop decisions to leadership.","dependencies":["Vendor cooperation","Legal review of MOUs","Task-force contacts"],"ownership":"Police department legal advisor with IT","skillsAdoption":"Command staff need a clear explanation of each flow to answer council and public questions.","governanceCheckpoints":["Inventory completion","Legal review","Council briefing","Annual re-inventory"],"acceptanceCriteria":["Proposed: every outbound ALPR flow listed with legal basis","Proposed: unapproved flows disabled and verified","Proposed: register published or briefed to council"],"risks":["Hidden vendor-side feeds","Conflict with state sharing laws","Loss of public trust","Task-force agreement disputes"]}},"retrievedAt":"2026-10-15T02:50:12Z","enrichedAt":"2026-10-15T02:55:11Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Command staff need a clear explanation of each flow to answer council and public questions.","procurementImplications":"Interpretation: ALPR data-flow inventory covering vendor integrations, MOUs and task-force agreements.","operatingModelImplications":"Operational owner: Police department legal advisor with IT.","sourceVerification":{"openedUrl":"https://www.aclu.org/news/privacy-technology/federal-alpr-database","referenceExcerpt":"Attempts to access HIDTA data via open records requests have been met with evasion","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}