Documented Incident

Data SharingPrivacyPolice MisusePublic Opposition

D.C. police decline to disclose who searched their Flock license-plate data or why

NOTUS reports that the Metropolitan Police Department operates 67 Flock automated license-plate readers that scan roughly 400,000 tags per day and retain data for up to three months, but has not disclosed who has queried that data or for what purposes. MPD denied a NOTUS records request for the information and, according to the outlet, has left a January request for Flock audit logs unanswered beyond the 15-business-day window set by D.C. open records law. Interim Chief Jeffery Carroll ended MPD's participation in Flock's National Lookup Tool in January, and outside agencies must now sign a memorandum of agreement to obtain D.C. data. An MPD spokesperson declined to answer whether the District's Flock data had ever been used by federal immigration enforcement.

Why this matters

Audit logs are the primary mechanism by which residents and legislators can verify that ALPR data is used only for stated purposes, so a jurisdiction's willingness to release them shapes what oversight is possible. D.C.'s situation also illustrates how data-sharing defaults can expose one city's records to agencies operating under different legal constraints.

Key facts

Sources

This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.

About this record

BlockFlockNow documents reported incidents involving Flock Safety cameras and automated license plate readers: council votes, contract decisions, misuse by authorized users, lawsuits, audits, and community response. Every record is reviewed by a person before publication. New to the topic? Start with What is Flock?, find meetings near you, or learn how to request your town's camera records.

Updated August 31, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.