{
  "record": {
    "id": "a436d47f171393c3",
    "code": "PAI-A436D47F",
    "force": "5,000+ US law enforcement agencies",
    "country": "United States",
    "country_code": "us",
    "is_country": true,
    "region": "United States",
    "technology": "Flock Safety ALPR",
    "technology_slug": "flock-safety-alpr",
    "vendor": "Flock Safety",
    "vendor_slug": "flock-safety",
    "programme": "",
    "status": "operational",
    "stage": "in-use",
    "evidence": "ngo",
    "evidence_is_claim": false,
    "since": "2018",
    "legal_basis": "Varies by state; no dedicated federal ALPR statute",
    "oversight": "Fragmented. State-level audits in some cases (e.g. Illinois), but no single national body.",
    "notes": "Fragmented by design: thousands of individual agencies each contract with Flock separately, with far less national standardisation of retention or access than a single national system would have. Scale as of August 2026 is roughly 120,000 cameras across 49 states, with a company-cited reach of 6,000 to 7,000 law enforcement agencies; sources differ on the exact headcount and the figures move quickly.\n\nThat fragmentation is where the most serious documented problems have surfaced. An Illinois state audit found federal immigration authorities had gained access to state plate-read data through an undisclosed CBP arrangement, in apparent tension with state law, and 47 agencies were subsequently removed. A Dayton, Ohio audit in May 2026 found camera data searched more than 7,100 times for immigration enforcement in breach of city policy; the city covered all 72 cameras with bin bags pending contract exit. In San Francisco, 299 improper queries were made over about a year by a regional intelligence centre. The University of Washington Center for Human Rights documented federal access to Washington state networks through front-door, back-door and side-door routes. The Electronic Frontier Foundation reported over eighty agencies entering search justifications using language perpetuating stereotypes about Romani people.\n\nIndividual officer misuse is now documented repeatedly: a Washington Post investigation found dozens of officers using the network to surveil former partners and romantic interests, and separate 2026 cases include a Georgia officer arrested in August, an Arizona officer who resigned after allegedly tracking his wife, and a North Carolina officer charged over 31 searches of her boyfriend's ex-wife's vehicle.\n\nVendor response, 13 August 2026: default retention cut from 30 days to 7; the previously optional abnormal-search monitoring tool made universal, having been enabled by only about a third of customers; automatic lockouts for suspicious search patterns; case numbers required for extended retention. Flock had earlier removed federal agencies from its national search network (August 2025) and required a NIBRS offence type on every search (December 2025).\n\nContraction is substantial but so is growth: around 53 cities had cancelled by late June 2026 and over 20 jurisdictions moved to drop Flock in July 2026 alone, while roughly 800 US cities approved new contracts during 2026. Ring cancelled a planned Flock integration in March 2026. Washington State's Driver Privacy Act (ESSB 6002), signed 30 March 2026 and effective immediately, imposes a 21-day retention cap, permitted-purpose limits, bans on immigration and reproductive-healthcare and protected-activity uses, collection bans near sensitive sites, mandatory registration with the Attorney General and annual audits.",
    "source": "Company statements; Illinois state audit findings, reported by State of Surveillance and the ACLU",
    "source_url": "https://stateofsurveillance.org/articles/surveillance/flock-safety-national-surveillance-database-how-it-works-2026/",
    "last_checked": "2026-08-26",
    "record_url": "https://www.policeainews.com/tracker/record/a436d47f171393c3"
  },
  "licence": "https://www.policeainews.com/data#licence"
}