Flock operates a single national network of automated license plate readers whose scale is measured in the hundreds of thousands of cameras and tens of billions of vehicle scans per month, and it is growing fast enough that any published count is stale within months.
Well supported
The case against thisThe headline scan and camera counts originate with Flock's own marketing and are repeated by outlets without independent measurement (techspot-2026-20-billion-scans). The direction and order of magnitude are well corroborated; any single number is not.
4 sources
TechSpot · 2026-08-01 · Secondary · national
Reports Flock operating more than 120,000 cameras in roughly 6,000 communities across 49 states, processing about 20 billion vehicle scans monthly, against growing municipal pushback.
- More than 120,000 cameras across roughly 6,000 communities in 49 states, as of mid-2026.
- About 20 billion vehicle scans per month.
The 20 billion figure originates with Flock and is repeated by outlets; it is a vendor-claim carried in secondary reporting, not an independent measurement. Growth is fast enough that any count is stale within months - February 2026 reporting said 72,000 cameras.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
Wikipedia · 2026-08-01 · Secondary · national
Corporate timeline: founding, funding, product lines and a chronology of controversies.
- Founded 2017 by Garrett Langley, Paige Todd and Matt Feury; Langley is CEO.
- About 950 million dollars raised at a 7.5 billion dollar valuation as of 2025, including a 275 million dollar round in March 2025.
- Product lines: Falcon and Sparrow plate readers, Condor PTZ cameras, Raven gunshot detection (extended to human distress detection in October 2025), Nova data platform, and drones following the October 2024 Aerodome acquisition.
- Company-stated scale: over 5,000 communities in 49 states, 20 billion vehicle scans monthly.
- August 2024: Mother Jones reported 13 or more agencies spent 920,000 dollars of opioid settlement funds on Flock cameras.
- 2021: IPVM reported a 10 percent error rate and Flock halted sales to IPVM.
- Roanoke: 30 of 41 gunshot detectors installed in locations that were never approved.
- Verona, Wisconsin: cameras stayed operational three months after the contract was rejected; Cleveland cameras stayed active after expiration.
- Oshkosh, Wisconsin rescinded its contract in August 2026 citing false statements.
Wikipedia is a finding aid, not a citation. Every item above must be traced to its underlying source before it appears in the dossier; the operational scale figures are Flock's own marketing claims.
The Daily Yonder · 2026-08-05 · Secondary · national
Examines Flock adoption by rural and small-town agencies, where oversight capacity is thinnest.
- Rural and small agencies are a significant and growing share of Flock's deployment base.
Relevant to the New Mexico chapter, where many participating agencies are small departments without dedicated legal or audit staff. Specific figures need to be read from the article before citing.
The constitutionally distinctive feature is not the photograph but the retroactive search: every vehicle is recorded regardless of suspicion, and any participating agency can later query where a given plate has been.
Well supported1 of 5 sources not read at source
The case against thisVehicles on public roads are in plain view and a single plate photograph implicates no reasonable expectation of privacy - the position Norfolk successfully argued at the district court (whro-2026-norfolk-ruling).
5 sources
Electronic Frontier Foundation · 2021-04-22 · Primary · CA
A public-records dataset covering 89 California agencies, and the single most useful statistic in this entire corpus: essentially none of what ALPRs collect relates to any investigation at the time it is collected.
- 99.9 percent of the surveillance data collected was not actively related to an investigation at the time of collection.
- In 2019 alone, 82 agencies collected more than 1 billion license plate scans.
- The dataset covers 89 agencies statewide; only 63 provided comprehensive separated data for both 2018 and 2019.
- Released April 2021 as a public records collection and dataset, downloadable and CC-BY licensed.
THE NUMBER TO LEAD WITH. The dragnet argument does not depend on misuse at all - it rests on this: the system is built to collect on everyone and the overwhelming majority of what it holds was never connected to any investigation. That is the structural definition of a general warrant, stated as a measured proportion rather than an adjective. NOT READ at source; the 99.9 percent figure comes from search summaries of EFF's own writeup and MUST be confirmed against the report and dataset before it is used publicly - it is exactly the kind of number that gets quoted back. Data is from 2018-2019 and predates the current network.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
Electronic Frontier Foundation · 2025-10-01 · Primary · TX
Court documents contradict Flock's and the Johnson County, Texas sheriff's public characterization of a nationwide plate search as a missing-person welfare check. The records describe a death investigation of a non-viable fetus after a self-managed abortion.
- Search reason recorded in the audit log: had an abortion, search for female.
- Two searches: one across 17,684 cameras on 1,295 networks, a second across 83,345 cameras on 6,809 networks.
- Searches ran about 2.5 hours after the initial call, roughly two weeks after the abortion.
- Flock publicly called critical coverage misleading, false and clickbait, and said she was searched for as a missing person, not a suspect.
- The lead detective's affidavit shows investigators consulted prosecutors about charges and collected abortion documentation; no charges were filed.
This is the anchor case for the vendor-credibility problem: the company's public account and the sworn record diverge. The dossier should present both and let the documents decide.
Massachusetts Supreme Judicial Court · 2020-04-16 · Primary · MA
The first appellate decision applying the Fourth Amendment to ALPRs. The court adopted the mosaic approach: four cameras on two bridges did not invade a reasonable expectation of privacy, but enough readers in enough places would.
- Police used ALPRs on the Bourne and Sagamore bridges to track the defendant's crossings over three months.
- Held: a person has a constitutionally protected expectation of privacy in the whole of his public movements.
- Held: the limited extent of this ALPR use did not invade that interest, but historical data from enough readers in enough locations would constitute a search.
McCarthy is the case both sides cite. It sets a threshold rather than a rule, which is exactly why camera density and retention are the facts that decide these cases.
Supreme Court of the United States · 2018-06-22 · Primary · national
Held that acquiring historical cell-site location information is a Fourth Amendment search requiring a warrant, and that the third-party doctrine does not extend to comprehensive location records.
- Seven days or more of historical cell-site location information is a search requiring a warrant.
- Roberts drew on the aggregation reasoning of the Alito and Sotomayor concurrences in United States v. Jones (2012).
- The opinion grounds the analysis in the Founding-era reaction to general warrants and writs of assistance.
The general-warrant framing is the dossier's spine: the objection is not to any single photograph but to a standing power to rummage retroactively.
The network is queried at a volume incompatible with the individualized-suspicion model used to sell it: more than 12 million searches by over 3,900 agencies in an 11-month window, and nearly 4 million searches by California agencies alone in about a year.
Well supported
The case against thisVolume alone does not establish impropriety; a high search count is consistent with heavy use in ordinary investigations. The reason field, not the count, is what shows misuse.
1 source
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
A single search by one local officer can reach tens of thousands of cameras across thousands of networks nationwide, making a local procurement decision a national exposure.
Well supported
The case against thisFlock has demonstrated it can restrict national lookups by state (404-2025-flock-removes-states), so reach is a configurable policy setting rather than a fixed property of the system.
2 sources
Electronic Frontier Foundation · 2025-10-01 · Primary · TX
Court documents contradict Flock's and the Johnson County, Texas sheriff's public characterization of a nationwide plate search as a missing-person welfare check. The records describe a death investigation of a non-viable fetus after a self-managed abortion.
- Search reason recorded in the audit log: had an abortion, search for female.
- Two searches: one across 17,684 cameras on 1,295 networks, a second across 83,345 cameras on 6,809 networks.
- Searches ran about 2.5 hours after the initial call, roughly two weeks after the abortion.
- Flock publicly called critical coverage misleading, false and clickbait, and said she was searched for as a missing person, not a suspect.
- The lead detective's affidavit shows investigators consulted prosecutors about charges and collected abortion documentation; no charges were filed.
This is the anchor case for the vendor-credibility problem: the company's public account and the sworn record diverge. The dossier should present both and let the documents decide.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
Federal immigration enforcement obtained access to local ALPR data through local agencies rather than through any contract of its own, at scale and in multiple states: an Illinois regulator found it violated state law, Virginia's network logged nearly 3,000 immigration-related searches in twelve months, and Texas school district logs show civil immigration searches outnumbering criminal ones two to one.
Well supported1 of 5 sources not read at source
The case against thisFlock says it halted the CBP pilot and cut off federal access when directed, and states its leadership was unaware of the pilot (ilsos-2025-flock-audit, govtech-2025-illinois-pledge). Whether that is exculpatory or itself the problem is the contested question.
5 sources
Illinois Secretary of State · 2025-08-25 · Primary · IL
A state audit found Flock violated Illinois law by allowing U.S. Customs and Border Protection access to Illinois plate data. The Secretary of State ordered access cut off immediately.
- The audit sampled 12 local agencies and found Flock lacked proper data-sharing safeguards.
- Flock was running a CBP pilot program that, per the audit, its own leadership was unaware of.
- A 2023 Illinois law bars sharing plate data for out-of-state abortion or immigration investigations; the state also invoked the Illinois TRUST Act.
This is a government finding of law violation by a regulator with subpoena power, not an advocacy claim. It is among the strongest single sources in the corpus.
404 Media · 2025-06-01 · Primary · national
After the ICE and abortion reporting, Flock cut off national lookups into cameras located in Illinois, California and Virginia. The company's ability to make that change unilaterally is itself evidence about who controls the data.
- Flock blocked out-of-state agencies from searching cameras inside Illinois, California and Virginia.
- More than 4,000 lookups had been run at the behest of federal agencies for immigration purposes, giving federal law enforcement side-door access to a tool it had no formal contract for.
- The Danville network audit alone contained 307 immigration-related searches by Texas agencies, going back to June 2024.
Vendor-side switch-flipping cuts both ways as evidence: it shows the sharing was a policy choice, not a technical necessity.
404 Media · 2025-08-08 · Primary · national
Members of Congress opened a formal investigation into Flock, demanding records of all searches touching ICE, CBP and abortion. The letter cites 404 Media's reporting directly.
- Rep. Raja Krishnamoorthi and Rep. Robert Garcia demanded details of all ICE, CBP and abortion-related searches of the national network.
- The investigation followed reporting that local police ran lookups on behalf of ICE and that a Texas officer searched nationwide for a woman who self-managed an abortion.
Article is partly paywalled; the findings above are the portion verifiable from the accessible text. Corroborated by the Wyden/Krishnamoorthi FTC letter of November 2025.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
Virginia Center for Investigative Journalism at WHRO · 2025-09-24 · Primary · VA
Analysis of Virginia's Flock network audit data finding thousands of immigration-related searches in a twelve-month window.
- Nearly 3,000 immigration-related searches on Virginia's Flock Safety network over a twelve-month period.
NOT READ in full. A second state-level quantification of immigration searches, independent of the Illinois audit and the Texas school district logs - which is what makes the pattern a pattern rather than an anecdote.
A Texas sheriff's office searched the national network for a woman in connection with a self-managed abortion, and the public account given by the agency and by Flock is contradicted by the court record.
Well supported
The case against thisFlock maintains the search was a missing-person welfare check and called contrary coverage false and clickbait (eff-2025-johnson-county-abortion). The affidavit describing a death investigation is the reason the dossier does not adopt that characterization.
3 sources
Electronic Frontier Foundation · 2025-10-01 · Primary · TX
Court documents contradict Flock's and the Johnson County, Texas sheriff's public characterization of a nationwide plate search as a missing-person welfare check. The records describe a death investigation of a non-viable fetus after a self-managed abortion.
- Search reason recorded in the audit log: had an abortion, search for female.
- Two searches: one across 17,684 cameras on 1,295 networks, a second across 83,345 cameras on 6,809 networks.
- Searches ran about 2.5 hours after the initial call, roughly two weeks after the abortion.
- Flock publicly called critical coverage misleading, false and clickbait, and said she was searched for as a missing person, not a suspect.
- The lead detective's affidavit shows investigators consulted prosecutors about charges and collected abortion documentation; no charges were filed.
This is the anchor case for the vendor-credibility problem: the company's public account and the sworn record diverge. The dossier should present both and let the documents decide.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
Agencies have searched the network in connection with protest activity, raising a First Amendment problem distinct from the Fourth Amendment one.
Well supported
The case against thisSearches connected to a protest may be investigating crimes committed at one, and the audit log records a stated reason rather than an adjudicated purpose.
2 sources
Electronic Frontier Foundation · 2025-11-01 · Primary · national
Documents federal, state and local agencies running searches of the national network in connection with protest activity.
- More than 50 agencies ran hundreds of searches connected to protest activity across a 10-month window.
- Delaware State Police queried the network nine times in March 2025 in connection with Direct Action Everywhere activists.
The First Amendment dimension is distinct from the Fourth and should be argued separately, not folded in.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
Recorded search reasons show the systems used well beyond the serious-crime rationale offered at procurement, including school residency verification, background checks and noise complaints.
Well supported
The case against thisPolicy can restrict permitted uses without removing the cameras; this is an argument for use limits rather than for abolition.
2 sources
Electronic Frontier Foundation · 2026-05-01 · Primary · national
Documents ALPR searches for purposes far outside the violent-crime rationale used to sell the systems, including school residency checks, background checks and noise complaints.
- Recorded search reasons include school residency verification, background checks and noise complaints.
Mission creep is the strongest available answer to the it is only for serious crime argument, because the evidence is the agencies' own recorded search reasons.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
Officers have used ALPR systems to track intimate partners and other private individuals, in dozens of documented cases, and the misuse was typically discovered by victims or by outside review rather than by the vendor's own monitoring.
Well supported1 of 4 sources not read at source
The case against thisFlock has since made an audit-assistance tool that flags abnormal use a requirement (ij-2026-stalking-cases). The cases nonetheless accrued over years while the system was marketed as audited.
4 sources
Institute for Justice · 2026-08-01 · Primary · national
Running tally of officers documented using ALPR systems to track current or former romantic partners, compiled from arrests, charges and internal investigations.
- At least 50 U.S. officers face accusations or charges of misusing plate readers, mostly Flock systems.
- In Georgia, IJ and Reason documented 18 officer arrests across multiple counties for Flock database misuse.
- Joplin, Missouri: one officer ran a single woman's plate nearly 400 times, accounting for about a quarter of the department's searches.
- Milwaukee: an officer tracked a partner and the partner's ex nearly 180 times over two months; surfaced only when the victims looked themselves up on HaveIBeenFlocked.com.
- Kentucky, August 2026: an officer was arrested after tracking his ex-girlfriend more than 2,000 times.
Counts rise as new cases are charged; cite the figure with its date. Nearly every case surfaced through an audit log or a victim's own lookup, not through the vendor's monitoring.
CNN · 2026-08-26 · Secondary · KY
A Kentucky officer was arrested for using the Flock system to track an ex-girlfriend more than 2,000 times.
- More than 2,000 searches of one private individual by a single officer before detection.
Corroborates the IJ tally's largest single-victim figure through a mainstream outlet.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
CNN · 2026-07-26 · Secondary · national
Major-network investigation into police use and misuse of Flock cameras.
- Documents the growth of both authorized use and documented misuse of the system by police.
NOT READ in full. Recorded because CNN is the kind of source that persuades a reader who discounts EFF and 404 Media; worth reading properly and extracting its specific cases.
ALPR misreads and stale hot-list entries have repeatedly led to innocent people, including children, being detained at gunpoint, with settlements in the hundreds of thousands to millions of dollars.
Well supported
The case against thisNearly every such case also involves an officer failing to visually verify the plate before acting, so the harm is attributable to policy and training as much as to the reader's accuracy.
2 sources
Electronic Frontier Foundation · 2024-11-01 · Primary · national
Case-by-case account of innocent drivers stopped at gunpoint after ALPR misreads or stale hot-list entries, with settlement figures.
- Brittney Gilliam, Aurora, Colorado, August 2020: a Colorado SUV matched to a stolen Montana motorcycle plate; family detained at gunpoint with children face-down on pavement; Aurora settled for 1.9 million dollars.
- Denise Green, San Francisco, March 2009: reader misread a 3 as a 7; officers drew guns; city paid 495,000 dollars.
- Jaclynn Gonzales, Espanola, New Mexico: reader mistook a 2 for a 7; detained at gunpoint, her 12-year-old sister placed in a patrol vehicle.
- Jason Burkleo, Atherton, California: misread an H as an M; detained at gunpoint.
- Brian Hofer, Contra Costa County, Thanksgiving 2019: hot list not updated after the vehicle was recovered; 49,500 dollar settlement.
- Isoke Robinson, Detroit: police queried all Dodge Chargers near a shooting; handcuffed at home, 2-year-old placed in a patrol car, car impounded three weeks.
- Cited study: ALPRs misread the state of one in ten plates, before counting other reading errors.
The Espanola case is the New Mexico entry in this list and belongs in the local chapter as well as the harms chapter.
Wikipedia · 2026-08-01 · Secondary · national
Corporate timeline: founding, funding, product lines and a chronology of controversies.
- Founded 2017 by Garrett Langley, Paige Todd and Matt Feury; Langley is CEO.
- About 950 million dollars raised at a 7.5 billion dollar valuation as of 2025, including a 275 million dollar round in March 2025.
- Product lines: Falcon and Sparrow plate readers, Condor PTZ cameras, Raven gunshot detection (extended to human distress detection in October 2025), Nova data platform, and drones following the October 2024 Aerodome acquisition.
- Company-stated scale: over 5,000 communities in 49 states, 20 billion vehicle scans monthly.
- August 2024: Mother Jones reported 13 or more agencies spent 920,000 dollars of opioid settlement funds on Flock cameras.
- 2021: IPVM reported a 10 percent error rate and Flock halted sales to IPVM.
- Roanoke: 30 of 41 gunshot detectors installed in locations that were never approved.
- Verona, Wisconsin: cameras stayed operational three months after the contract was rejected; Cleveland cameras stayed active after expiration.
- Oshkosh, Wisconsin rescinded its contract in August 2026 citing false statements.
Wikipedia is a finding aid, not a citation. Every item above must be traced to its underlying source before it appears in the dossier; the operational scale figures are Flock's own marketing claims.
New Mexico has its own ALPR misidentification case: in Espanola a reader mistook a 2 for a 7, and the driver was detained at gunpoint with her 12-year-old sister placed in a patrol vehicle.
Well supported
2 sources
Electronic Frontier Foundation · 2024-11-01 · Primary · national
Case-by-case account of innocent drivers stopped at gunpoint after ALPR misreads or stale hot-list entries, with settlement figures.
- Brittney Gilliam, Aurora, Colorado, August 2020: a Colorado SUV matched to a stolen Montana motorcycle plate; family detained at gunpoint with children face-down on pavement; Aurora settled for 1.9 million dollars.
- Denise Green, San Francisco, March 2009: reader misread a 3 as a 7; officers drew guns; city paid 495,000 dollars.
- Jaclynn Gonzales, Espanola, New Mexico: reader mistook a 2 for a 7; detained at gunpoint, her 12-year-old sister placed in a patrol vehicle.
- Jason Burkleo, Atherton, California: misread an H as an M; detained at gunpoint.
- Brian Hofer, Contra Costa County, Thanksgiving 2019: hot list not updated after the vehicle was recovered; 49,500 dollar settlement.
- Isoke Robinson, Detroit: police queried all Dodge Chargers near a shooting; handcuffed at home, 2-year-old placed in a patrol car, car impounded three weeks.
- Cited study: ALPRs misread the state of one in ten plates, before counting other reading errors.
The Espanola case is the New Mexico entry in this list and belongs in the local chapter as well as the harms chapter.
KOB 4 · undated · Primary · NM
Statewide New Mexico accounting of which agencies run ALPRs, how long they keep the data, and who they share it with.
- Bernalillo County Sheriff's Office: 21 fixed cameras planned, 30-day retention, sharing with 88 agencies including some in Arizona, Colorado and Texas.
- Albuquerque Police Department: about 250 fixed cameras, one-year retention.
- New Mexico State Police: 180-day retention, sharing with hundreds of agencies including Border Patrol and ATF.
- At the time of reporting, no New Mexico law regulated ALPR access or retention.
- Sheriff John Allen on the technology: it is really a no brainer.
- NMSP Chief Troy Weisler declined an interview.
Publication date not stated on the page; the reporting predates SB 40 and the August 2026 BCSO cancellation, both of which changed the picture. Date must be pinned before this is cited for current state.
Under Carpenter and the Jones concurrences, aggregated location data can constitute a Fourth Amendment search even though each individual observation is public, and McCarthy applied that reasoning to ALPRs specifically.
Well supported
The case against thisMcCarthy sets a threshold rather than a rule and found the ALPR use before it lawful. Courts have divided on how dense a network must be, which is why Norfolk lost at the district court.
2 sources
Supreme Court of the United States · 2018-06-22 · Primary · national
Held that acquiring historical cell-site location information is a Fourth Amendment search requiring a warrant, and that the third-party doctrine does not extend to comprehensive location records.
- Seven days or more of historical cell-site location information is a search requiring a warrant.
- Roberts drew on the aggregation reasoning of the Alito and Sotomayor concurrences in United States v. Jones (2012).
- The opinion grounds the analysis in the Founding-era reaction to general warrants and writs of assistance.
The general-warrant framing is the dossier's spine: the objection is not to any single photograph but to a standing power to rummage retroactively.
Massachusetts Supreme Judicial Court · 2020-04-16 · Primary · MA
The first appellate decision applying the Fourth Amendment to ALPRs. The court adopted the mosaic approach: four cameras on two bridges did not invade a reasonable expectation of privacy, but enough readers in enough places would.
- Police used ALPRs on the Bourne and Sagamore bridges to track the defendant's crossings over three months.
- Held: a person has a constitutionally protected expectation of privacy in the whole of his public movements.
- Held: the limited extent of this ALPR use did not invade that interest, but historical data from enough readers in enough locations would constitute a search.
McCarthy is the case both sides cite. It sets a threshold rather than a rule, which is exactly why camera density and retention are the facts that decide these cases.
The district court upheld Norfolk's 176-camera network because it covers 75 designated areas and so locates a vehicle only briefly, rather than tracking the whole of a person's movements - plaintiffs' cars were photographed about 475 and 325 times in four and a half months, roughly 2 to 3 full plate matches per day. The court warned the line could be crossed later.
Well supported
The case against thisThis is the strongest pro-ALPR holding available and should be stated plainly: on this reasoning the constitutional question turns on coverage, and Norfolk planned to grow from 176 cameras toward more than 230. Note also that the court itself acknowledged Baltimore's aerial program left MULTI-HOUR gaps and was still a search - so gaps alone were never the distinction.
3 sources
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
WHRO Public Media · 2026-01-27 · Secondary · VA
Judge Davis ruled for the city on the merits, finding the Norfolk network not yet extensive enough to constitute a Fourth Amendment search, while warning that ALPR surveillance could cross that line.
- Plaintiff Lee Schmidt's vehicle was photographed 475 times in 4.5 months, with captures 40 to 50 minutes apart, leaving sizable gaps in his movements.
- 176 cameras at the time of the ruling, with Norfolk police planning more than 230 total.
- Virginia's searchable retention period is 21 days.
- Davis wrote that ALPR surveillance could become too intrusive at some point, but concluded not today for Norfolk.
- Plaintiffs, represented by the Institute for Justice, appealed.
Camera count differs across sources: 172 (Feb 2025 IJ), 175 and 176 (2026 coverage). The network grew; cite the count with its date. This ruling's gaps reasoning is the argument Chatrie later undercuts.
Institute for Justice · 2025-02-06 · Primary · VA
Chief Judge Mark Davis of the Eastern District of Virginia denied Norfolk's motion to dismiss Schmidt v. City of Norfolk, holding that a reasonable person could believe the Flock network violates societal privacy expectations under Carpenter.
- Case: Schmidt v. City of Norfolk, E.D. Va., Chief Judge Mark Davis.
- 172 Flock cameras in Norfolk at the time of filing.
- The court analogized the network to Carpenter's concern with secretly recording and cataloging the whole of tens of thousands of individuals' movements over an extended period.
This is the motion-to-dismiss stage, not a merits holding. The same judge later ruled for the city; see ch-2026-norfolk-constitutional.
Federal retention dwarfs any local policy: CBP holds border ALPR data for 15 years, so a local 21-day or 30-day retention rule does not bound how long a record of a given trip exists.
Well supported
The case against thisFederal border collection is a separate legal regime with its own authorities; it is not governed by the local contract and is not evidence about what the local vendor retains.
2 sources
Electronic Frontier Foundation · 2025-12-02 · Primary · national
Field guide documenting federal and covert ALPR infrastructure across the borderlands, including retention periods far longer than any local policy.
- CBP systems at all land ports of entry capture vehicles entering and exiting.
- Interior checkpoints, from a few to more than 60 miles inland, carry CBP ALPR systems.
- CBP retains this data for 15 years; agents can generally search the recent five years.
- About 100 covert ALPR sites identified across the border region, disguised in orange construction barrels and yellow sandbags, often in sets of three with solar panels.
- CBP solicited 100 additional covert trail cameras with plate capture in July 2025.
- Flock Safety camera poles documented outside the Santa Teresa Border Patrol station in New Mexico.
- CBP announced plans to integrate port-of-entry ALPRs into DEA's National License Plate Reader Program.
The 15-year federal retention is the number that reframes the local debate: a 21-day or 30-day local policy does not bound what the federal layer keeps.
KOB 4 · undated · Primary · NM
Statewide New Mexico accounting of which agencies run ALPRs, how long they keep the data, and who they share it with.
- Bernalillo County Sheriff's Office: 21 fixed cameras planned, 30-day retention, sharing with 88 agencies including some in Arizona, Colorado and Texas.
- Albuquerque Police Department: about 250 fixed cameras, one-year retention.
- New Mexico State Police: 180-day retention, sharing with hundreds of agencies including Border Patrol and ATF.
- At the time of reporting, no New Mexico law regulated ALPR access or retention.
- Sheriff John Allen on the technology: it is really a no brainer.
- NMSP Chief Troy Weisler declined an interview.
Publication date not stated on the page; the reporting predates SB 40 and the August 2026 BCSO cancellation, both of which changed the picture. Date must be pinned before this is cited for current state.
New Mexico sits inside the border enforcement zone, where federal ALPR infrastructure - including roughly 100 covert sites disguised as construction barrels and sandbags - overlays the local camera network, and Flock poles have been documented outside the Santa Teresa Border Patrol station.
Well supported
The case against thisDocumentation of a Flock pole outside a Border Patrol station establishes proximity, not that Border Patrol operates or queries that specific camera.
1 source
Electronic Frontier Foundation · 2025-12-02 · Primary · national
Field guide documenting federal and covert ALPR infrastructure across the borderlands, including retention periods far longer than any local policy.
- CBP systems at all land ports of entry capture vehicles entering and exiting.
- Interior checkpoints, from a few to more than 60 miles inland, carry CBP ALPR systems.
- CBP retains this data for 15 years; agents can generally search the recent five years.
- About 100 covert ALPR sites identified across the border region, disguised in orange construction barrels and yellow sandbags, often in sets of three with solar panels.
- CBP solicited 100 additional covert trail cameras with plate capture in July 2025.
- Flock Safety camera poles documented outside the Santa Teresa Border Patrol station in New Mexico.
- CBP announced plans to integrate port-of-entry ALPRs into DEA's National License Plate Reader Program.
The 15-year federal retention is the number that reframes the local debate: a 21-day or 30-day local policy does not bound what the federal layer keeps.
Before SB 40, New Mexico had no statute governing ALPR retention or access, and retention varied by agency from 30 days to a full year, with New Mexico State Police sharing with hundreds of agencies including Border Patrol.
Well supported
2 sources
KOB 4 · undated · Primary · NM
Statewide New Mexico accounting of which agencies run ALPRs, how long they keep the data, and who they share it with.
- Bernalillo County Sheriff's Office: 21 fixed cameras planned, 30-day retention, sharing with 88 agencies including some in Arizona, Colorado and Texas.
- Albuquerque Police Department: about 250 fixed cameras, one-year retention.
- New Mexico State Police: 180-day retention, sharing with hundreds of agencies including Border Patrol and ATF.
- At the time of reporting, no New Mexico law regulated ALPR access or retention.
- Sheriff John Allen on the technology: it is really a no brainer.
- NMSP Chief Troy Weisler declined an interview.
Publication date not stated on the page; the reporting predates SB 40 and the August 2026 BCSO cancellation, both of which changed the picture. Date must be pinned before this is cited for current state.
ACLU of New Mexico · 2026-02-01 · Primary · NM
New Mexico's first statewide ALPR statute, restricting out-of-state sharing and requiring annual agency reporting.
- Agencies may not share ALPR data with out-of-state third parties absent a formal affirmation that it will not be used to prosecute healthcare legal in New Mexico, enforce federal immigration law, or target constitutionally protected activity.
- ALPR information is designated a non-public record; access requires express consent or a valid court order.
- Agencies must file annual ALPR use reports with the Department of Public Safety.
- Passed the House 42-22.
Advocacy-organization summary of a statute. Before the dossier states any operative provision as law, read the enrolled bill text; sponsor summaries routinely describe an introduced version.
New Mexico ALPR data was accessed thousands of times by out-of-state law enforcement, with recorded search reasons including immigration, ICE and HSI.
Well supported
The case against thisBoth accounts trace to the same ACLU-NM records request. A second, independent production of the underlying audit logs would strengthen this materially; the dossier should seek one.
2 sources
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
The Las Cruces Flock agreement signed 12 September 2024 records 21 plate readers - 6 Multi-Purpose LPR and Video Fixed units and 15 Falcons - at 141,850 dollars, with a 30-day retention period and automatic renewal. The widely reported figure of about 737,000 dollars over five years is NOT what the signed agreement says.
Well supported
The case against thisThe two figures may both be true of different things - a not-to-exceed authorization or a five-year projection versus an executed order billed at signing. Print the document's number with the document's date and treat the press figure as press until someone reconciles them. Camera counts across sources remain a growth curve: 21 contracted Sept 2024, 18 stated by the chief in Dec 2024, 22 in July 2025 records, 45 plus 7 in Feb 2026 reporting.
4 sources
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
Local governments are cancelling Flock contracts, and the objections now come from inside law enforcement as well as from civil liberties groups.
Well supported1 of 4 sources not read at source
The case against thisCancellations remain a minority of deployments; the network continued to grow through the same period (techspot-2026-20-billion-scans).
4 sources
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
Government Technology · 2025-08-27 · Secondary · IL
Flock's response to the Illinois audit finding, including commitments to change its data-sharing controls.
- Flock halted cooperation with federal agencies in Illinois after the Secretary of State's order.
- Evanston and Oak Park ended their contracts.
Included so the vendor's own remediation position is represented rather than only its critics.
404 Media · 2025-01-01 · Primary · national
Flock sent a trademark cease and desist to Will Freeman, creator of the crowdsourced DeFlock camera map. EFF refused on his behalf and the map stayed up.
- Flock's lawyers demanded Freeman cease all use of the name DeFlock, claiming trademark dilution and false advertising.
- EFF replied that the demand had no legal basis and that the project sits within its First Amendment rights, citing anti-dilution carve-outs for noncommercial use and for criticism of a mark owner.
- DeFlock now hosts a crowdsourced map of more than 115,000 ALPR camera locations.
A company that maps every vehicle objecting to being mapped is the cleanest illustration of the asymmetry the dossier is about.
KRQE · 2026-08-01 · Secondary · NM
A running count of New Mexico agencies ending Flock contracts.
- By August 2026 a third New Mexico law enforcement agency had cut ties with Flock Safety.
NOT READ; date approximate. Identifies that New Mexico cancellations had reached at least three agencies - Bernalillo County and Taos are two candidates in this corpus, and the third should be named from the article.
Flock's public accounts have repeatedly diverged from the underlying records - in the abortion search, in the CEO's TED talk anchor story, and in municipal findings of false statements - which is why the dossier tiers company claims separately.
Well supported
The case against thisFlock declined to comment on the TED case rather than disputing it, and characterizes the abortion coverage as false. Where the company disputes a fact, the dossier states the dispute.
4 sources
TED · 2026-04-01 · Vendor claim · national
Flock's CEO makes the public case for pervasive camera networks at TED2026, opening with a child-rescue story attributed to a single detective and a single Flock camera.
- Langley's stated premise: it is too easy to get away with crime in the United States.
- Presents a network of plate readers, cameras, drones and audio sensors as the remedy.
- Opens with a narrative of one detective tracking a suspect vehicle in real time and rescuing an abducted girl.
Tiered vendor-claim. This is the argument the dossier must answer at full strength, and the specific anchor story is disputed - see ipvm-2026-ted-debunk.
IPVM · 2026-06-18 · Primary · national
IPVM matched the TED talk's anchor story to State v. Edward Ahrens and found the public record contradicts the telling in several material respects.
- The actual case was a multi-day, multi-agency operation across Tennessee and Georgia, not one detective acting alone.
- Phone pinging and warrants, not plate readers, drove the intercept; Flock is not mentioned anywhere in the 197-page TBI report.
- Fixed LPR cameras capture single moments and cannot track a moving vehicle in real time as described.
- The stop occurred in Georgia on an interstate exit ramp, not at the Tennessee jurisdictional boundary.
- No public record mentions the girl being bound.
- Langley's thousands of such stories daily framing is set against roughly 100 to 200 true stranger abductions annually nationwide.
- Flock declined to comment or to confirm or deny the case over a month of reporting.
Updated July 20, 2026. This is the cleanest available test of vendor claims against a primary record, and it is the pairing the dossier should lead the efficacy chapter with.
Electronic Frontier Foundation · 2025-10-01 · Primary · TX
Court documents contradict Flock's and the Johnson County, Texas sheriff's public characterization of a nationwide plate search as a missing-person welfare check. The records describe a death investigation of a non-viable fetus after a self-managed abortion.
- Search reason recorded in the audit log: had an abortion, search for female.
- Two searches: one across 17,684 cameras on 1,295 networks, a second across 83,345 cameras on 6,809 networks.
- Searches ran about 2.5 hours after the initial call, roughly two weeks after the abortion.
- Flock publicly called critical coverage misleading, false and clickbait, and said she was searched for as a missing person, not a suspect.
- The lead detective's affidavit shows investigators consulted prosecutors about charges and collected abortion documentation; no charges were filed.
This is the anchor case for the vendor-credibility problem: the company's public account and the sworn record diverge. The dossier should present both and let the documents decide.
Wikipedia · 2026-08-01 · Secondary · national
Corporate timeline: founding, funding, product lines and a chronology of controversies.
- Founded 2017 by Garrett Langley, Paige Todd and Matt Feury; Langley is CEO.
- About 950 million dollars raised at a 7.5 billion dollar valuation as of 2025, including a 275 million dollar round in March 2025.
- Product lines: Falcon and Sparrow plate readers, Condor PTZ cameras, Raven gunshot detection (extended to human distress detection in October 2025), Nova data platform, and drones following the October 2024 Aerodome acquisition.
- Company-stated scale: over 5,000 communities in 49 states, 20 billion vehicle scans monthly.
- August 2024: Mother Jones reported 13 or more agencies spent 920,000 dollars of opioid settlement funds on Flock cameras.
- 2021: IPVM reported a 10 percent error rate and Flock halted sales to IPVM.
- Roanoke: 30 of 41 gunshot detectors installed in locations that were never approved.
- Verona, Wisconsin: cameras stayed operational three months after the contract was rejected; Cleveland cameras stayed active after expiration.
- Oshkosh, Wisconsin rescinded its contract in August 2026 citing false statements.
Wikipedia is a finding aid, not a citation. Every item above must be traced to its underlying source before it appears in the dossier; the operational scale figures are Flock's own marketing claims.
Removing Flock does not remove the dragnet: Motorola's Vigilant and DRN run a commercial plate database built from fleet vehicles, and Axon's acquisition of Fusus fuses ALPR with live video and other feeds in more than 250 real-time crime centers.
Well supported
The case against thisDifferent vendors operate under different contracts and legal constraints; a policy fix aimed at one is not automatically wrong for being partial.
2 sources
American Civil Liberties Union · undated · Primary · national
Survey of the non-Flock ALPR market, principally Motorola Solutions' Vigilant and its commercial DRN arm.
- DRN is a Motorola Solutions company; Vigilant gives police access to the same commercially collected data.
- DRN contracts with tow trucks and other fleet vehicles to carry cameras and collect plate reads as they drive.
- Law enforcement customers have access to billions of historical scans, with tens of millions of new scans added monthly.
- Motorola markets historical travel analysis over an archive spanning more than 17 years.
Establishes that banning one vendor does not end the dragnet. Specific scan counts vary widely across sources and vendor marketing; treat each figure as vendor-claim unless independently sourced.
Police1 · 2024-02-08 · Secondary · national
Axon completed its acquisition of Fusus, whose platform aggregates live video, data and sensor feeds from many sources into a single real-time crime center view.
- Acquisition completed February 2024.
- Fusus aggregates live video, data and sensor feeds from disparate sources simultaneously.
- Axon has since announced fixed ALPR cameras (Outpost, Lightpost) and a Ring integration for citizen video sharing.
- Real-time crime centers have expanded to more than 250 cities and counties.
The fusion layer is the part that matters constitutionally: plate reads become a location dragnet only when joined to identity, video and other feeds in one interface.
The network audit log - the system's own record of who searched what and why - is the single most effective transparency instrument available to residents, and it is obtainable by public records request.
Well supported
The case against thisThe reason field is free text entered by the searching officer, so it is evidence of what was typed, not of what was actually done. It understates misuse and can misdescribe it in either direction.
4 sources
Electronic Frontier Foundation · 2026-06-01 · Primary · national
A how-to for residents seeking their own agency's network audit to determine whether local cameras have been searched for immigration purposes.
- Network audit logs are obtainable by public records request and record the stated reason for each search.
- The audit is the document that shows whether local cameras served federal immigration enforcement.
This is the operational bridge between the dossier and the module: the same audit file the /flock module already ingests is the one residents are told to request.
Illinois Secretary of State · 2025-08-25 · Primary · IL
A state audit found Flock violated Illinois law by allowing U.S. Customs and Border Protection access to Illinois plate data. The Secretary of State ordered access cut off immediately.
- The audit sampled 12 local agencies and found Flock lacked proper data-sharing safeguards.
- Flock was running a CBP pilot program that, per the audit, its own leadership was unaware of.
- A 2023 Illinois law bars sharing plate data for out-of-state abortion or immigration investigations; the state also invoked the Illinois TRUST Act.
This is a government finding of law violation by a regulator with subpoena power, not an advocacy claim. It is among the strongest single sources in the corpus.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
American Civil Liberties Union · undated · Primary · national
The ACLU's national organizing toolkit: how to find cameras, read the contract, and press a council, plus model policy language.
- Three phases: locate cameras, engage the council, organize a coalition.
- Points to DeFlock, HaveIBeenFlocked, EFF's Atlas of Surveillance and ALPR.watch for locating cameras.
- Model guardrails: retention limited to hours or days rather than weeks or more; no sharing absent a felony warrant; use restricted to defined scenarios; annual public reporting.
- Records guidance: search council agendas, minutes and consent agendas for ALPR items, then request the contract directly.
This project's get-the-flock-out micronode is deliberately named after this campaign; the dossier should link to the ACLU toolkit rather than compete with it.
Flock sent a trademark cease and desist to the volunteer who mapped its cameras; EFF refused it on First Amendment grounds and the map, now covering more than 115,000 camera locations, stayed up.
Well supported
The case against thisA trademark objection to a name is not a legal position about public mapping as such, and the company did not pursue it.
1 source
404 Media · 2025-01-01 · Primary · national
Flock sent a trademark cease and desist to Will Freeman, creator of the crowdsourced DeFlock camera map. EFF refused on his behalf and the map stayed up.
- Flock's lawyers demanded Freeman cease all use of the name DeFlock, claiming trademark dilution and false advertising.
- EFF replied that the demand had no legal basis and that the project sits within its First Amendment rights, citing anti-dilution carve-outs for noncommercial use and for criticism of a mark owner.
- DeFlock now hosts a crowdsourced map of more than 115,000 ALPR camera locations.
A company that maps every vehicle objecting to being mapped is the cleanest illustration of the asymmetry the dossier is about.
Roughly 75 percent of Flock's law enforcement customers have opted into the National Lookup Tool, which lets every other enrolled agency search their data - an opt-in rate the company attributes to restricting nationwide search access to agencies that share their own data.
Well supported
The case against thisFlock states that sharing with federal agencies is default off for every local department. Both can be true: near-universal opt-in among police agencies is a separate setting from federal access, and the dossier should not conflate them.
2 sources
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Flock Safety · undated · Vendor claim · national
Flock's own account of how network sharing and federal cooperation work. Included so the company's position is in the corpus in its own words rather than only as characterized by critics.
- Flock states that sharing with federal agencies is default off for every local police department.
Tiered vendor-claim; never render as fact. Set against the Wyden letter's finding that roughly 75 percent of law enforcement customers opted into the National Lookup Tool, and against the Illinois audit finding of a CBP pilot. Default-off for federal and 75-percent-opted-in for nationwide are both capable of being true; the dossier should state both.
The network's reach is not an accident of adoption but a design incentive: an agency gets nationwide search only by contributing its own cameras, so joining to search means joining to be searched.
Well supported
The case against thisReciprocity is a defensible design for a voluntary mutual-aid network, and no agency is compelled to enroll. The objection is that the residents whose cars are photographed never made that trade.
1 source
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Federal agents obtained Flock access by using local officers' credentials rather than any account of their own, and it went undetected: a DEA officer ran searches on a Palos Heights detective's account, which the detective said was common practice for his task force.
Well supported
The case against thisThis is credential misuse by individual officers, not a vendor sharing policy. The systemic point is that no MFA requirement meant nothing stopped or logged it as federal access.
1 source
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Flock does not require multi-factor authentication of law enforcement customers, still supports SMS codes, and lacks native phishing-resistant MFA - and at least 35 customer accounts have had passwords stolen by infostealer malware, with Flock accounts offered for sale on a Russian-language cybercrime forum.
Well supported
The case against thisFlock does offer MFA and Palos Heights enabled it once alerted. The lawmakers' position is that offering is not requiring, and that the FTC has treated failure to require MFA as an unfair practice in four prior actions.
1 source
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Congressional scrutiny of Flock is bipartisan: a Democratic senator and representative asked the FTC to investigate in November 2025, and a Republican Judiciary subcommittee chairman opened his own investigation in August 2026, writing that Congress never authorized the network the industry built.
Well supported2 of 6 sources not read at source
The case against thisInvestigations are not findings, and none of these has yet produced a legal conclusion against the company.
6 sources
Office of U.S. Senator Josh Hawley · 2026-08-26 · Primary · national
The chairman of the Senate Judiciary Subcommittee on Crime and Counterterrorism opened an investigation into Flock, demanding documents from CEO Garrett Langley. Notable because it puts congressional scrutiny of Flock on a bipartisan footing.
- Sen. Josh Hawley, chairman of the Judiciary Subcommittee on Crime and Counterterrorism, opened the investigation August 26, 2026.
- Documents and information demanded from CEO Garrett Langley by September 8, 2026.
- Hawley: Congress never authorized the network your industry has built.
- Hawley: Your company's internal policies are, in practice, the only safeguards for hundreds of millions of Americans.
- Hawley: Americans do not surrender their privacy rights when they drive to work, drop their kids off at school, or go to church.
- Cites more than 120,000 cameras across 49 states, more than 20 billion vehicle scans monthly, and an 8.3 billion dollar valuation.
Pairs with wyden-2025-ftc-letter to show scrutiny is not partisan - a Democratic senator and representative in November 2025, a Republican subcommittee chairman in August 2026. That framing matters in a council chamber. The demand annex was not published with the release; the response deadline has likely passed and the reply is worth seeking.
Axios · 2026-08-26 · Secondary · national
Broke the Hawley investigation, framing it as bipartisan convergence against Flock.
- First reported Hawley's investigation on August 26, 2026.
Corroborates hawley-2026-flock-investigation through an outlet independent of the senator's own office.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
404 Media · 2025-08-08 · Primary · national
Members of Congress opened a formal investigation into Flock, demanding records of all searches touching ICE, CBP and abortion. The letter cites 404 Media's reporting directly.
- Rep. Raja Krishnamoorthi and Rep. Robert Garcia demanded details of all ICE, CBP and abortion-related searches of the national network.
- The investigation followed reporting that local police ran lookups on behalf of ICE and that a Texas officer searched nationwide for a woman who self-managed an abortion.
Article is partly paywalled; the findings above are the portion verifiable from the accessible text. Corroborated by the Wyden/Krishnamoorthi FTC letter of November 2025.
U.S. House of Representatives · 2025-08-06 · Primary · national
The primary document behind the August 2025 congressional investigation - the letter itself, demanding records of ICE, CBP and abortion-related searches.
- Dated August 6, 2025, signed by Reps. Robert Garcia and Raja Krishnamoorthi.
NOT READ - the House server returned HTTP 403 to automated fetching on 2026-08-30. This is the PRIMARY document for the congressional investigation, currently represented in this corpus only through 404 Media's account of it. Retrieve it by other means; it should be read the way the Wyden letter was, and that reading changed what the Wyden entry said.
U.S. Senate Judiciary Subcommittee on Crime and Counterterrorism / Daily Caller · 2026-08-26 · Secondary · national
What the Senate subcommittee actually asked Flock to produce, and the company's response.
- Deadline of September 8, 2026 for Flock to produce documents on who has access to the information the cameras gather.
- The subcommittee sought documentation of data retention policies, search verification protocols, internal security practices, and records of confirmed system misuse since 2021.
- Flock spokesperson Paris Lewbel said the company has received the letter and appreciates the opportunity to provide the subcommittee with additional information about Flock and our technology.
The demand for RECORDS OF CONFIRMED MISUSE SINCE 2021 is the item to watch: if produced, it would be the first company-wide misuse tally not assembled from journalists' records requests. The deadline has now passed - whether anything was produced, and whether it becomes public, is the single most tractable follow-up in this corpus. Ingested from secondary coverage; the letter and its annex were not obtained.
Las Cruces councilors are seeking a city-level surveillance ordinance, regular audits and an independently run public transparency portal, on the ground that a departmental policy can be changed by the department at any time.
Well supported
The case against thisLCPD says it already applies safeguards exceeding state requirements and is building a transparency portal. The council's answer is that a vendor-supplied portal maintained by the department is not an independent audit.
2 sources
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
New Mexico SB 40 was signed March 4, 2026 as Chapter 20 and took effect July 1, 2026, making it the state's first ALPR statute.
Well supported
The case against thisThe enrolled statutory text remains unread by this project; every description of its operative provisions here comes from sponsor and press summaries.
2 sources
Source New Mexico · 2026-07-01 · Secondary · NM
Coverage of SB 40 taking effect, with the enactment details the advocacy summaries omit.
- SB 40 was signed by the governor March 4, 2026 and became Chapter 20.
- The law took effect July 1, 2026.
Supplies the chapter number and effective date. The enrolled statutory text is at legiscan.com/NM/text/SB40/id/3386165, which returned HTTP 403 to automated fetching on 2026-08-30 and remains UNREAD. Until someone reads it, no operative provision of SB 40 should be quoted as law.
ACLU of New Mexico · 2026-02-01 · Primary · NM
New Mexico's first statewide ALPR statute, restricting out-of-state sharing and requiring annual agency reporting.
- Agencies may not share ALPR data with out-of-state third parties absent a formal affirmation that it will not be used to prosecute healthcare legal in New Mexico, enforce federal immigration law, or target constitutionally protected activity.
- ALPR information is designated a non-public record; access requires express consent or a valid court order.
- Agencies must file annual ALPR use reports with the Department of Public Safety.
- Passed the House 42-22.
Advocacy-organization summary of a statute. Before the dossier states any operative provision as law, read the enrolled bill text; sponsor summaries routinely describe an introduced version.
New Mexico's SB 40 sets no retention limit at all. It restricts who ALPR data may be shared with and mandates reporting, but nothing in the act caps how long any agency may keep it.
Well supported
The case against thisRetention was arguably left to agencies deliberately, and the sharing restrictions and reporting duties bite regardless of how long data is held. But the pre-SB 40 spread - 30 days at BCSO, a year at APD, 180 days at NMSP - is untouched by the statute.
1 source
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
SB 40 makes ALPR information confidential and not a public record under the Inspection of Public Records Act - closing the records-request route that produced the evidence of misuse in the first place, while opening a mandated annual reporting route in its place.
Well supported
The case against thisThe exclusion covers ALPR information itself, and Section 2(B) expressly excludes information used for auditing an ALPR from that definition - so audit material is arguably still reachable. That reading is untested; a lawyer should check it before anyone relies on it.
3 sources
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
SB 40's real transparency instrument is Section 4: every New Mexico agency must report annually to DPS the total queries and their purposes, every agency granted access, every out-of-state agency that queried, identified instances of unauthorized use, and warrants and subpoenas received - with DPS publishing aggregated data by July 1 each year.
Well supported
The case against thisReporting is self-assessed: unauthorized-use counts are determined by each agency's own audit policy, so an agency without a real audit policy can truthfully report zero. First reports covering calendar 2026 are due April 1, 2027, with DPS aggregation by July 1, 2027 - nothing is published yet.
1 source
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
SB 40 is enforceable: the attorney general, a district attorney, or DPS may act; courts may grant injunctive relief and assess 10,000 dollars or actual damages per intentional violation, whichever is greater; non-complying agencies can lose data-sharing privileges and non-complying vendors can have authorization suspended or terminated.
Well supported
The case against thisThe penalty attaches only to intentional violations of Section 3, a meaningful evidentiary hurdle, and no enforcement action has yet been brought under the act.
1 source
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
SB 40 reaches beyond police: it defines an ALPR to include devices owned or operated by non-law-enforcement entities, and separately bars making ALPR information available to non-law-enforcement officers or agencies.
Well supported
2 sources
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
State fusion centers circulated bulletins directing police to monitor anti-Flock advocacy on TikTok and Instagram, flag upcoming DeFlock events, and increase patrols around ALPR cameras - conflating lawful opposition to surveillance with camera vandalism.
Well supported
The case against thisCamera destruction is real and documented, and bulletins about property crime against public infrastructure are ordinary police business. The objection is to monitoring the speech and the organizers rather than the vandalism.
2 sources
404 Media · 2026-07-01 · Primary · national
State fusion centers circulated bulletins directing police to monitor anti-Flock advocacy on social media, warn of upcoming DeFlock events, and increase patrols around ALPR cameras.
- Fusion center bulletins monitored viral anti-Flock Instagram posts and warned local police about upcoming DeFlock events.
- Bulletins directed officers to increase patrols around ALPR cameras and warned about devices that could be used to identify camera locations.
- Dozens of state fusion centers circulated such memos across agencies during summer 2026, per documents obtained by journalist Dan Boguslaw.
- The documents tie people who politically oppose mass surveillance to vigilantes who destroy cameras.
- DeFlock creator Will Freeman said the project has never called for disabling cameras or covering plates, describing it as a grassroots mapping tool for civic engagement and local political pressure.
The sharpest First Amendment material in the corpus: the surveillance apparatus monitoring the people organizing against it. Keep the distinction Freeman draws - lawful mapping and advocacy versus camera vandalism - because the bulletins blur it and the dossier must not.
Electronic Frontier Foundation · 2025-11-01 · Primary · national
Documents federal, state and local agencies running searches of the national network in connection with protest activity.
- More than 50 agencies ran hundreds of searches connected to protest activity across a 10-month window.
- Delaware State Police queried the network nine times in March 2025 in connection with Direct Action Everywhere activists.
The First Amendment dimension is distinct from the Fourth and should be argued separately, not folded in.
Flock planned to extend its gunshot-detection microphones to listen for human screaming and distress, then withdrew the feature in July 2026 after public pressure - though the microphones themselves remain deployed and listening.
Well supported
The case against thisFlock says the system cannot understand speech, analyze language or identify voices, does not record by default, and processes only a rolling five-second window.
2 sources
Electronic Frontier Foundation · 2025-10-03 · Primary · national
The original warning that Flock's acoustic gunshot detectors, formerly Raven, would be extended to detect human distress sounds.
- Flock planned to deploy Distress Detection through its existing acoustic gunshot detection devices, formerly Flock Raven and later renamed Audio Detection.
- EFF's long-standing objection is that these are high-powered microphones mounted above densely populated streets.
Pairs with eff-2026-audio-distress-victory as a before-and-after. Relevant to Las Cruces, whose 2021 contract included a free Raven audio product that was not carried into the September 2024 renewal.
Electronic Frontier Foundation · 2026-07-01 · Primary · national
Flock withdrew its plan to use its gunshot-detection microphone network to listen for human screaming and distress, after public pressure. The microphones remain deployed.
- Flock removed the human distress detection element after what it called careful consideration and community consultation.
- The acoustic detectors remain installed and continue listening for gunshots and vehicle crashes.
- Flock says the system cannot understand speech, analyze language or identify voices, and that audio is not recorded by default, with a rolling five-second window continually processed.
- EFF's Matthew Guariglia called gunshot microphones being used to listen for screaming exactly the type of mission creep seen with other surveillance technology.
- Marketing materials originally showed police receiving an alert for screaming; the ad was later amended to say distress.
Important as a counterexample: sustained public pressure reversed a specific rollout. Cite it when someone says opposition changes nothing. Note the microphones themselves stayed - the win was over a feature, not the hardware.
Sustained public opposition changes outcomes: Flock withdrew the distress-detection rollout, Illinois forced federal access off, councils across roughly 23 states cancelled or declined to renew during 2026, and Denver removed all 110 of its cameras at contract expiry.
Well supported1 of 5 sources not read at source
The case against thisThe network grew over the same period. Cancellation counts vary by counting rule - 23 councils, 30-plus cities, 56 municipalities and 80 all appear in 2026 coverage - so no total should be printed without its source and rule.
5 sources
Electronic Frontier Foundation · 2026-07-01 · Primary · national
Flock withdrew its plan to use its gunshot-detection microphone network to listen for human screaming and distress, after public pressure. The microphones remain deployed.
- Flock removed the human distress detection element after what it called careful consideration and community consultation.
- The acoustic detectors remain installed and continue listening for gunshots and vehicle crashes.
- Flock says the system cannot understand speech, analyze language or identify voices, and that audio is not recorded by default, with a rolling five-second window continually processed.
- EFF's Matthew Guariglia called gunshot microphones being used to listen for screaming exactly the type of mission creep seen with other surveillance technology.
- Marketing materials originally showed police receiving an alert for screaming; the ad was later amended to say distress.
Important as a counterexample: sustained public pressure reversed a specific rollout. Cite it when someone says opposition changes nothing. Note the microphones themselves stayed - the win was over a feature, not the hardware.
Illinois Secretary of State · 2025-08-25 · Primary · IL
A state audit found Flock violated Illinois law by allowing U.S. Customs and Border Protection access to Illinois plate data. The Secretary of State ordered access cut off immediately.
- The audit sampled 12 local agencies and found Flock lacked proper data-sharing safeguards.
- Flock was running a CBP pilot program that, per the audit, its own leadership was unaware of.
- A 2023 Illinois law bars sharing plate data for out-of-state abortion or immigration investigations; the state also invoked the Illinois TRUST Act.
This is a government finding of law violation by a regulator with subpoena power, not an advocacy claim. It is among the strongest single sources in the corpus.
Washington Examiner · 2026-08-01 · Secondary · national
Tally of municipal cancellations across the country during 2026.
- Roughly 23 city councils voted to cancel, not renew, reject or deactivate Flock ALPRs since the start of 2026, across 23 states.
- Denver removed all 110 of its cameras when its contract expired March 31, 2026.
- Austin, Evanston, Oak Park, San Marcos, Sedona and Hays County among those that ended, rejected or declined to expand contracts.
Cancellation tallies vary widely by source and counting rule - 23 councils, 30-plus cities, 56 municipalities and 80 all appear in 2026 coverage. Do not print a total without naming the source's counting rule and date; these are not the same measure.
Hoodline · 2026-08-01 · Secondary · TX
A Texas city cancelled its Flock deal after the scale of outside searches became public.
- Pflugerville, Texas ended its Flock camera deal after 1.6 million outside searches surfaced.
NOT YET READ in full. The 1.6 million figure resembles the San Francisco figure in the California class action; confirm they are distinct before citing both, or the dossier will double-count one number.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
Schmidt v. City of Norfolk is on appeal to the Fourth Circuit as No. 26-1227, with amicus support spanning the ACLU, EFF, EPIC, the Cato Institute and the New Civil Liberties Alliance.
Well supported2 of 4 sources not read at source
The case against thisAmicus breadth does not predict outcome, and the panel has not ruled. Track the docket rather than assume reversal.
4 sources
Institute for Justice · 2026-04-01 · Primary · VA
IJ's case page for the Norfolk challenge, now on appeal to the Fourth Circuit as No. 26-1227.
- Suit filed October 2024 by Norfolk resident Lee Schmidt and Portsmouth resident Crystal Arrington.
- District court granted summary judgment for the city in January 2026.
- On appeal to the Fourth Circuit as Schmidt v. City of Norfolk, No. 26-1227.
- Amicus briefs filed by the ACLU, EFF, Cato Institute, EPIC and the New Civil Liberties Alliance as of April 2026.
The docket number is the thing to track. The breadth of the amicus coalition - libertarian and civil-liberties groups together - is itself an argument that this is not a partisan question.
Electronic Privacy Information Center · 2026-04-01 · Primary · VA
EPIC's amicus brief to the Fourth Circuit supporting the plaintiffs-appellants.
- Filed April 2026 in support of plaintiffs-appellants and reversal.
NOT YET READ. The amicus briefs are the best available distillation of the constitutional argument against ALPR networks, written to persuade a federal appellate court rather than a general audience. Reading this and the NCLA and Cato briefs is the highest-value remaining ingest for the legal chapter.
New Civil Liberties Alliance · 2026-04-20 · Primary · VA
NCLA amicus brief supporting reversal of the district court's judgment for Norfolk.
- Filed April 20, 2026 in support of plaintiffs-appellants and reversal.
NOT YET READ. Included so the docket's amicus record is complete in the corpus.
WHRO Public Media · 2026-01-27 · Secondary · VA
Judge Davis ruled for the city on the merits, finding the Norfolk network not yet extensive enough to constitute a Fourth Amendment search, while warning that ALPR surveillance could cross that line.
- Plaintiff Lee Schmidt's vehicle was photographed 475 times in 4.5 months, with captures 40 to 50 minutes apart, leaving sizable gaps in his movements.
- 176 cameras at the time of the ruling, with Norfolk police planning more than 230 total.
- Virginia's searchable retention period is 21 days.
- Davis wrote that ALPR surveillance could become too intrusive at some point, but concluded not today for Norfolk.
- Plaintiffs, represented by the Institute for Justice, appealed.
Camera count differs across sources: 172 (Feb 2025 IJ), 175 and 176 (2026 coverage). The network grew; cite the count with its date. This ruling's gaps reasoning is the argument Chatrie later undercuts.
ICE has no direct contract with Flock and no direct access - and obtained data anyway, through local agencies running lookups on its behalf and through federal agents using local officers' credentials.
Well supported1 of 5 sources not read at source
The case against thisFlock's denial is accurate on its own terms, and in January 2026 it added a single-toggle federal sharing shutoff. The point is that the absence of a contract was never the safeguard it was presented as.
5 sources
Flock Safety · 2026-02-01 · Vendor claim · national
Flock's own position on ICE access, plus the administrative controls it added in early 2026.
- Flock states it does not work with ICE and that ICE has no direct access to Flock cameras, systems or data unless the agencies controlling that data expressly and deliberately allow it.
- January 2026: Flock added an admin setting letting any agency turn off all federal sharing with a single toggle.
- February 2026: Flock added a post-login disclaimer citing CJIS requirements and relevant state immigration and reproductive care laws.
Tiered vendor-claim. The denial is narrowly true and beside the point: the documented route was never a direct ICE contract but local agencies running lookups and passing results on, plus federal agents using local officers' credentials. Note ICE has cooperative agreements with more than 2,300 jurisdictions.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
404 Media · 2025-06-01 · Primary · national
After the ICE and abortion reporting, Flock cut off national lookups into cameras located in Illinois, California and Virginia. The company's ability to make that change unilaterally is itself evidence about who controls the data.
- Flock blocked out-of-state agencies from searching cameras inside Illinois, California and Virginia.
- More than 4,000 lookups had been run at the behest of federal agencies for immigration purposes, giving federal law enforcement side-door access to a tool it had no formal contract for.
- The Danville network audit alone contained 307 immigration-related searches by Texas agencies, going back to June 2024.
Vendor-side switch-flipping cuts both ways as evidence: it shows the sharing was a policy choice, not a technical necessity.
Star Tribune · 2026-01-01 · Secondary · MN
Local police searched Twin Cities ALPR cameras for immigration enforcement during a federal enforcement surge.
- Twin Cities-area police ran immigration-related searches of Flock cameras during a DHS metro surge.
NOT YET READ in full; ingested from search summary. Useful as a second metro-area instance of the same pattern documented in Illinois and Texas. Date is approximate and must be pinned before citing.
Illinois Secretary of State · 2025-08-25 · Primary · IL
A state audit found Flock violated Illinois law by allowing U.S. Customs and Border Protection access to Illinois plate data. The Secretary of State ordered access cut off immediately.
- The audit sampled 12 local agencies and found Flock lacked proper data-sharing safeguards.
- Flock was running a CBP pilot program that, per the audit, its own leadership was unaware of.
- A 2023 Illinois law bars sharing plate data for out-of-state abortion or immigration investigations; the state also invoked the Illinois TRUST Act.
This is a government finding of law violation by a regulator with subpoena power, not an advocacy claim. It is among the strongest single sources in the corpus.
The Fourth Circuit already holds, en banc, that persistent surveillance of a whole city is a Fourth Amendment search - Leaders of a Beautiful Struggle v. Baltimore Police Department - and that the analysis looks to what the data can reveal, not to the raw data alone. That is binding precedent in the very court now hearing the Norfolk appeal.
Well supported1 of 3 sources not read at source
The case against thisBaltimore's aerial program watched a whole city continuously from above; Norfolk's cameras sit at fixed points and leave gaps, which is exactly the distinction the district court drew. Whether the precedent controls is the question on appeal, not a settled answer.
3 sources
Electronic Privacy Information Center · 2026-04-20 · Primary · VA
EPIC's Fourth Circuit brief urging reversal in Norfolk. The single best distillation of the constitutional argument in the corpus, written to persuade a federal appellate court, and it rests on the Fourth Circuit's own binding precedent rather than on Carpenter alone.
- District court case number is 2:24-cv-00621-MSD-LRL, E.D. Va., Judge Mark S. Davis; appeal is No. 26-1227.
- Central argument: the court need only follow its own established rule in Leaders of a Beautiful Struggle v. Baltimore Police Department, 2 F.4th 330 (4th Cir. 2021), which assessed Baltimore's aerial surveillance program by looking at not only the raw data but what that data can reveal.
- Frames the Fourth Amendment guideposts from Carpenter as securing the privacies of life against arbitrary power (Boyd) and placing obstacles in the way of a too permeating police surveillance (Di Re).
- Argues modern ALPR systems must be judged on evolving capabilities and the inferences they enable, per Kyllo and Carpenter, not as scattered individual data points.
- Second argument: AI-enabled ALPR systems are predictive policing systems, built on unvetted, outdated and biased data overrepresenting poor and minority populations, generating suspicion inside a proprietary black box that cannot be examined or challenged - implicating the Fourth, Fifth and Sixth Amendments.
- Concludes that absent strict safeguards ALPRs revive the arbitrary powers of the reviled general warrant, and that a warrant is the proper first obstacle.
- From the litigation record (JA citations), Flock's system can stream live video and capture clips, identify other vehicles traveling with a vehicle of interest, and analyze a vehicle's past travel history to offer probabilities for where it will go next.
- Cites CRS R48160: as of 2020 every police department serving over one million residents, and about 90 percent of sheriffs' offices with 500 or more sworn deputies, were already using ALPRs.
- Notes Virginia's default retention was up to 30 days at the time of the relevant events and up to 21 days under Va. Code 2.2-5517 as of briefing, with longer retention where data is deemed relevant to an ongoing investigation.
READ IN FULL from the filed PDF on 2026-08-30. The Leaders of a Beautiful Struggle argument is the most important legal find in this corpus: it is binding Fourth Circuit precedent holding persistent aerial surveillance a search, in the very circuit now hearing Norfolk. The predictive-policing framing is also the strongest available answer to the it-is-just-photographs defense, because the system's own marketed features include next-location prediction.
United States Court of Appeals for the Fourth Circuit · 2021-06-24 · Primary · national
The en banc Fourth Circuit held that Baltimore's Aerial Investigation Research program - persistent aerial surveillance of the whole city - was a Fourth Amendment search under Carpenter, because the analysis must consider not only the raw data but what that data can reveal.
- Held that accessing the aerial surveillance program's data is a search requiring a warrant.
- Established in this circuit that the inquiry looks to what data can reveal, not merely to what was individually collected.
NOT YET READ IN FULL; ingested via EPIC's brief, which quotes it at 344. This is binding precedent in the circuit now deciding Schmidt, which makes it the most consequential authority in the corpus. Read the opinion before the dossier characterizes its holding any further.
Institute for Justice · 2026-04-01 · Primary · VA
IJ's case page for the Norfolk challenge, now on appeal to the Fourth Circuit as No. 26-1227.
- Suit filed October 2024 by Norfolk resident Lee Schmidt and Portsmouth resident Crystal Arrington.
- District court granted summary judgment for the city in January 2026.
- On appeal to the Fourth Circuit as Schmidt v. City of Norfolk, No. 26-1227.
- Amicus briefs filed by the ACLU, EFF, Cato Institute, EPIC and the New Civil Liberties Alliance as of April 2026.
The docket number is the thing to track. The breadth of the amicus coalition - libertarian and civil-liberties groups together - is itself an argument that this is not a partisan question.
Modern ALPR is not a passive record but a predictive policing system: the marketed and record-documented features include identifying vehicles traveling together and estimating where a vehicle will go next, with the reasoning inside a proprietary black box.
Well supported
The case against thisPrediction features assist investigations that would otherwise be done by hand, and no court has held predictive analysis of lawfully collected data to be a search. EPIC's argument that this implicates the Fourth, Fifth and Sixth Amendments is an argument, not a holding.
3 sources
Electronic Privacy Information Center · 2026-04-20 · Primary · VA
EPIC's Fourth Circuit brief urging reversal in Norfolk. The single best distillation of the constitutional argument in the corpus, written to persuade a federal appellate court, and it rests on the Fourth Circuit's own binding precedent rather than on Carpenter alone.
- District court case number is 2:24-cv-00621-MSD-LRL, E.D. Va., Judge Mark S. Davis; appeal is No. 26-1227.
- Central argument: the court need only follow its own established rule in Leaders of a Beautiful Struggle v. Baltimore Police Department, 2 F.4th 330 (4th Cir. 2021), which assessed Baltimore's aerial surveillance program by looking at not only the raw data but what that data can reveal.
- Frames the Fourth Amendment guideposts from Carpenter as securing the privacies of life against arbitrary power (Boyd) and placing obstacles in the way of a too permeating police surveillance (Di Re).
- Argues modern ALPR systems must be judged on evolving capabilities and the inferences they enable, per Kyllo and Carpenter, not as scattered individual data points.
- Second argument: AI-enabled ALPR systems are predictive policing systems, built on unvetted, outdated and biased data overrepresenting poor and minority populations, generating suspicion inside a proprietary black box that cannot be examined or challenged - implicating the Fourth, Fifth and Sixth Amendments.
- Concludes that absent strict safeguards ALPRs revive the arbitrary powers of the reviled general warrant, and that a warrant is the proper first obstacle.
- From the litigation record (JA citations), Flock's system can stream live video and capture clips, identify other vehicles traveling with a vehicle of interest, and analyze a vehicle's past travel history to offer probabilities for where it will go next.
- Cites CRS R48160: as of 2020 every police department serving over one million residents, and about 90 percent of sheriffs' offices with 500 or more sworn deputies, were already using ALPRs.
- Notes Virginia's default retention was up to 30 days at the time of the relevant events and up to 21 days under Va. Code 2.2-5517 as of briefing, with longer retention where data is deemed relevant to an ongoing investigation.
READ IN FULL from the filed PDF on 2026-08-30. The Leaders of a Beautiful Struggle argument is the most important legal find in this corpus: it is binding Fourth Circuit precedent holding persistent aerial surveillance a search, in the very circuit now hearing Norfolk. The predictive-policing framing is also the strongest available answer to the it-is-just-photographs defense, because the system's own marketed features include next-location prediction.
Associated Press · 2025-11-20 · Primary · national
AP investigation revealing a secretive Border Patrol predictive intelligence program that scores drivers' travel patterns from license plate reads and refers them for stops, searches and arrests.
- Border Patrol is monitoring millions of American drivers nationwide in a secretive predictive intelligence program.
- An algorithm flags vehicles as suspicious based on where they came from, where they were going, and which route they took.
- Flagged drivers are pulled over on pretextual grounds - speeding, failure to signal, window tint, a dangling air freshener - and in some cases searched and arrested.
- Border Patrol defined its own criteria for suspicion, including driving on backcountry roads, being in a rental car, or making short trips to the border region.
- The agency has for years hidden details of the program; readers are often disguised along highways inside traffic safety equipment such as drums and barrels.
The most important source in the corpus for the New Mexico chapter. It shows the federal layer doing exactly what critics say the local layer enables - pattern-of-life scoring without suspicion - and it explains the pretextual-stop mechanism that hides the surveillance from the person stopped. AP is the wire original; the PBS URL is a syndication and was chosen because it fetches. Read the AP original before quoting.
404 Media · 2025-05-13 · Primary · national
Internal slides, Slack messages and meeting audio show Flock building Nova, a product designed to join plate reads to identified people using data-broker records and breach data.
- Nova is designed to jump from license plate reader to person, without a warrant or court order.
- Some data available through the platform came from breaches rather than public or commercially available records, including data from a hacked parking meter app.
- The product raised objections from Flock's own employees.
Flock later told employees Nova would not use dark-web data; separate code analysis reported selectors for Social Security numbers, credit card numbers and crypto wallets. Treat the company's denial and the code analysis as a live dispute, not a settled fact.
Border Patrol runs a secretive predictive program that scores drivers' travel patterns from plate reads and refers the flagged for pretextual traffic stops - detaining people for driving backcountry roads, renting a car, or making short trips near the border.
Well supported
The case against thisThe federal program operates under distinct border-search authorities, and the stops themselves are made on independently observed traffic violations. That is precisely the objection: the pretext hides the surveillance from the person stopped.
2 sources
Associated Press · 2025-11-20 · Primary · national
AP investigation revealing a secretive Border Patrol predictive intelligence program that scores drivers' travel patterns from license plate reads and refers them for stops, searches and arrests.
- Border Patrol is monitoring millions of American drivers nationwide in a secretive predictive intelligence program.
- An algorithm flags vehicles as suspicious based on where they came from, where they were going, and which route they took.
- Flagged drivers are pulled over on pretextual grounds - speeding, failure to signal, window tint, a dangling air freshener - and in some cases searched and arrested.
- Border Patrol defined its own criteria for suspicion, including driving on backcountry roads, being in a rental car, or making short trips to the border region.
- The agency has for years hidden details of the program; readers are often disguised along highways inside traffic safety equipment such as drums and barrels.
The most important source in the corpus for the New Mexico chapter. It shows the federal layer doing exactly what critics say the local layer enables - pattern-of-life scoring without suspicion - and it explains the pretextual-stop mechanism that hides the surveillance from the person stopped. AP is the wire original; the PBS URL is a syndication and was chosen because it fetches. Read the AP original before quoting.
Electronic Frontier Foundation · 2025-12-02 · Primary · national
Field guide documenting federal and covert ALPR infrastructure across the borderlands, including retention periods far longer than any local policy.
- CBP systems at all land ports of entry capture vehicles entering and exiting.
- Interior checkpoints, from a few to more than 60 miles inland, carry CBP ALPR systems.
- CBP retains this data for 15 years; agents can generally search the recent five years.
- About 100 covert ALPR sites identified across the border region, disguised in orange construction barrels and yellow sandbags, often in sets of three with solar panels.
- CBP solicited 100 additional covert trail cameras with plate capture in July 2025.
- Flock Safety camera poles documented outside the Santa Teresa Border Patrol station in New Mexico.
- CBP announced plans to integrate port-of-entry ALPRs into DEA's National License Plate Reader Program.
The 15-year federal retention is the number that reframes the local debate: a 21-day or 30-day local policy does not bound what the federal layer keeps.
An ALPR statute does not by itself change agency behavior: California legislated in 2015 and its own auditor found agencies flagrantly non-compliant by 2020, and Virginia's own Crime Commission found agencies out of compliance within months of its 2025 law - with nearly a third of agencies not even responding to the survey.
Well supported
The case against thisBoth findings led to corrective measures, and New Mexico's SB 40 has enforcement provisions California's SB 34 lacked - AG, DA and DPS enforcement, 10,000 dollars per intentional violation, and revocable sharing privileges. The lesson is that compliance must be measured, not assumed.
4 sources
California State Auditor · 2020-02-01 · Primary · CA
A state audit, prompted by EFF's legislative advocacy, finding California agencies broadly out of compliance with SB 34.
- Agencies did not make informed decisions about sharing ALPR images with other entities.
- Agencies did not consider how they use ALPR data when setting retention periods.
- Agencies followed poor practices for granting staff access to ALPR systems.
- Agencies failed to audit system use.
The single best precedent for what an ALPR statute achieves without enforcement: California legislated in 2015, and by 2020 its own auditor found agencies flagrantly non-compliant. Pair with vscc-2026-alpr-report - two states, same finding, five years apart.
Virginia State Crime Commission · 2026-01-21 · Primary · VA
A state legislative commission's survey of every law enforcement agency in Virginia, measuring ALPR adoption, vendor share and statutory compliance after Virginia's 2025 ALPR law took effect. The only rigorous state-level census of ALPR use in the corpus.
- All 361 Virginia law enforcement agencies were surveyed; 251 responded, a 70 percent response rate.
- 63 percent of responding agencies (159 of 251) reported using ALPR.
- 86 percent of ALPR-using agencies (137 of 159) reported Flock Safety as their vendor.
- The Commission found that some Virginia agencies are NOT using ALPR in accordance with the new statute.
- Almost one-third of agencies did not respond at all, so their ALPR use is unknown.
- Before legislation effective July 1, 2025, no statewide statutory or regulatory framework governed law enforcement ALPR use in Virginia - no limits on use, retention or sharing.
- As of December 2025, Charlottesville and Staunton were ending their ALPR use.
- Cites Virginia Center for Investigative Journalism, September 16 2025: one small Virginia town's surveillance network recorded nearly 7 million hits, based on June 2024 to June 2025 data.
READ from the Commission's own PDF on 2026-08-30. Directly relevant to New Mexico: Virginia passed its ALPR law a year before SB 40, and its own legislature found agencies out of compliance and a third of agencies simply not answering. That is the empirical answer to anyone who says SB 40 settles the New Mexico question. The 86 percent Flock share is also the best evidence that vendor-specific reform is close to sector-wide reform.
Electronic Frontier Foundation · 2023-10-01 · Primary · CA
California's Attorney General concluded that state agencies sharing ALPR data with out-of-state agencies violates SB 34.
- California SB 34 (2015) prohibits California agencies from sharing ALPR data with non-California agencies, and requires a published usage and privacy policy.
- The California DOJ declared out-of-state sharing unlawful in 2023.
Context for the 2026 California class action, which alleges the sharing continued anyway. A state law plus an attorney general opinion did not stop the conduct - relevant when assessing what SB 40 will actually accomplish in New Mexico.
Gibbs Mura / Courthouse News (complaint PDF) · 2026-02-26 · Primary · CA
Class action filed in San Francisco Superior Court alleging Flock violated California's ALPR Privacy Act by sharing plate data with out-of-state and federal agencies.
- Filed February 26, 2026 by Gibbs Mura with Milberg PLLC in San Francisco Superior Court.
- Alleges out-of-state and federal agencies queried San Francisco's Flock database more than 1.6 million times in seven months, between mid-2024 and early 2025.
- Seeks 2,500 dollars per violation under California Civil Code section 1798.90.55.
Allegations in a complaint are not findings. Cite as what is alleged, and check the docket for rulings before the dossier treats any of it as established.
The only rigorous state census of ALPR use found 63 percent of responding Virginia agencies using ALPR and 86 percent of those using Flock - meaning that in that state, regulating Flock is very nearly regulating the entire sector.
Well supported
The case against thisVirginia is not necessarily representative, and 30 percent of agencies did not respond, so the true adoption rate is unknown and probably higher.
1 source
Virginia State Crime Commission · 2026-01-21 · Primary · VA
A state legislative commission's survey of every law enforcement agency in Virginia, measuring ALPR adoption, vendor share and statutory compliance after Virginia's 2025 ALPR law took effect. The only rigorous state-level census of ALPR use in the corpus.
- All 361 Virginia law enforcement agencies were surveyed; 251 responded, a 70 percent response rate.
- 63 percent of responding agencies (159 of 251) reported using ALPR.
- 86 percent of ALPR-using agencies (137 of 159) reported Flock Safety as their vendor.
- The Commission found that some Virginia agencies are NOT using ALPR in accordance with the new statute.
- Almost one-third of agencies did not respond at all, so their ALPR use is unknown.
- Before legislation effective July 1, 2025, no statewide statutory or regulatory framework governed law enforcement ALPR use in Virginia - no limits on use, retention or sharing.
- As of December 2025, Charlottesville and Staunton were ending their ALPR use.
- Cites Virginia Center for Investigative Journalism, September 16 2025: one small Virginia town's surveillance network recorded nearly 7 million hits, based on June 2024 to June 2025 data.
READ from the Commission's own PDF on 2026-08-30. Directly relevant to New Mexico: Virginia passed its ALPR law a year before SB 40, and its own legislature found agencies out of compliance and a third of agencies simply not answering. That is the empirical answer to anyone who says SB 40 settles the New Mexico question. The 86 percent Flock share is also the best evidence that vendor-specific reform is close to sector-wide reform.
At least 60 Flock Condor cameras sat on the open internet with no authentication, exposing live feeds, 30 days of archived video and in some cases administrative controls - meaning the network's security failures expose the public it records, not only its police customers.
Well supported
The case against thisThis was a misconfiguration affecting a small fraction of deployed devices, and it was remediated after disclosure. The structural point stands: the people recorded had no relationship with the vendor and no way to know.
3 sources
404 Media · 2025-12-29 · Primary · national
At least 60 Flock Condor pan-tilt-zoom cameras were reachable on the open internet with no authentication, exposing live feeds, 30 days of archived video and in some cases administrative controls.
- At least 60 Condor PTZ cameras were publicly accessible on the open internet without authentication, found via Shodan.
- Anyone with a browser could view live footage and download 30 days of archived video; some instances exposed admin panels allowing settings changes, log access and diagnostics.
- Corroborated independently by technologist Benn Jordan and security researcher Jon GainSec Gaines.
- Condor cameras track people rather than vehicles and can be set to zoom automatically on faces in parking lots, streets and playgrounds.
- A Douglas County, Colorado camera was among those compromised while exposed.
This is the concrete realization of the risk in the Wyden letter: the security of the network is the security of everyone recorded by it. Note the product distinction - Condor is a people-tracking PTZ camera, not a plate reader - which matters when an agency says it only bought license plate readers.
Benn Jordan (YouTube) · 2026-01-01 · Secondary · national
A widely viewed technical investigation of Flock's ALPR systems by a technologist, demonstrating both plate-recognition defeat and the exposed-camera security failures.
- Reported at roughly 3 million views; among the most watched public explainers on Flock.
- Demonstrates defeating plate recognition with a near-invisible applied pattern, causing misreads and in some cases non-detection; the pattern was deliberately not published because using it may be illegal.
- Jordan participated in the research that found Flock cameras accessible over the open internet, including archived footage and deletion capability.
- Jordan also supplied congressional offices the screenshot of a Russian-language forum offering Flock accounts for sale, cited in the Wyden FTC letter.
URL IS A SEARCH QUERY, NOT THE VIDEO - the canonical watch URL was not captured and must be pinned before citing. Handle the evasion material carefully: the dossier's position is transparency and law, not defeating cameras, and at least one state has criminalized ALPR jamming. Cite Jordan for the security findings, not as a how-to.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Flock's Condor cameras track people rather than vehicles and can be set to zoom automatically on faces in parking lots, streets and playgrounds - so an agency that says it bought license plate readers may be operating something materially different.
Well supported
The case against thisPTZ cameras are ordinary municipal equipment and predate ALPR networks. The objection is to their integration into the same searchable platform, which is what makes the Las Cruces contract's inclusion of PTZ cameras worth reading closely.
2 sources
404 Media · 2025-12-29 · Primary · national
At least 60 Flock Condor pan-tilt-zoom cameras were reachable on the open internet with no authentication, exposing live feeds, 30 days of archived video and in some cases administrative controls.
- At least 60 Condor PTZ cameras were publicly accessible on the open internet without authentication, found via Shodan.
- Anyone with a browser could view live footage and download 30 days of archived video; some instances exposed admin panels allowing settings changes, log access and diagnostics.
- Corroborated independently by technologist Benn Jordan and security researcher Jon GainSec Gaines.
- Condor cameras track people rather than vehicles and can be set to zoom automatically on faces in parking lots, streets and playgrounds.
- A Douglas County, Colorado camera was among those compromised while exposed.
This is the concrete realization of the risk in the Wyden letter: the security of the network is the security of everyone recorded by it. Note the product distinction - Condor is a people-tracking PTZ camera, not a plate reader - which matters when an agency says it only bought license plate readers.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
There is no comprehensive federal statute governing ALPRs. Congress has left the field entirely to Fourth Amendment litigation and to state and local law - which is why a city council vote is currently the only democratic check on a national network.
Well supported2 of 3 sources not read at source
The case against thisFederal legislation could preempt stronger state protections as easily as create them, so the absence of a federal statute is not automatically the worse outcome.
3 sources
Congressional Research Service · undated · Primary · national
Congress's own research arm on the legal status of ALPRs.
- There is no comprehensive federal statute governing ALPR technology; Congress has left the field to Fourth Amendment litigation and to state and local law.
NOT YET READ in full. The no-federal-statute point is the structural fact underneath Hawley's line that Congress never authorized the network the industry built, and underneath the argument that a city council is currently the only body making this decision. Companion report CRS R48160 carries the adoption statistics cited in EPIC's brief.
Office of U.S. Senator Josh Hawley · 2026-08-26 · Primary · national
The chairman of the Senate Judiciary Subcommittee on Crime and Counterterrorism opened an investigation into Flock, demanding documents from CEO Garrett Langley. Notable because it puts congressional scrutiny of Flock on a bipartisan footing.
- Sen. Josh Hawley, chairman of the Judiciary Subcommittee on Crime and Counterterrorism, opened the investigation August 26, 2026.
- Documents and information demanded from CEO Garrett Langley by September 8, 2026.
- Hawley: Congress never authorized the network your industry has built.
- Hawley: Your company's internal policies are, in practice, the only safeguards for hundreds of millions of Americans.
- Hawley: Americans do not surrender their privacy rights when they drive to work, drop their kids off at school, or go to church.
- Cites more than 120,000 cameras across 49 states, more than 20 billion vehicle scans monthly, and an 8.3 billion dollar valuation.
Pairs with wyden-2025-ftc-letter to show scrutiny is not partisan - a Democratic senator and representative in November 2025, a Republican subcommittee chairman in August 2026. That framing matters in a council chamber. The demand annex was not published with the release; the response deadline has likely passed and the reply is worth seeking.
Stateline · 2025-10-10 · Secondary · national
Survey of 2025 state legislative activity on ALPRs, finding wide interest but few enactments.
- Only three states enacted license plate reader laws in 2025 despite widespread legislative interest.
NOT YET READ in full. Useful for placing New Mexico's 2026 SB 40 in national context: statutes of this kind remain rare, which makes New Mexico's an unusually good test case.
Model ALPR policy language already exists and does not need inventing: the ACLU toolkit, the Brennan Center's recommendations and state-by-state comparisons give a council ready-made guardrails - retention limits, felony-warrant conditions on sharing, enumerated permitted uses, and annual public reporting.
Well supported2 of 4 sources not read at source
The case against thisNeither the Brennan report nor the GovTech ranking has been read by this project, and both are undated in the corpus. Read them before handing a council language attributed to them.
4 sources
American Civil Liberties Union · undated · Primary · national
The ACLU's national organizing toolkit: how to find cameras, read the contract, and press a council, plus model policy language.
- Three phases: locate cameras, engage the council, organize a coalition.
- Points to DeFlock, HaveIBeenFlocked, EFF's Atlas of Surveillance and ALPR.watch for locating cameras.
- Model guardrails: retention limited to hours or days rather than weeks or more; no sharing absent a felony warrant; use restricted to defined scenarios; annual public reporting.
- Records guidance: search council agendas, minutes and consent agendas for ALPR items, then request the contract directly.
This project's get-the-flock-out micronode is deliberately named after this campaign; the dossier should link to the ACLU toolkit rather than compete with it.
Brennan Center for Justice · undated · Primary · national
Brennan Center analysis of ALPR legal status with model policy recommendations.
- Provides policy recommendations for law enforcement ALPR use alongside a legal-status survey.
NOT YET READ; date not captured. Worth reading alongside the ACLU toolkit when drafting the Las Cruces ordinance language the councilors have asked for.
Government Technology · undated · Secondary · national
A comparative ranking of state ALPR statutes on privacy and data-sharing protections.
- Provides a state-by-state comparison of ALPR statutory protections.
NOT YET READ; date not captured. Potentially the fastest way to place New Mexico against its neighbors - Texas has no ALPR statute at all, which matters given Texas agencies searched New Mexico cameras.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
Dona Ana County's sheriff runs about 30 Flock cameras with 22 more planned under a 162,000 dollar consolidated agreement, and says every search must carry a case number, verified by monthly self-audit.
Well supported
The case against thisThe case-number rule and the monthly self-audit are exactly the controls the national audit logs show being satisfied by free-text entries, and a self-audit is the agency checking its own work. That is a reason to verify rather than a reason to disbelieve - and the county's first SB 40 report, due April 1 2027, is where it becomes checkable.
1 source
KFOX 14 · 2026-06-24 · Primary · local:dona-ana-county
The county sheriff's office expanding its Flock deployment, with the clearest statement in the corpus of the safeguards a New Mexico agency claims to apply.
- About 30 cameras currently deployed, with 22 more planned within a year.
- 162,000 dollars approved for the yearly subscription and new cameras, already within the sheriff's approved budget, under one consolidated agreement.
- Lt. Eric Flores: there has to be a case number and therefore a crime associated with that vehicle.
- Flores: the cameras aren't used to surveil just everyday citizens.
- Flores: we've been able to basically solve many many crimes that normally we wouldn't have had leads on.
- Stated safeguards include monthly self-audits verifying that each query has an associated case number.
This is the local case FOR the cameras, and the dossier must carry it at full strength. Two things to test rather than assume: the case-number requirement is exactly the kind of control the national audit logs show being satisfied by free-text entries, and a MONTHLY SELF-AUDIT is the agency checking its own work - the same self-assessment weakness built into SB 40's reporting. Neither observation disproves the claim; both are checkable against the county's own SB 40 report due April 1, 2027.
Local officials make a concrete case for the cameras - auto theft, homicides, missing persons, a solved Las Cruces hit-and-run - and the dossier carries it at full strength rather than pretending it does not exist.
Well supported
The case against thisFederal research finds little evidence ALPRs reduce crime, and case anecdotes are not clearance statistics. But arrests and recoveries do measurably rise with ALPR-equipped patrols, so the honest position is that the tool works at the margins and the question is what it costs.
3 sources
KFOX 14 · 2026-06-24 · Primary · local:dona-ana-county
The county sheriff's office expanding its Flock deployment, with the clearest statement in the corpus of the safeguards a New Mexico agency claims to apply.
- About 30 cameras currently deployed, with 22 more planned within a year.
- 162,000 dollars approved for the yearly subscription and new cameras, already within the sheriff's approved budget, under one consolidated agreement.
- Lt. Eric Flores: there has to be a case number and therefore a crime associated with that vehicle.
- Flores: the cameras aren't used to surveil just everyday citizens.
- Flores: we've been able to basically solve many many crimes that normally we wouldn't have had leads on.
- Stated safeguards include monthly self-audits verifying that each query has an associated case number.
This is the local case FOR the cameras, and the dossier must carry it at full strength. Two things to test rather than assume: the case-number requirement is exactly the kind of control the national audit logs show being satisfied by free-text entries, and a MONTHLY SELF-AUDIT is the agency checking its own work - the same self-assessment weakness built into SB 40's reporting. Neither observation disproves the claim; both are checkable against the county's own SB 40 report due April 1, 2027.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
National Institute of Justice / CrimeSolutions · undated · Primary · national
Federal research summary on what is and is not known about ALPR effectiveness.
- There is little evidence that ALPRs reduce crime, and less is known about their effect on clearance rates.
- Empirical research has not kept pace with deployment; few rigorous evaluations exist.
- Randomized ALPR patrol of auto-theft hot spots found no reduction in auto theft or crime generally.
- Arrests and vehicle recoveries were two to three times more likely during patrols using the technology.
A government source conceding thin evidence is more useful in a council chamber than an advocacy source saying the same thing. Verify the publication date before citing.
License plate readers are one layer of a stack already deployed around Las Cruces: drones, body cameras, iris scanners, SWAT facial recognition, truck-mounted thermal imaging, and a federal border apparatus of fixed towers, remote video systems, MQ-9 drones and an aerostat at Deming.
Well supported
The case against thisEach system was acquired separately for a stated purpose, and no single one constitutes a dragnet. The mosaic argument is precisely that the aggregate is the thing to assess, which is why an inventory belongs in the record.
3 sources
Electronic Frontier Foundation · undated · Primary · local:dona-ana-county
EFF's county-level inventory of surveillance technology in Dona Ana County - the single most complete picture of what is actually deployed around Las Cruces, and it reaches well past license plate readers.
- Agencies deploying local surveillance: Dona Ana County Sheriff's Office, Las Cruces Police Department, Sunland Park Police Department, New Mexico State University Police and New Mexico State Police.
- The Multi-Agency Tactical Response Information eXchange (MATRIX) fusion center in El Paso integrates records from 20 agencies across both counties and has access to certain surveillance cameras throughout the region.
- Dona Ana County shares 45 miles of border with Mexico.
- Federal presence nearby: 28 CBP Integrated Fixed Tower systems, up to 69 Remote Video Surveillance Systems, MQ-9 drones, and an aerostat at Deming monitoring aircraft within 200 miles.
- Sheriff's office acquired two BI2 Technologies iris scanning cameras (14,000 dollars plus a donation).
- A 50,000 dollar OD Tactical eyewear system with facial recognition was acquired for SWAT operations.
- County approved 161,000 dollars for three ALPR speed trailers in school zones in 2017.
- NMSU Police have operated drones since 2017; State Police use thermal imagery and 3D modeling.
- Strongwatch truck-mounted mobile camera systems with a 138,750 dollar thermal imaging upgrade in 2016.
Page is undated and several entries are from the 2015-2017 period, so this is a cumulative inventory rather than a current snapshot - date each line before citing. The MATRIX fusion center is the important find: it is the regional mechanism by which Las Cruces-area data joins an El Paso, Texas hub, and Texas has no ALPR statute at all. Published in Spanish; relevant for a majority-Hispanic county.
Electronic Frontier Foundation · 2025-12-02 · Primary · national
Field guide documenting federal and covert ALPR infrastructure across the borderlands, including retention periods far longer than any local policy.
- CBP systems at all land ports of entry capture vehicles entering and exiting.
- Interior checkpoints, from a few to more than 60 miles inland, carry CBP ALPR systems.
- CBP retains this data for 15 years; agents can generally search the recent five years.
- About 100 covert ALPR sites identified across the border region, disguised in orange construction barrels and yellow sandbags, often in sets of three with solar panels.
- CBP solicited 100 additional covert trail cameras with plate capture in July 2025.
- Flock Safety camera poles documented outside the Santa Teresa Border Patrol station in New Mexico.
- CBP announced plans to integrate port-of-entry ALPRs into DEA's National License Plate Reader Program.
The 15-year federal retention is the number that reframes the local debate: a 21-day or 30-day local policy does not bound what the federal layer keeps.
Associated Press · 2025-11-20 · Primary · national
AP investigation revealing a secretive Border Patrol predictive intelligence program that scores drivers' travel patterns from license plate reads and refers them for stops, searches and arrests.
- Border Patrol is monitoring millions of American drivers nationwide in a secretive predictive intelligence program.
- An algorithm flags vehicles as suspicious based on where they came from, where they were going, and which route they took.
- Flagged drivers are pulled over on pretextual grounds - speeding, failure to signal, window tint, a dangling air freshener - and in some cases searched and arrested.
- Border Patrol defined its own criteria for suspicion, including driving on backcountry roads, being in a rental car, or making short trips to the border region.
- The agency has for years hidden details of the program; readers are often disguised along highways inside traffic safety equipment such as drums and barrels.
The most important source in the corpus for the New Mexico chapter. It shows the federal layer doing exactly what critics say the local layer enables - pattern-of-life scoring without suspicion - and it explains the pretextual-stop mechanism that hides the surveillance from the person stopped. AP is the wire original; the PBS URL is a syndication and was chosen because it fetches. Read the AP original before quoting.
Syracuse's council approved a 26-camera Flock deployment without knowing published research showed the readers misread the state on roughly one in ten plates; a majority said afterward they had not been told.
Well supported
The case against thisThe research was public and the council could have found it. That is the point of asking what a staff report contained: procurement failures are usually omissions, not lies.
2 sources
Central Current · 2024-08-13 · Primary · NY
Syracuse councilors approved a 26-camera Flock deployment without knowing about published research on the system's error rate; several said so afterward.
- IPVM research found Flock misread the state on roughly 1 in 10 plates, logged plate reads multiple times, and regularly got vehicle characteristics and car make wrong.
- A majority of the Common Council was unaware of the research before voting; at least four councilors expressed concern on learning of it.
- Councilor Rita Paniagua: I had no idea that there's a percent of misreads.
- The council approved the 26-camera deployment on July 1, 2024.
The cleanest documented instance of the procurement failure this project's alpr_staff_reports subsystem is built to detect: the decision-makers did not have the material fact. Directly transferable to a Las Cruces or Dona Ana County council question - what were you told about the error rate before you voted?
IPVM · 2021-01-01 · Primary · national
Independent bench testing of Flock's readers, the origin of the widely cited one-in-ten state misread figure - and of Flock's decision to stop selling to its tester.
- Flock misidentified the state on roughly one in ten reads.
- The system logged plate reads multiple times and regularly misclassified vehicle type and make.
- Flock subsequently blocked IPVM from purchasing its cameras for testing.
- Flock retracted a statement about the IPVM research after IPVM refuted its claims.
URL IS RECONSTRUCTED AND UNVERIFIED - the canonical IPVM report URL was not captured; pin it before citing. The 2021 date is approximate. A vendor cutting off the independent lab that tested it is itself a finding, and it is the reason no current independent accuracy test exists.
After independent testing found roughly one-in-ten state misreads, Flock blocked the testing firm from buying its cameras - which is why no current independent accuracy measurement of the system exists.
Well supported
The case against thisA company may choose its customers, and IPVM is a commercial research firm with its own interests. The consequence stands regardless of motive: accuracy claims about Flock now come from Flock or from records requests, not from independent testing.
2 sources
IPVM · 2021-01-01 · Primary · national
Independent bench testing of Flock's readers, the origin of the widely cited one-in-ten state misread figure - and of Flock's decision to stop selling to its tester.
- Flock misidentified the state on roughly one in ten reads.
- The system logged plate reads multiple times and regularly misclassified vehicle type and make.
- Flock subsequently blocked IPVM from purchasing its cameras for testing.
- Flock retracted a statement about the IPVM research after IPVM refuted its claims.
URL IS RECONSTRUCTED AND UNVERIFIED - the canonical IPVM report URL was not captured; pin it before citing. The 2021 date is approximate. A vendor cutting off the independent lab that tested it is itself a finding, and it is the reason no current independent accuracy test exists.
Wikipedia · 2026-08-01 · Secondary · national
Corporate timeline: founding, funding, product lines and a chronology of controversies.
- Founded 2017 by Garrett Langley, Paige Todd and Matt Feury; Langley is CEO.
- About 950 million dollars raised at a 7.5 billion dollar valuation as of 2025, including a 275 million dollar round in March 2025.
- Product lines: Falcon and Sparrow plate readers, Condor PTZ cameras, Raven gunshot detection (extended to human distress detection in October 2025), Nova data platform, and drones following the October 2024 Aerodome acquisition.
- Company-stated scale: over 5,000 communities in 49 states, 20 billion vehicle scans monthly.
- August 2024: Mother Jones reported 13 or more agencies spent 920,000 dollars of opioid settlement funds on Flock cameras.
- 2021: IPVM reported a 10 percent error rate and Flock halted sales to IPVM.
- Roanoke: 30 of 41 gunshot detectors installed in locations that were never approved.
- Verona, Wisconsin: cameras stayed operational three months after the contract was rejected; Cleveland cameras stayed active after expiration.
- Oshkosh, Wisconsin rescinded its contract in August 2026 citing false statements.
Wikipedia is a finding aid, not a citation. Every item above must be traced to its underlying source before it appears in the dossier; the operational scale figures are Flock's own marketing claims.
Large police agencies, not only councils and advocacy groups, are reopening or ending Flock agreements - LAPD renegotiated over civil liberties concerns, and Bernalillo County's sheriff cancelled outright.
Well supported1 of 2 sources not read at source
The case against thisRenegotiation is not cancellation, and both agencies continue to use surveillance technology generally.
2 sources
Fortune · 2026-07-15 · Secondary · CA
The largest municipal police department in the West reopening its Flock agreement over civil liberties concerns.
- LAPD renegotiated its Flock agreement citing serious concerns around civil liberties, including immigration and privacy issues.
NOT READ in full. Notable because the objection comes from a large police department rather than a council or an advocacy group - the same pattern as Sheriff Allen in Bernalillo County.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
Flock's public LPR policy page and the terms its contracts actually incorporate do not describe the same thing: the policy page says 7-day default deletion and under-1-percent de-identified training use, while the live Terms of Service set no retention at all (it lives on the Order Form) and contain no training-data guardrail, only a perpetual license to use customer data to support and improve products.
Well supported
The case against thisCORRECTION: this dossier previously said the no-sale clause had been deleted, following February 2026 clause analyses. The terms read at source on 2026-08-30 DO contain one - Flock shall not sell Customer Data. Either it was restored or the earlier reading was wrong, and this project has not compared versions. The perpetual irrevocable license and the absence of a training-data section are confirmed at source.
5 sources
Flock Safety · undated · Vendor claim · national
Flock's public-facing LPR policy - the document a council is most likely to be shown.
- Flock states it defaults to deleting LPR data every 7 days on a rolling basis, adjustable per customer.
- States that LPR data gathered on behalf of customers is owned by the customer, who controls sharing.
- States Flock uses under 1 percent of LPR images, stripped of identifying information and metadata, solely to improve services through machine learning.
- States it will not sell, publish or disclose customer LPR data for commercial purposes without consent - but may disclose where legally required or where it reasonably believes access is necessary to comply with legal process, enforce agreements, or address security and fraud concerns.
Tiered vendor-claim, and the most important one in the corpus to hold against the contract. The policy page describes de-identified, sub-1-percent training use; the February 2026 terms DELETED the Training Data section imposing exactly those limits, and deleted the no-sale clause. A council shown this page is not being shown the agreement it would sign.
Flock Safety · 2026-08-21 · Vendor claim · national
The live terms that Flock order forms incorporate by reference - read directly rather than through commentary, and they differ from the February 2026 clause analyses in one important respect.
- License grant, quoted: Customer hereby grants to Flock a limited, non-exclusive, royalty-free, irrevocable, perpetual, worldwide license to (a) use and disclose Customer Data to provide the Flock Services; and (b) use Customer Data to support and improve Flock's products and services.
- A NO-SALE CLAUSE IS PRESENT in the current terms: For the avoidance of doubt, Flock shall not sell Customer Data.
- Data ownership: as between Flock and Customer, all right, title and interest in and to Customer Data belong to and are retained by Customer.
- No dedicated training-data section; the support-and-improve language is what would cover model training.
- Retention is not fixed in the terms - the Retention Period is defined as the period specified in the applicable Order Form.
- Termination for material breach uncured within 30 days, bankruptcy or insolvency, or when no active Order Forms exist; auto-renewal is handled on the Order Form rather than here.
- Governing law is Georgia; disputes go to AAA mediation and then binding arbitration under AAA Commercial Arbitration Rules.
READ AT SOURCE 2026-08-30 - and it CORRECTS this dossier. Chapter 6b, following contemporaneous February 2026 clause-level analyses by the ACLU and Footnote4a, said the no-sale clause had been DELETED. The current terms contain one. Either it was restored between February and August 2026, or the earlier reading was wrong; this project has not compared the versions itself and cannot say which. What is NOT in dispute and is confirmed here at source: the license to Flock is irrevocable and perpetual, there is no dedicated training-data guardrail, governing law is Georgia and disputes go to arbitration. Retention lives on the Order Form, which is why the Dona Ana Order Form matters.
American Civil Liberties Union · 2026-04-16 · Primary · national
ACLU analysis of Flock's revised terms and conditions, identifying four changes that shift control of the data from the customer city to the company.
- The clause Flock does not own and shall not sell Customer Data is absent from the updated terms.
- New terms grant Flock the exclusive right to determine and control the method, timing, format, and medium of a customer's access to its own data - with customers receiving degraded, low-resolution copies lacking metadata such as timestamps.
- Flock gains perpetual rights to use customer data to support and improve its services, retaining access after the customer's contract terminates.
- Expanded liability protections shield Flock even for willful misconduct or gross negligence; disputes go to private arbitration under Georgia law; and termination is made harder, including where cities decline or defund programs.
- ACLU advises municipalities to examine the changes closely, seek legal counsel before entering or renewing, and consider not installing mass surveillance systems at all.
The degraded-copy point deserves emphasis: a city that cannot get full-resolution data with metadata cannot independently audit its own system, which undercuts every locally promised safeguard including case-number verification.
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
Flock's terms grant it an irrevocable, perpetual, worldwide license to use customer data to improve its products - surviving termination of the contract, so a city that cancels does not get its data out of the company's models.
Well supported1 of 4 sources not read at source
The case against thisLangley defends this as standard software licensing, customers retain ownership of the data, and the current terms do include a no-sale clause. LAPD and others renegotiated to strike the license, which shows it is negotiable rather than inherent.
4 sources
Flock Safety · 2026-08-21 · Vendor claim · national
The live terms that Flock order forms incorporate by reference - read directly rather than through commentary, and they differ from the February 2026 clause analyses in one important respect.
- License grant, quoted: Customer hereby grants to Flock a limited, non-exclusive, royalty-free, irrevocable, perpetual, worldwide license to (a) use and disclose Customer Data to provide the Flock Services; and (b) use Customer Data to support and improve Flock's products and services.
- A NO-SALE CLAUSE IS PRESENT in the current terms: For the avoidance of doubt, Flock shall not sell Customer Data.
- Data ownership: as between Flock and Customer, all right, title and interest in and to Customer Data belong to and are retained by Customer.
- No dedicated training-data section; the support-and-improve language is what would cover model training.
- Retention is not fixed in the terms - the Retention Period is defined as the period specified in the applicable Order Form.
- Termination for material breach uncured within 30 days, bankruptcy or insolvency, or when no active Order Forms exist; auto-renewal is handled on the Order Form rather than here.
- Governing law is Georgia; disputes go to AAA mediation and then binding arbitration under AAA Commercial Arbitration Rules.
READ AT SOURCE 2026-08-30 - and it CORRECTS this dossier. Chapter 6b, following contemporaneous February 2026 clause-level analyses by the ACLU and Footnote4a, said the no-sale clause had been DELETED. The current terms contain one. Either it was restored between February and August 2026, or the earlier reading was wrong; this project has not compared the versions itself and cannot say which. What is NOT in dispute and is confirmed here at source: the license to Flock is irrevocable and perpetual, there is no dedicated training-data guardrail, governing law is Georgia and disputes go to arbitration. Retention lives on the Order Form, which is why the Dona Ana Order Form matters.
American Civil Liberties Union · 2026-04-16 · Primary · national
ACLU analysis of Flock's revised terms and conditions, identifying four changes that shift control of the data from the customer city to the company.
- The clause Flock does not own and shall not sell Customer Data is absent from the updated terms.
- New terms grant Flock the exclusive right to determine and control the method, timing, format, and medium of a customer's access to its own data - with customers receiving degraded, low-resolution copies lacking metadata such as timestamps.
- Flock gains perpetual rights to use customer data to support and improve its services, retaining access after the customer's contract terminates.
- Expanded liability protections shield Flock even for willful misconduct or gross negligence; disputes go to private arbitration under Georgia law; and termination is made harder, including where cities decline or defund programs.
- ACLU advises municipalities to examine the changes closely, seek legal counsel before entering or renewing, and consider not installing mass surveillance systems at all.
The degraded-copy point deserves emphasis: a city that cannot get full-resolution data with metadata cannot independently audit its own system, which undercuts every locally promised safeguard including case-number verification.
Fortune · 2026-08-24 · Secondary · national
Business-press assessment of Flock's trajectory amid the privacy backlash, including customer pushback on contract terms.
- Privacy experts say Flock's contracts allow it to retain certain data to train its models.
- LAPD and many other customers are renegotiating contracts specifically to add language barring the company from using collected data.
- CEO Garrett Langley defends the perpetual training-data license as a standard software industry provision necessary for continuous improvement of AI and machine learning models.
NOT READ in full. Carries Flock's own defense of the perpetual license, which the dossier should quote rather than paraphrase when it is read at source.
The revised terms give Flock exclusive control over the method, timing, format and medium of a customer's access to its own data, with cities receiving degraded low-resolution copies stripped of metadata such as timestamps - which means a city cannot independently verify the safeguards it promises residents.
Well supported
The case against thisAgencies retain access through Flock's own interface and audit tools, which is how the misuse cases were in fact documented. The point is that the verification runs through the vendor, which is why Las Cruces councilors are asking for an independently run portal.
4 sources
American Civil Liberties Union · 2026-04-16 · Primary · national
ACLU analysis of Flock's revised terms and conditions, identifying four changes that shift control of the data from the customer city to the company.
- The clause Flock does not own and shall not sell Customer Data is absent from the updated terms.
- New terms grant Flock the exclusive right to determine and control the method, timing, format, and medium of a customer's access to its own data - with customers receiving degraded, low-resolution copies lacking metadata such as timestamps.
- Flock gains perpetual rights to use customer data to support and improve its services, retaining access after the customer's contract terminates.
- Expanded liability protections shield Flock even for willful misconduct or gross negligence; disputes go to private arbitration under Georgia law; and termination is made harder, including where cities decline or defund programs.
- ACLU advises municipalities to examine the changes closely, seek legal counsel before entering or renewing, and consider not installing mass surveillance systems at all.
The degraded-copy point deserves emphasis: a city that cannot get full-resolution data with metadata cannot independently audit its own system, which undercuts every locally promised safeguard including case-number verification.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
KFOX 14 · 2026-06-24 · Primary · local:dona-ana-county
The county sheriff's office expanding its Flock deployment, with the clearest statement in the corpus of the safeguards a New Mexico agency claims to apply.
- About 30 cameras currently deployed, with 22 more planned within a year.
- 162,000 dollars approved for the yearly subscription and new cameras, already within the sheriff's approved budget, under one consolidated agreement.
- Lt. Eric Flores: there has to be a case number and therefore a crime associated with that vehicle.
- Flores: the cameras aren't used to surveil just everyday citizens.
- Flores: we've been able to basically solve many many crimes that normally we wouldn't have had leads on.
- Stated safeguards include monthly self-audits verifying that each query has an associated case number.
This is the local case FOR the cameras, and the dossier must carry it at full strength. Two things to test rather than assume: the case-number requirement is exactly the kind of control the national audit logs show being satisfied by free-text entries, and a MONTHLY SELF-AUDIT is the agency checking its own work - the same self-assessment weakness built into SB 40's reporting. Neither observation disproves the claim; both are checkable against the county's own SB 40 report due April 1, 2027.
The Fourth Amendment's target was structural, not merely intrusive: writs of assistance let officers search any house without naming the house or the goods, never expired, and were called by James Otis in 1761 the worst instrument of arbitrary power - the objection was that they named no person, no place and no thing.
Well supported1 of 3 sources not read at source
The case against thisApplying an eighteenth-century objection to house-searching to twenty-first-century photography of cars on public roads is an analogy, and courts have not accepted it as to ALPRs. The analogy's force is structural - a standing, unexpiring, unparticularized power to search - not sentimental.
3 sources
National Constitution Center · 1761-02-24 · Primary · national
The founding-era argument against general warrants, delivered by James Otis before the Superior Court of Massachusetts in 1761.
- Writs of assistance authorized customhouse officers to search any house for smuggled goods without specifying either the house or the goods.
- Otis called the writ the worst instrument of arbitrary power.
- Otis lost the case; John Adams later wrote that his argument was the moment when the Child Independence was born.
- Colonial resistance to the writs produced the Fourth Amendment's demand that a valid warrant particularly describe the place to be searched.
The historical anchor for the dossier's central claim. The operative feature of a general warrant was never its intrusiveness in a single instance - it was that it named no person, no place and no thing, and did not expire. That is a structural description, and it is testable against an ALPR network.
Constitution Annotated, Library of Congress · undated · Primary · national
Congress's own annotated constitutional history of the Fourth Amendment's origins in resistance to general warrants and writs of assistance.
- Colonial experience of and resistance to the writs informed the Fourth Amendment's demand that a valid warrant particularly describe the place to be searched.
- Renewed customs efforts to obtain writs after 1767 produced the resistance that led to the prohibition on unreasonable searches and seizures.
NOT READ in full; undated. Preferred over advocacy sources for the historical claim because it is the Library of Congress rather than a party to the argument.
Supreme Court of the United States · 2018-06-22 · Primary · national
Held that acquiring historical cell-site location information is a Fourth Amendment search requiring a warrant, and that the third-party doctrine does not extend to comprehensive location records.
- Seven days or more of historical cell-site location information is a search requiring a warrant.
- Roberts drew on the aggregation reasoning of the Alito and Sotomayor concurrences in United States v. Jones (2012).
- The opinion grounds the analysis in the Founding-era reaction to general warrants and writs of assistance.
The general-warrant framing is the dossier's spine: the objection is not to any single photograph but to a standing power to rummage retroactively.
ICE does hold a direct national license plate reader contract - with Motorola's Vigilant, not Flock. More than 9,000 ICE personnel have had access to a commercial database of roughly two billion plate records growing by about 100 million a month, which also feeds Palantir and Thomson Reuters CLEAR.
Well supported1 of 4 sources not read at source
The case against thisFlock's statement that it does not work with ICE remains accurate about Flock. The dollar figures and dates here span 2018 to 2026 across mixed reporting and need verification before being stated in the present tense.
4 sources
Homeland Security Today · 2018-01-08 · Secondary · national
ICE contracted directly with Vigilant Solutions for nationwide license plate reader data on a sole-source basis - the contract Flock's ICE denial does not cover.
- ICE issued a sole source contract to Vigilant Solutions, per a justification and approval notice published January 8, 2018.
- Reported at more than 7 million dollars initially, with a 22.8 million dollar contract for database access running through 2026.
- Since late 2017 more than 9,000 ICE personnel have had access to privately collected plate scans from the 50 most populous US metro areas, plus millions more scans from local law enforcement.
- The Vigilant database is described as containing nearly two billion records and growing by roughly 100 million records per month, sourced from local law enforcement and vehicle repossession agencies.
- Vigilant data feeds into Palantir systems and is accessible through Thomson Reuters CLEAR.
THE DECISIVE ECOSYSTEM FACT. Flock's statement that it does not work with ICE is accurate about Flock and irrelevant to the question a resident is actually asking. ICE has held a direct national ALPR contract for years - with Motorola's Vigilant, not Flock. Dates and dollar figures here span 2018 to 2026 and come from mixed reporting; verify the current contract status before citing the 22.8 million figure as present-tense.
American Civil Liberties Union · undated · Primary · national
ACLU account of DHS access to commercial license plate databases.
- Documents DHS component access to commercially collected plate location data.
NOT READ; undated. Ingested as the advocacy counterpart to the ICE-Vigilant contract reporting. Read before citing.
American Civil Liberties Union · undated · Primary · national
Survey of the non-Flock ALPR market, principally Motorola Solutions' Vigilant and its commercial DRN arm.
- DRN is a Motorola Solutions company; Vigilant gives police access to the same commercially collected data.
- DRN contracts with tow trucks and other fleet vehicles to carry cameras and collect plate reads as they drive.
- Law enforcement customers have access to billions of historical scans, with tens of millions of new scans added monthly.
- Motorola markets historical travel analysis over an archive spanning more than 17 years.
Establishes that banning one vendor does not end the dragnet. Specific scan counts vary widely across sources and vendor marketing; treat each figure as vendor-claim unless independently sourced.
Flock Safety · 2026-02-01 · Vendor claim · national
Flock's own position on ICE access, plus the administrative controls it added in early 2026.
- Flock states it does not work with ICE and that ICE has no direct access to Flock cameras, systems or data unless the agencies controlling that data expressly and deliberately allow it.
- January 2026: Flock added an admin setting letting any agency turn off all federal sharing with a single toggle.
- February 2026: Flock added a post-login disclaimer citing CJIS requirements and relevant state immigration and reproductive care laws.
Tiered vendor-claim. The denial is narrowly true and beside the point: the documented route was never a direct ICE contract but local agencies running lookups and passing results on, plus federal agents using local officers' credentials. Note ICE has cooperative agreements with more than 2,300 jurisdictions.
Because ICE contracts directly with a different vendor and commercial collectors gather plate data with no government contract at all, a city that cancels Flock has narrowed its exposure without ending it.
Well supported
The case against thisNarrowing exposure is still a real result, and a local government can only control its own contracts. The argument is for state and federal action alongside local cancellation, not against cancellation.
3 sources
Homeland Security Today · 2018-01-08 · Secondary · national
ICE contracted directly with Vigilant Solutions for nationwide license plate reader data on a sole-source basis - the contract Flock's ICE denial does not cover.
- ICE issued a sole source contract to Vigilant Solutions, per a justification and approval notice published January 8, 2018.
- Reported at more than 7 million dollars initially, with a 22.8 million dollar contract for database access running through 2026.
- Since late 2017 more than 9,000 ICE personnel have had access to privately collected plate scans from the 50 most populous US metro areas, plus millions more scans from local law enforcement.
- The Vigilant database is described as containing nearly two billion records and growing by roughly 100 million records per month, sourced from local law enforcement and vehicle repossession agencies.
- Vigilant data feeds into Palantir systems and is accessible through Thomson Reuters CLEAR.
THE DECISIVE ECOSYSTEM FACT. Flock's statement that it does not work with ICE is accurate about Flock and irrelevant to the question a resident is actually asking. ICE has held a direct national ALPR contract for years - with Motorola's Vigilant, not Flock. Dates and dollar figures here span 2018 to 2026 and come from mixed reporting; verify the current contract status before citing the 22.8 million figure as present-tense.
American Civil Liberties Union · undated · Primary · national
Survey of the non-Flock ALPR market, principally Motorola Solutions' Vigilant and its commercial DRN arm.
- DRN is a Motorola Solutions company; Vigilant gives police access to the same commercially collected data.
- DRN contracts with tow trucks and other fleet vehicles to carry cameras and collect plate reads as they drive.
- Law enforcement customers have access to billions of historical scans, with tens of millions of new scans added monthly.
- Motorola markets historical travel analysis over an archive spanning more than 17 years.
Establishes that banning one vendor does not end the dragnet. Specific scan counts vary widely across sources and vendor marketing; treat each figure as vendor-claim unless independently sourced.
Police1 · 2024-02-08 · Secondary · national
Axon completed its acquisition of Fusus, whose platform aggregates live video, data and sensor feeds from many sources into a single real-time crime center view.
- Acquisition completed February 2024.
- Fusus aggregates live video, data and sensor feeds from disparate sources simultaneously.
- Axon has since announced fixed ALPR cameras (Outpost, Lightpost) and a Ring integration for citizen video sharing.
- Real-time crime centers have expanded to more than 250 cities and counties.
The fusion layer is the part that matters constitutionally: plate reads become a location dragnet only when joined to identity, video and other feeds in one interface.
Money from opioid litigation settlements has been spent on ALPR cameras: one Louisiana parish spent its entire 465,000 dollar allocation on Flock, Pensacola spent 108,000 dollars on 18 cameras, and 13 or more agencies were reported spending 920,000 dollars of settlement funds this way.
Well supported1 of 3 sources not read at source
The case against thisSettlement terms in some states permit law enforcement uses, and sheriffs argue drug interdiction is a legitimate application. A review panel majority nonetheless judged 66 percent of the evaluated Louisiana law enforcement spending inappropriate, and Pensacola reversed course.
3 sources
KFF Health News · 2026-08-27 · Primary · LA
Investigation into Louisiana sheriffs' spending of opioid settlement funds, including a parish that spent its entire allocation on Flock cameras.
- Louisiana is the only state directing 20 percent of opioid settlement payouts to sheriffs, the largest law enforcement carve-out nationwide.
- Terrebonne Parish spent its entire 465,000 dollars on Flock crime cameras.
- Of 38 sheriffs' offices giving evaluable detail, 29 had at least one expenditure judged an inappropriate use of opioid settlement money; a review panel majority disapproved of 66 percent of every dollar those offices reported spending.
- Sheriffs are not required to proactively report spending to the public, so tracking it requires records requests or waiting for audits.
Reported jointly with Verite News and STAT. The funding-source question is a distinct governance angle from the Fourth Amendment one and often lands harder locally: money settled for addiction treatment buying surveillance cameras.
Pensacola News Journal (via Yahoo) · 2026-01-01 · Secondary · FL
Pensacola's use of opioid litigation settlement money to buy Flock cameras, and the legal question it raised.
- In July 2025 Pensacola approved a two-year, 108,000 dollar contract for 18 Flock cameras using national opioid litigation settlement money.
- Public criticism focused on whether the funds should have gone to treatment rather than surveillance technology.
- Flock opponents later won a reversal, with no further opioid money going to cameras.
NOT READ in full; date approximate. Corroborates the Louisiana pattern in a second state, and shows the funding objection succeeding.
Wikipedia · 2026-08-01 · Secondary · national
Corporate timeline: founding, funding, product lines and a chronology of controversies.
- Founded 2017 by Garrett Langley, Paige Todd and Matt Feury; Langley is CEO.
- About 950 million dollars raised at a 7.5 billion dollar valuation as of 2025, including a 275 million dollar round in March 2025.
- Product lines: Falcon and Sparrow plate readers, Condor PTZ cameras, Raven gunshot detection (extended to human distress detection in October 2025), Nova data platform, and drones following the October 2024 Aerodome acquisition.
- Company-stated scale: over 5,000 communities in 49 states, 20 billion vehicle scans monthly.
- August 2024: Mother Jones reported 13 or more agencies spent 920,000 dollars of opioid settlement funds on Flock cameras.
- 2021: IPVM reported a 10 percent error rate and Flock halted sales to IPVM.
- Roanoke: 30 of 41 gunshot detectors installed in locations that were never approved.
- Verona, Wisconsin: cameras stayed operational three months after the contract was rejected; Cleveland cameras stayed active after expiration.
- Oshkosh, Wisconsin rescinded its contract in August 2026 citing false statements.
Wikipedia is a finding aid, not a citation. Every item above must be traced to its underlying source before it appears in the dossier; the operational scale figures are Flock's own marketing claims.
People are physically destroying ALPR cameras and being arrested for it; organizers against the cameras publicly reject vandalism, and the mapping projects have never called for disabling cameras. Fusion center bulletins nonetheless treat lawful advocacy and property destruction as one phenomenon.
Well supported
The case against thisCamera destruction is a genuine crime with genuine costs, including a fire near homes in one South Carolina case, and police attention to it is ordinary. The objection is to the conflation, not to investigating the vandalism.
3 sources
TechCrunch · 2026-02-23 · Secondary · national
Coverage of a national pattern of people physically destroying Flock cameras, and the arrests that follow.
- A national trend of individuals cutting down, burning or otherwise destroying ALPR cameras, with arrests across multiple states.
- August 2026: three 19-year-olds arrested in Chester County, South Carolina, charged with criminal conspiracy and destruction of property after cutting down a camera pole and striking the camera until its battery pack exploded and caught fire.
- July 2026: a man arrested in Monterey County, California, accused of damaging at least three cameras.
- A Suffolk man was charged with destroying 13 cameras.
- Anti-Flock organizers have publicly distanced themselves from vandalism; former Clover Town Council member Brittany Farr: I do not condone the defacing, damaging, or destruction of Flock cameras for any reason.
INCLUDED SO THE DOSSIER CAN DRAW THE LINE, NOT BLUR IT. Vandalism is a real phenomenon, it is a crime, and this project does not endorse it. It matters here for one reason: fusion center bulletins used it to justify monitoring lawful advocates, and organizers themselves reject it. Dates and details are from search summaries and need full-text confirmation.
404 Media · 2026-07-01 · Primary · national
State fusion centers circulated bulletins directing police to monitor anti-Flock advocacy on social media, warn of upcoming DeFlock events, and increase patrols around ALPR cameras.
- Fusion center bulletins monitored viral anti-Flock Instagram posts and warned local police about upcoming DeFlock events.
- Bulletins directed officers to increase patrols around ALPR cameras and warned about devices that could be used to identify camera locations.
- Dozens of state fusion centers circulated such memos across agencies during summer 2026, per documents obtained by journalist Dan Boguslaw.
- The documents tie people who politically oppose mass surveillance to vigilantes who destroy cameras.
- DeFlock creator Will Freeman said the project has never called for disabling cameras or covering plates, describing it as a grassroots mapping tool for civic engagement and local political pressure.
The sharpest First Amendment material in the corpus: the surveillance apparatus monitoring the people organizing against it. Keep the distinction Freeman draws - lawful mapping and advocacy versus camera vandalism - because the bulletins blur it and the dossier must not.
404 Media · 2025-01-01 · Primary · national
Flock sent a trademark cease and desist to Will Freeman, creator of the crowdsourced DeFlock camera map. EFF refused on his behalf and the map stayed up.
- Flock's lawyers demanded Freeman cease all use of the name DeFlock, claiming trademark dilution and false advertising.
- EFF replied that the demand had no legal basis and that the project sits within its First Amendment rights, citing anti-dilution carve-outs for noncommercial use and for criticism of a mark owner.
- DeFlock now hosts a crowdsourced map of more than 115,000 ALPR camera locations.
A company that maps every vehicle objecting to being mapped is the cleanest illustration of the asymmetry the dossier is about.
The documented path from evidence to consequence runs reporting to records request to official investigation to cancellation: 404 Media's work produced a congressional investigation, an Illinois Secretary of State investigation that found a violation of state law, and a wave of municipal cancellations.
Well supported
The case against thisThe reporting relied on audit logs that agencies released; where an agency refuses or a state exempts the records, the pipeline does not start. New Mexico's SB 40 IPRA carve-out is exactly that risk.
4 sources
IPVM · 2025-08-01 · Secondary · national
Account of how 404 Media's Flock reporting translated into official action.
- Jason Koebler notes the reporting spurred an ongoing congressional investigation and an ongoing Illinois Secretary of State investigation, with numerous towns dropping the system.
Useful for the causal chain from reporting to records request to oversight to cancellation - the mechanism this project is trying to reproduce locally.
Illinois Secretary of State · 2025-08-25 · Primary · IL
A state audit found Flock violated Illinois law by allowing U.S. Customs and Border Protection access to Illinois plate data. The Secretary of State ordered access cut off immediately.
- The audit sampled 12 local agencies and found Flock lacked proper data-sharing safeguards.
- Flock was running a CBP pilot program that, per the audit, its own leadership was unaware of.
- A 2023 Illinois law bars sharing plate data for out-of-state abortion or immigration investigations; the state also invoked the Illinois TRUST Act.
This is a government finding of law violation by a regulator with subpoena power, not an advocacy claim. It is among the strongest single sources in the corpus.
404 Media · 2025-08-08 · Primary · national
Members of Congress opened a formal investigation into Flock, demanding records of all searches touching ICE, CBP and abortion. The letter cites 404 Media's reporting directly.
- Rep. Raja Krishnamoorthi and Rep. Robert Garcia demanded details of all ICE, CBP and abortion-related searches of the national network.
- The investigation followed reporting that local police ran lookups on behalf of ICE and that a Texas officer searched nationwide for a woman who self-managed an abortion.
Article is partly paywalled; the findings above are the portion verifiable from the accessible text. Corroborated by the Wyden/Krishnamoorthi FTC letter of November 2025.
Washington Examiner · 2026-08-01 · Secondary · national
Tally of municipal cancellations across the country during 2026.
- Roughly 23 city councils voted to cancel, not renew, reject or deactivate Flock ALPRs since the start of 2026, across 23 states.
- Denver removed all 110 of its cameras when its contract expired March 31, 2026.
- Austin, Evanston, Oak Park, San Marcos, Sedona and Hays County among those that ended, rejected or declined to expand contracts.
Cancellation tallies vary widely by source and counting rule - 23 councils, 30-plus cities, 56 municipalities and 80 all appear in 2026 coverage. Do not print a total without naming the source's counting rule and date; these are not the same measure.
The weight of judicial authority currently runs AGAINST the argument this dossier makes: a federal court collecting the cases in 2025 found that nearly every court to address the question has held that querying an ALPR database is not a Fourth Amendment search.
Well supported
The case against thisThe same court signaled that changing ALPR capabilities could turn such queries into searches, and most of the collected cases predate networked nationwide systems, retroactive search across 80,000-plus cameras, and plate-to-person joins. But anyone who tells a council the courts have settled this in favor of privacy is wrong.
4 sources
United States District Court, Southern District of New York · 2025-09-19 · Secondary · NY
A federal district court collecting the ALPR case law and finding that nearly every court to address the question has held that querying an ALPR database is not a Fourth Amendment search - while signaling openness to revisiting that as the technology changes.
- The court collected cases showing that nearly every court addressing the issue has held ALPR database queries are not Fourth Amendment searches.
- The court indicated that changes in ALPR capabilities may be relevant in future cases and could turn such queries into searches.
THE SINGLE MOST IMPORTANT COUNTERPOINT IN THE CORPUS, and the dossier is weaker if it hides this. INGESTED SECOND-HAND from a commentary article; the opinion itself has NOT been read. Read it before quoting the nearly-every-court characterization, and check whether the collected cases predate the modern networked systems.
Flock Safety · undated · Vendor claim · national
Flock's own brief on why ALPRs survive Fourth Amendment scrutiny. Tiered vendor-claim, but it is the most efficient index of the authority running AGAINST this dossier's argument, and every case it names is real.
- Relies on United States v. Knotts (1983): travel on public roads reveals direction and stops without triggering the Fourth Amendment.
- Relies on United States v. Jones (2012) for the proposition that visual observation is not a search, the warrant requirement there resting on physical trespass.
- Argues Carpenter was expressly narrow and did not call into question conventional camera-based tools.
- Cites United States v. Yang (9th Cir. 2019) and United States v. Wilcox (11th Cir. 2011) as upholding warrantless ALPR use.
- Cites Schmidt v. City of Norfolk (E.D. Va. 2026) for the holding that limited, fixed-location ALPR deployments do not track the whole of a person's movements.
- Cites State v. Simonson (Wash. Ct. App. 2026): ALPR momentary observation of vehicles in public view does not invade a privacy expectation.
- Cites Commonwealth v. McCarthy (Mass.) and Commonwealth v. Church (Va. Ct. App. 2025), the latter rejecting the reasoning of Commonwealth v. Bell.
- Acknowledges Commonwealth v. Bell (Norfolk Cir. Ct. 2024) as the sole decision finding warrantless ALPR use unconstitutional, and notes multiple courts including the Virginia Court of Appeals have since rejected it.
- Design arguments: the systems log vehicles not people; fixed cameras produce discrete point-in-time observations rather than the roughly 101 pings per day at issue in Carpenter; a 30-day default retention with hard deletion prevents long-term dossiers; there is no ability to search specifically for images of people; agencies own their data; audit trails are retained indefinitely.
TIERED VENDOR-CLAIM, BUT READ IT ANYWAY - this is the argument that will be made back at any council. Two of its design claims are contradicted elsewhere in this corpus: the 30-day-default framing sits against Flock's own LPR policy page saying 7 days and against Virginia's 21-day statute, and 'no ability to search specifically for images of people' sits against the Condor product, which tracks people and can zoom on faces. Those are the two points to press.
WHRO Public Media · 2026-01-27 · Secondary · VA
Judge Davis ruled for the city on the merits, finding the Norfolk network not yet extensive enough to constitute a Fourth Amendment search, while warning that ALPR surveillance could cross that line.
- Plaintiff Lee Schmidt's vehicle was photographed 475 times in 4.5 months, with captures 40 to 50 minutes apart, leaving sizable gaps in his movements.
- 176 cameras at the time of the ruling, with Norfolk police planning more than 230 total.
- Virginia's searchable retention period is 21 days.
- Davis wrote that ALPR surveillance could become too intrusive at some point, but concluded not today for Norfolk.
- Plaintiffs, represented by the Institute for Justice, appealed.
Camera count differs across sources: 172 (Feb 2025 IJ), 175 and 176 (2026 coverage). The network grew; cite the count with its date. This ruling's gaps reasoning is the argument Chatrie later undercuts.
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
The cases against the dragnet argument are specific and should be named rather than waved at: Knotts (public roads), Jones (visual observation is not a search), Carpenter's express narrowness, Yang (9th Cir.), Wilcox (11th Cir.), Simonson (Wash. Ct. App. 2026), Church (Va. Ct. App. 2025) and the Norfolk summary judgment.
Well supported
The case against thisThese are collected from the vendor's own advocacy page and have not been read individually; verify each holding before relying on this list. That the list comes from Flock does not make it wrong.
3 sources
Flock Safety · undated · Vendor claim · national
Flock's own brief on why ALPRs survive Fourth Amendment scrutiny. Tiered vendor-claim, but it is the most efficient index of the authority running AGAINST this dossier's argument, and every case it names is real.
- Relies on United States v. Knotts (1983): travel on public roads reveals direction and stops without triggering the Fourth Amendment.
- Relies on United States v. Jones (2012) for the proposition that visual observation is not a search, the warrant requirement there resting on physical trespass.
- Argues Carpenter was expressly narrow and did not call into question conventional camera-based tools.
- Cites United States v. Yang (9th Cir. 2019) and United States v. Wilcox (11th Cir. 2011) as upholding warrantless ALPR use.
- Cites Schmidt v. City of Norfolk (E.D. Va. 2026) for the holding that limited, fixed-location ALPR deployments do not track the whole of a person's movements.
- Cites State v. Simonson (Wash. Ct. App. 2026): ALPR momentary observation of vehicles in public view does not invade a privacy expectation.
- Cites Commonwealth v. McCarthy (Mass.) and Commonwealth v. Church (Va. Ct. App. 2025), the latter rejecting the reasoning of Commonwealth v. Bell.
- Acknowledges Commonwealth v. Bell (Norfolk Cir. Ct. 2024) as the sole decision finding warrantless ALPR use unconstitutional, and notes multiple courts including the Virginia Court of Appeals have since rejected it.
- Design arguments: the systems log vehicles not people; fixed cameras produce discrete point-in-time observations rather than the roughly 101 pings per day at issue in Carpenter; a 30-day default retention with hard deletion prevents long-term dossiers; there is no ability to search specifically for images of people; agencies own their data; audit trails are retained indefinitely.
TIERED VENDOR-CLAIM, BUT READ IT ANYWAY - this is the argument that will be made back at any council. Two of its design claims are contradicted elsewhere in this corpus: the 30-day-default framing sits against Flock's own LPR policy page saying 7 days and against Virginia's 21-day statute, and 'no ability to search specifically for images of people' sits against the Condor product, which tracks people and can zoom on faces. Those are the two points to press.
United States District Court, Southern District of New York · 2025-09-19 · Secondary · NY
A federal district court collecting the ALPR case law and finding that nearly every court to address the question has held that querying an ALPR database is not a Fourth Amendment search - while signaling openness to revisiting that as the technology changes.
- The court collected cases showing that nearly every court addressing the issue has held ALPR database queries are not Fourth Amendment searches.
- The court indicated that changes in ALPR capabilities may be relevant in future cases and could turn such queries into searches.
THE SINGLE MOST IMPORTANT COUNTERPOINT IN THE CORPUS, and the dossier is weaker if it hides this. INGESTED SECOND-HAND from a commentary article; the opinion itself has NOT been read. Read it before quoting the nearly-every-court characterization, and check whether the collected cases predate the modern networked systems.
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
The camera map is already an open dataset: DeFlock stores submissions in OpenStreetMap rather than a private database, the ALPR-tagged node registry passed 336,000 worldwide by early 2026, and anyone can pull an area's camera points through the Overpass API. EFF separately publishes CC-BY licensed ALPR datasets built from public records.
Well supported
The case against thisThe 336,000 figure counts ALPR-tagged OSM nodes worldwide across all vendors and is NOT a count of Flock cameras; presenting it as one would be a serious error. Crowdsourced entries are unverified by construction.
3 sources
DeFlock / FoggedLens · 2026-01-01 · Secondary · national
The crowdsourced ALPR mapping project, which stores its data in OpenStreetMap rather than a private database - making the whole camera registry openly queryable.
- DeFlock does not run a private camera database; submissions go into OpenStreetMap, the openly licensed world map.
- By early 2026 the OpenStreetMap registry of ALPR-tagged nodes passed 336,000 worldwide, covering Flock plus other vendors including Motorola Vigilant, Axon Fleet and Genetec.
- The raw data can be queried through the Overpass API by selecting nodes tagged with a surveillance type of ALPR, pulling every camera point for an area at once.
- Created by the privacy-focused collective FoggedLens; Will Freeman is the founder.
DIRECTLY ACTIONABLE FOR THE MODULE: an Overpass API query bounded to New Mexico would give the /flock page a camera map without any scraping, from an openly licensed source that updates itself. Note the 336,000 figure is ALPR-tagged OSM nodes WORLDWIDE across all vendors - it is not a count of Flock cameras and must never be presented as one. Crowdsourced data is unverified by construction.
Electronic Frontier Foundation · undated · Primary · national
EFF's downloadable, openly licensed datasets on police surveillance technology, including several ALPR-specific collections built from public records.
- The Atlas of Surveillance main dataset is published as CSV and regularly updated.
- Data Driven - ALPR Data (January 2020): CSV from public records on Vigilant Solutions usage, including plates scanned, watch list matches and inter-agency sharing reports.
- Data Driven 2: California Dragnet (April 2021): covering 89 California law enforcement agencies.
- California Automated License Plate Readers (February 2020): raw, unaltered data from the California State Auditor survey obtained by CPRA request.
- All EFF materials are CC-BY licensed, reusable with attribution.
DIRECTLY ACTIONABLE FOR THE MODULE. These are openly licensed CSVs of exactly the kind the /flock module already ingests, and the CC-BY terms permit reuse with attribution. The Vigilant dataset is especially useful because the module currently has no non-Flock vendor data at all.
404 Media · 2025-01-01 · Primary · national
Flock sent a trademark cease and desist to Will Freeman, creator of the crowdsourced DeFlock camera map. EFF refused on his behalf and the map stayed up.
- Flock's lawyers demanded Freeman cease all use of the name DeFlock, claiming trademark dilution and false advertising.
- EFF replied that the demand had no legal basis and that the project sits within its First Amendment rights, citing anti-dilution carve-outs for noncommercial use and for criticism of a mark owner.
- DeFlock now hosts a crowdsourced map of more than 115,000 ALPR camera locations.
A company that maps every vehicle objecting to being mapped is the cleanest illustration of the asymmetry the dossier is about.
Las Cruces has not merely bought plate readers: its contract integrates with Peregrine, a data-fusion platform founded by a former Palantir executive that unifies body-camera footage, dispatch records and other feeds into one searchable real-time system serving agencies covering more than 80 million Americans.
Well supported
The case against thisPeregrine is a data management and search tool, and integrating records a department already holds is not new collection. The mosaic argument is precisely about aggregation, so the integration is the part worth examining rather than the cameras alone.
3 sources
Contrary Research / CB Insights / 9th Street Journal · 2025-08-01 · Secondary · national
The data-fusion platform that Las Cruces' Flock contract integrates with: it unifies fragmented law enforcement data - body camera footage, dispatch records and more - into a single real-time searchable system.
- Founded 2018 by former Palantir executive Nick Noone and technologist Ben Rudolph; roughly a quarter of the team are Palantir alumni.
- Unifies fragmented law enforcement data from body-camera footage to dispatch records into one real-time system for search, analysis and decision-making.
- As of August 2025 serves agencies covering more than 80 million Americans; 250 million dollars raised at a 2.5 billion dollar valuation.
- In Durham, residents objected to a police software contract citing data privacy and predictive policing concerns.
THE LOCAL HOOK. Las Cruces' contract includes a Peregrine integration, so the fusion layer this dossier describes in the abstract is already contracted for in Las Cruces. Company details come from investor-facing research profiles, which are promotional in tone - verify independently before citing figures.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
A retention limit is not what it appears to be. The Norfolk court records that a 21-day retention does not prevent long-term retention of ALPR data DOWNLOADED out of the system - and a New Mexico police chief told his own commission the same thing: data purges after 30 days unless downloaded and saved as evidence, and live-view footage used in an investigation can be downloaded and saved permanently.
Well supported
The case against thisDownloaded records are typically pulled into a specific case file, which is ordinary evidence handling and subject to its own rules. But it means every retention figure quoted to a council - 7 days, 21, 30, or New Mexico's none - describes the database, not the copies taken out of it.
4 sources
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
City of Alamogordo City Commission · 2026-08-11 · Primary · NM
The most thorough public accountability session on ALPR in the New Mexico record: a police chief answering commissioners' direct questions about retention, tracking, sharing, redaction, hacking and internal misuse. Several of his answers confirm arguments this dossier makes nationally.
- The city is under a TWO-YEAR agreement with Flock Safety.
- RETENTION: data is automatically purged after 30 days UNLESS DOWNLOADED AND SAVED AS EVIDENCE. Live-view data from major intersection cameras is kept 7 days.
- Asked whether data is saved when a crime occurs rather than erased, the chief said yes - officers can download and PERMANENTLY save live-view footage used in an investigation.
- SHARING: data is shared with other local police agencies, the minutes giving Dallas, Texas as an example, to track fleeing suspects - but not with federal agencies.
- Asked directly whether the cameras use AI to build a continuous database tracking citizens' movements past multiple cameras, the chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - but that Alamogordo's cameras are placed for single fixed-point reads rather than continuous tracking.
- The Flock system does not display driver's license, registration, insurance or immigration information - but officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
- Hot list alerts carry a 3 to 5 minute delay; partial plate and vehicle-characteristic searches are supported.
- Accounts are created manually by a single named administrator; policy requires a legitimate law enforcement reason for any search, per NCIC standards; the system is audited monthly, both programmatically and manually.
- The system does NOT automatically redact faces - redactions in the demonstration video were done manually by the City Clerk and her staff.
- Police have access to Flock cameras in business parking lots only if the business explicitly grants it, and no access to residential Ring cameras unless a resident shares footage.
- Cost framing offered by the chief: an officer costs the city about 94,000 dollars a year, and the Flock system essentially places an officer at a fixed point 24 hours a day, 365 days a year.
- Case examples given: a stolen-vehicle report resolved as a legal repossession, avoiding a high-risk felony stop; a sexual assault suspect arrested within 30 minutes from a vehicle description; an armed disturbance resolved in 2 minutes; a shooting suspect identified with nine felony charges within 4 hours.
- The department's hit-and-run crash rate increased by 76 percent.
ORIGINAL RESEARCH, 2026-08-30, from the Alamogordo CivicClerk record (August 11 minutes carried in the August 25 packet, file 3957). THIS IS THE BEST LOCAL ACCOUNTABILITY DOCUMENT IN THE CORPUS and it cuts in every direction at once. It is a model of what a commission SHOULD ask. It also contains a New Mexico chief confirming, in his own words, three things this dossier argues from national sources: the 30-day retention does not bind DOWNLOADED records; consecutive cameras would technically produce continuous tracking; and the plate is a bridge into NCIC even though Flock itself shows no registration or immigration data. And the sharing answer - not federal, but yes to other local agencies including in TEXAS - is precisely the route by which New Mexico data reaches a state with no ALPR statute. The stolen-vehicle-as-repossession example is a genuine harm PREVENTED, and belongs in the record too.
Flock Safety · undated · Vendor claim · national
Flock's public-facing LPR policy - the document a council is most likely to be shown.
- Flock states it defaults to deleting LPR data every 7 days on a rolling basis, adjustable per customer.
- States that LPR data gathered on behalf of customers is owned by the customer, who controls sharing.
- States Flock uses under 1 percent of LPR images, stripped of identifying information and metadata, solely to improve services through machine learning.
- States it will not sell, publish or disclose customer LPR data for commercial purposes without consent - but may disclose where legally required or where it reasonably believes access is necessary to comply with legal process, enforce agreements, or address security and fraud concerns.
Tiered vendor-claim, and the most important one in the corpus to hold against the contract. The policy page describes de-identified, sub-1-percent training use; the February 2026 terms DELETED the Training Data section imposing exactly those limits, and deleted the no-sale clause. A council shown this page is not being shown the agreement it would sign.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
The Norfolk court expressly said this experimentation is best handled with public input and with guardrails erected by state legislatures or local governing bodies - a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting.
Well supported
The case against thisA court declining to constitutionalize an issue and pointing to legislatures is also a court declining to help. The invitation cuts both ways, but it is quotable at a council in a way that a loss is not.
3 sources
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
American Civil Liberties Union · undated · Primary · national
The ACLU's national organizing toolkit: how to find cameras, read the contract, and press a council, plus model policy language.
- Three phases: locate cameras, engage the council, organize a coalition.
- Points to DeFlock, HaveIBeenFlocked, EFF's Atlas of Surveillance and ALPR.watch for locating cameras.
- Model guardrails: retention limited to hours or days rather than weeks or more; no sharing absent a felony warrant; use restricted to defined scenarios; annual public reporting.
- Records guidance: search council agendas, minutes and consent agendas for ALPR items, then request the contract directly.
This project's get-the-flock-out micronode is deliberately named after this campaign; the dossier should link to the ACLU toolkit rather than compete with it.
The gaps-in-coverage framing widely reported from Norfolk is narrower than it sounds: the same order acknowledges Baltimore's aerial program left multi-hour gaps and was still held a search. What distinguished Norfolk was coverage of 75 designated areas rather than everyone everywhere outside.
Well supported1 of 3 sources not read at source
The case against thisThe distinction is real - a camera at an intersection is not a plane over a city - but it is a distinction about comprehensiveness of coverage, not about temporal gaps, and it gets weaker as camera density rises.
3 sources
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
United States Court of Appeals for the Fourth Circuit · 2021-06-24 · Primary · national
The en banc Fourth Circuit held that Baltimore's Aerial Investigation Research program - persistent aerial surveillance of the whole city - was a Fourth Amendment search under Carpenter, because the analysis must consider not only the raw data but what that data can reveal.
- Held that accessing the aerial surveillance program's data is a search requiring a warrant.
- Established in this circuit that the inquiry looks to what data can reveal, not merely to what was individually collected.
NOT YET READ IN FULL; ingested via EPIC's brief, which quotes it at 344. This is binding precedent in the circuit now deciding Schmidt, which makes it the most consequential authority in the corpus. Read the opinion before the dossier characterizes its holding any further.
Electronic Privacy Information Center · 2026-04-20 · Primary · VA
EPIC's Fourth Circuit brief urging reversal in Norfolk. The single best distillation of the constitutional argument in the corpus, written to persuade a federal appellate court, and it rests on the Fourth Circuit's own binding precedent rather than on Carpenter alone.
- District court case number is 2:24-cv-00621-MSD-LRL, E.D. Va., Judge Mark S. Davis; appeal is No. 26-1227.
- Central argument: the court need only follow its own established rule in Leaders of a Beautiful Struggle v. Baltimore Police Department, 2 F.4th 330 (4th Cir. 2021), which assessed Baltimore's aerial surveillance program by looking at not only the raw data but what that data can reveal.
- Frames the Fourth Amendment guideposts from Carpenter as securing the privacies of life against arbitrary power (Boyd) and placing obstacles in the way of a too permeating police surveillance (Di Re).
- Argues modern ALPR systems must be judged on evolving capabilities and the inferences they enable, per Kyllo and Carpenter, not as scattered individual data points.
- Second argument: AI-enabled ALPR systems are predictive policing systems, built on unvetted, outdated and biased data overrepresenting poor and minority populations, generating suspicion inside a proprietary black box that cannot be examined or challenged - implicating the Fourth, Fifth and Sixth Amendments.
- Concludes that absent strict safeguards ALPRs revive the arbitrary powers of the reviled general warrant, and that a warrant is the proper first obstacle.
- From the litigation record (JA citations), Flock's system can stream live video and capture clips, identify other vehicles traveling with a vehicle of interest, and analyze a vehicle's past travel history to offer probabilities for where it will go next.
- Cites CRS R48160: as of 2020 every police department serving over one million residents, and about 90 percent of sheriffs' offices with 500 or more sworn deputies, were already using ALPRs.
- Notes Virginia's default retention was up to 30 days at the time of the relevant events and up to 21 days under Va. Code 2.2-5517 as of briefing, with longer retention where data is deemed relevant to an ongoing investigation.
READ IN FULL from the filed PDF on 2026-08-30. The Leaders of a Beautiful Struggle argument is the most important legal find in this corpus: it is binding Fourth Circuit precedent holding persistent aerial surveillance a search, in the very circuit now hearing Norfolk. The predictive-policing framing is also the strongest available answer to the it-is-just-photographs defense, because the system's own marketed features include next-location prediction.
EFF's formal position, published in August 2026, is that ALPR mass surveillance is irredeemably harmful and should not exist - with warrant requirements, deletion deadlines and use restrictions as harm reduction only if elimination fails.
Well supported
The case against thisThis dossier does not adopt that position. It argues the warrant requirement and the transparency instruments, which is a narrower ask; a reader should be able to see the difference rather than have the two blurred together.
2 sources
Electronic Frontier Foundation · 2026-08-26 · Primary · national
EFF's formal position, published four days before this dossier: ALPR mass surveillance should not exist, and where it cannot be eliminated it should be constrained by warrant requirements, deletion deadlines and use restrictions.
- EFF calls for complete elimination, describing ALPR mass surveillance as irredeemably harmful and not fixable by policy adjustment alone.
- Harm-reduction measures if elimination is not achievable: a warrant requirement for police database searches, data deletion deadlines, and use restrictions limiting database access.
- Core argument: the danger is indiscriminate, continuous collection and retention of location data on every driver regardless of suspicion, which technical safeguards cannot remedy.
- Points to state-level statutory limits, citing California approaches as precedent.
The clearest statement of the maximalist position, and worth naming as such. This dossier's own posture is narrower - it argues the warrant requirement and the transparency instruments rather than elimination - and a reader should be able to see the difference.
Electronic Frontier Foundation · 2026-08-01 · Primary · national
EFF's assessment of the reform package Flock announced in 2026, arguing the changes leave the underlying dragnet intact.
- Flock conceded its technology required reform after sustained reporting and oversight.
- EFF's position is that feature-level changes cannot make a warrantless, retroactively searchable national network constitutional.
Pair with govtech-2025-illinois-pledge and the NBC reform coverage so the reform debate is presented from both sides.
A single PBS News Hour segment puts both cases on the record side by side - a police chief describing a recovered stolen vehicle with a 14-month-old inside, and a journalist explaining why a warrantless national database qualitatively changes the surveillance - which makes it the most useful single artifact to hand someone who has heard only one side.
Well supported
1 source
PBS News Hour · 2026-07-15 · Secondary · national
National broadcast segment putting both sides on the record, and the source of Flock's largest public efficacy claim.
- Flock's Josh Thomas claims the technology helps solve somewhere between 800,000 and a million crimes every calendar year, and that it accounts for roughly 20 to 25 percent of all reported crime in America.
- Aurora Police Chief Todd Chamberlain describes a December 2024 case tracking a stolen vehicle with a 14-month-old inside, and says without that Flock technology we might not have found that for two or three days later.
- 404 Media's Joseph Cox: when you have a national database of these cameras that can be queried by law enforcement without a warrant, that qualitatively shifts something about the surveillance.
- Denver resident Chrisanna Elser interviewed as someone wrongly accused on incomplete data matching.
- Cites over 100,000 Flock cameras across all 50 states, 30-day searchable retention, and dozens of cities cancelling in the past year.
THE 20-25 PERCENT CLAIM NEEDS HANDLING WITH CARE. It is a vendor claim delivered on air with no stated methodology, and its phrasing - accounts for 20 to 25 percent of all reported crime - does not define what accounts for means. Do not repeat it, and do not dismiss it either; ask what the denominator is. The same segment is the best single artifact showing both cases side by side, which makes it useful to hand to a council member who has heard only one.
This is no longer a trade-press or advocacy story: it has been covered by PBS News Hour, NPR, CBS News and the Washington Post, alongside the trade and independent outlets that broke it.
Well supported4 of 5 sources not read at source
The case against thisBreadth of coverage is not evidence about the underlying facts. It matters for one practical reason: a council member who discounts EFF or 404 Media can be handed a PBS segment instead.
5 sources
PBS News Hour · 2026-07-15 · Secondary · national
National broadcast segment putting both sides on the record, and the source of Flock's largest public efficacy claim.
- Flock's Josh Thomas claims the technology helps solve somewhere between 800,000 and a million crimes every calendar year, and that it accounts for roughly 20 to 25 percent of all reported crime in America.
- Aurora Police Chief Todd Chamberlain describes a December 2024 case tracking a stolen vehicle with a 14-month-old inside, and says without that Flock technology we might not have found that for two or three days later.
- 404 Media's Joseph Cox: when you have a national database of these cameras that can be queried by law enforcement without a warrant, that qualitatively shifts something about the surveillance.
- Denver resident Chrisanna Elser interviewed as someone wrongly accused on incomplete data matching.
- Cites over 100,000 Flock cameras across all 50 states, 30-day searchable retention, and dozens of cities cancelling in the past year.
THE 20-25 PERCENT CLAIM NEEDS HANDLING WITH CARE. It is a vendor claim delivered on air with no stated methodology, and its phrasing - accounts for 20 to 25 percent of all reported crime - does not define what accounts for means. Do not repeat it, and do not dismiss it either; ask what the denominator is. The same segment is the best single artifact showing both cases side by side, which makes it useful to hand to a council member who has heard only one.
NPR · 2026-02-17 · Secondary · national
National radio coverage of the municipal cancellation wave and the immigration-access concerns driving it.
- Attributes cancellations principally to privacy concerns and federal immigration agents accessing local data.
NOT READ in full. Useful as a mainstream-outlet corroboration of the cancellation trend for audiences that discount advocacy sources.
The Washington Post · 2026-08-13 · Secondary · national
Major-newspaper coverage of Flock's August 2026 reform announcements.
- Reports Flock announcing changes in response to sustained public backlash.
NOT READ; likely paywalled. Recorded so the corpus reflects that the story reached national newspapers of record, not only trade and advocacy press.
CBS News · 2026-01-01 · Secondary · national
Consumer-facing explainer on how an individual can check whether their own plate appears in Flock search records.
- Describes how a member of the public can check whether their plate has been searched, via tools including HaveIBeenFlocked.
NOT READ; date approximate. Practically the most useful item in the corpus for an ordinary resident, and the mechanism by which several officer-misuse cases were discovered by their victims.
InvestigateTV · 2026-08-01 · Secondary · national
Broadcast investigative special examining law enforcement use of Flock cameras and the state of oversight.
- Investigative television treatment of Flock usage and oversight gaps.
NOT WATCHED; date approximate. Recorded with a canonical watch URL. Brendan Keefe is an established investigative broadcaster, which makes this worth actually viewing and summarizing properly.
An ordinary resident can check whether their own plate has been searched - the mechanism by which several officer-misuse cases were discovered by their victims rather than by any oversight body.
Well supported1 of 3 sources not read at source
The case against thisThese lookup tools are third-party and their coverage and accuracy vary; a negative result is not proof no search occurred. The authoritative record is the agency's own audit log.
3 sources
CBS News · 2026-01-01 · Secondary · national
Consumer-facing explainer on how an individual can check whether their own plate appears in Flock search records.
- Describes how a member of the public can check whether their plate has been searched, via tools including HaveIBeenFlocked.
NOT READ; date approximate. Practically the most useful item in the corpus for an ordinary resident, and the mechanism by which several officer-misuse cases were discovered by their victims.
Institute for Justice · 2026-08-01 · Primary · national
Running tally of officers documented using ALPR systems to track current or former romantic partners, compiled from arrests, charges and internal investigations.
- At least 50 U.S. officers face accusations or charges of misusing plate readers, mostly Flock systems.
- In Georgia, IJ and Reason documented 18 officer arrests across multiple counties for Flock database misuse.
- Joplin, Missouri: one officer ran a single woman's plate nearly 400 times, accounting for about a quarter of the department's searches.
- Milwaukee: an officer tracked a partner and the partner's ex nearly 180 times over two months; surfaced only when the victims looked themselves up on HaveIBeenFlocked.com.
- Kentucky, August 2026: an officer was arrested after tracking his ex-girlfriend more than 2,000 times.
Counts rise as new cases are charged; cite the figure with its date. Nearly every case surfaced through an audit log or a victim's own lookup, not through the vendor's monitoring.
Electronic Frontier Foundation · 2026-06-01 · Primary · national
A how-to for residents seeking their own agency's network audit to determine whether local cameras have been searched for immigration purposes.
- Network audit logs are obtainable by public records request and record the stated reason for each search.
- The audit is the document that shows whether local cameras served federal immigration enforcement.
This is the operational bridge between the dossier and the module: the same audit file the /flock module already ingests is the one residents are told to request.
The most common response in a council chamber is not a legal argument but the nothing-to-hide objection, and the dossier should be ready for it with an answer rather than an eye-roll.
Well supported
The case against thisThese talks are a decade old and not ALPR-specific; they are rhetoric to borrow, never evidence about Flock. The strongest concrete answer is the record itself - the abortion search, the officers stalking partners, the immigration lookups - all involving people who had nothing to hide.
4 sources
TED · 2014-10-10 · Secondary · national
The standard answer to the nothing-to-hide argument, delivered at TEDGlobal in Rio.
- Argues for why privacy matters to people who believe they are doing nothing wrong.
Not ALPR-specific. Included because the nothing-to-hide objection is the single most common response in a council chamber, and this is the best-known rebuttal to hand someone. Cite it as rhetoric, never as evidence about Flock.
TED · 2014-01-01 · Secondary · national
On the private industry that grew up to sell surveillance capability to governments - the structural point that most closely anticipates the Flock model.
- Describes governments buying surveillance capability through private companies rather than building it themselves.
Not ALPR-specific and now over a decade old. Its relevance is the structure it names: the capability is procured from a vendor, which is why a vendor's contract terms end up governing a constitutional question.
Electronic Frontier Foundation · 2025-10-01 · Primary · TX
Court documents contradict Flock's and the Johnson County, Texas sheriff's public characterization of a nationwide plate search as a missing-person welfare check. The records describe a death investigation of a non-viable fetus after a self-managed abortion.
- Search reason recorded in the audit log: had an abortion, search for female.
- Two searches: one across 17,684 cameras on 1,295 networks, a second across 83,345 cameras on 6,809 networks.
- Searches ran about 2.5 hours after the initial call, roughly two weeks after the abortion.
- Flock publicly called critical coverage misleading, false and clickbait, and said she was searched for as a missing person, not a suspect.
- The lead detective's affidavit shows investigators consulted prosecutors about charges and collected abortion documentation; no charges were filed.
This is the anchor case for the vendor-credibility problem: the company's public account and the sworn record diverge. The dossier should present both and let the documents decide.
Institute for Justice · 2026-08-01 · Primary · national
Running tally of officers documented using ALPR systems to track current or former romantic partners, compiled from arrests, charges and internal investigations.
- At least 50 U.S. officers face accusations or charges of misusing plate readers, mostly Flock systems.
- In Georgia, IJ and Reason documented 18 officer arrests across multiple counties for Flock database misuse.
- Joplin, Missouri: one officer ran a single woman's plate nearly 400 times, accounting for about a quarter of the department's searches.
- Milwaukee: an officer tracked a partner and the partner's ex nearly 180 times over two months; surfaced only when the victims looked themselves up on HaveIBeenFlocked.com.
- Kentucky, August 2026: an officer was arrested after tracking his ex-girlfriend more than 2,000 times.
Counts rise as new cases are charged; cite the figure with its date. Nearly every case surfaced through an audit log or a victim's own lookup, not through the vendor's monitoring.
Five cameras in a low-crime Virginia town of no particular note captured more than 60,000 vehicles a month and were accessed by outside agencies 6.9 million times in twelve months. A small town's procurement decision is a national exposure decision.
Well supported
The case against thisThis covers June 2024 to June 2025, before Virginia's ALPR law took effect, so it describes an unregulated baseline rather than current practice. That is precisely why it is the right comparison for a New Mexico town: it is what the arrangement looks like with no statute in place.
3 sources
Virginia Center for Investigative Journalism at WHRO · 2025-09-17 · Primary · VA
The single clearest illustration of how a small town's five cameras become national infrastructure: Bridgewater, Virginia, low crime, five cameras, and 6.9 million outside accesses in twelve months.
- Bridgewater, Virginia has five Flock cameras capturing more than 60,000 vehicles a month despite a low crime rate.
- Outside law enforcement agencies across the country accessed Bridgewater's data 6.9 million times over twelve months through the Flock network.
- Built from network audit data obtained through multiple public records requests.
- A companion VCIJ analysis found nearly 3,000 immigration-related searches on Virginia's Flock network over a recent twelve-month period.
THE BEST SINGLE ANALOGY FOR A SMALL NEW MEXICO TOWN. Five cameras is a scale any village council recognizes; 6.9 million outside accesses is the part nobody votes on. Note the Virginia State Crime Commission's own report cites this story and points out it covers June 2024 to June 2025, BEFORE Virginia's ALPR law took effect - so it describes the unregulated baseline, which is exactly what pre-SB 40 New Mexico was.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
Cameras contracted by school districts have been searched for immigration enforcement: in one Texas district's audit logs, searches for civil immigration reasons were more than TWICE as frequent as those involving immigrants suspected or convicted of a crime. About 100 school districts nationwide contract with Flock.
Well supported
The case against thisThe searches were run by police agencies, not by school staff, and a camera on a school's perimeter photographs a public street like any other. The civil-versus-criminal ratio is nonetheless the direct answer to the claim that this targets dangerous criminals.
3 sources
The 74 (with The Guardian) · 2026-02-01 · Primary · national
Joint investigation finding police searching a national ALPR database - including cameras contracted by school districts - for immigration purposes, built from hundreds of thousands of audit log entries.
- Hundreds of thousands of audit log entries over a month show police searching the national ALPR database, including school district cameras, for immigration-related investigations.
- The audit logs came from Texas school districts contracting with Flock.
- In the Alvin school district logs, searches for civil immigration reasons - such as locating someone unlawfully present - were more than twice as frequent as those involving immigrants suspected or convicted of a crime.
- Roughly 100 school districts nationwide have contracted with Flock, per government procurement records.
- ICE has no official contract with Flock but has asked state and local agencies to search cameras on its behalf.
The civil-versus-criminal ratio is the finding that answers the standard defense that this targets dangerous criminals. Published with The Guardian in February 2026. Relevant to Las Cruces, whose contract integrates cameras on the outside of PUBLIC SCHOOL buildings.
404 Media · 2025-06-01 · Primary · national
After the ICE and abortion reporting, Flock cut off national lookups into cameras located in Illinois, California and Virginia. The company's ability to make that change unilaterally is itself evidence about who controls the data.
- Flock blocked out-of-state agencies from searching cameras inside Illinois, California and Virginia.
- More than 4,000 lookups had been run at the behest of federal agencies for immigration purposes, giving federal law enforcement side-door access to a tool it had no formal contract for.
- The Danville network audit alone contained 307 immigration-related searches by Texas agencies, going back to June 2024.
Vendor-side switch-flipping cuts both ways as evidence: it shows the sharing was a policy choice, not a technical necessity.
Illinois Secretary of State · 2025-08-25 · Primary · IL
A state audit found Flock violated Illinois law by allowing U.S. Customs and Border Protection access to Illinois plate data. The Secretary of State ordered access cut off immediately.
- The audit sampled 12 local agencies and found Flock lacked proper data-sharing safeguards.
- Flock was running a CBP pilot program that, per the audit, its own leadership was unaware of.
- A 2023 Illinois law bars sharing plate data for out-of-state abortion or immigration investigations; the state also invoked the Illinois TRUST Act.
This is a government finding of law violation by a regulator with subpoena power, not an advocacy claim. It is among the strongest single sources in the corpus.
New Mexico regulated ALPR sharing while its general consumer data privacy bill died in the same session - so the commercial layer, including data brokers and fleet-based plate collection, is untouched by New Mexico law.
Well supported
The case against thisSB 40 does reach non-law-enforcement ALPR operators within the state, so the gap is narrower than none. But nothing in New Mexico law reaches a national commercial plate database compiled outside it.
4 sources
ACLU of New Mexico · 2026-02-01 · Primary · NM
New Mexico's attempted comprehensive consumer data privacy bill, which failed in the 2026 session - leaving the state without a general data privacy law behind SB 40.
- SB 53, CHISPA, sponsored by Sen. Angel Charley, would have required online for-profit entities to obtain consent before collecting information nonessential to their business.
- Would have applied to entities processing data from as few as 15,000 consumers, well below the 100,000 threshold common elsewhere, with an affirmative necessity standard for most processing.
- Included a private right of action with penalties of 2,500 dollars per negligent and 7,500 dollars per intentional violation per affected consumer.
- Passed the Senate Health and Public Affairs Committee but failed to advance; as of May 2026 New Mexico has no comprehensive consumer data privacy law.
Important context for SB 40's limits: New Mexico regulated ALPR sharing specifically while its general data privacy bill died. The commercial layer - data brokers, DRN-style fleet collection - is therefore untouched by New Mexico law. Advocacy-source summary of a bill; read the bill text before describing provisions as law, which they are not.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
American Civil Liberties Union · undated · Primary · national
Survey of the non-Flock ALPR market, principally Motorola Solutions' Vigilant and its commercial DRN arm.
- DRN is a Motorola Solutions company; Vigilant gives police access to the same commercially collected data.
- DRN contracts with tow trucks and other fleet vehicles to carry cameras and collect plate reads as they drive.
- Law enforcement customers have access to billions of historical scans, with tens of millions of new scans added monthly.
- Motorola markets historical travel analysis over an archive spanning more than 17 years.
Establishes that banning one vendor does not end the dragnet. Specific scan counts vary widely across sources and vendor marketing; treat each figure as vendor-claim unless independently sourced.
Homeland Security Today · 2018-01-08 · Secondary · national
ICE contracted directly with Vigilant Solutions for nationwide license plate reader data on a sole-source basis - the contract Flock's ICE denial does not cover.
- ICE issued a sole source contract to Vigilant Solutions, per a justification and approval notice published January 8, 2018.
- Reported at more than 7 million dollars initially, with a 22.8 million dollar contract for database access running through 2026.
- Since late 2017 more than 9,000 ICE personnel have had access to privately collected plate scans from the 50 most populous US metro areas, plus millions more scans from local law enforcement.
- The Vigilant database is described as containing nearly two billion records and growing by roughly 100 million records per month, sourced from local law enforcement and vehicle repossession agencies.
- Vigilant data feeds into Palantir systems and is accessible through Thomson Reuters CLEAR.
THE DECISIVE ECOSYSTEM FACT. Flock's statement that it does not work with ICE is accurate about Flock and irrelevant to the question a resident is actually asking. ICE has held a direct national ALPR contract for years - with Motorola's Vigilant, not Flock. Dates and dollar figures here span 2018 to 2026 and come from mixed reporting; verify the current contract status before citing the 22.8 million figure as present-tense.
Virginia is the most useful comparison for New Mexico: it legislated a year earlier, its own legislature then audited compliance and found agencies out of step, it hosts the leading federal litigation, and its communities are still organizing.
Well supported1 of 4 sources not read at source
The case against thisVirginia's statute and politics differ from New Mexico's, and its ALPR law is not SB 40. The value is methodological - it shows what to measure a year after a statute passes.
4 sources
Virginia State Crime Commission · 2026-01-21 · Primary · VA
A state legislative commission's survey of every law enforcement agency in Virginia, measuring ALPR adoption, vendor share and statutory compliance after Virginia's 2025 ALPR law took effect. The only rigorous state-level census of ALPR use in the corpus.
- All 361 Virginia law enforcement agencies were surveyed; 251 responded, a 70 percent response rate.
- 63 percent of responding agencies (159 of 251) reported using ALPR.
- 86 percent of ALPR-using agencies (137 of 159) reported Flock Safety as their vendor.
- The Commission found that some Virginia agencies are NOT using ALPR in accordance with the new statute.
- Almost one-third of agencies did not respond at all, so their ALPR use is unknown.
- Before legislation effective July 1, 2025, no statewide statutory or regulatory framework governed law enforcement ALPR use in Virginia - no limits on use, retention or sharing.
- As of December 2025, Charlottesville and Staunton were ending their ALPR use.
- Cites Virginia Center for Investigative Journalism, September 16 2025: one small Virginia town's surveillance network recorded nearly 7 million hits, based on June 2024 to June 2025 data.
READ from the Commission's own PDF on 2026-08-30. Directly relevant to New Mexico: Virginia passed its ALPR law a year before SB 40, and its own legislature found agencies out of compliance and a third of agencies simply not answering. That is the empirical answer to anyone who says SB 40 settles the New Mexico question. The 86 percent Flock share is also the best evidence that vendor-specific reform is close to sector-wide reform.
Virginia Center for Investigative Journalism at WHRO · 2025-09-17 · Primary · VA
The single clearest illustration of how a small town's five cameras become national infrastructure: Bridgewater, Virginia, low crime, five cameras, and 6.9 million outside accesses in twelve months.
- Bridgewater, Virginia has five Flock cameras capturing more than 60,000 vehicles a month despite a low crime rate.
- Outside law enforcement agencies across the country accessed Bridgewater's data 6.9 million times over twelve months through the Flock network.
- Built from network audit data obtained through multiple public records requests.
- A companion VCIJ analysis found nearly 3,000 immigration-related searches on Virginia's Flock network over a recent twelve-month period.
THE BEST SINGLE ANALOGY FOR A SMALL NEW MEXICO TOWN. Five cameras is a scale any village council recognizes; 6.9 million outside accesses is the part nobody votes on. Note the Virginia State Crime Commission's own report cites this story and points out it covers June 2024 to June 2025, BEFORE Virginia's ALPR law took effect - so it describes the unregulated baseline, which is exactly what pre-SB 40 New Mexico was.
Virginia Center for Investigative Journalism at WHRO · 2026-08-14 · Secondary · VA
Follow-up on Virginia communities organizing against Flock deployments.
- Documents continued local pushback in Virginia as deployments spread.
NOT READ in full. Virginia is the most useful comparison state for New Mexico: it legislated a year earlier, its legislature audited compliance, and it hosts the leading federal litigation.
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
McCarthy supplies a usable test rather than a bare outcome: would a person reasonably expect their movements to be aggregated so government can ascertain at will their political and religious beliefs and habits; does the system reveal more than a passerby would observe; and does the aggregate yield a detailed profile of associations - political, religious, amicable and amorous.
Well supported
The case against thisMcCarthy applied those factors and still found no search. The factors are a framework, not a verdict, and running them honestly on a small deployment may produce the answer that it does not cross the line.
3 sources
Berkeley Journal of Criminal Law, Vol. 26:1 · 2021-01-01 · Primary · national
Law review survey of how lower courts have applied the mosaic theory after Carpenter, with a dedicated section on ALPRs. It supplies the analytical framework - McCarthy's factors - for asking whether a given network crosses the line.
- Surveys post-Carpenter lower court decisions across cell-site data, GPS, ALPRs, pole cameras, telephony metadata and aerial surveillance, both applying and declining the mosaic theory.
- Finds that while courts have been willing to APPLY the mosaic theory to ALPRs, they have unanimously concluded that ALPR use to track individuals is not a search.
- In McCarthy the court explicitly adopted the mosaic theory as its theoretical foundation, reasoning that the color of a single stone depicts little but by stepping back one can see a complete mosaic.
- McCarthy's factors: whether a person would reasonably expect movements to be recorded and aggregated so government can ascertain at will their political and religious beliefs and sexual habits; whether the government action revealed more than a passerby would normally observe; and what the aggregate reveals - a highly detailed profile not simply of where we go but by easy inference of our associations, political, religious, amicable and amorous.
- Quotes the reasoning that the whole of a person's movements over a month is not actually exposed to the public because the likelihood a stranger would observe all of them is essentially nil.
- The McCarthy facts: four ALPRs on two bridges, a spreadsheet of dates, times, directions and lanes over about ten weeks, showing 48 crossings.
- Author was a J.D. candidate at UC Berkeley; article published 2021.
READ IN PART on 2026-08-30 - the introduction and the ALPR section. THE USEFUL PART IS THE TEST, not the outcome. McCarthy's three factors are a checklist a council or a court can run against a specific deployment, and the underlying facts are the comparison that matters: FOUR cameras on two bridges producing 48 crossings in ten weeks was held not a search. Norfolk was 176 cameras and 475 photographs of one car in four and a half months. Doña Ana County plans 52. Note the article is from 2021 and predates the networked national systems.
Massachusetts Supreme Judicial Court · 2020-04-16 · Primary · MA
The first appellate decision applying the Fourth Amendment to ALPRs. The court adopted the mosaic approach: four cameras on two bridges did not invade a reasonable expectation of privacy, but enough readers in enough places would.
- Police used ALPRs on the Bourne and Sagamore bridges to track the defendant's crossings over three months.
- Held: a person has a constitutionally protected expectation of privacy in the whole of his public movements.
- Held: the limited extent of this ALPR use did not invade that interest, but historical data from enough readers in enough locations would constitute a search.
McCarthy is the case both sides cite. It sets a threshold rather than a rule, which is exactly why camera density and retention are the facts that decide these cases.
Electronic Privacy Information Center · 2026-04-20 · Primary · VA
EPIC's Fourth Circuit brief urging reversal in Norfolk. The single best distillation of the constitutional argument in the corpus, written to persuade a federal appellate court, and it rests on the Fourth Circuit's own binding precedent rather than on Carpenter alone.
- District court case number is 2:24-cv-00621-MSD-LRL, E.D. Va., Judge Mark S. Davis; appeal is No. 26-1227.
- Central argument: the court need only follow its own established rule in Leaders of a Beautiful Struggle v. Baltimore Police Department, 2 F.4th 330 (4th Cir. 2021), which assessed Baltimore's aerial surveillance program by looking at not only the raw data but what that data can reveal.
- Frames the Fourth Amendment guideposts from Carpenter as securing the privacies of life against arbitrary power (Boyd) and placing obstacles in the way of a too permeating police surveillance (Di Re).
- Argues modern ALPR systems must be judged on evolving capabilities and the inferences they enable, per Kyllo and Carpenter, not as scattered individual data points.
- Second argument: AI-enabled ALPR systems are predictive policing systems, built on unvetted, outdated and biased data overrepresenting poor and minority populations, generating suspicion inside a proprietary black box that cannot be examined or challenged - implicating the Fourth, Fifth and Sixth Amendments.
- Concludes that absent strict safeguards ALPRs revive the arbitrary powers of the reviled general warrant, and that a warrant is the proper first obstacle.
- From the litigation record (JA citations), Flock's system can stream live video and capture clips, identify other vehicles traveling with a vehicle of interest, and analyze a vehicle's past travel history to offer probabilities for where it will go next.
- Cites CRS R48160: as of 2020 every police department serving over one million residents, and about 90 percent of sheriffs' offices with 500 or more sworn deputies, were already using ALPRs.
- Notes Virginia's default retention was up to 30 days at the time of the relevant events and up to 21 days under Va. Code 2.2-5517 as of briefing, with longer retention where data is deemed relevant to an ongoing investigation.
READ IN FULL from the filed PDF on 2026-08-30. The Leaders of a Beautiful Struggle argument is the most important legal find in this corpus: it is binding Fourth Circuit precedent holding persistent aerial surveillance a search, in the very circuit now hearing Norfolk. The predictive-policing framing is also the strongest available answer to the it-is-just-photographs defense, because the system's own marketed features include next-location prediction.
The comparison that makes the mosaic argument concrete: FOUR cameras on two bridges, producing 48 crossings over ten weeks, was held not a search in McCarthy. Norfolk is 176 cameras and 475 photographs of a single car in four and a half months. Doña Ana County is heading for 52 and Las Cruces has dozens.
Well supported
The case against thisCamera counts are not directly comparable across cases - what matters legally is coverage of a person's movements, not the number of devices. Norfolk's 176 cameras covering 75 areas were still held insufficient, so raw counts alone do not decide it.
5 sources
Berkeley Journal of Criminal Law, Vol. 26:1 · 2021-01-01 · Primary · national
Law review survey of how lower courts have applied the mosaic theory after Carpenter, with a dedicated section on ALPRs. It supplies the analytical framework - McCarthy's factors - for asking whether a given network crosses the line.
- Surveys post-Carpenter lower court decisions across cell-site data, GPS, ALPRs, pole cameras, telephony metadata and aerial surveillance, both applying and declining the mosaic theory.
- Finds that while courts have been willing to APPLY the mosaic theory to ALPRs, they have unanimously concluded that ALPR use to track individuals is not a search.
- In McCarthy the court explicitly adopted the mosaic theory as its theoretical foundation, reasoning that the color of a single stone depicts little but by stepping back one can see a complete mosaic.
- McCarthy's factors: whether a person would reasonably expect movements to be recorded and aggregated so government can ascertain at will their political and religious beliefs and sexual habits; whether the government action revealed more than a passerby would normally observe; and what the aggregate reveals - a highly detailed profile not simply of where we go but by easy inference of our associations, political, religious, amicable and amorous.
- Quotes the reasoning that the whole of a person's movements over a month is not actually exposed to the public because the likelihood a stranger would observe all of them is essentially nil.
- The McCarthy facts: four ALPRs on two bridges, a spreadsheet of dates, times, directions and lanes over about ten weeks, showing 48 crossings.
- Author was a J.D. candidate at UC Berkeley; article published 2021.
READ IN PART on 2026-08-30 - the introduction and the ALPR section. THE USEFUL PART IS THE TEST, not the outcome. McCarthy's three factors are a checklist a council or a court can run against a specific deployment, and the underlying facts are the comparison that matters: FOUR cameras on two bridges producing 48 crossings in ten weeks was held not a search. Norfolk was 176 cameras and 475 photographs of one car in four and a half months. Doña Ana County plans 52. Note the article is from 2021 and predates the networked national systems.
Massachusetts Supreme Judicial Court · 2020-04-16 · Primary · MA
The first appellate decision applying the Fourth Amendment to ALPRs. The court adopted the mosaic approach: four cameras on two bridges did not invade a reasonable expectation of privacy, but enough readers in enough places would.
- Police used ALPRs on the Bourne and Sagamore bridges to track the defendant's crossings over three months.
- Held: a person has a constitutionally protected expectation of privacy in the whole of his public movements.
- Held: the limited extent of this ALPR use did not invade that interest, but historical data from enough readers in enough locations would constitute a search.
McCarthy is the case both sides cite. It sets a threshold rather than a rule, which is exactly why camera density and retention are the facts that decide these cases.
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
KFOX 14 · 2026-06-24 · Primary · local:dona-ana-county
The county sheriff's office expanding its Flock deployment, with the clearest statement in the corpus of the safeguards a New Mexico agency claims to apply.
- About 30 cameras currently deployed, with 22 more planned within a year.
- 162,000 dollars approved for the yearly subscription and new cameras, already within the sheriff's approved budget, under one consolidated agreement.
- Lt. Eric Flores: there has to be a case number and therefore a crime associated with that vehicle.
- Flores: the cameras aren't used to surveil just everyday citizens.
- Flores: we've been able to basically solve many many crimes that normally we wouldn't have had leads on.
- Stated safeguards include monthly self-audits verifying that each query has an associated case number.
This is the local case FOR the cameras, and the dossier must carry it at full strength. Two things to test rather than assume: the case-number requirement is exactly the kind of control the national audit logs show being satisfied by free-text entries, and a MONTHLY SELF-AUDIT is the agency checking its own work - the same self-assessment weakness built into SB 40's reporting. Neither observation disproves the claim; both are checkable against the county's own SB 40 report due April 1, 2027.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
A 2021 law review survey found that courts have been willing to APPLY the mosaic theory to ALPRs and have nonetheless unanimously concluded that ALPR tracking is not a search - so the doctrine being available has not been enough.
Well supported
The case against thisThe survey predates the networked national systems, retroactive nationwide search and plate-to-person joins now at issue, and Rinaldi expressly left room for changing capabilities to change the answer.
2 sources
Berkeley Journal of Criminal Law, Vol. 26:1 · 2021-01-01 · Primary · national
Law review survey of how lower courts have applied the mosaic theory after Carpenter, with a dedicated section on ALPRs. It supplies the analytical framework - McCarthy's factors - for asking whether a given network crosses the line.
- Surveys post-Carpenter lower court decisions across cell-site data, GPS, ALPRs, pole cameras, telephony metadata and aerial surveillance, both applying and declining the mosaic theory.
- Finds that while courts have been willing to APPLY the mosaic theory to ALPRs, they have unanimously concluded that ALPR use to track individuals is not a search.
- In McCarthy the court explicitly adopted the mosaic theory as its theoretical foundation, reasoning that the color of a single stone depicts little but by stepping back one can see a complete mosaic.
- McCarthy's factors: whether a person would reasonably expect movements to be recorded and aggregated so government can ascertain at will their political and religious beliefs and sexual habits; whether the government action revealed more than a passerby would normally observe; and what the aggregate reveals - a highly detailed profile not simply of where we go but by easy inference of our associations, political, religious, amicable and amorous.
- Quotes the reasoning that the whole of a person's movements over a month is not actually exposed to the public because the likelihood a stranger would observe all of them is essentially nil.
- The McCarthy facts: four ALPRs on two bridges, a spreadsheet of dates, times, directions and lanes over about ten weeks, showing 48 crossings.
- Author was a J.D. candidate at UC Berkeley; article published 2021.
READ IN PART on 2026-08-30 - the introduction and the ALPR section. THE USEFUL PART IS THE TEST, not the outcome. McCarthy's three factors are a checklist a council or a court can run against a specific deployment, and the underlying facts are the comparison that matters: FOUR cameras on two bridges producing 48 crossings in ten weeks was held not a search. Norfolk was 176 cameras and 475 photographs of one car in four and a half months. Doña Ana County plans 52. Note the article is from 2021 and predates the networked national systems.
United States District Court, Southern District of New York · 2025-09-19 · Secondary · NY
A federal district court collecting the ALPR case law and finding that nearly every court to address the question has held that querying an ALPR database is not a Fourth Amendment search - while signaling openness to revisiting that as the technology changes.
- The court collected cases showing that nearly every court addressing the issue has held ALPR database queries are not Fourth Amendment searches.
- The court indicated that changes in ALPR capabilities may be relevant in future cases and could turn such queries into searches.
THE SINGLE MOST IMPORTANT COUNTERPOINT IN THE CORPUS, and the dossier is weaker if it hides this. INGESTED SECOND-HAND from a commentary article; the opinion itself has NOT been read. Read it before quoting the nearly-every-court characterization, and check whether the collected cases predate the modern networked systems.
The network was built on roughly 658 million dollars of venture capital across eight rounds, led latterly by Andreessen Horowitz, with early money from Y Combinator and Thiel-associated funds, at an 8.4 billion dollar valuation as of April 2026 - a private company whose internal policies are, in a senator's words, the only safeguards for hundreds of millions of Americans.
Well supported
The case against thisPeter Thiel is NOT a founder or board member; Founders Fund holds a minority stake from the 2025 round. That association is frequently overstated, and overstating it costs credibility on everything else. Venture funding is also not itself an argument about constitutionality.
3 sources
Flock Safety / TechCrunch / Bedrock Capital · 2026-04-17 · Secondary · national
Who capitalized the network: roughly 658 million dollars over eight rounds, led latterly by Andreessen Horowitz, with early money from Y Combinator and Thiel-associated funds.
- About 658 million dollars raised over eight rounds; Series D and E of 150 million each, and a 275 million dollar Series F in March 2025 at a 7.5 billion dollar valuation.
- Series D led by Andreessen Horowitz with Matrix and Bedrock; later rounds added Greenoaks, Meritech, Sands Capital, Founders Fund, Kleiner Perkins, Tiger Global and Y Combinator.
- Early venture capital came substantially from PayPal-associated firms including Peter Thiel's Founders Fund, Bedrock Capital, Y Combinator and Initialized Capital.
- Peter Thiel is not a founder or board member; Founders Fund invested in the 2025 Series F and holds a minority stake.
- Valued at 8.4 billion dollars as of April 17, 2026, and cited at 8.3 billion in Hawley's August 2026 letter.
Assembled from mixed sources including the company's own announcements and an ownership-explainer site of unverified quality; treat individual figures as approximate. The Thiel detail is included WITH its correction - he is not a founder or board member - because that association is frequently overstated, and a dossier that overstates it loses credibility on everything else.
Office of U.S. Senator Josh Hawley · 2026-08-26 · Primary · national
The chairman of the Senate Judiciary Subcommittee on Crime and Counterterrorism opened an investigation into Flock, demanding documents from CEO Garrett Langley. Notable because it puts congressional scrutiny of Flock on a bipartisan footing.
- Sen. Josh Hawley, chairman of the Judiciary Subcommittee on Crime and Counterterrorism, opened the investigation August 26, 2026.
- Documents and information demanded from CEO Garrett Langley by September 8, 2026.
- Hawley: Congress never authorized the network your industry has built.
- Hawley: Your company's internal policies are, in practice, the only safeguards for hundreds of millions of Americans.
- Hawley: Americans do not surrender their privacy rights when they drive to work, drop their kids off at school, or go to church.
- Cites more than 120,000 cameras across 49 states, more than 20 billion vehicle scans monthly, and an 8.3 billion dollar valuation.
Pairs with wyden-2025-ftc-letter to show scrutiny is not partisan - a Democratic senator and representative in November 2025, a Republican subcommittee chairman in August 2026. That framing matters in a council chamber. The demand annex was not published with the release; the response deadline has likely passed and the reply is worth seeking.
KFF Health News · 2026-08-27 · Primary · LA
Investigation into Louisiana sheriffs' spending of opioid settlement funds, including a parish that spent its entire allocation on Flock cameras.
- Louisiana is the only state directing 20 percent of opioid settlement payouts to sheriffs, the largest law enforcement carve-out nationwide.
- Terrebonne Parish spent its entire 465,000 dollars on Flock crime cameras.
- Of 38 sheriffs' offices giving evaluable detail, 29 had at least one expenditure judged an inappropriate use of opioid settlement money; a review panel majority disapproved of 66 percent of every dollar those offices reported spending.
- Sheriffs are not required to proactively report spending to the public, so tracking it requires records requests or waiting for audits.
Reported jointly with Verite News and STAT. The funding-source question is a distinct governance angle from the Fourth Amendment one and often lands harder locally: money settled for addiction treatment buying surveillance cameras.
Public counts of New Mexico ALPR cameras - 983 across 51 municipalities, or 955 statewide depending on the tracker - are crowdsourced and disagree with each other. They are for locating cameras to verify, not for citing as totals.
Well supported
The case against thisThe authoritative count will be SB 40's Section 4 reporting, where each agency must state total cameras owned or leased - first due April 1, 2027.
3 sources
MyTownView / DeFlock The USA / flockcameralocations.com · 2026-08-01 · Secondary · NM
Crowdsourced counts of ALPR cameras across New Mexico, useful for locating deployments and useless as an authoritative total.
- One tracker documents 983 cameras across 51 New Mexico municipalities; DeFlock reports 955 ALPR readers statewide, ranking New Mexico 30th of 52 states and territories.
- Documented deployments include Las Cruces, Albuquerque, Santa Fe, Rio Rancho, Roswell, Farmington, Bloomfield, Milan, Capitan, Hobbs, Clovis, Los Lunas, Taos, Carlsbad and Alamogordo.
- Otero County alone shows 56 documented cameras; Doña Ana County 99.
- In late July 2026 the Town of Taos Council voted to end its Flock contract.
CROWDSOURCED AND UNVERIFIED BY CONSTRUCTION. The two headline totals disagree (983 vs 955) because of differing collection dates and methods, and several of these sites are ad-supported aggregators of DeFlock/OpenStreetMap data rather than independent collectors. Use for LOCATING cameras to verify in person or by records request; never cite as an authoritative count. The Taos cancellation should be confirmed against the council's own minutes.
DeFlock / FoggedLens · 2026-01-01 · Secondary · national
The crowdsourced ALPR mapping project, which stores its data in OpenStreetMap rather than a private database - making the whole camera registry openly queryable.
- DeFlock does not run a private camera database; submissions go into OpenStreetMap, the openly licensed world map.
- By early 2026 the OpenStreetMap registry of ALPR-tagged nodes passed 336,000 worldwide, covering Flock plus other vendors including Motorola Vigilant, Axon Fleet and Genetec.
- The raw data can be queried through the Overpass API by selecting nodes tagged with a surveillance type of ALPR, pulling every camera point for an area at once.
- Created by the privacy-focused collective FoggedLens; Will Freeman is the founder.
DIRECTLY ACTIONABLE FOR THE MODULE: an Overpass API query bounded to New Mexico would give the /flock page a camera map without any scraping, from an openly licensed source that updates itself. Note the 336,000 figure is ALPR-tagged OSM nodes WORLDWIDE across all vendors - it is not a count of Flock cameras and must never be presented as one. Crowdsourced data is unverified by construction.
EFF Atlas of Surveillance · 2025-07-01 · Primary · local:las-cruces
Atlas of Surveillance record for Las Cruces PD ALPR deployment, sourced to public records.
- Vendor: Flock Safety.
- 22 automated license plate readers, per records obtained July 2025.
- Source cited: public records via MuckRock.
22 devices here against 45 readers in the February 2026 Haussamen reporting. Not necessarily a contradiction - different dates and possibly different device categories - but the dossier must present both with their dates rather than pick one.
All three neighboring states that New Mexico agencies share ALPR data with - Arizona, Colorado and Texas - are among 26 states with NO ALPR legislation at all. SB 40's written-declaration requirement is the only instrument standing between New Mexico data and three unregulated jurisdictions.
Well supported
The case against thisA written declaration is a real legal instrument with a 10,000 dollar penalty behind it, and Bernalillo County's sheriff has already barred specific counties over ICE connections. But the declaration is enforced by New Mexico against a New Mexico sharer - it does not bind the out-of-state recipient once the data has moved.
4 sources
Government Technology, reporting the NYU Policing Project analysis · 2026-08-18 · Primary · national
The Policing Project at NYU School of Law scored every state's ALPR regulation on seven criteria. The finding that matters most to New Mexico is about its neighbors.
- Seven criteria: privacy protections, false positive verification, data sharing protocols, protest monitoring restrictions, compliance audits, transparency requirements, and enforcement mechanisms.
- Highest scorers at 6 of 7: Connecticut, Oregon, Virginia and Washington.
- TWENTY-SIX STATES HAVE NO ALPR LEGISLATION AT ALL, including Arizona, Colorado and Texas.
- Washington D.C., Florida and Tennessee have laws that do not meet the organization's definition of effective regulation.
- New Mexico is not referenced in the article; individual scores are not published for most states.
THE LOCAL POINT IS THE NEIGHBORS. Bernalillo County shared ALPR data with 88 agencies including some in Arizona, Colorado and Texas - and all three of those states have NO ALPR statute whatsoever. New Mexico's SB 40 written declaration requirement is therefore the only instrument standing between New Mexico data and three unregulated jurisdictions. New Mexico's own score is not stated here; retrieve the underlying Policing Project scorecard directly.
KOB 4 · undated · Primary · NM
Statewide New Mexico accounting of which agencies run ALPRs, how long they keep the data, and who they share it with.
- Bernalillo County Sheriff's Office: 21 fixed cameras planned, 30-day retention, sharing with 88 agencies including some in Arizona, Colorado and Texas.
- Albuquerque Police Department: about 250 fixed cameras, one-year retention.
- New Mexico State Police: 180-day retention, sharing with hundreds of agencies including Border Patrol and ATF.
- At the time of reporting, no New Mexico law regulated ALPR access or retention.
- Sheriff John Allen on the technology: it is really a no brainer.
- NMSP Chief Troy Weisler declined an interview.
Publication date not stated on the page; the reporting predates SB 40 and the August 2026 BCSO cancellation, both of which changed the picture. Date must be pinned before this is cited for current state.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
The policy work is done and does not need reinventing: the Brennan Center's seven recommendations - immediate deletion of non-matching scans, retention in days not months, a warrant for historical searches, two-step scanning, independent hot-list verification, published policies with disclosed audit results, and disparate-impact audits - map almost one to one onto what Las Cruces councilors are asking for.
Well supported
The case against thisThe Brennan report is from 2020 and its legal-status section is superseded by Rinaldi, Norfolk and Chatrie. The recommendations are the durable part, but a council adopting them should have counsel confirm they fit New Mexico law as it stands after SB 40.
4 sources
Brennan Center for Justice · 2020-09-10 · Primary · national
Seven concrete policy recommendations for ALPR regulation - the closest thing in the corpus to ready-made ordinance language for a city council.
- Retention and warrants: delete non-matching plate scans immediately; if retained, limit to days rather than months; require a warrant for historical database searches absent emergency.
- Two-step scanning: the first query reveals only registration and hot-list status, and accessing personal information requires a basis for further police action.
- Hot list verification: mandate independent verification of hot-list data and real-time updates to prevent erroneous stops.
- Public transparency and input: communities participate in deployment decisions; policies published; audit results disclosed.
- Audit logs: track automated alerts, officer access to historical data, and all inter-agency data-sharing arrangements.
- Disparate impact audits: evaluate whether deployment disproportionately targets marginalized communities or protected activities.
- Safeguard effectiveness audits: regular review that access controls and retention actually function.
- Legal status as of 2020: no bright-line warrant rule; appeals courts had avoided direct engagement with Carpenter's application to ALPR.
READ on 2026-08-30, closing a gap this dossier had flagged as unread. Published 2020, so its legal-status section is superseded by Rinaldi, Norfolk and Chatrie - but the RECOMMENDATIONS are the durable part and map almost one to one onto what Las Cruces councilors are asking for. Hot-list verification and two-step scanning are the two that directly address the wrong-car gunpoint stops.
American Civil Liberties Union · undated · Primary · national
The ACLU's national organizing toolkit: how to find cameras, read the contract, and press a council, plus model policy language.
- Three phases: locate cameras, engage the council, organize a coalition.
- Points to DeFlock, HaveIBeenFlocked, EFF's Atlas of Surveillance and ALPR.watch for locating cameras.
- Model guardrails: retention limited to hours or days rather than weeks or more; no sharing absent a felony warrant; use restricted to defined scenarios; annual public reporting.
- Records guidance: search council agendas, minutes and consent agendas for ALPR items, then request the contract directly.
This project's get-the-flock-out micronode is deliberately named after this campaign; the dossier should link to the ACLU toolkit rather than compete with it.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Government Technology, reporting the NYU Policing Project analysis · 2026-08-18 · Primary · national
The Policing Project at NYU School of Law scored every state's ALPR regulation on seven criteria. The finding that matters most to New Mexico is about its neighbors.
- Seven criteria: privacy protections, false positive verification, data sharing protocols, protest monitoring restrictions, compliance audits, transparency requirements, and enforcement mechanisms.
- Highest scorers at 6 of 7: Connecticut, Oregon, Virginia and Washington.
- TWENTY-SIX STATES HAVE NO ALPR LEGISLATION AT ALL, including Arizona, Colorado and Texas.
- Washington D.C., Florida and Tennessee have laws that do not meet the organization's definition of effective regulation.
- New Mexico is not referenced in the article; individual scores are not published for most states.
THE LOCAL POINT IS THE NEIGHBORS. Bernalillo County shared ALPR data with 88 agencies including some in Arizona, Colorado and Texas - and all three of those states have NO ALPR statute whatsoever. New Mexico's SB 40 written declaration requirement is therefore the only instrument standing between New Mexico data and three unregulated jurisdictions. New Mexico's own score is not stated here; retrieve the underlying Policing Project scorecard directly.
The specific fix for wrong-car stops at gunpoint is not better cameras but hot-list hygiene and procedure: independent verification of hot-list data, real-time updates, and a two-step process where the first query returns only registration and hot-list status.
Well supported
The case against thisMost of these incidents also involved an officer failing to visually verify the plate before drawing a weapon, which is a training and use-of-force question no database rule reaches.
3 sources
Brennan Center for Justice · 2020-09-10 · Primary · national
Seven concrete policy recommendations for ALPR regulation - the closest thing in the corpus to ready-made ordinance language for a city council.
- Retention and warrants: delete non-matching plate scans immediately; if retained, limit to days rather than months; require a warrant for historical database searches absent emergency.
- Two-step scanning: the first query reveals only registration and hot-list status, and accessing personal information requires a basis for further police action.
- Hot list verification: mandate independent verification of hot-list data and real-time updates to prevent erroneous stops.
- Public transparency and input: communities participate in deployment decisions; policies published; audit results disclosed.
- Audit logs: track automated alerts, officer access to historical data, and all inter-agency data-sharing arrangements.
- Disparate impact audits: evaluate whether deployment disproportionately targets marginalized communities or protected activities.
- Safeguard effectiveness audits: regular review that access controls and retention actually function.
- Legal status as of 2020: no bright-line warrant rule; appeals courts had avoided direct engagement with Carpenter's application to ALPR.
READ on 2026-08-30, closing a gap this dossier had flagged as unread. Published 2020, so its legal-status section is superseded by Rinaldi, Norfolk and Chatrie - but the RECOMMENDATIONS are the durable part and map almost one to one onto what Las Cruces councilors are asking for. Hot-list verification and two-step scanning are the two that directly address the wrong-car gunpoint stops.
Electronic Frontier Foundation · 2024-11-01 · Primary · national
Case-by-case account of innocent drivers stopped at gunpoint after ALPR misreads or stale hot-list entries, with settlement figures.
- Brittney Gilliam, Aurora, Colorado, August 2020: a Colorado SUV matched to a stolen Montana motorcycle plate; family detained at gunpoint with children face-down on pavement; Aurora settled for 1.9 million dollars.
- Denise Green, San Francisco, March 2009: reader misread a 3 as a 7; officers drew guns; city paid 495,000 dollars.
- Jaclynn Gonzales, Espanola, New Mexico: reader mistook a 2 for a 7; detained at gunpoint, her 12-year-old sister placed in a patrol vehicle.
- Jason Burkleo, Atherton, California: misread an H as an M; detained at gunpoint.
- Brian Hofer, Contra Costa County, Thanksgiving 2019: hot list not updated after the vehicle was recovered; 49,500 dollar settlement.
- Isoke Robinson, Detroit: police queried all Dodge Chargers near a shooting; handcuffed at home, 2-year-old placed in a patrol car, car impounded three weeks.
- Cited study: ALPRs misread the state of one in ten plates, before counting other reading errors.
The Espanola case is the New Mexico entry in this list and belongs in the local chapter as well as the harms chapter.
Central Current · 2024-08-13 · Primary · NY
Syracuse councilors approved a 26-camera Flock deployment without knowing about published research on the system's error rate; several said so afterward.
- IPVM research found Flock misread the state on roughly 1 in 10 plates, logged plate reads multiple times, and regularly got vehicle characteristics and car make wrong.
- A majority of the Common Council was unaware of the research before voting; at least four councilors expressed concern on learning of it.
- Councilor Rita Paniagua: I had no idea that there's a percent of misreads.
- The council approved the 26-camera deployment on July 1, 2024.
The cleanest documented instance of the procurement failure this project's alpr_staff_reports subsystem is built to detect: the decision-makers did not have the material fact. Directly transferable to a Las Cruces or Dona Ana County council question - what were you told about the error rate before you voted?
A warrant requirement on police would not touch the commercial layer: the repossession industry built a private nationwide plate-location database that DRN sells to insurers, private investigators and resellers, reportedly for about 20 dollars a search, and a reporter used it to track a specific person from a plate number alone.
Well supported
The case against thisThis reporting is from 2019 and pricing and products may have changed. New Mexico's SB 40 does bar sharing ALPR information with non-law-enforcement, which reaches in-state operators - but nothing in New Mexico law reaches a national commercial database compiled elsewhere, and the state's general privacy bill died.
4 sources
Vice / Techdirt / ABC7 Los Angeles · 2019-09-23 · Primary · national
The layer no council ever votes on: a private plate-location database built by the repossession industry and sold to insurers, private investigators and anyone else who pays.
- Digital Recognition Network, a Fort Worth company, is the largest provider of license-plate-recognition systems and sells the data to insurance companies, private investigators and other repossession agents.
- DRN resells access to other companies who cater to further clients, including TLO, which sells database access to law enforcement and to private entities such as law firms, process servers and private investigators.
- Reported access priced at roughly 20 dollars a search.
- A reporter used the tool to track a specific person's vehicle across the United States from the plate number alone.
- Unlike law enforcement databases, these private databases can be accessed by nearly anyone for nearly any reason.
Dated 2019; pricing and product names may have changed, and DRN is now a Motorola Solutions company. The structural point is unchanged and is the strongest answer to any purely public-sector reform: a warrant requirement on police does nothing about a commercial database sold to private buyers. Byline is Joseph Cox, then at Vice, later a founder of 404 Media.
American Civil Liberties Union · undated · Primary · national
Survey of the non-Flock ALPR market, principally Motorola Solutions' Vigilant and its commercial DRN arm.
- DRN is a Motorola Solutions company; Vigilant gives police access to the same commercially collected data.
- DRN contracts with tow trucks and other fleet vehicles to carry cameras and collect plate reads as they drive.
- Law enforcement customers have access to billions of historical scans, with tens of millions of new scans added monthly.
- Motorola markets historical travel analysis over an archive spanning more than 17 years.
Establishes that banning one vendor does not end the dragnet. Specific scan counts vary widely across sources and vendor marketing; treat each figure as vendor-claim unless independently sourced.
Homeland Security Today · 2018-01-08 · Secondary · national
ICE contracted directly with Vigilant Solutions for nationwide license plate reader data on a sole-source basis - the contract Flock's ICE denial does not cover.
- ICE issued a sole source contract to Vigilant Solutions, per a justification and approval notice published January 8, 2018.
- Reported at more than 7 million dollars initially, with a 22.8 million dollar contract for database access running through 2026.
- Since late 2017 more than 9,000 ICE personnel have had access to privately collected plate scans from the 50 most populous US metro areas, plus millions more scans from local law enforcement.
- The Vigilant database is described as containing nearly two billion records and growing by roughly 100 million records per month, sourced from local law enforcement and vehicle repossession agencies.
- Vigilant data feeds into Palantir systems and is accessible through Thomson Reuters CLEAR.
THE DECISIVE ECOSYSTEM FACT. Flock's statement that it does not work with ICE is accurate about Flock and irrelevant to the question a resident is actually asking. ICE has held a direct national ALPR contract for years - with Motorola's Vigilant, not Flock. Dates and dollar figures here span 2018 to 2026 and come from mixed reporting; verify the current contract status before citing the 22.8 million figure as present-tense.
ACLU of New Mexico · 2026-02-01 · Primary · NM
New Mexico's attempted comprehensive consumer data privacy bill, which failed in the 2026 session - leaving the state without a general data privacy law behind SB 40.
- SB 53, CHISPA, sponsored by Sen. Angel Charley, would have required online for-profit entities to obtain consent before collecting information nonessential to their business.
- Would have applied to entities processing data from as few as 15,000 consumers, well below the 100,000 threshold common elsewhere, with an affirmative necessity standard for most processing.
- Included a private right of action with penalties of 2,500 dollars per negligent and 7,500 dollars per intentional violation per affected consumer.
- Passed the Senate Health and Public Affairs Committee but failed to advance; as of May 2026 New Mexico has no comprehensive consumer data privacy law.
Important context for SB 40's limits: New Mexico regulated ALPR sharing specifically while its general data privacy bill died. The commercial layer - data brokers, DRN-style fleet collection - is therefore untouched by New Mexico law. Advocacy-source summary of a bill; read the bill text before describing provisions as law, which they are not.
The Las Cruces cameras were installed and operating well before they entered the council's record: the contract dates to 2021 with a September 2024 renewal, while the first substantive council discussion of them is public comment on June 2, 2025 - by a member of the public who is now a city councilor.
Well supported
The case against thisThe public record scanned begins with minutes, and earlier discussion could exist in unscanned agenda packets or other bodies. The 2021 contract date and September 2024 renewal come from reporting, not from the contract itself, which remains unread.
3 sources
City of Las Cruces Document Center (lascruces.civicweb.net), scanned by this project · 2026-08-30 · Primary · local:las-cruces
An original full-text search of the Las Cruces council record for Flock and ALPR terms, run against the city's own CivicWeb Document Center. It establishes when the cameras entered the public record - and that the contract itself does not appear in it as a vote.
- SCANNED: 95 City Council minutes documents totaling 2,389 pages, plus 200 agenda documents (HTML) spanning council meetings, work sessions and special meetings 2019-2026.
- 16 minutes documents contain Flock, ALPR, license plate or plate reader as whole words.
- The earliest substantive discussion is June 2, 2025, in public comment by Michael Harris - then a member of the public, later a city councilor - who described automated license plate reading cameras appearing on private property and city rights-of-way, naming at least 10 locations including Lohman, University, Missouri, and sites at Lowe's and Home Depot.
- Mentions escalate sharply through 2026: January 5 (11), January 20 (19), February 17 (11), April 6 (11), June 1 (13).
- NOT FOUND ON THE PORTAL: in the documents scanned, no Flock or ALPR mention occurs within 400 characters of a resolution number, ordinance number, contract award, contract amendment, or a carried motion. The searched record contains public comment and councilor discussion, not a procurement vote.
- CONTROL: a comparable police technology procurement IS in the record and IS findable by the same method - the Axon body camera and Taser contract, including Resolution No. 25-057 amending Contract 20-21-054 to increase it by 446,625.57 dollars for a total not to exceed 2,324,799.79 dollars, appears on the November 4, 2024 council agenda.
- AGENDA PACKETS SCANNED: the six full council agenda packets spanning August 5 through October 21, 2024 - the window around the reported September 2024 renewal - total 4,106 pages (960, 891, 634, 215, 585 and 821). They contain ZERO occurrences of Flock, ALPR, license plate, plate reader or automated license. The words surveillance and camera appear at most once across all six.
- EXTRACTION VALIDATED on those packets: 430,000 to 1,112,000 characters extracted per packet, with RESOLUTION appearing 88-146 times, contract 78-379 times and Police 16-97 times - so the zero is a real absence, not a failed parse.
- THE DOMINGUEZ-ERA RECORD WAS SEARCHED AND IS CLEAN. Las Cruces adopted Flock in January 2022 per its own chief, so the decision would fall in 2021 under Chief Miguel Dominguez. Scanned: 96 council and WORK SESSION agenda packets for 2021-2022 (29,404 pages, 52.2 million characters) plus 72 council and work session minutes documents for 2020-2022 (1,398 pages). Occurrences of flock, ALPR, license plate reader, plate reader and automated license: ZERO.
- SEARCH TERMS WERE WIDENED IN CASE THE ITEM WAS NAMED DIFFERENTLY. Across those same 96 packets: flock 0, ALPR 0, plate reader 0, Vigilant 0, Genetec 0, real-time crime 0. Camera appeared in 41 documents and surveillance in 19, but reading the contexts found only Axon body cameras, park and City Hall security cameras, and a resident's suggestion of a camera above a dam. Motorola appeared 664 times in two documents and is two-way radio equipment (MotoTRBO, EVX-S24). Leonardo, the parent of the ELSAG plate-reader line, appeared 45 times and is a person's surname in a payment listing.
- CONTROLS AND EXTRACTION VALIDATED across the 2021-2022 packets: 7,994 matches for RESOLUTION, Police or contract; zero parse failures; and the 31 documents extracting under 5,000 characters are all one-to-five-page work session cover sheets with normal text density of 571 to 1,294 characters per page. Chief Dominguez is named 375 times across 37 documents, confirming the era is well covered. Chief Story appears zero times, consistent with his arriving later.
- February 17, 2026 minutes record a meeting with Flock representatives over Zoom, at which councilors were told, in the speaker's words, that Flock has never and will never integrate facial recognition into its product; the councilor noted they came away not entirely comforted.
- The same February 17, 2026 discussion raised the Mountain View, California incident, where Flock shared city data on the nationwide network and the company's response was that the city was not a client at the time and it was a demo system.
- April 6, 2026 minutes reference an op-ed by Councilors Bencomo and Harris opposing Flock, and record that LCPD invited Las Cruces residents to register their doorbell cameras with Flock.
- January 20, 2026 public comment cited the Aurora, Colorado false-flag stop and its 1.9 million dollar settlement, an approximately 10 percent error rate, Carpenter v. United States, and the assertion that Flock's own patent describes a dynamic surveillance network.
ORIGINAL RESEARCH by this project on 2026-08-30, using the city's own public Document Center - the same portal scripts/alpr/adapters/civicweb.py targets. METHOD AND ITS LIMITS, stated so the finding can be checked or overturned: agendas are published as HTML and minutes as PDF, so both were fetched and searched separately; matching used whole-word regex on extracted text. AN EARLIER PASS OF THIS SCAN PRODUCED NINE FALSE POSITIVES for 'alpr' because the text had been whitespace-stripped before matching, turning 'capital projects', 'biblical principles' and 'real problems' into apparent hits - the space-stripping was unnecessary for these PDFs and was removed. THE NEGATIVE FINDING IS BOUNDED: it means NOT FOUND IN THE DOCUMENTS SCANNED, never that no vote occurred. The six agenda packets for August-October 2024 HAVE now been scanned (4,106 pages, extraction validated against RESOLUTION/contract/Police counts). The 2021-2022 council and work session packets and the 2020-2022 minutes have NOW been scanned as well - see the Dominguez-era findings above. Still not scanned: agenda packets for 2023 and 2025, minutes attachments, and the Utilities and Planning and Zoning bodies. NOTE ON CONTROLS: the Axon control fires on the council AGENDA listing and in three minutes documents, but Axon and Taser appear zero times inside these six packets, so for the packets specifically the positive control is the presence of RESOLUTION, contract and Police text rather than a known police-technology procurement. A contract can also be executed administratively below a council approval threshold, or ride inside a consent-agenda item whose title names neither the vendor nor the technology. Any of those would explain the absence without any impropriety. VERIFY before publishing: pull the September 2024 agenda packet and the city's purchasing records directly.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
EFF Atlas of Surveillance · 2025-07-01 · Primary · local:las-cruces
Atlas of Surveillance record for Las Cruces PD ALPR deployment, sourced to public records.
- Vendor: Flock Safety.
- 22 automated license plate readers, per records obtained July 2025.
- Source cited: public records via MuckRock.
22 devices here against 45 readers in the February 2026 Haussamen reporting. Not necessarily a contradiction - different dates and possibly different device categories - but the dossier must present both with their dates rather than pick one.
Las Cruces is not a standoff between residents and a hostile police department: the two councilors most critical of the technology came away from a two-hour LCPD briefing wanting a citywide policy while expressing trust in their own department.
Well supported
The case against thisTrust in current personnel is exactly the argument for a written policy rather than against one - Harris's stated point is that departmental policies can change. A dossier that misdescribes the local temperature would be corrected in the room.
3 sources
New Mexico News Port · 2026-08-18 · Secondary · local:las-cruces
Fuller account of the Las Cruces councilors' oversight push, including their reaction after two hours with an LCPD lieutenant.
- Councilors Michael Harris and Johana Bencomo seek a city-level surveillance policy and a public portal showing how police collect, search and share vehicle data.
- They raised the issue after about two hours with an LCPD lieutenant going through the city's use of Flock in detail.
- Harris remains uneasy about what he called creeping surveillance but came away impressed by some of the safeguards LCPD has in place, and wants a citywide policy rather than departmental rules.
- Bencomo continues to oppose mass surveillance but expressed confidence in the LCPD team after the discussion: I have trust in him and the team that we can move forward into this place of being very transparent and honest and responsible with the kind of data that we are collecting from our residents.
IMPORTANT FOR TONE. The two councilors most critical of the technology both came away from a detailed briefing with a measure of confidence in their own department while still wanting a citywide policy. A dossier that renders Las Cruces as a fight between residents and a hostile police department would misdescribe the actual local situation, and would be corrected in the room.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
KFOX 14 · 2026-06-24 · Primary · local:dona-ana-county
The county sheriff's office expanding its Flock deployment, with the clearest statement in the corpus of the safeguards a New Mexico agency claims to apply.
- About 30 cameras currently deployed, with 22 more planned within a year.
- 162,000 dollars approved for the yearly subscription and new cameras, already within the sheriff's approved budget, under one consolidated agreement.
- Lt. Eric Flores: there has to be a case number and therefore a crime associated with that vehicle.
- Flores: the cameras aren't used to surveil just everyday citizens.
- Flores: we've been able to basically solve many many crimes that normally we wouldn't have had leads on.
- Stated safeguards include monthly self-audits verifying that each query has an associated case number.
This is the local case FOR the cameras, and the dossier must carry it at full strength. Two things to test rather than assume: the case-number requirement is exactly the kind of control the national audit logs show being satisfied by free-text entries, and a MONTHLY SELF-AUDIT is the agency checking its own work - the same self-assessment weakness built into SB 40's reporting. Neither observation disproves the claim; both are checkable against the county's own SB 40 report due April 1, 2027.
Flock employees live-viewed a Jewish Community Center's children's gymnastics room, pool and playground to demo the product to prospective police customers - one vice president pulled the feed 185 times - and the company's CEO later apologized for poor judgement.
Well supported2 of 3 sources not read at source
The case against thisFlock confirmed the access while disputing how it was characterized, apologized, and agreed to stop using that footage. The pattern is what matters: this is the second documented instance of the vendor searching or viewing customer data for sales purposes.
3 sources
404 Media · 2026-05-01 · Primary · GA
Flock employees live-viewed cameras inside a Jewish Community Center's children's gymnastics room, pool, fitness studios and playground to demonstrate the product to prospective police customers. A resident found it in the access logs.
- Flock staff, including a vice president who pulled up the feed 185 times since early 2025, live-viewed cameras in a JCC children's gymnastics room, pool, fitness studios and a playground, to demonstrate capabilities to prospective police department customers.
- Discovered when Dunwoody, Georgia resident Jason Hunyar filed a public records request for Flock's access logs within the city's camera network, and published his findings.
- The logs showed 1,271 outside agencies had been granted live-view permissions and 358 could record the streams.
- Flock confirmed the access happened as part of sales demonstrations while disputing how residents and activists characterized it.
- CEO Garrett Langley personally apologized to the Jewish community center, acknowledged poor judgement, promised radical transparency, and agreed to stop using Dunwoody footage for demonstrations.
- Dunwoody's city council renewed the contract anyway.
NOT READ at 404 Media (paywalled); assembled from multiple secondary accounts and the resident's own Substack, and should be confirmed. THIS IS THE DOSSIER'S METHOD WORKING AND ITS LIMIT IN ONE STORY: a single resident's records request for the access logs surfaced conduct no oversight body had found - and the council renewed regardless. Cite it when arguing for the audit log, and cite it again when someone assumes disclosure alone decides anything. The 1,271 live-view agencies figure is the most concrete illustration in the corpus of what joining the network actually grants.
Mountain View Voice · 2026-08-26 · Secondary · CA
Three improper searches of a California city's camera data were run by Flock itself, for product demonstrations, without the police department's permission.
- Redwood City police stated three improper searches were made by Flock for demonstration purposes with their technology.
- That demonstration was done without the department's permission.
NOT READ in full. This is a distinct category from officer misuse and from federal access: the VENDOR searching a customer's data for sales demos without asking. It pairs with the reported use of Jewish Community Center video in sales demos and bears directly on the contract terms question - who controls the data - in chapter 6b.
Wikipedia · 2026-08-01 · Secondary · national
Corporate timeline: founding, funding, product lines and a chronology of controversies.
- Founded 2017 by Garrett Langley, Paige Todd and Matt Feury; Langley is CEO.
- About 950 million dollars raised at a 7.5 billion dollar valuation as of 2025, including a 275 million dollar round in March 2025.
- Product lines: Falcon and Sparrow plate readers, Condor PTZ cameras, Raven gunshot detection (extended to human distress detection in October 2025), Nova data platform, and drones following the October 2024 Aerodome acquisition.
- Company-stated scale: over 5,000 communities in 49 states, 20 billion vehicle scans monthly.
- August 2024: Mother Jones reported 13 or more agencies spent 920,000 dollars of opioid settlement funds on Flock cameras.
- 2021: IPVM reported a 10 percent error rate and Flock halted sales to IPVM.
- Roanoke: 30 of 41 gunshot detectors installed in locations that were never approved.
- Verona, Wisconsin: cameras stayed operational three months after the contract was rejected; Cleveland cameras stayed active after expiration.
- Oshkosh, Wisconsin rescinded its contract in August 2026 citing false statements.
Wikipedia is a finding aid, not a citation. Every item above must be traced to its underlying source before it appears in the dossier; the operational scale figures are Flock's own marketing claims.
A single resident's public records request for the access logs surfaced conduct that no oversight body had found - and the city council renewed the contract anyway.
Well supported1 of 3 sources not read at source
The case against thisDisclosure is necessary and not sufficient. Cite this for the power of the audit log, and cite it again against any assumption that publishing the facts settles the question.
3 sources
404 Media · 2026-05-01 · Primary · GA
Flock employees live-viewed cameras inside a Jewish Community Center's children's gymnastics room, pool, fitness studios and playground to demonstrate the product to prospective police customers. A resident found it in the access logs.
- Flock staff, including a vice president who pulled up the feed 185 times since early 2025, live-viewed cameras in a JCC children's gymnastics room, pool, fitness studios and a playground, to demonstrate capabilities to prospective police department customers.
- Discovered when Dunwoody, Georgia resident Jason Hunyar filed a public records request for Flock's access logs within the city's camera network, and published his findings.
- The logs showed 1,271 outside agencies had been granted live-view permissions and 358 could record the streams.
- Flock confirmed the access happened as part of sales demonstrations while disputing how residents and activists characterized it.
- CEO Garrett Langley personally apologized to the Jewish community center, acknowledged poor judgement, promised radical transparency, and agreed to stop using Dunwoody footage for demonstrations.
- Dunwoody's city council renewed the contract anyway.
NOT READ at 404 Media (paywalled); assembled from multiple secondary accounts and the resident's own Substack, and should be confirmed. THIS IS THE DOSSIER'S METHOD WORKING AND ITS LIMIT IN ONE STORY: a single resident's records request for the access logs surfaced conduct no oversight body had found - and the council renewed regardless. Cite it when arguing for the audit log, and cite it again when someone assumes disclosure alone decides anything. The 1,271 live-view agencies figure is the most concrete illustration in the corpus of what joining the network actually grants.
Electronic Frontier Foundation · 2026-06-01 · Primary · national
A how-to for residents seeking their own agency's network audit to determine whether local cameras have been searched for immigration purposes.
- Network audit logs are obtainable by public records request and record the stated reason for each search.
- The audit is the document that shows whether local cameras served federal immigration enforcement.
This is the operational bridge between the dossier and the module: the same audit file the /flock module already ingests is the one residents are told to request.
IPVM · 2025-08-01 · Secondary · national
Account of how 404 Media's Flock reporting translated into official action.
- Jason Koebler notes the reporting spurred an ongoing congressional investigation and an ongoing Illinois Secretary of State investigation, with numerous towns dropping the system.
Useful for the causal chain from reporting to records request to oversight to cancellation - the mechanism this project is trying to reproduce locally.
The Senate subcommittee asked Flock to produce records of confirmed system misuse since 2021, along with retention policies, search verification protocols and security practices, by September 8, 2026.
Well supported1 of 2 sources not read at source
The case against thisIngested from secondary coverage; the letter's annex was not obtained. If a company-wide misuse tally is produced it would be the first not assembled by journalists from records requests - and the deadline has now passed, making this the most tractable follow-up in the corpus.
2 sources
U.S. Senate Judiciary Subcommittee on Crime and Counterterrorism / Daily Caller · 2026-08-26 · Secondary · national
What the Senate subcommittee actually asked Flock to produce, and the company's response.
- Deadline of September 8, 2026 for Flock to produce documents on who has access to the information the cameras gather.
- The subcommittee sought documentation of data retention policies, search verification protocols, internal security practices, and records of confirmed system misuse since 2021.
- Flock spokesperson Paris Lewbel said the company has received the letter and appreciates the opportunity to provide the subcommittee with additional information about Flock and our technology.
The demand for RECORDS OF CONFIRMED MISUSE SINCE 2021 is the item to watch: if produced, it would be the first company-wide misuse tally not assembled from journalists' records requests. The deadline has now passed - whether anything was produced, and whether it becomes public, is the single most tractable follow-up in this corpus. Ingested from secondary coverage; the letter and its annex were not obtained.
Office of U.S. Senator Josh Hawley · 2026-08-26 · Primary · national
The chairman of the Senate Judiciary Subcommittee on Crime and Counterterrorism opened an investigation into Flock, demanding documents from CEO Garrett Langley. Notable because it puts congressional scrutiny of Flock on a bipartisan footing.
- Sen. Josh Hawley, chairman of the Judiciary Subcommittee on Crime and Counterterrorism, opened the investigation August 26, 2026.
- Documents and information demanded from CEO Garrett Langley by September 8, 2026.
- Hawley: Congress never authorized the network your industry has built.
- Hawley: Your company's internal policies are, in practice, the only safeguards for hundreds of millions of Americans.
- Hawley: Americans do not surrender their privacy rights when they drive to work, drop their kids off at school, or go to church.
- Cites more than 120,000 cameras across 49 states, more than 20 billion vehicle scans monthly, and an 8.3 billion dollar valuation.
Pairs with wyden-2025-ftc-letter to show scrutiny is not partisan - a Democratic senator and representative in November 2025, a Republican subcommittee chairman in August 2026. That framing matters in a council chamber. The demand annex was not published with the release; the response deadline has likely passed and the reply is worth seeking.
New Mexico set up the purchasing channel itself: statewide price agreement 30-00000-22-00018, titled License Plate Recognition, carries five awarded vendors including Flock Group Inc. and is open to all state agencies, political subdivisions and local public bodies. A New Mexico city or county can buy plate readers off it without running its own procurement.
Well supported
The case against thisThis is lawful and ordinary public purchasing - cooperative agreements exist to save small bodies from duplicating procurements. The consequence is nonetheless that the decision most affecting residents can be made without any local legislative act, which is a design choice the state made and can revisit.
3 sources
State of New Mexico General Services Department, Purchasing Division · 2026-01-09 · Primary · NM
The mechanism by which any New Mexico public body can buy license plate readers without running its own procurement. A statewide price agreement titled License Plate Recognition, with Flock Group Inc. among the awarded vendors, open to every agency and political subdivision in the state.
- Agreement number 30-00000-22-00018, titled License Plate Recognition, issued by the New Mexico General Services Department Purchasing Division.
- FIVE awarded vendors, of which Flock Group Inc. is one (Supplier ID 0000170812).
- Term: January 13, 2023 through January 12, 2027, extended by Amendment Eight from January 12, 2026 at the same price, terms and conditions.
- Ship To reads: All State of New Mexico agencies, commissions, institutions, political subdivisions and local public bodies allowed by law.
- Amendment Eight signed January 9, 2026 by State Purchasing Agent Dorothy Mendonca; procurement specialist Theresa Mendibles.
- Dona Ana County's June 9, 2026 approval was of USE of this agreement, not a competitive procurement of its own.
OBTAINED FROM PRIMARY SOURCE on 2026-08-30, inside the Dona Ana County BOCC agenda packet for June 9, 2026 (428 pages), retrieved through the county's CivicClerk API. THIS IS THE STRUCTURAL EXPLANATION FOR THE LAS CRUCES GAP and it is entirely lawful: a New Mexico public body does not have to run a procurement, or necessarily hold a council vote, to buy Flock - it can buy off the statewide price agreement. That reframes 'procurement that outruns consent' from a suspicion about one city into a description of how the state set the system up. IT IS ALSO THE MOST DIRECT POLICY LEVER IN THE CORPUS: the agreement is a state instrument, it can be conditioned or allowed to lapse, and IT EXPIRES JANUARY 12, 2027. The full Flock Safety Agreement was listed among the packet's supporting documents but its terms did not appear in the extracted text - retrieve it from GSD directly.
Dona Ana County Board of County Commissioners · 2026-06-09 · Primary · local:dona-ana-county
The county's own record of buying Flock: a named agenda item, a staff summary, a roll-call vote, and a link to the meeting video - the complete opposite of what the Las Cruces record contains.
- Item 12: Approve use of New Mexico State Pricing Agreement 30-00000-22-00018 with Flock Group Inc. for license plate reader cameras and annual subscription services in the amount of 162,000 dollars, and delegate signature authority to the County Manager for all related documents.
- Initiating department: Dona Ana County Sheriff's Office; contact person Kim Stewart, Sheriff.
- Staff summary states: DASO currently utilizes Flock cameras throughout the county. The cameras are license plate readers used for crime resolution and prevention.
- Financial impact stated as funds included in the Sheriff's Office FY26 budget; administrative approvals by the Finance Director and Purchasing Manager, June 4-5, 2026.
- Passed on a roll call recorded in the June 23, 2026 minutes: motion by Chair Manuel Sanchez, second by Commissioner Christopher Schaljo-Hernandez; Schaljo-Hernandez, Kimble, Chaparro and Sanchez voting yes, Vice Chair Gloria Gameros absent - carried 4-0.
- The minutes carry a timestamped link to the meeting video at the item: https://youtu.be/1nJov8_XGmg?t=20873
- The agenda is published in English and Spanish.
ORIGINAL RESEARCH, retrieved 2026-08-30 by scanning all 158 published files (28.3 million characters) in the county's CivicClerk portal. This is what an ALPR purchase looks like when it goes through a public body properly: named vendor, named agreement, dollar figure, sponsoring official, staff summary, recorded roll-call vote, and video. It is the control for the Las Cruces finding, and it is also the honest counterweight - the county did this in the open. Note the supporting documentation list includes a Flock Safety Agreement whose terms were NOT in the extracted text; that agreement is the thing to request next.
City of Las Cruces Document Center (lascruces.civicweb.net), scanned by this project · 2026-08-30 · Primary · local:las-cruces
An original full-text search of the Las Cruces council record for Flock and ALPR terms, run against the city's own CivicWeb Document Center. It establishes when the cameras entered the public record - and that the contract itself does not appear in it as a vote.
- SCANNED: 95 City Council minutes documents totaling 2,389 pages, plus 200 agenda documents (HTML) spanning council meetings, work sessions and special meetings 2019-2026.
- 16 minutes documents contain Flock, ALPR, license plate or plate reader as whole words.
- The earliest substantive discussion is June 2, 2025, in public comment by Michael Harris - then a member of the public, later a city councilor - who described automated license plate reading cameras appearing on private property and city rights-of-way, naming at least 10 locations including Lohman, University, Missouri, and sites at Lowe's and Home Depot.
- Mentions escalate sharply through 2026: January 5 (11), January 20 (19), February 17 (11), April 6 (11), June 1 (13).
- NOT FOUND ON THE PORTAL: in the documents scanned, no Flock or ALPR mention occurs within 400 characters of a resolution number, ordinance number, contract award, contract amendment, or a carried motion. The searched record contains public comment and councilor discussion, not a procurement vote.
- CONTROL: a comparable police technology procurement IS in the record and IS findable by the same method - the Axon body camera and Taser contract, including Resolution No. 25-057 amending Contract 20-21-054 to increase it by 446,625.57 dollars for a total not to exceed 2,324,799.79 dollars, appears on the November 4, 2024 council agenda.
- AGENDA PACKETS SCANNED: the six full council agenda packets spanning August 5 through October 21, 2024 - the window around the reported September 2024 renewal - total 4,106 pages (960, 891, 634, 215, 585 and 821). They contain ZERO occurrences of Flock, ALPR, license plate, plate reader or automated license. The words surveillance and camera appear at most once across all six.
- EXTRACTION VALIDATED on those packets: 430,000 to 1,112,000 characters extracted per packet, with RESOLUTION appearing 88-146 times, contract 78-379 times and Police 16-97 times - so the zero is a real absence, not a failed parse.
- THE DOMINGUEZ-ERA RECORD WAS SEARCHED AND IS CLEAN. Las Cruces adopted Flock in January 2022 per its own chief, so the decision would fall in 2021 under Chief Miguel Dominguez. Scanned: 96 council and WORK SESSION agenda packets for 2021-2022 (29,404 pages, 52.2 million characters) plus 72 council and work session minutes documents for 2020-2022 (1,398 pages). Occurrences of flock, ALPR, license plate reader, plate reader and automated license: ZERO.
- SEARCH TERMS WERE WIDENED IN CASE THE ITEM WAS NAMED DIFFERENTLY. Across those same 96 packets: flock 0, ALPR 0, plate reader 0, Vigilant 0, Genetec 0, real-time crime 0. Camera appeared in 41 documents and surveillance in 19, but reading the contexts found only Axon body cameras, park and City Hall security cameras, and a resident's suggestion of a camera above a dam. Motorola appeared 664 times in two documents and is two-way radio equipment (MotoTRBO, EVX-S24). Leonardo, the parent of the ELSAG plate-reader line, appeared 45 times and is a person's surname in a payment listing.
- CONTROLS AND EXTRACTION VALIDATED across the 2021-2022 packets: 7,994 matches for RESOLUTION, Police or contract; zero parse failures; and the 31 documents extracting under 5,000 characters are all one-to-five-page work session cover sheets with normal text density of 571 to 1,294 characters per page. Chief Dominguez is named 375 times across 37 documents, confirming the era is well covered. Chief Story appears zero times, consistent with his arriving later.
- February 17, 2026 minutes record a meeting with Flock representatives over Zoom, at which councilors were told, in the speaker's words, that Flock has never and will never integrate facial recognition into its product; the councilor noted they came away not entirely comforted.
- The same February 17, 2026 discussion raised the Mountain View, California incident, where Flock shared city data on the nationwide network and the company's response was that the city was not a client at the time and it was a demo system.
- April 6, 2026 minutes reference an op-ed by Councilors Bencomo and Harris opposing Flock, and record that LCPD invited Las Cruces residents to register their doorbell cameras with Flock.
- January 20, 2026 public comment cited the Aurora, Colorado false-flag stop and its 1.9 million dollar settlement, an approximately 10 percent error rate, Carpenter v. United States, and the assertion that Flock's own patent describes a dynamic surveillance network.
ORIGINAL RESEARCH by this project on 2026-08-30, using the city's own public Document Center - the same portal scripts/alpr/adapters/civicweb.py targets. METHOD AND ITS LIMITS, stated so the finding can be checked or overturned: agendas are published as HTML and minutes as PDF, so both were fetched and searched separately; matching used whole-word regex on extracted text. AN EARLIER PASS OF THIS SCAN PRODUCED NINE FALSE POSITIVES for 'alpr' because the text had been whitespace-stripped before matching, turning 'capital projects', 'biblical principles' and 'real problems' into apparent hits - the space-stripping was unnecessary for these PDFs and was removed. THE NEGATIVE FINDING IS BOUNDED: it means NOT FOUND IN THE DOCUMENTS SCANNED, never that no vote occurred. The six agenda packets for August-October 2024 HAVE now been scanned (4,106 pages, extraction validated against RESOLUTION/contract/Police counts). The 2021-2022 council and work session packets and the 2020-2022 minutes have NOW been scanned as well - see the Dominguez-era findings above. Still not scanned: agenda packets for 2023 and 2025, minutes attachments, and the Utilities and Planning and Zoning bodies. NOTE ON CONTROLS: the Axon control fires on the council AGENDA listing and in three minutes documents, but Axon and Taser appear zero times inside these six packets, so for the packets specifically the positive control is the presence of RESOLUTION, contract and Police text rather than a known police-technology procurement. A contract can also be executed administratively below a council approval threshold, or ride inside a consent-agenda item whose title names neither the vendor nor the technology. Any of those would explain the absence without any impropriety. VERIFY before publishing: pull the September 2024 agenda packet and the city's purchasing records directly.
The state price agreement that makes Flock purchasable across New Mexico without local procurement EXPIRES JANUARY 12, 2027, having already been extended once by Amendment Eight. It is a state instrument that can be conditioned, renegotiated or allowed to lapse.
Well supported
The case against thisLetting it lapse would not stop purchases - bodies could procure individually - and four other vendors are on the same agreement. Its value is as a single statewide point of leverage where SB 40's obligations could be attached as conditions of award.
3 sources
State of New Mexico General Services Department, Purchasing Division · 2026-01-09 · Primary · NM
The mechanism by which any New Mexico public body can buy license plate readers without running its own procurement. A statewide price agreement titled License Plate Recognition, with Flock Group Inc. among the awarded vendors, open to every agency and political subdivision in the state.
- Agreement number 30-00000-22-00018, titled License Plate Recognition, issued by the New Mexico General Services Department Purchasing Division.
- FIVE awarded vendors, of which Flock Group Inc. is one (Supplier ID 0000170812).
- Term: January 13, 2023 through January 12, 2027, extended by Amendment Eight from January 12, 2026 at the same price, terms and conditions.
- Ship To reads: All State of New Mexico agencies, commissions, institutions, political subdivisions and local public bodies allowed by law.
- Amendment Eight signed January 9, 2026 by State Purchasing Agent Dorothy Mendonca; procurement specialist Theresa Mendibles.
- Dona Ana County's June 9, 2026 approval was of USE of this agreement, not a competitive procurement of its own.
OBTAINED FROM PRIMARY SOURCE on 2026-08-30, inside the Dona Ana County BOCC agenda packet for June 9, 2026 (428 pages), retrieved through the county's CivicClerk API. THIS IS THE STRUCTURAL EXPLANATION FOR THE LAS CRUCES GAP and it is entirely lawful: a New Mexico public body does not have to run a procurement, or necessarily hold a council vote, to buy Flock - it can buy off the statewide price agreement. That reframes 'procurement that outruns consent' from a suspicion about one city into a description of how the state set the system up. IT IS ALSO THE MOST DIRECT POLICY LEVER IN THE CORPUS: the agreement is a state instrument, it can be conditioned or allowed to lapse, and IT EXPIRES JANUARY 12, 2027. The full Flock Safety Agreement was listed among the packet's supporting documents but its terms did not appear in the extracted text - retrieve it from GSD directly.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
ACLU of New Mexico · 2026-02-01 · Primary · NM
New Mexico's attempted comprehensive consumer data privacy bill, which failed in the 2026 session - leaving the state without a general data privacy law behind SB 40.
- SB 53, CHISPA, sponsored by Sen. Angel Charley, would have required online for-profit entities to obtain consent before collecting information nonessential to their business.
- Would have applied to entities processing data from as few as 15,000 consumers, well below the 100,000 threshold common elsewhere, with an affirmative necessity standard for most processing.
- Included a private right of action with penalties of 2,500 dollars per negligent and 7,500 dollars per intentional violation per affected consumer.
- Passed the Senate Health and Public Affairs Committee but failed to advance; as of May 2026 New Mexico has no comprehensive consumer data privacy law.
Important context for SB 40's limits: New Mexico regulated ALPR sharing specifically while its general data privacy bill died. The commercial layer - data brokers, DRN-style fleet collection - is therefore untouched by New Mexico law. Advocacy-source summary of a bill; read the bill text before describing provisions as law, which they are not.
Dona Ana County runs a second, non-Flock plate reader system: Axon Fleet 3 in-car cameras licensed for ALPR, on contract from December 2025 into February 2029 - roughly 31,000 dollars a year for the license line alone, within a package totaling about 134,000 dollars.
Well supported
The case against thisMobile readers on patrol vehicles are a different surveillance profile from fixed pole cameras - they follow the patrol, not every driver on a road. The point stands that a campaign aimed only at Flock would leave this untouched. Figures are read from an extracted packet and need confirming against the executed contract.
3 sources
Dona Ana County Board of County Commissioners · 2025-10-14 · Primary · local:dona-ana-county
The county runs a SECOND ALPR system that has nothing to do with Flock: Axon Fleet 3 in-car cameras licensed for automatic license plate recognition, on contract into 2029.
- Line items include AXON FLEET 3 - ALPR LICENSE - 1 CAMERA at 61.72 dollars per unit, 39 units across 12 months, totaling 28,884.96 dollars plus 2,423.44 tax, 31,308.40 dollars.
- A Refresh AXON Fleet 3 System line covering true-up, Fleet 3 Basic and ALPR license at 10,421.19 dollars times 12, totaling 125,054.28 dollars; a related grand total of 134,261.31 dollars appears in the packet.
- Contract dates on the Axon Evidence and Fleet lines run 12/01/2025 to 02/28/2029.
- These are vehicle-mounted readers on patrol units, not fixed pole cameras.
FOUND BY ORIGINAL RESEARCH in the county's own packet. IMPORTANT CORRECTIVE TO A DOSSIER THAT TALKS ONLY ABOUT FLOCK: Dona Ana County deputies drive mobile plate readers licensed from Axon, on contract into 2029, entirely separate from the county's Flock cameras. A local campaign aimed only at Flock would leave this untouched. Line-item figures are read from an extracted packet and should be confirmed against the executed contract.
Police1 · 2024-02-08 · Secondary · national
Axon completed its acquisition of Fusus, whose platform aggregates live video, data and sensor feeds from many sources into a single real-time crime center view.
- Acquisition completed February 2024.
- Fusus aggregates live video, data and sensor feeds from disparate sources simultaneously.
- Axon has since announced fixed ALPR cameras (Outpost, Lightpost) and a Ring integration for citizen video sharing.
- Real-time crime centers have expanded to more than 250 cities and counties.
The fusion layer is the part that matters constitutionally: plate reads become a location dragnet only when joined to identity, video and other feeds in one interface.
American Civil Liberties Union · undated · Primary · national
Survey of the non-Flock ALPR market, principally Motorola Solutions' Vigilant and its commercial DRN arm.
- DRN is a Motorola Solutions company; Vigilant gives police access to the same commercially collected data.
- DRN contracts with tow trucks and other fleet vehicles to carry cameras and collect plate reads as they drive.
- Law enforcement customers have access to billions of historical scans, with tens of millions of new scans added monthly.
- Motorola markets historical travel analysis over an archive spanning more than 17 years.
Establishes that banning one vendor does not end the dragnet. Specific scan counts vary widely across sources and vendor marketing; treat each figure as vendor-claim unless independently sourced.
The county's June 2026 approval is a usable template for what residents should ask their own body to produce: named vendor, named agreement, dollar amount, sponsoring official, written staff summary, recorded roll-call vote, and a timestamped link to the meeting video - published in English and Spanish.
Well supported
The case against thisProcedural transparency is not the same as substantive scrutiny: the staff summary here is three sentences and says nothing about retention, sharing, federal access or the audit obligations SB 40 imposes. Getting the vote on the record is a floor, not a ceiling.
3 sources
Dona Ana County Board of County Commissioners · 2026-06-09 · Primary · local:dona-ana-county
The county's own record of buying Flock: a named agenda item, a staff summary, a roll-call vote, and a link to the meeting video - the complete opposite of what the Las Cruces record contains.
- Item 12: Approve use of New Mexico State Pricing Agreement 30-00000-22-00018 with Flock Group Inc. for license plate reader cameras and annual subscription services in the amount of 162,000 dollars, and delegate signature authority to the County Manager for all related documents.
- Initiating department: Dona Ana County Sheriff's Office; contact person Kim Stewart, Sheriff.
- Staff summary states: DASO currently utilizes Flock cameras throughout the county. The cameras are license plate readers used for crime resolution and prevention.
- Financial impact stated as funds included in the Sheriff's Office FY26 budget; administrative approvals by the Finance Director and Purchasing Manager, June 4-5, 2026.
- Passed on a roll call recorded in the June 23, 2026 minutes: motion by Chair Manuel Sanchez, second by Commissioner Christopher Schaljo-Hernandez; Schaljo-Hernandez, Kimble, Chaparro and Sanchez voting yes, Vice Chair Gloria Gameros absent - carried 4-0.
- The minutes carry a timestamped link to the meeting video at the item: https://youtu.be/1nJov8_XGmg?t=20873
- The agenda is published in English and Spanish.
ORIGINAL RESEARCH, retrieved 2026-08-30 by scanning all 158 published files (28.3 million characters) in the county's CivicClerk portal. This is what an ALPR purchase looks like when it goes through a public body properly: named vendor, named agreement, dollar figure, sponsoring official, staff summary, recorded roll-call vote, and video. It is the control for the Las Cruces finding, and it is also the honest counterweight - the county did this in the open. Note the supporting documentation list includes a Flock Safety Agreement whose terms were NOT in the extracted text; that agreement is the thing to request next.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Brennan Center for Justice · 2020-09-10 · Primary · national
Seven concrete policy recommendations for ALPR regulation - the closest thing in the corpus to ready-made ordinance language for a city council.
- Retention and warrants: delete non-matching plate scans immediately; if retained, limit to days rather than months; require a warrant for historical database searches absent emergency.
- Two-step scanning: the first query reveals only registration and hot-list status, and accessing personal information requires a basis for further police action.
- Hot list verification: mandate independent verification of hot-list data and real-time updates to prevent erroneous stops.
- Public transparency and input: communities participate in deployment decisions; policies published; audit results disclosed.
- Audit logs: track automated alerts, officer access to historical data, and all inter-agency data-sharing arrangements.
- Disparate impact audits: evaluate whether deployment disproportionately targets marginalized communities or protected activities.
- Safeguard effectiveness audits: regular review that access controls and retention actually function.
- Legal status as of 2020: no bright-line warrant rule; appeals courts had avoided direct engagement with Carpenter's application to ALPR.
READ on 2026-08-30, closing a gap this dossier had flagged as unread. Published 2020, so its legal-status section is superseded by Rinaldi, Norfolk and Chatrie - but the RECOMMENDATIONS are the durable part and map almost one to one onto what Las Cruces councilors are asking for. Hot-list verification and two-step scanning are the two that directly address the wrong-car gunpoint stops.
Flock publishes state-specific contract provisions for Connecticut, Oregon, Virginia, Washington, Indiana and Texas - and NOT for New Mexico, even though SB 40 took effect July 1 2026 and imposes duties closely resembling Connecticut's. The June 2026 Dona Ana order form incorporates that page as it stands.
Well supported
The case against thisA vendor page is not the only way to comply - SB 40 binds the AGENCY as the ALPR user regardless of what the vendor's contract says, and provisions may be added later or handled in a Master Services Agreement not seen here. Recheck the page before relying on the absence. But it is a concrete question to put to GSD and to every New Mexico agency: have SB 40 terms been added to your Flock contract?
3 sources
Flock Safety · 2026-08-01 · Vendor claim · national
The page Flock order forms incorporate by reference for customers in listed states - and New Mexico is not one of them.
- States covered: Connecticut, Oregon, Virginia, Washington, Indiana and Texas.
- NEW MEXICO IS NOT COVERED. No New Mexico-specific provisions are listed.
- Connecticut bars sharing where Flock reasonably believes the data may be used to investigate a suspected immigration violation, and restricts sharing that would identify people seeking, providing or receiving reproductive health care permitted under Connecticut law.
- Connecticut and Washington mandate a maximum 21-day retention, or shorter if the customer requests.
- Virginia requires Flock to immediately notify the customer on receipt of any subpoena duces tecum, search warrant execution, or other third-party request for data.
- Connecticut bars sharing with third parties without the customer's prior express written authorization.
CHECKED 2026-08-30. THE FINDING IS THE ABSENCE. New Mexico's SB 40 took effect July 1 2026 and imposes exactly these kinds of duties - no sharing where there is reasonable belief of immigration or protected-health-care use, a written declaration before any out-of-state access - yet New Mexico is not among the states with provisions on this page, and the June 2026 Dona Ana order form incorporates the page as it stands. Compare Connecticut, whose provisions read almost like SB 40. This is concrete, checkable and directly actionable: ask GSD and every New Mexico agency whether SB 40 terms have been added to their Flock contracts. Recheck the page before relying on the absence - vendor pages change.
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
The contractual retention for a New Mexico agency is 30 days - stated on the face of the Dona Ana County order form - not the 7 days on Flock's public policy page and not the 30 in its legal-argument page by coincidence. Retention is set per Order Form, so the only way to know a given agency's is to read its contract.
Well supported
The case against this30 days is a real limit and shorter than New Mexico State Police's 180 days or Albuquerque's year. It is also unbounded by statute, since SB 40 sets no retention limit, and the Norfolk order shows a retention period does not govern records downloaded out of the system.
4 sources
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
Flock Safety · 2026-08-21 · Vendor claim · national
The live terms that Flock order forms incorporate by reference - read directly rather than through commentary, and they differ from the February 2026 clause analyses in one important respect.
- License grant, quoted: Customer hereby grants to Flock a limited, non-exclusive, royalty-free, irrevocable, perpetual, worldwide license to (a) use and disclose Customer Data to provide the Flock Services; and (b) use Customer Data to support and improve Flock's products and services.
- A NO-SALE CLAUSE IS PRESENT in the current terms: For the avoidance of doubt, Flock shall not sell Customer Data.
- Data ownership: as between Flock and Customer, all right, title and interest in and to Customer Data belong to and are retained by Customer.
- No dedicated training-data section; the support-and-improve language is what would cover model training.
- Retention is not fixed in the terms - the Retention Period is defined as the period specified in the applicable Order Form.
- Termination for material breach uncured within 30 days, bankruptcy or insolvency, or when no active Order Forms exist; auto-renewal is handled on the Order Form rather than here.
- Governing law is Georgia; disputes go to AAA mediation and then binding arbitration under AAA Commercial Arbitration Rules.
READ AT SOURCE 2026-08-30 - and it CORRECTS this dossier. Chapter 6b, following contemporaneous February 2026 clause-level analyses by the ACLU and Footnote4a, said the no-sale clause had been DELETED. The current terms contain one. Either it was restored between February and August 2026, or the earlier reading was wrong; this project has not compared the versions itself and cannot say which. What is NOT in dispute and is confirmed here at source: the license to Flock is irrevocable and perpetual, there is no dedicated training-data guardrail, governing law is Georgia and disputes go to arbitration. Retention lives on the Order Form, which is why the Dona Ana Order Form matters.
Flock Safety · undated · Vendor claim · national
Flock's public-facing LPR policy - the document a council is most likely to be shown.
- Flock states it defaults to deleting LPR data every 7 days on a rolling basis, adjustable per customer.
- States that LPR data gathered on behalf of customers is owned by the customer, who controls sharing.
- States Flock uses under 1 percent of LPR images, stripped of identifying information and metadata, solely to improve services through machine learning.
- States it will not sell, publish or disclose customer LPR data for commercial purposes without consent - but may disclose where legally required or where it reasonably believes access is necessary to comply with legal process, enforce agreements, or address security and fraud concerns.
Tiered vendor-claim, and the most important one in the corpus to hold against the contract. The policy page describes de-identified, sub-1-percent training use; the February 2026 terms DELETED the Training Data section imposing exactly those limits, and deleted the no-sale clause. A council shown this page is not being shown the agreement it would sign.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
Nationwide lookup is not an incidental setting but a contracted product feature: the Dona Ana order form lists Nationwide Network license plate lookup, described in the contract itself as leveraging a nationwide system boasting 10 billion additional plate reads per month, alongside State Network lookup and Law Enforcement Network Access.
Well supported
The case against thisLookup-only access is narrower than live camera access, and Flock states federal sharing is default off. The point is that a resident asking whether the county is on the national network can be answered from the contract, and the answer is yes.
3 sources
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
Office of U.S. Senator Ron Wyden · 2025-11-03 · Primary · national
Two members of Congress asked the FTC to investigate Flock for negligent cybersecurity, arguing that its failure to require multi-factor authentication is an unfair business practice under Section 5 of the FTC Act. The letter is also the best public source on how the National Lookup Tool is actually configured.
- Dated November 3, 2025, to FTC Chair Andrew N. Ferguson, signed by Sen. Ron Wyden and Rep. Raja Krishnamoorthi.
- Flock reportedly contracts with over 5,000 police departments, 1,000 businesses and numerous homeowners associations across 49 states.
- Flock told Congress in August 2025 that approximately 75 percent of its law enforcement customers have opted into the National Lookup Tool, which lets any other enrolled customer search their data.
- The letter attributes that high opt-in rate to Flock restricting nationwide search access to agencies that agree to share their own data.
- Data is searchable not only by plate number but by make, model and even bumper stickers.
- Flock confirmed to Congress in October 2025 that it does not require MFA; it still supports SMS codes, and does not natively support phishing-resistant MFA, which CISA calls the gold standard.
- Congressional staff found via Hudson Rock that passwords for at least 35 Flock customer accounts had been stolen by infostealer malware.
- Security researcher Benn Jordan provided the offices a screenshot of a Russian-language cybercrime forum offering Flock accounts for sale.
- Unraveled Press reported August 11, 2025 that a DEA officer used a Palos Heights, Illinois detective's Flock account to run searches, and the detective confirmed it was common practice for his DEA task force to use his credentials.
- A July 9, 2025 Palos Heights Deputy Chief memo shows the department did not enable the MFA option until after a 404 Media reporter identified the password sharing.
- The letter cites four FTC actions - Uber, Chegg, Drizly and Blackbaud - holding that failure to require MFA is an unfair practice.
- It also cites California Civil Code section 1798.90.53, requiring ALPR operators to maintain reasonable security safeguards.
VERIFIED by extracting the letter PDF itself on 2026-08-30, after a first pass wrongly attributed two findings to it. CONFIRMED ABSENT from this letter: any statement that Flock's software filters were easily bypassed, or that Flock did not audit how its network was being used. Those claims appear in secondary coverage of Wyden's oversight and belong to some other document; do not cite this letter for them. The FTC has made no findings - this is a request.
Flock Safety · undated · Vendor claim · national
Flock's account of who can reach data collected by a customer's cameras.
- Flock states law enforcement cannot access a customer's Flock camera data unless the customer chooses to share it, and that no agency has access unless the organization intentionally grants it.
Tiered vendor-claim. Narrowly consistent with the record - the sharing was opt-in - and beside the point, since roughly 75 percent of law enforcement customers opted into the National Lookup Tool and the incentive to do so is built into the product.
The Dona Ana contract renews automatically for successive one-year terms unless a party gives notice of non-renewal at least 30 days before the term ends - the auto-renewal term this project's procurement subsystem is built to look for.
Well supported
The case against thisAuto-renewal with a 30-day notice window is ordinary in municipal software contracts. It matters because ending the program requires a calendared decision in advance rather than simply declining to act.
3 sources
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
American Civil Liberties Union · 2026-04-16 · Primary · national
ACLU analysis of Flock's revised terms and conditions, identifying four changes that shift control of the data from the customer city to the company.
- The clause Flock does not own and shall not sell Customer Data is absent from the updated terms.
- New terms grant Flock the exclusive right to determine and control the method, timing, format, and medium of a customer's access to its own data - with customers receiving degraded, low-resolution copies lacking metadata such as timestamps.
- Flock gains perpetual rights to use customer data to support and improve its services, retaining access after the customer's contract terminates.
- Expanded liability protections shield Flock even for willful misconduct or gross negligence; disputes go to private arbitration under Georgia law; and termination is made harder, including where cities decline or defund programs.
- ACLU advises municipalities to examine the changes closely, seek legal counsel before entering or renewing, and consider not installing mass surveillance systems at all.
The degraded-copy point deserves emphasis: a city that cannot get full-resolution data with metadata cannot independently audit its own system, which undercuts every locally promised safeguard including case-number verification.
The contracted Vehicle Fingerprint search covers vehicle type, make, color, plate state, bumper stickers, decals, roof racks - and explicitly missing or covered plates, meaning the system is sold as able to find vehicles whose plates cannot be read.
Well supported
The case against thisIdentifying a vehicle without a readable plate is useful in exactly the stolen-vehicle cases agencies cite. It also undercuts the framing that these devices merely read government-issued identifiers intended to be visible.
3 sources
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
Electronic Privacy Information Center · 2026-04-20 · Primary · VA
EPIC's Fourth Circuit brief urging reversal in Norfolk. The single best distillation of the constitutional argument in the corpus, written to persuade a federal appellate court, and it rests on the Fourth Circuit's own binding precedent rather than on Carpenter alone.
- District court case number is 2:24-cv-00621-MSD-LRL, E.D. Va., Judge Mark S. Davis; appeal is No. 26-1227.
- Central argument: the court need only follow its own established rule in Leaders of a Beautiful Struggle v. Baltimore Police Department, 2 F.4th 330 (4th Cir. 2021), which assessed Baltimore's aerial surveillance program by looking at not only the raw data but what that data can reveal.
- Frames the Fourth Amendment guideposts from Carpenter as securing the privacies of life against arbitrary power (Boyd) and placing obstacles in the way of a too permeating police surveillance (Di Re).
- Argues modern ALPR systems must be judged on evolving capabilities and the inferences they enable, per Kyllo and Carpenter, not as scattered individual data points.
- Second argument: AI-enabled ALPR systems are predictive policing systems, built on unvetted, outdated and biased data overrepresenting poor and minority populations, generating suspicion inside a proprietary black box that cannot be examined or challenged - implicating the Fourth, Fifth and Sixth Amendments.
- Concludes that absent strict safeguards ALPRs revive the arbitrary powers of the reviled general warrant, and that a warrant is the proper first obstacle.
- From the litigation record (JA citations), Flock's system can stream live video and capture clips, identify other vehicles traveling with a vehicle of interest, and analyze a vehicle's past travel history to offer probabilities for where it will go next.
- Cites CRS R48160: as of 2020 every police department serving over one million residents, and about 90 percent of sheriffs' offices with 500 or more sworn deputies, were already using ALPRs.
- Notes Virginia's default retention was up to 30 days at the time of the relevant events and up to 21 days under Va. Code 2.2-5517 as of briefing, with longer retention where data is deemed relevant to an ongoing investigation.
READ IN FULL from the filed PDF on 2026-08-30. The Leaders of a Beautiful Struggle argument is the most important legal find in this corpus: it is binding Fourth Circuit precedent holding persistent aerial surveillance a search, in the very circuit now hearing Norfolk. The predictive-policing framing is also the strongest available answer to the it-is-just-photographs defense, because the system's own marketed features include next-location prediction.
Benn Jordan (YouTube) · 2026-01-01 · Secondary · national
A widely viewed technical investigation of Flock's ALPR systems by a technologist, demonstrating both plate-recognition defeat and the exposed-camera security failures.
- Reported at roughly 3 million views; among the most watched public explainers on Flock.
- Demonstrates defeating plate recognition with a near-invisible applied pattern, causing misreads and in some cases non-detection; the pattern was deliberately not published because using it may be illegal.
- Jordan participated in the research that found Flock cameras accessible over the open internet, including archived footage and deletion capability.
- Jordan also supplied congressional offices the screenshot of a Russian-language forum offering Flock accounts for sale, cited in the Wyden FTC letter.
URL IS A SEARCH QUERY, NOT THE VIDEO - the canonical watch URL was not captured and must be pinned before citing. Handle the evasion material carefully: the dossier's position is transparency and law, not defeating cameras, and at least one state has criminalized ALPR jamming. Cite Jordan for the security findings, not as a how-to.
Albuquerque's city council legislated an ALPR retention limit of FOURTEEN DAYS in 2013, then amended it to ONE YEAR in 2023 at the department's request - a twenty-six-fold increase, enacted in the open, in New Mexico.
Well supported
The case against thisThe 2023 justification is a real one: longer retention does help locate missing persons and stolen vehicles, and the ongoing-investigation exception existed in both versions. The point is not that the council acted improperly - it is that a written limit is a starting position, not a settlement.
3 sources
City of Albuquerque, Twentieth Council · 2013-11-04 · Primary · NM
A New Mexico city council legislating an ALPR retention limit by resolution - in 2013, at fourteen days - and saying plainly why.
- Enacted policy: APD shall purge each license plate image and all associated information from its databases within FOURTEEN (14) DAYS from the date of collection, unless a longer period is required for a particular image or information because of an ongoing criminal investigation.
- Sponsored by Councilor Brad Winter; introduced September 16, 2013; passed November 4, 2013.
- Recital: license plate images are in a format that allows storage and archiving for indefinite periods of time.
- Recital: in addition to its interests in detection and prevention of crime, the City has a legitimate interest in protecting the privacy of private citizens driving and parking in public places but not involved in any criminal activity.
OBTAINED IN FULL from Albuquerque's Legistar API on 2026-08-30 (matter 8918, text version 11728). PRECEDENT THAT SETTLES A LOCAL ARGUMENT: a New Mexico city council can and did legislate ALPR retention by simple resolution, thirteen years before Las Cruces councilors began asking for a surveillance policy. The privacy recital is quotable almost verbatim into a Las Cruces ordinance.
City of Albuquerque, Twenty Fifth Council · 2023-12-04 · Primary · NM
The same council, ten years later, replacing its fourteen-day purge rule with one year - a twenty-six-fold increase, requested by the department.
- Amends R-13-220 so that APD shall purge each license plate image and all associated information within ONE (1) YEAR from the date of collection, unless longer retention is required because of an ongoing criminal investigation.
- Sponsored by Councilor Renee Grout, marked BY REQUEST; introduced August 21, 2023; passed December 4, 2023.
- Recital acknowledges the council previously required APD to purge such information after fourteen days.
- Stated justification: APD can more effectively locate missing persons and stolen vehicles if permitted to access the information for a longer period of time.
- The 2013 privacy recital - the City's legitimate interest in protecting private citizens not involved in criminal activity - does not appear among the 2023 recitals.
OBTAINED IN FULL from Legistar on 2026-08-30 (matter 13444, text version 18198). THE CLEAREST DOCUMENTED CASE OF RETENTION DRIFT IN THE CORPUS, and it is local: 14 days to 365 days, a 26-fold increase, enacted by a New Mexico city council at the department's request. This is the direct answer to any assumption that writing a limit down settles the question - and note what changed between the two texts: the privacy rationale is simply absent from the amendment.
KOB 4 · undated · Primary · NM
Statewide New Mexico accounting of which agencies run ALPRs, how long they keep the data, and who they share it with.
- Bernalillo County Sheriff's Office: 21 fixed cameras planned, 30-day retention, sharing with 88 agencies including some in Arizona, Colorado and Texas.
- Albuquerque Police Department: about 250 fixed cameras, one-year retention.
- New Mexico State Police: 180-day retention, sharing with hundreds of agencies including Border Patrol and ATF.
- At the time of reporting, no New Mexico law regulated ALPR access or retention.
- Sheriff John Allen on the technology: it is really a no brainer.
- NMSP Chief Troy Weisler declined an interview.
Publication date not stated on the page; the reporting predates SB 40 and the August 2026 BCSO cancellation, both of which changed the picture. Date must be pinned before this is cited for current state.
The strongest argument for a durable ALPR ordinance is also the strongest caution about one: Albuquerque wrote its limit into a council resolution and then loosened it by a factor of twenty-six, and the privacy rationale from the 2013 text does not appear in the 2023 amendment at all.
Well supported
The case against thisCouncilor Harris's point in Las Cruces was that departmental policies can change; this shows council resolutions can too. The answer is not to give up on writing rules but to attach the things that survive drift - mandatory public reporting, sunset clauses requiring an affirmative revote, and an independent audit.
3 sources
City of Albuquerque, Twentieth Council · 2013-11-04 · Primary · NM
A New Mexico city council legislating an ALPR retention limit by resolution - in 2013, at fourteen days - and saying plainly why.
- Enacted policy: APD shall purge each license plate image and all associated information from its databases within FOURTEEN (14) DAYS from the date of collection, unless a longer period is required for a particular image or information because of an ongoing criminal investigation.
- Sponsored by Councilor Brad Winter; introduced September 16, 2013; passed November 4, 2013.
- Recital: license plate images are in a format that allows storage and archiving for indefinite periods of time.
- Recital: in addition to its interests in detection and prevention of crime, the City has a legitimate interest in protecting the privacy of private citizens driving and parking in public places but not involved in any criminal activity.
OBTAINED IN FULL from Albuquerque's Legistar API on 2026-08-30 (matter 8918, text version 11728). PRECEDENT THAT SETTLES A LOCAL ARGUMENT: a New Mexico city council can and did legislate ALPR retention by simple resolution, thirteen years before Las Cruces councilors began asking for a surveillance policy. The privacy recital is quotable almost verbatim into a Las Cruces ordinance.
City of Albuquerque, Twenty Fifth Council · 2023-12-04 · Primary · NM
The same council, ten years later, replacing its fourteen-day purge rule with one year - a twenty-six-fold increase, requested by the department.
- Amends R-13-220 so that APD shall purge each license plate image and all associated information within ONE (1) YEAR from the date of collection, unless longer retention is required because of an ongoing criminal investigation.
- Sponsored by Councilor Renee Grout, marked BY REQUEST; introduced August 21, 2023; passed December 4, 2023.
- Recital acknowledges the council previously required APD to purge such information after fourteen days.
- Stated justification: APD can more effectively locate missing persons and stolen vehicles if permitted to access the information for a longer period of time.
- The 2013 privacy recital - the City's legitimate interest in protecting private citizens not involved in criminal activity - does not appear among the 2023 recitals.
OBTAINED IN FULL from Legistar on 2026-08-30 (matter 13444, text version 18198). THE CLEAREST DOCUMENTED CASE OF RETENTION DRIFT IN THE CORPUS, and it is local: 14 days to 365 days, a 26-fold increase, enacted by a New Mexico city council at the department's request. This is the direct answer to any assumption that writing a limit down settles the question - and note what changed between the two texts: the privacy rationale is simply absent from the amendment.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Las Cruces councilors asking for a city surveillance policy do not need to invent one or wait for the state: Albuquerque's council legislated ALPR retention by simple resolution in 2013, and its privacy recital - the City's legitimate interest in protecting private citizens driving and parking in public places but not involved in any criminal activity - is quotable almost verbatim.
Well supported
The case against thisA retention-purge resolution is narrower than the citywide surveillance policy Las Cruces councilors describe, and Albuquerque's own experience shows such a resolution can be amended later.
4 sources
City of Albuquerque, Twentieth Council · 2013-11-04 · Primary · NM
A New Mexico city council legislating an ALPR retention limit by resolution - in 2013, at fourteen days - and saying plainly why.
- Enacted policy: APD shall purge each license plate image and all associated information from its databases within FOURTEEN (14) DAYS from the date of collection, unless a longer period is required for a particular image or information because of an ongoing criminal investigation.
- Sponsored by Councilor Brad Winter; introduced September 16, 2013; passed November 4, 2013.
- Recital: license plate images are in a format that allows storage and archiving for indefinite periods of time.
- Recital: in addition to its interests in detection and prevention of crime, the City has a legitimate interest in protecting the privacy of private citizens driving and parking in public places but not involved in any criminal activity.
OBTAINED IN FULL from Albuquerque's Legistar API on 2026-08-30 (matter 8918, text version 11728). PRECEDENT THAT SETTLES A LOCAL ARGUMENT: a New Mexico city council can and did legislate ALPR retention by simple resolution, thirteen years before Las Cruces councilors began asking for a surveillance policy. The privacy recital is quotable almost verbatim into a Las Cruces ordinance.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Brennan Center for Justice · 2020-09-10 · Primary · national
Seven concrete policy recommendations for ALPR regulation - the closest thing in the corpus to ready-made ordinance language for a city council.
- Retention and warrants: delete non-matching plate scans immediately; if retained, limit to days rather than months; require a warrant for historical database searches absent emergency.
- Two-step scanning: the first query reveals only registration and hot-list status, and accessing personal information requires a basis for further police action.
- Hot list verification: mandate independent verification of hot-list data and real-time updates to prevent erroneous stops.
- Public transparency and input: communities participate in deployment decisions; policies published; audit results disclosed.
- Audit logs: track automated alerts, officer access to historical data, and all inter-agency data-sharing arrangements.
- Disparate impact audits: evaluate whether deployment disproportionately targets marginalized communities or protected activities.
- Safeguard effectiveness audits: regular review that access controls and retention actually function.
- Legal status as of 2020: no bright-line warrant rule; appeals courts had avoided direct engagement with Carpenter's application to ALPR.
READ on 2026-08-30, closing a gap this dossier had flagged as unread. Published 2020, so its legal-status section is superseded by Rinaldi, Norfolk and Chatrie - but the RECOMMENDATIONS are the durable part and map almost one to one onto what Las Cruces councilors are asking for. Hot-list verification and two-step scanning are the two that directly address the wrong-car gunpoint stops.
New Mexico News Port · 2026-08-18 · Secondary · local:las-cruces
Fuller account of the Las Cruces councilors' oversight push, including their reaction after two hours with an LCPD lieutenant.
- Councilors Michael Harris and Johana Bencomo seek a city-level surveillance policy and a public portal showing how police collect, search and share vehicle data.
- They raised the issue after about two hours with an LCPD lieutenant going through the city's use of Flock in detail.
- Harris remains uneasy about what he called creeping surveillance but came away impressed by some of the safeguards LCPD has in place, and wants a citywide policy rather than departmental rules.
- Bencomo continues to oppose mass surveillance but expressed confidence in the LCPD team after the discussion: I have trust in him and the team that we can move forward into this place of being very transparent and honest and responsible with the kind of data that we are collecting from our residents.
IMPORTANT FOR TONE. The two councilors most critical of the technology both came away from a detailed briefing with a measure of confidence in their own department while still wanting a citywide policy. A dossier that renders Las Cruces as a fight between residents and a hostile police department would misdescribe the actual local situation, and would be corrected in the room.
Las Cruces was the first agency in New Mexico to adopt Flock, starting with license plate readers in January 2022 - stated by Chief Jeremy Story on the record at a neighboring city's commission meeting.
Well supported
The case against thisA chief's public statement is strong evidence of adoption date but not a document; the contract would confirm it.
2 sources
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
Flock's route into a New Mexico city ran through a neighboring police chief: at Alamogordo's December 2024 commission meeting, the LAS CRUCES chief presented alongside two Flock employees, one of whom is the company's named contact on the state price agreement.
Well supported1 of 3 sources not read at source
The case against thisChiefs sharing experience with neighboring departments is ordinary and valuable, and Story's framing - sister cities, crime does not respect borders - is a real argument. It is still worth naming plainly that a public agency's chief appeared as a credibility witness in a vendor's sales presentation to another government.
3 sources
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
State of New Mexico General Services Department, Purchasing Division · 2026-01-09 · Primary · NM
The mechanism by which any New Mexico public body can buy license plate readers without running its own procurement. A statewide price agreement titled License Plate Recognition, with Flock Group Inc. among the awarded vendors, open to every agency and political subdivision in the state.
- Agreement number 30-00000-22-00018, titled License Plate Recognition, issued by the New Mexico General Services Department Purchasing Division.
- FIVE awarded vendors, of which Flock Group Inc. is one (Supplier ID 0000170812).
- Term: January 13, 2023 through January 12, 2027, extended by Amendment Eight from January 12, 2026 at the same price, terms and conditions.
- Ship To reads: All State of New Mexico agencies, commissions, institutions, political subdivisions and local public bodies allowed by law.
- Amendment Eight signed January 9, 2026 by State Purchasing Agent Dorothy Mendonca; procurement specialist Theresa Mendibles.
- Dona Ana County's June 9, 2026 approval was of USE of this agreement, not a competitive procurement of its own.
OBTAINED FROM PRIMARY SOURCE on 2026-08-30, inside the Dona Ana County BOCC agenda packet for June 9, 2026 (428 pages), retrieved through the county's CivicClerk API. THIS IS THE STRUCTURAL EXPLANATION FOR THE LAS CRUCES GAP and it is entirely lawful: a New Mexico public body does not have to run a procurement, or necessarily hold a council vote, to buy Flock - it can buy off the statewide price agreement. That reframes 'procurement that outruns consent' from a suspicion about one city into a description of how the state set the system up. IT IS ALSO THE MOST DIRECT POLICY LEVER IN THE CORPUS: the agreement is a state instrument, it can be conditioned or allowed to lapse, and IT EXPIRES JANUARY 12, 2027. The full Flock Safety Agreement was listed among the packet's supporting documents but its terms did not appear in the extracted text - retrieve it from GSD directly.
404 Media · undated · Primary · national
Interview with Jonathan Paz, a former Flock employee whose job was persuading city councils and other bodies to buy Flock cameras, and who became disillusioned with the company.
- Jonathan Paz's role at Flock was convincing city councils and similar bodies to purchase Flock cameras.
- He left disillusioned and spoke publicly about the company.
NOT LISTENED TO; URL is the podcast tag page, not the episode. HIGH VALUE IF PINNED: an insider account of how the sales pitch to councils is constructed is directly relevant to the staff-report-versus-contract comparison this project runs. Find the specific episode, listen, and record what he actually says before attributing anything to him.
Local-federal ALPR cooperation is stated plainly in New Mexico council minutes: Alamogordo's chief described partnering with Border Patrol on two kidnapping suspects in November 2024, with Border Patrol entering the vehicle into its own plate reader, getting a hit, and an arrest the next day.
Well supported
The case against thisThis is a serious crime and a legitimate use, described by the chief as a success. It also documents the routine channel between a small New Mexico department and federal border ALPR infrastructure - the same channel that carries immigration searches elsewhere in this dossier.
3 sources
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
Electronic Frontier Foundation · 2025-12-02 · Primary · national
Field guide documenting federal and covert ALPR infrastructure across the borderlands, including retention periods far longer than any local policy.
- CBP systems at all land ports of entry capture vehicles entering and exiting.
- Interior checkpoints, from a few to more than 60 miles inland, carry CBP ALPR systems.
- CBP retains this data for 15 years; agents can generally search the recent five years.
- About 100 covert ALPR sites identified across the border region, disguised in orange construction barrels and yellow sandbags, often in sets of three with solar panels.
- CBP solicited 100 additional covert trail cameras with plate capture in July 2025.
- Flock Safety camera poles documented outside the Santa Teresa Border Patrol station in New Mexico.
- CBP announced plans to integrate port-of-entry ALPRs into DEA's National License Plate Reader Program.
The 15-year federal retention is the number that reframes the local debate: a 21-day or 30-day local policy does not bound what the federal layer keeps.
Associated Press · 2025-11-20 · Primary · national
AP investigation revealing a secretive Border Patrol predictive intelligence program that scores drivers' travel patterns from license plate reads and refers them for stops, searches and arrests.
- Border Patrol is monitoring millions of American drivers nationwide in a secretive predictive intelligence program.
- An algorithm flags vehicles as suspicious based on where they came from, where they were going, and which route they took.
- Flagged drivers are pulled over on pretextual grounds - speeding, failure to signal, window tint, a dangling air freshener - and in some cases searched and arrested.
- Border Patrol defined its own criteria for suspicion, including driving on backcountry roads, being in a rental car, or making short trips to the border region.
- The agency has for years hidden details of the program; readers are often disguised along highways inside traffic safety equipment such as drums and barrels.
The most important source in the corpus for the New Mexico chapter. It shows the federal layer doing exactly what critics say the local layer enables - pattern-of-life scoring without suspicion - and it explains the pretextual-stop mechanism that hides the surveillance from the person stopped. AP is the wire original; the PBS URL is a syndication and was chosen because it fetches. Read the AP original before quoting.
What New Mexico departments describe buying is not cameras but a Real-Time Crime Center: Alamogordo's chief presented plate readers and live-view PTZ cameras as components of an RTCC, and Las Cruces' chief said its RTCC would be operational in February 2025.
Well supported
The case against thisAlamogordo's chief addressed the objection directly - an RTCC is not a big brother or government overreach - and centralizing feeds a department already has is not new collection. The mosaic argument is about aggregation, which is what an RTCC is for.
4 sources
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
Contrary Research / CB Insights / 9th Street Journal · 2025-08-01 · Secondary · national
The data-fusion platform that Las Cruces' Flock contract integrates with: it unifies fragmented law enforcement data - body camera footage, dispatch records and more - into a single real-time searchable system.
- Founded 2018 by former Palantir executive Nick Noone and technologist Ben Rudolph; roughly a quarter of the team are Palantir alumni.
- Unifies fragmented law enforcement data from body-camera footage to dispatch records into one real-time system for search, analysis and decision-making.
- As of August 2025 serves agencies covering more than 80 million Americans; 250 million dollars raised at a 2.5 billion dollar valuation.
- In Durham, residents objected to a police software contract citing data privacy and predictive policing concerns.
THE LOCAL HOOK. Las Cruces' contract includes a Peregrine integration, so the fusion layer this dossier describes in the abstract is already contracted for in Las Cruces. Company details come from investor-facing research profiles, which are promotional in tone - verify independently before citing figures.
Police1 · 2024-02-08 · Secondary · national
Axon completed its acquisition of Fusus, whose platform aggregates live video, data and sensor feeds from many sources into a single real-time crime center view.
- Acquisition completed February 2024.
- Fusus aggregates live video, data and sensor feeds from disparate sources simultaneously.
- Axon has since announced fixed ALPR cameras (Outpost, Lightpost) and a Ring integration for citizen video sharing.
- Real-time crime centers have expanded to more than 250 cities and counties.
The fusion layer is the part that matters constitutionally: plate reads become a location dragnet only when joined to identity, video and other feeds in one interface.
Asked directly whether the cameras build a continuous database of citizens' movements, a New Mexico police chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - while saying his own city's cameras are placed for single fixed-point reads instead.
Well supported
The case against thisThis is a candid and accurate answer, and his distinction is the same one the Norfolk court drew - coverage, not capability, is what makes a mosaic. It also concedes the mechanism: whether a deployment tracks continuously is a question of how many cameras are placed where, which is a dial that turns as deployments grow.
3 sources
City of Alamogordo City Commission · 2026-08-11 · Primary · NM
The most thorough public accountability session on ALPR in the New Mexico record: a police chief answering commissioners' direct questions about retention, tracking, sharing, redaction, hacking and internal misuse. Several of his answers confirm arguments this dossier makes nationally.
- The city is under a TWO-YEAR agreement with Flock Safety.
- RETENTION: data is automatically purged after 30 days UNLESS DOWNLOADED AND SAVED AS EVIDENCE. Live-view data from major intersection cameras is kept 7 days.
- Asked whether data is saved when a crime occurs rather than erased, the chief said yes - officers can download and PERMANENTLY save live-view footage used in an investigation.
- SHARING: data is shared with other local police agencies, the minutes giving Dallas, Texas as an example, to track fleeing suspects - but not with federal agencies.
- Asked directly whether the cameras use AI to build a continuous database tracking citizens' movements past multiple cameras, the chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - but that Alamogordo's cameras are placed for single fixed-point reads rather than continuous tracking.
- The Flock system does not display driver's license, registration, insurance or immigration information - but officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
- Hot list alerts carry a 3 to 5 minute delay; partial plate and vehicle-characteristic searches are supported.
- Accounts are created manually by a single named administrator; policy requires a legitimate law enforcement reason for any search, per NCIC standards; the system is audited monthly, both programmatically and manually.
- The system does NOT automatically redact faces - redactions in the demonstration video were done manually by the City Clerk and her staff.
- Police have access to Flock cameras in business parking lots only if the business explicitly grants it, and no access to residential Ring cameras unless a resident shares footage.
- Cost framing offered by the chief: an officer costs the city about 94,000 dollars a year, and the Flock system essentially places an officer at a fixed point 24 hours a day, 365 days a year.
- Case examples given: a stolen-vehicle report resolved as a legal repossession, avoiding a high-risk felony stop; a sexual assault suspect arrested within 30 minutes from a vehicle description; an armed disturbance resolved in 2 minutes; a shooting suspect identified with nine felony charges within 4 hours.
- The department's hit-and-run crash rate increased by 76 percent.
ORIGINAL RESEARCH, 2026-08-30, from the Alamogordo CivicClerk record (August 11 minutes carried in the August 25 packet, file 3957). THIS IS THE BEST LOCAL ACCOUNTABILITY DOCUMENT IN THE CORPUS and it cuts in every direction at once. It is a model of what a commission SHOULD ask. It also contains a New Mexico chief confirming, in his own words, three things this dossier argues from national sources: the 30-day retention does not bind DOWNLOADED records; consecutive cameras would technically produce continuous tracking; and the plate is a bridge into NCIC even though Flock itself shows no registration or immigration data. And the sharing answer - not federal, but yes to other local agencies including in TEXAS - is precisely the route by which New Mexico data reaches a state with no ALPR statute. The stolen-vehicle-as-repossession example is a genuine harm PREVENTED, and belongs in the record too.
Massachusetts Supreme Judicial Court · 2020-04-16 · Primary · MA
The first appellate decision applying the Fourth Amendment to ALPRs. The court adopted the mosaic approach: four cameras on two bridges did not invade a reasonable expectation of privacy, but enough readers in enough places would.
- Police used ALPRs on the Bourne and Sagamore bridges to track the defendant's crossings over three months.
- Held: a person has a constitutionally protected expectation of privacy in the whole of his public movements.
- Held: the limited extent of this ALPR use did not invade that interest, but historical data from enough readers in enough locations would constitute a search.
McCarthy is the case both sides cite. It sets a threshold rather than a rule, which is exactly why camera density and retention are the facts that decide these cases.
United States District Court, Eastern District of Virginia · 2026-01-27 · Primary · VA
The order the Fourth Circuit is reviewing: summary judgment for Norfolk, distinguishing Carpenter on the ground that fixed cameras capture discrete moments rather than the sum of a person's movements.
- 51-page opinion, ECF No. 191, filed January 27, 2026. Case No. 2:24-cv-00621-MSD-RJK.
- The court frames the dispositive question as whether alleged dragnet type law enforcement practices under Knotts have become so intrusive that they violate a reasonable expectation of privacy in the whole of a person's physical movements under Carpenter.
- The court states that federal and state courts analyzing ALPR claims have ALMOST UNIFORMLY concluded that neither photographing a plate on a public roadway nor maintaining and querying a database of ALPR photos is a warrantless search, citing Rinaldi v. Sylvester, 2025 WL 2682691, at *17 (S.D.N.Y. Sept. 19, 2025) as collecting those cases.
- Norfolk operates 176 Flock cameras around the clock, pole-mounted beside public roadways, photographing virtually every passing vehicle and storing the images in a searchable database.
- The cameras cover 75 designated areas; the court reasons they are capable of locating a vehicle only for the brief time it is within one of those areas.
- Retention: the system retained ALPR data for 30 days, and now generally retains it for 21 days following a mid-2025 state statute.
- CRITICAL: the court records that this retention period does not prevent the long-term retention of ALPR data that is DOWNLOADED from the Flock system.
- Undisputed that plaintiffs' vehicles were photographed approximately 475 and 325 times during a four-and-a-half month period in early 2025.
- During an average 21-day retention period the system captured full plate matches of plaintiffs' vehicles an average of 2 to 3 times per day.
- Plaintiffs were held to HAVE STANDING to challenge the collection and storage of their vehicles' images.
- The court distinguishes Leaders of a Beautiful Struggle: Baltimore's AIR program tracked the whole of every vehicle's and pedestrian's movements anywhere outside in the city even though the planes did not fly at night or in poor weather, leaving multi-hour gaps in coverage.
- Quoting Carpenter's caution not to embarrass the future, the court states that such experimentation is best achieved with input from the public and with guardrails erected by STATE LEGISLATURES OR LOCAL GOVERNING BODIES, as is the case in Virginia.
- Cites Justice Alito's concurrence in Jones on new technology trading privacy for convenience, and on privacy concerns spurring legislative enactment.
READ FROM THE ORDER ITSELF on 2026-08-30, replacing an earlier entry based on an automated summary and press coverage. CORRECTION: the docket is 2:24-cv-00621-MSD-RJK, not MSD-LRL as press coverage had it. THREE THINGS THE PRESS COVERAGE MISSED. (1) The 21-day retention does not bind DOWNLOADED data - an officer who downloads a record keeps it indefinitely, which undercuts every retention-based defense including the vendor's. (2) The court's own distinction of Beautiful Struggle concedes that multi-hour GAPS in coverage did not save Baltimore's program - so the gaps reasoning is narrower than reported; what mattered was that AIR tracked everyone everywhere outside, while Norfolk's cameras cover 75 designated areas. (3) The court expressly points to state legislatures and local governing bodies as the right place for guardrails. That is a judicial invitation to exactly the municipal ordinance Las Cruces councilors are drafting, and it should be quoted to them.
Alamogordo's chief told his commission the department shares ALPR data with other local police agencies - giving Dallas, Texas as the example - while not sharing with federal agencies. Texas has no ALPR statute at all.
Well supported
The case against thisSharing to track fleeing suspects across state lines is a real investigative need, and declining federal sharing is a deliberate limit the department chose. The point is that the not-federal answer, which is the one commissioners usually ask for, leaves open the route that actually carried New Mexico data into Texas - and SB 40 now requires a written declaration before any such out-of-state access.
4 sources
City of Alamogordo City Commission · 2026-08-11 · Primary · NM
The most thorough public accountability session on ALPR in the New Mexico record: a police chief answering commissioners' direct questions about retention, tracking, sharing, redaction, hacking and internal misuse. Several of his answers confirm arguments this dossier makes nationally.
- The city is under a TWO-YEAR agreement with Flock Safety.
- RETENTION: data is automatically purged after 30 days UNLESS DOWNLOADED AND SAVED AS EVIDENCE. Live-view data from major intersection cameras is kept 7 days.
- Asked whether data is saved when a crime occurs rather than erased, the chief said yes - officers can download and PERMANENTLY save live-view footage used in an investigation.
- SHARING: data is shared with other local police agencies, the minutes giving Dallas, Texas as an example, to track fleeing suspects - but not with federal agencies.
- Asked directly whether the cameras use AI to build a continuous database tracking citizens' movements past multiple cameras, the chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - but that Alamogordo's cameras are placed for single fixed-point reads rather than continuous tracking.
- The Flock system does not display driver's license, registration, insurance or immigration information - but officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
- Hot list alerts carry a 3 to 5 minute delay; partial plate and vehicle-characteristic searches are supported.
- Accounts are created manually by a single named administrator; policy requires a legitimate law enforcement reason for any search, per NCIC standards; the system is audited monthly, both programmatically and manually.
- The system does NOT automatically redact faces - redactions in the demonstration video were done manually by the City Clerk and her staff.
- Police have access to Flock cameras in business parking lots only if the business explicitly grants it, and no access to residential Ring cameras unless a resident shares footage.
- Cost framing offered by the chief: an officer costs the city about 94,000 dollars a year, and the Flock system essentially places an officer at a fixed point 24 hours a day, 365 days a year.
- Case examples given: a stolen-vehicle report resolved as a legal repossession, avoiding a high-risk felony stop; a sexual assault suspect arrested within 30 minutes from a vehicle description; an armed disturbance resolved in 2 minutes; a shooting suspect identified with nine felony charges within 4 hours.
- The department's hit-and-run crash rate increased by 76 percent.
ORIGINAL RESEARCH, 2026-08-30, from the Alamogordo CivicClerk record (August 11 minutes carried in the August 25 packet, file 3957). THIS IS THE BEST LOCAL ACCOUNTABILITY DOCUMENT IN THE CORPUS and it cuts in every direction at once. It is a model of what a commission SHOULD ask. It also contains a New Mexico chief confirming, in his own words, three things this dossier argues from national sources: the 30-day retention does not bind DOWNLOADED records; consecutive cameras would technically produce continuous tracking; and the plate is a bridge into NCIC even though Flock itself shows no registration or immigration data. And the sharing answer - not federal, but yes to other local agencies including in TEXAS - is precisely the route by which New Mexico data reaches a state with no ALPR statute. The stolen-vehicle-as-repossession example is a genuine harm PREVENTED, and belongs in the record too.
Government Technology, reporting the NYU Policing Project analysis · 2026-08-18 · Primary · national
The Policing Project at NYU School of Law scored every state's ALPR regulation on seven criteria. The finding that matters most to New Mexico is about its neighbors.
- Seven criteria: privacy protections, false positive verification, data sharing protocols, protest monitoring restrictions, compliance audits, transparency requirements, and enforcement mechanisms.
- Highest scorers at 6 of 7: Connecticut, Oregon, Virginia and Washington.
- TWENTY-SIX STATES HAVE NO ALPR LEGISLATION AT ALL, including Arizona, Colorado and Texas.
- Washington D.C., Florida and Tennessee have laws that do not meet the organization's definition of effective regulation.
- New Mexico is not referenced in the article; individual scores are not published for most states.
THE LOCAL POINT IS THE NEIGHBORS. Bernalillo County shared ALPR data with 88 agencies including some in Arizona, Colorado and Texas - and all three of those states have NO ALPR statute whatsoever. New Mexico's SB 40 written declaration requirement is therefore the only instrument standing between New Mexico data and three unregulated jurisdictions. New Mexico's own score is not stated here; retrieve the underlying Policing Project scorecard directly.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
The answer that a plate reader shows no registration, insurance or immigration data is true and incomplete: officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
Well supported
The case against thisRunning a plate through NCIC is ordinary police work that long predates ALPR. What ALPR changes is the volume of plates available to run and the fact that they can be pulled retroactively from a location and time rather than from an officer's own observation.
2 sources
City of Alamogordo City Commission · 2026-08-11 · Primary · NM
The most thorough public accountability session on ALPR in the New Mexico record: a police chief answering commissioners' direct questions about retention, tracking, sharing, redaction, hacking and internal misuse. Several of his answers confirm arguments this dossier makes nationally.
- The city is under a TWO-YEAR agreement with Flock Safety.
- RETENTION: data is automatically purged after 30 days UNLESS DOWNLOADED AND SAVED AS EVIDENCE. Live-view data from major intersection cameras is kept 7 days.
- Asked whether data is saved when a crime occurs rather than erased, the chief said yes - officers can download and PERMANENTLY save live-view footage used in an investigation.
- SHARING: data is shared with other local police agencies, the minutes giving Dallas, Texas as an example, to track fleeing suspects - but not with federal agencies.
- Asked directly whether the cameras use AI to build a continuous database tracking citizens' movements past multiple cameras, the chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - but that Alamogordo's cameras are placed for single fixed-point reads rather than continuous tracking.
- The Flock system does not display driver's license, registration, insurance or immigration information - but officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
- Hot list alerts carry a 3 to 5 minute delay; partial plate and vehicle-characteristic searches are supported.
- Accounts are created manually by a single named administrator; policy requires a legitimate law enforcement reason for any search, per NCIC standards; the system is audited monthly, both programmatically and manually.
- The system does NOT automatically redact faces - redactions in the demonstration video were done manually by the City Clerk and her staff.
- Police have access to Flock cameras in business parking lots only if the business explicitly grants it, and no access to residential Ring cameras unless a resident shares footage.
- Cost framing offered by the chief: an officer costs the city about 94,000 dollars a year, and the Flock system essentially places an officer at a fixed point 24 hours a day, 365 days a year.
- Case examples given: a stolen-vehicle report resolved as a legal repossession, avoiding a high-risk felony stop; a sexual assault suspect arrested within 30 minutes from a vehicle description; an armed disturbance resolved in 2 minutes; a shooting suspect identified with nine felony charges within 4 hours.
- The department's hit-and-run crash rate increased by 76 percent.
ORIGINAL RESEARCH, 2026-08-30, from the Alamogordo CivicClerk record (August 11 minutes carried in the August 25 packet, file 3957). THIS IS THE BEST LOCAL ACCOUNTABILITY DOCUMENT IN THE CORPUS and it cuts in every direction at once. It is a model of what a commission SHOULD ask. It also contains a New Mexico chief confirming, in his own words, three things this dossier argues from national sources: the 30-day retention does not bind DOWNLOADED records; consecutive cameras would technically produce continuous tracking; and the plate is a bridge into NCIC even though Flock itself shows no registration or immigration data. And the sharing answer - not federal, but yes to other local agencies including in TEXAS - is precisely the route by which New Mexico data reaches a state with no ALPR statute. The stolen-vehicle-as-repossession example is a genuine harm PREVENTED, and belongs in the record too.
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
Alamogordo's August 2026 session is the model for what a governing body should ask: commissioners put direct questions about continuous tracking, hacking, internal misuse, face redaction, doorbell and business camera access, and what the system costs against an officer's salary - and got specific answers on the record.
Well supported
The case against thisThe answers are the department's own account, unaudited by anyone outside it - the monthly audit the chief describes is run by the department on itself. A hearing is a floor, not a substitute for the independent audit and public reporting the dossier recommends elsewhere.
4 sources
City of Alamogordo City Commission · 2026-08-11 · Primary · NM
The most thorough public accountability session on ALPR in the New Mexico record: a police chief answering commissioners' direct questions about retention, tracking, sharing, redaction, hacking and internal misuse. Several of his answers confirm arguments this dossier makes nationally.
- The city is under a TWO-YEAR agreement with Flock Safety.
- RETENTION: data is automatically purged after 30 days UNLESS DOWNLOADED AND SAVED AS EVIDENCE. Live-view data from major intersection cameras is kept 7 days.
- Asked whether data is saved when a crime occurs rather than erased, the chief said yes - officers can download and PERMANENTLY save live-view footage used in an investigation.
- SHARING: data is shared with other local police agencies, the minutes giving Dallas, Texas as an example, to track fleeing suspects - but not with federal agencies.
- Asked directly whether the cameras use AI to build a continuous database tracking citizens' movements past multiple cameras, the chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - but that Alamogordo's cameras are placed for single fixed-point reads rather than continuous tracking.
- The Flock system does not display driver's license, registration, insurance or immigration information - but officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
- Hot list alerts carry a 3 to 5 minute delay; partial plate and vehicle-characteristic searches are supported.
- Accounts are created manually by a single named administrator; policy requires a legitimate law enforcement reason for any search, per NCIC standards; the system is audited monthly, both programmatically and manually.
- The system does NOT automatically redact faces - redactions in the demonstration video were done manually by the City Clerk and her staff.
- Police have access to Flock cameras in business parking lots only if the business explicitly grants it, and no access to residential Ring cameras unless a resident shares footage.
- Cost framing offered by the chief: an officer costs the city about 94,000 dollars a year, and the Flock system essentially places an officer at a fixed point 24 hours a day, 365 days a year.
- Case examples given: a stolen-vehicle report resolved as a legal repossession, avoiding a high-risk felony stop; a sexual assault suspect arrested within 30 minutes from a vehicle description; an armed disturbance resolved in 2 minutes; a shooting suspect identified with nine felony charges within 4 hours.
- The department's hit-and-run crash rate increased by 76 percent.
ORIGINAL RESEARCH, 2026-08-30, from the Alamogordo CivicClerk record (August 11 minutes carried in the August 25 packet, file 3957). THIS IS THE BEST LOCAL ACCOUNTABILITY DOCUMENT IN THE CORPUS and it cuts in every direction at once. It is a model of what a commission SHOULD ask. It also contains a New Mexico chief confirming, in his own words, three things this dossier argues from national sources: the 30-day retention does not bind DOWNLOADED records; consecutive cameras would technically produce continuous tracking; and the plate is a bridge into NCIC even though Flock itself shows no registration or immigration data. And the sharing answer - not federal, but yes to other local agencies including in TEXAS - is precisely the route by which New Mexico data reaches a state with no ALPR statute. The stolen-vehicle-as-repossession example is a genuine harm PREVENTED, and belongs in the record too.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Brennan Center for Justice · 2020-09-10 · Primary · national
Seven concrete policy recommendations for ALPR regulation - the closest thing in the corpus to ready-made ordinance language for a city council.
- Retention and warrants: delete non-matching plate scans immediately; if retained, limit to days rather than months; require a warrant for historical database searches absent emergency.
- Two-step scanning: the first query reveals only registration and hot-list status, and accessing personal information requires a basis for further police action.
- Hot list verification: mandate independent verification of hot-list data and real-time updates to prevent erroneous stops.
- Public transparency and input: communities participate in deployment decisions; policies published; audit results disclosed.
- Audit logs: track automated alerts, officer access to historical data, and all inter-agency data-sharing arrangements.
- Disparate impact audits: evaluate whether deployment disproportionately targets marginalized communities or protected activities.
- Safeguard effectiveness audits: regular review that access controls and retention actually function.
- Legal status as of 2020: no bright-line warrant rule; appeals courts had avoided direct engagement with Carpenter's application to ALPR.
READ on 2026-08-30, closing a gap this dossier had flagged as unread. Published 2020, so its legal-status section is superseded by Rinaldi, Norfolk and Chatrie - but the RECOMMENDATIONS are the durable part and map almost one to one onto what Las Cruces councilors are asking for. Hot-list verification and two-step scanning are the two that directly address the wrong-car gunpoint stops.
Dona Ana County Board of County Commissioners · 2026-06-09 · Primary · local:dona-ana-county
The county's own record of buying Flock: a named agenda item, a staff summary, a roll-call vote, and a link to the meeting video - the complete opposite of what the Las Cruces record contains.
- Item 12: Approve use of New Mexico State Pricing Agreement 30-00000-22-00018 with Flock Group Inc. for license plate reader cameras and annual subscription services in the amount of 162,000 dollars, and delegate signature authority to the County Manager for all related documents.
- Initiating department: Dona Ana County Sheriff's Office; contact person Kim Stewart, Sheriff.
- Staff summary states: DASO currently utilizes Flock cameras throughout the county. The cameras are license plate readers used for crime resolution and prevention.
- Financial impact stated as funds included in the Sheriff's Office FY26 budget; administrative approvals by the Finance Director and Purchasing Manager, June 4-5, 2026.
- Passed on a roll call recorded in the June 23, 2026 minutes: motion by Chair Manuel Sanchez, second by Commissioner Christopher Schaljo-Hernandez; Schaljo-Hernandez, Kimble, Chaparro and Sanchez voting yes, Vice Chair Gloria Gameros absent - carried 4-0.
- The minutes carry a timestamped link to the meeting video at the item: https://youtu.be/1nJov8_XGmg?t=20873
- The agenda is published in English and Spanish.
ORIGINAL RESEARCH, retrieved 2026-08-30 by scanning all 158 published files (28.3 million characters) in the county's CivicClerk portal. This is what an ALPR purchase looks like when it goes through a public body properly: named vendor, named agreement, dollar figure, sponsoring official, staff summary, recorded roll-call vote, and video. It is the control for the Las Cruces finding, and it is also the honest counterweight - the county did this in the open. Note the supporting documentation list includes a Flock Safety Agreement whose terms were NOT in the extracted text; that agreement is the thing to request next.
The local record includes harms prevented, not only harms caused: an Alamogordo stolen-vehicle report was quickly identified as a lawful repossession, avoiding a high-risk felony traffic stop of an innocent driver.
Well supported
The case against thisThis is the mirror image of the wrong-car gunpoint cases, and a dossier that carries those and omits this is not describing the record. It also supports the Brennan Center's hot-list verification recommendation, which is aimed at exactly this failure mode.
2 sources
City of Alamogordo City Commission · 2026-08-11 · Primary · NM
The most thorough public accountability session on ALPR in the New Mexico record: a police chief answering commissioners' direct questions about retention, tracking, sharing, redaction, hacking and internal misuse. Several of his answers confirm arguments this dossier makes nationally.
- The city is under a TWO-YEAR agreement with Flock Safety.
- RETENTION: data is automatically purged after 30 days UNLESS DOWNLOADED AND SAVED AS EVIDENCE. Live-view data from major intersection cameras is kept 7 days.
- Asked whether data is saved when a crime occurs rather than erased, the chief said yes - officers can download and PERMANENTLY save live-view footage used in an investigation.
- SHARING: data is shared with other local police agencies, the minutes giving Dallas, Texas as an example, to track fleeing suspects - but not with federal agencies.
- Asked directly whether the cameras use AI to build a continuous database tracking citizens' movements past multiple cameras, the chief answered that TECHNICALLY, if a city has multiple cameras lined up consecutively, it will show consecutive reads of a vehicle - but that Alamogordo's cameras are placed for single fixed-point reads rather than continuous tracking.
- The Flock system does not display driver's license, registration, insurance or immigration information - but officers can take a plate captured by Flock and run it through NCIC, which they already had access to.
- Hot list alerts carry a 3 to 5 minute delay; partial plate and vehicle-characteristic searches are supported.
- Accounts are created manually by a single named administrator; policy requires a legitimate law enforcement reason for any search, per NCIC standards; the system is audited monthly, both programmatically and manually.
- The system does NOT automatically redact faces - redactions in the demonstration video were done manually by the City Clerk and her staff.
- Police have access to Flock cameras in business parking lots only if the business explicitly grants it, and no access to residential Ring cameras unless a resident shares footage.
- Cost framing offered by the chief: an officer costs the city about 94,000 dollars a year, and the Flock system essentially places an officer at a fixed point 24 hours a day, 365 days a year.
- Case examples given: a stolen-vehicle report resolved as a legal repossession, avoiding a high-risk felony stop; a sexual assault suspect arrested within 30 minutes from a vehicle description; an armed disturbance resolved in 2 minutes; a shooting suspect identified with nine felony charges within 4 hours.
- The department's hit-and-run crash rate increased by 76 percent.
ORIGINAL RESEARCH, 2026-08-30, from the Alamogordo CivicClerk record (August 11 minutes carried in the August 25 packet, file 3957). THIS IS THE BEST LOCAL ACCOUNTABILITY DOCUMENT IN THE CORPUS and it cuts in every direction at once. It is a model of what a commission SHOULD ask. It also contains a New Mexico chief confirming, in his own words, three things this dossier argues from national sources: the 30-day retention does not bind DOWNLOADED records; consecutive cameras would technically produce continuous tracking; and the plate is a bridge into NCIC even though Flock itself shows no registration or immigration data. And the sharing answer - not federal, but yes to other local agencies including in TEXAS - is precisely the route by which New Mexico data reaches a state with no ALPR statute. The stolen-vehicle-as-repossession example is a genuine harm PREVENTED, and belongs in the record too.
Electronic Frontier Foundation · 2024-11-01 · Primary · national
Case-by-case account of innocent drivers stopped at gunpoint after ALPR misreads or stale hot-list entries, with settlement figures.
- Brittney Gilliam, Aurora, Colorado, August 2020: a Colorado SUV matched to a stolen Montana motorcycle plate; family detained at gunpoint with children face-down on pavement; Aurora settled for 1.9 million dollars.
- Denise Green, San Francisco, March 2009: reader misread a 3 as a 7; officers drew guns; city paid 495,000 dollars.
- Jaclynn Gonzales, Espanola, New Mexico: reader mistook a 2 for a 7; detained at gunpoint, her 12-year-old sister placed in a patrol vehicle.
- Jason Burkleo, Atherton, California: misread an H as an M; detained at gunpoint.
- Brian Hofer, Contra Costa County, Thanksgiving 2019: hot list not updated after the vehicle was recovered; 49,500 dollar settlement.
- Isoke Robinson, Detroit: police queried all Dodge Chargers near a shooting; handcuffed at home, 2-year-old placed in a patrol car, car impounded three weeks.
- Cited study: ALPRs misread the state of one in ten plates, before counting other reading errors.
The Espanola case is the New Mexico entry in this list and belongs in the local chapter as well as the harms chapter.
Where a Flock purchase does not appear as an agenda item it can still appear in the accounts: in Carlsbad the company shows up in a vendor payment register across three 2026 council packets, and in Hobbs inside a budget line noting Flock invoices. The financial reports are where to look when the agendas are silent.
Well supported
The case against thisThe amounts found are small and may be incidental or partial-year, and neither city was verified as operating cameras. The method is the point: a resident reading only agendas would never see the spending, while the accounts payable register and budget detail carry it.
3 sources
Cities of Carlsbad and Hobbs, New Mexico, scanned by this project · 2026-08-30 · Primary · NM
Two more New Mexico cities scanned. Flock appears in both - but as a line in a vendor payment register and a note inside a budget line, never as a deliberated item.
- Carlsbad: 130 published files scanned, 8.8 million characters. FLOCK GROUP INC, Atlanta GA appears in a vendor payment register across three 2026 council packets (May 26, June 23, July 28) at 375.88 dollars year-to-date purchases and payments.
- Hobbs: 121 published files scanned, 11.8 million characters. One mention, inside a budget document: a line noting funds For Inveris Training invoices & Flock invoices within an equipment-over-5000-dollars account.
- Neither city's record contains a Flock agenda item, staff report or vote in the documents scanned.
- Santa Fe's CivicClerk portal resolves but no files were retrieved before the scan window closed; it remains unscanned.
ORIGINAL RESEARCH, 2026-08-30, via the CivicClerk OData API. SMALL FINDING, USEFUL SHAPE. The Carlsbad figure is tiny and may be a partial-year or incidental purchase - do not present 375.88 dollars as the cost of a camera program. What matters is WHERE the spending surfaces: in a payment register and a budget note, which is what buying off a statewide price agreement looks like from the outside. A resident reading agendas would never see it; a resident reading the accounts payable register would. Neither city was verified as operating cameras.
City of Las Cruces Document Center (lascruces.civicweb.net), scanned by this project · 2026-08-30 · Primary · local:las-cruces
An original full-text search of the Las Cruces council record for Flock and ALPR terms, run against the city's own CivicWeb Document Center. It establishes when the cameras entered the public record - and that the contract itself does not appear in it as a vote.
- SCANNED: 95 City Council minutes documents totaling 2,389 pages, plus 200 agenda documents (HTML) spanning council meetings, work sessions and special meetings 2019-2026.
- 16 minutes documents contain Flock, ALPR, license plate or plate reader as whole words.
- The earliest substantive discussion is June 2, 2025, in public comment by Michael Harris - then a member of the public, later a city councilor - who described automated license plate reading cameras appearing on private property and city rights-of-way, naming at least 10 locations including Lohman, University, Missouri, and sites at Lowe's and Home Depot.
- Mentions escalate sharply through 2026: January 5 (11), January 20 (19), February 17 (11), April 6 (11), June 1 (13).
- NOT FOUND ON THE PORTAL: in the documents scanned, no Flock or ALPR mention occurs within 400 characters of a resolution number, ordinance number, contract award, contract amendment, or a carried motion. The searched record contains public comment and councilor discussion, not a procurement vote.
- CONTROL: a comparable police technology procurement IS in the record and IS findable by the same method - the Axon body camera and Taser contract, including Resolution No. 25-057 amending Contract 20-21-054 to increase it by 446,625.57 dollars for a total not to exceed 2,324,799.79 dollars, appears on the November 4, 2024 council agenda.
- AGENDA PACKETS SCANNED: the six full council agenda packets spanning August 5 through October 21, 2024 - the window around the reported September 2024 renewal - total 4,106 pages (960, 891, 634, 215, 585 and 821). They contain ZERO occurrences of Flock, ALPR, license plate, plate reader or automated license. The words surveillance and camera appear at most once across all six.
- EXTRACTION VALIDATED on those packets: 430,000 to 1,112,000 characters extracted per packet, with RESOLUTION appearing 88-146 times, contract 78-379 times and Police 16-97 times - so the zero is a real absence, not a failed parse.
- THE DOMINGUEZ-ERA RECORD WAS SEARCHED AND IS CLEAN. Las Cruces adopted Flock in January 2022 per its own chief, so the decision would fall in 2021 under Chief Miguel Dominguez. Scanned: 96 council and WORK SESSION agenda packets for 2021-2022 (29,404 pages, 52.2 million characters) plus 72 council and work session minutes documents for 2020-2022 (1,398 pages). Occurrences of flock, ALPR, license plate reader, plate reader and automated license: ZERO.
- SEARCH TERMS WERE WIDENED IN CASE THE ITEM WAS NAMED DIFFERENTLY. Across those same 96 packets: flock 0, ALPR 0, plate reader 0, Vigilant 0, Genetec 0, real-time crime 0. Camera appeared in 41 documents and surveillance in 19, but reading the contexts found only Axon body cameras, park and City Hall security cameras, and a resident's suggestion of a camera above a dam. Motorola appeared 664 times in two documents and is two-way radio equipment (MotoTRBO, EVX-S24). Leonardo, the parent of the ELSAG plate-reader line, appeared 45 times and is a person's surname in a payment listing.
- CONTROLS AND EXTRACTION VALIDATED across the 2021-2022 packets: 7,994 matches for RESOLUTION, Police or contract; zero parse failures; and the 31 documents extracting under 5,000 characters are all one-to-five-page work session cover sheets with normal text density of 571 to 1,294 characters per page. Chief Dominguez is named 375 times across 37 documents, confirming the era is well covered. Chief Story appears zero times, consistent with his arriving later.
- February 17, 2026 minutes record a meeting with Flock representatives over Zoom, at which councilors were told, in the speaker's words, that Flock has never and will never integrate facial recognition into its product; the councilor noted they came away not entirely comforted.
- The same February 17, 2026 discussion raised the Mountain View, California incident, where Flock shared city data on the nationwide network and the company's response was that the city was not a client at the time and it was a demo system.
- April 6, 2026 minutes reference an op-ed by Councilors Bencomo and Harris opposing Flock, and record that LCPD invited Las Cruces residents to register their doorbell cameras with Flock.
- January 20, 2026 public comment cited the Aurora, Colorado false-flag stop and its 1.9 million dollar settlement, an approximately 10 percent error rate, Carpenter v. United States, and the assertion that Flock's own patent describes a dynamic surveillance network.
ORIGINAL RESEARCH by this project on 2026-08-30, using the city's own public Document Center - the same portal scripts/alpr/adapters/civicweb.py targets. METHOD AND ITS LIMITS, stated so the finding can be checked or overturned: agendas are published as HTML and minutes as PDF, so both were fetched and searched separately; matching used whole-word regex on extracted text. AN EARLIER PASS OF THIS SCAN PRODUCED NINE FALSE POSITIVES for 'alpr' because the text had been whitespace-stripped before matching, turning 'capital projects', 'biblical principles' and 'real problems' into apparent hits - the space-stripping was unnecessary for these PDFs and was removed. THE NEGATIVE FINDING IS BOUNDED: it means NOT FOUND IN THE DOCUMENTS SCANNED, never that no vote occurred. The six agenda packets for August-October 2024 HAVE now been scanned (4,106 pages, extraction validated against RESOLUTION/contract/Police counts). The 2021-2022 council and work session packets and the 2020-2022 minutes have NOW been scanned as well - see the Dominguez-era findings above. Still not scanned: agenda packets for 2023 and 2025, minutes attachments, and the Utilities and Planning and Zoning bodies. NOTE ON CONTROLS: the Axon control fires on the council AGENDA listing and in three minutes documents, but Axon and Taser appear zero times inside these six packets, so for the packets specifically the positive control is the presence of RESOLUTION, contract and Police text rather than a known police-technology procurement. A contract can also be executed administratively below a council approval threshold, or ride inside a consent-agenda item whose title names neither the vendor nor the technology. Any of those would explain the absence without any impropriety. VERIFY before publishing: pull the September 2024 agenda packet and the city's purchasing records directly.
State of New Mexico General Services Department, Purchasing Division · 2026-01-09 · Primary · NM
The mechanism by which any New Mexico public body can buy license plate readers without running its own procurement. A statewide price agreement titled License Plate Recognition, with Flock Group Inc. among the awarded vendors, open to every agency and political subdivision in the state.
- Agreement number 30-00000-22-00018, titled License Plate Recognition, issued by the New Mexico General Services Department Purchasing Division.
- FIVE awarded vendors, of which Flock Group Inc. is one (Supplier ID 0000170812).
- Term: January 13, 2023 through January 12, 2027, extended by Amendment Eight from January 12, 2026 at the same price, terms and conditions.
- Ship To reads: All State of New Mexico agencies, commissions, institutions, political subdivisions and local public bodies allowed by law.
- Amendment Eight signed January 9, 2026 by State Purchasing Agent Dorothy Mendonca; procurement specialist Theresa Mendibles.
- Dona Ana County's June 9, 2026 approval was of USE of this agreement, not a competitive procurement of its own.
OBTAINED FROM PRIMARY SOURCE on 2026-08-30, inside the Dona Ana County BOCC agenda packet for June 9, 2026 (428 pages), retrieved through the county's CivicClerk API. THIS IS THE STRUCTURAL EXPLANATION FOR THE LAS CRUCES GAP and it is entirely lawful: a New Mexico public body does not have to run a procurement, or necessarily hold a council vote, to buy Flock - it can buy off the statewide price agreement. That reframes 'procurement that outruns consent' from a suspicion about one city into a description of how the state set the system up. IT IS ALSO THE MOST DIRECT POLICY LEVER IN THE CORPUS: the agreement is a state instrument, it can be conditioned or allowed to lapse, and IT EXPIRES JANUARY 12, 2027. The full Flock Safety Agreement was listed among the packet's supporting documents but its terms did not appear in the extracted text - retrieve it from GSD directly.
Dona Ana County's first ALPR commitment was never described as one: an October 2024 item summarized entirely as equipping thirty-five Ford Explorers for 3.4 million dollars carried, 140 pages later, a five-year Axon license for automated license plate recognition on 26 patrol vehicles at 107,906.45 dollars. The words ALPR, license plate, plate reader, camera and surveillance appear NOWHERE in the item title or executive summary.
Well supported
The case against thisNothing was hidden: the Axon quote was attached to the packet and the dollar figure appeared in the price summary. The claim is only that a commissioner reading the item title and summary would have learned they were buying vehicles, not committing to five years of plate recognition. Whether the omission was deliberate is NOT established and must not be asserted.
1 source
Dona Ana County Board of County Commissioners · 2024-10-22 · Primary · local:dona-ana-county
The county's FIRST ALPR commitment, and it was never described as one. A vehicle-outfitting item summarized entirely as fleet replacement carried, 140 pages later, a five-year automated license plate recognition license for 26 patrol vehicles.
- Item as presented: Use New Mexico State Pricing agreement and county contracts to fully equip thirty-five 2025 Ford Explorer Police Interceptor Hybrids for use as Law Enforcement Vehicles, total 3,433,242.04 dollars including labor.
- Stated rationale: adherence to the established vehicle replacement plan based on mileage and age of vehicles, paid from FY25 capital outlay.
- THE STAFF REPORT REGION - item title, summary, supporting-documentation list and financial impact, 1,540 characters - CONTAINS NONE of the words ALPR, license plate, plate reader, camera or surveillance.
- The Summary of Price Quotes lists Adventure Enterprises with an Axon 60 Month Lease of 399,552.31 dollars, marked Contract Pending approval of BOCC, at 79,910.47 dollars a year.
- All seven ALPR references in the 409-page packet sit on pages 149 and 151, inside the attached Axon quote.
- The line item: AXON FLEET 3 - ALPR LICENSE - 1 CAMERA, quantity 26, 60 months, 64.01 dollars each, 99,855.60 dollars plus 8,050.85 tax, totaling 107,906.45 dollars.
- Software term 03/15/2025 to 03/14/2030; invoiced as Year 1 through Year 5 at 19,971.11 dollars plus 1,610.17 tax annually for the ALPR license line.
- Administrative approvals: Finance Director and Purchasing Manager (Oct 15-16 2024), County Attorney Nelson Goodin, final approval by DASO Undersheriff Tessa Abeyta.
ORIGINAL RESEARCH, 2026-08-30, from the county's own packet via the CivicClerk API. THIS IS A STAFF-REPORT-VERSUS-CONTRACT DIVERGENCE OF EXACTLY THE KIND api/app/models.py alpr_discrepancies EXISTS TO RECORD, and it meets the no-quote-no-candidate rule: the passage on each side is quoted with a page locator. STATE IT CAREFULLY. Nothing here is unlawful or hidden - the contract quote was attached to the packet and the dollar figure was in the price summary. The claim is narrower and checkable: a commissioner reading the item title and executive summary would have learned they were buying vehicles, not that they were committing to five years of automated license plate recognition. Whether that omission was deliberate is NOT established and should not be asserted.
The county expanded that mobile ALPR fleet from 26 licenses to 39 - a 50 percent increase - on the CONSENT AGENDA, among items the board approves by one motion as recurring or routine business, with the technology named nowhere in the item description.
Well supported
The case against thisConsent agendas are ordinary, lawful and efficient, and any commissioner may pull an item for discussion. The point stands that a half-again expansion of plate recognition was characterized as routine business.
2 sources
Dona Ana County Board of County Commissioners · 2025-10-14 · Primary · local:dona-ana-county
A year later the county expanded its mobile ALPR fleet by half again - and did it on the consent agenda, among items the board is asked to approve by one motion as recurring or routine business.
- Consent Agenda Item 5: Utilize New Mexico State Pricing and County Contracts with Phil Long Ford (2,990,687.00), Adventure Enterprises (42,935.06), AXON ENTERPRISE (134,261.31), Code 3 Services (302,198.17), MPH Industries (86,806.30), Stop Stick (5,157.00) and Enchanted Technology Solutions (73,285.80) to purchase and fully equip vehicles. Sponsoring official: Kim Stewart, Sheriff.
- The consent agenda is introduced as items of recurring or routine business the Board will be asked to approve BY ONE MOTION.
- The item description names vendors and dollar amounts but not the technology; ALPR appears only on packet pages 43, 52 and 54.
- Line item: AXON FLEET 3 - ALPR LICENSE - 1 CAMERA, quantity 39, at 61.72 dollars, 28,884.96 dollars plus 2,423.44 tax.
- A Refresh AXON Fleet 3 System line - true up, Fleet 3 Basic, ALPR license - at 10,421.19 dollars times 12, totaling 125,054.28 dollars.
- Contract dates on the Axon lines: 12/01/2025 to 02/28/2029.
- The same meeting's consent agenda separately included 60 Tasers, 10 devices and 150 body worn cameras for the Detention Center at 216,010.85 dollars.
ORIGINAL RESEARCH, 2026-08-30. THE MISSION-CREEP DATA POINT: mobile ALPR licenses go from 26 to 39, a 50 percent increase, inside a routine vehicle purchase on a consent agenda. Consent agendas are ordinary and lawful, and any commissioner may pull an item from one. The narrow, checkable claim is that a 50 percent expansion of automated license plate recognition was presented as recurring or routine business and approved by one motion, with the technology named nowhere in the item description.
Dona Ana County Board of County Commissioners · 2024-10-22 · Primary · local:dona-ana-county
The county's FIRST ALPR commitment, and it was never described as one. A vehicle-outfitting item summarized entirely as fleet replacement carried, 140 pages later, a five-year automated license plate recognition license for 26 patrol vehicles.
- Item as presented: Use New Mexico State Pricing agreement and county contracts to fully equip thirty-five 2025 Ford Explorer Police Interceptor Hybrids for use as Law Enforcement Vehicles, total 3,433,242.04 dollars including labor.
- Stated rationale: adherence to the established vehicle replacement plan based on mileage and age of vehicles, paid from FY25 capital outlay.
- THE STAFF REPORT REGION - item title, summary, supporting-documentation list and financial impact, 1,540 characters - CONTAINS NONE of the words ALPR, license plate, plate reader, camera or surveillance.
- The Summary of Price Quotes lists Adventure Enterprises with an Axon 60 Month Lease of 399,552.31 dollars, marked Contract Pending approval of BOCC, at 79,910.47 dollars a year.
- All seven ALPR references in the 409-page packet sit on pages 149 and 151, inside the attached Axon quote.
- The line item: AXON FLEET 3 - ALPR LICENSE - 1 CAMERA, quantity 26, 60 months, 64.01 dollars each, 99,855.60 dollars plus 8,050.85 tax, totaling 107,906.45 dollars.
- Software term 03/15/2025 to 03/14/2030; invoiced as Year 1 through Year 5 at 19,971.11 dollars plus 1,610.17 tax annually for the ALPR license line.
- Administrative approvals: Finance Director and Purchasing Manager (Oct 15-16 2024), County Attorney Nelson Goodin, final approval by DASO Undersheriff Tessa Abeyta.
ORIGINAL RESEARCH, 2026-08-30, from the county's own packet via the CivicClerk API. THIS IS A STAFF-REPORT-VERSUS-CONTRACT DIVERGENCE OF EXACTLY THE KIND api/app/models.py alpr_discrepancies EXISTS TO RECORD, and it meets the no-quote-no-candidate rule: the passage on each side is quoted with a page locator. STATE IT CAREFULLY. Nothing here is unlawful or hidden - the contract quote was attached to the packet and the dollar figure was in the price summary. The claim is narrower and checkable: a commissioner reading the item title and executive summary would have learned they were buying vehicles, not that they were committing to five years of automated license plate recognition. Whether that omission was deliberate is NOT established and should not be asserted.
Read in sequence, Dona Ana County's three ALPR actions show the procurement getting MORE transparent, not less: hidden inside a vehicle purchase (Oct 2024), expanded on a consent agenda (Oct 2025), then named in the item title with a sponsoring sheriff, a dollar figure and a recorded 4-0 roll call (Jun 2026).
Well supported
The case against thisThe 2026 improvement is real and worth crediting. It also coincides with the technology becoming publicly controversial, so it may reflect changed external pressure rather than changed internal practice - and the 2026 staff summary is still only three sentences, silent on retention, sharing and federal access.
3 sources
Dona Ana County Board of County Commissioners · 2024-10-22 · Primary · local:dona-ana-county
The county's FIRST ALPR commitment, and it was never described as one. A vehicle-outfitting item summarized entirely as fleet replacement carried, 140 pages later, a five-year automated license plate recognition license for 26 patrol vehicles.
- Item as presented: Use New Mexico State Pricing agreement and county contracts to fully equip thirty-five 2025 Ford Explorer Police Interceptor Hybrids for use as Law Enforcement Vehicles, total 3,433,242.04 dollars including labor.
- Stated rationale: adherence to the established vehicle replacement plan based on mileage and age of vehicles, paid from FY25 capital outlay.
- THE STAFF REPORT REGION - item title, summary, supporting-documentation list and financial impact, 1,540 characters - CONTAINS NONE of the words ALPR, license plate, plate reader, camera or surveillance.
- The Summary of Price Quotes lists Adventure Enterprises with an Axon 60 Month Lease of 399,552.31 dollars, marked Contract Pending approval of BOCC, at 79,910.47 dollars a year.
- All seven ALPR references in the 409-page packet sit on pages 149 and 151, inside the attached Axon quote.
- The line item: AXON FLEET 3 - ALPR LICENSE - 1 CAMERA, quantity 26, 60 months, 64.01 dollars each, 99,855.60 dollars plus 8,050.85 tax, totaling 107,906.45 dollars.
- Software term 03/15/2025 to 03/14/2030; invoiced as Year 1 through Year 5 at 19,971.11 dollars plus 1,610.17 tax annually for the ALPR license line.
- Administrative approvals: Finance Director and Purchasing Manager (Oct 15-16 2024), County Attorney Nelson Goodin, final approval by DASO Undersheriff Tessa Abeyta.
ORIGINAL RESEARCH, 2026-08-30, from the county's own packet via the CivicClerk API. THIS IS A STAFF-REPORT-VERSUS-CONTRACT DIVERGENCE OF EXACTLY THE KIND api/app/models.py alpr_discrepancies EXISTS TO RECORD, and it meets the no-quote-no-candidate rule: the passage on each side is quoted with a page locator. STATE IT CAREFULLY. Nothing here is unlawful or hidden - the contract quote was attached to the packet and the dollar figure was in the price summary. The claim is narrower and checkable: a commissioner reading the item title and executive summary would have learned they were buying vehicles, not that they were committing to five years of automated license plate recognition. Whether that omission was deliberate is NOT established and should not be asserted.
Dona Ana County Board of County Commissioners · 2025-10-14 · Primary · local:dona-ana-county
A year later the county expanded its mobile ALPR fleet by half again - and did it on the consent agenda, among items the board is asked to approve by one motion as recurring or routine business.
- Consent Agenda Item 5: Utilize New Mexico State Pricing and County Contracts with Phil Long Ford (2,990,687.00), Adventure Enterprises (42,935.06), AXON ENTERPRISE (134,261.31), Code 3 Services (302,198.17), MPH Industries (86,806.30), Stop Stick (5,157.00) and Enchanted Technology Solutions (73,285.80) to purchase and fully equip vehicles. Sponsoring official: Kim Stewart, Sheriff.
- The consent agenda is introduced as items of recurring or routine business the Board will be asked to approve BY ONE MOTION.
- The item description names vendors and dollar amounts but not the technology; ALPR appears only on packet pages 43, 52 and 54.
- Line item: AXON FLEET 3 - ALPR LICENSE - 1 CAMERA, quantity 39, at 61.72 dollars, 28,884.96 dollars plus 2,423.44 tax.
- A Refresh AXON Fleet 3 System line - true up, Fleet 3 Basic, ALPR license - at 10,421.19 dollars times 12, totaling 125,054.28 dollars.
- Contract dates on the Axon lines: 12/01/2025 to 02/28/2029.
- The same meeting's consent agenda separately included 60 Tasers, 10 devices and 150 body worn cameras for the Detention Center at 216,010.85 dollars.
ORIGINAL RESEARCH, 2026-08-30. THE MISSION-CREEP DATA POINT: mobile ALPR licenses go from 26 to 39, a 50 percent increase, inside a routine vehicle purchase on a consent agenda. Consent agendas are ordinary and lawful, and any commissioner may pull an item from one. The narrow, checkable claim is that a 50 percent expansion of automated license plate recognition was presented as recurring or routine business and approved by one motion, with the technology named nowhere in the item description.
Dona Ana County Board of County Commissioners · 2026-06-09 · Primary · local:dona-ana-county
The county's own record of buying Flock: a named agenda item, a staff summary, a roll-call vote, and a link to the meeting video - the complete opposite of what the Las Cruces record contains.
- Item 12: Approve use of New Mexico State Pricing Agreement 30-00000-22-00018 with Flock Group Inc. for license plate reader cameras and annual subscription services in the amount of 162,000 dollars, and delegate signature authority to the County Manager for all related documents.
- Initiating department: Dona Ana County Sheriff's Office; contact person Kim Stewart, Sheriff.
- Staff summary states: DASO currently utilizes Flock cameras throughout the county. The cameras are license plate readers used for crime resolution and prevention.
- Financial impact stated as funds included in the Sheriff's Office FY26 budget; administrative approvals by the Finance Director and Purchasing Manager, June 4-5, 2026.
- Passed on a roll call recorded in the June 23, 2026 minutes: motion by Chair Manuel Sanchez, second by Commissioner Christopher Schaljo-Hernandez; Schaljo-Hernandez, Kimble, Chaparro and Sanchez voting yes, Vice Chair Gloria Gameros absent - carried 4-0.
- The minutes carry a timestamped link to the meeting video at the item: https://youtu.be/1nJov8_XGmg?t=20873
- The agenda is published in English and Spanish.
ORIGINAL RESEARCH, retrieved 2026-08-30 by scanning all 158 published files (28.3 million characters) in the county's CivicClerk portal. This is what an ALPR purchase looks like when it goes through a public body properly: named vendor, named agreement, dollar figure, sponsoring official, staff summary, recorded roll-call vote, and video. It is the control for the Las Cruces finding, and it is also the honest counterweight - the county did this in the open. Note the supporting documentation list includes a Flock Safety Agreement whose terms were NOT in the extracted text; that agreement is the thing to request next.
Las Cruces adopted Flock in January 2022, so the decision belongs to 2021 under Chief Miguel Dominguez - and a scan of 96 council and work session agenda packets from 2021-2022 (29,404 pages) plus the 2020-2022 minutes finds no mention of Flock, ALPR or plate readers by any vendor name.
Well supported
The case against thisBOUNDED NEGATIVE, and there are several lawful explanations that would fully account for it: purchase off the statewide price agreement requiring no local vote, execution below a council approval threshold, closed session, an unscanned body, or unpublished documents. The 2023 and 2025 packets were not scanned. This is not evidence of concealment and must never be presented as such.
3 sources
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
The targeted search for the Las Cruces Flock decision in the era it must have happened - 2021, under Chief Miguel Dominguez, in work sessions and council meetings. It is not in the published record.
- SCANNED: 96 agenda packets from the 2021 and 2022 City Council and Work Session folders - 29,404 pages, 52.2 million characters - plus 72 council and work session minutes documents for 2020-2022, 1,398 pages.
- Occurrences of flock, ALPR, license plate reader, plate reader, automated license: ZERO in the packets. One apparent hit in the September 2020 minutes is a resident's letter about unlicensed UTVs and is not ALPR.
- Widened vendor search across the same packets: Vigilant 0, Genetec 0, real-time crime 0. Motorola's 664 mentions in two documents are two-way radio price schedules. Leonardo's 45 mentions are a surname in a payment listing. Camera and surveillance mentions resolve to Axon body cameras, park and City Hall security, and a dam-safety suggestion.
- Controls: 7,994 matches for RESOLUTION, Police or contract across the packets; zero parse failures; the 31 low-character documents are short work session cover sheets with normal density.
- Chief Dominguez is named 375 times across 37 documents; Chief Story zero times - the correct era was searched.
- Las Cruces began operating plate readers in January 2022 per Chief Jeremy Story's own later statement, so the decision falls squarely inside the scanned window.
ORIGINAL RESEARCH, 2026-08-30, answering a specific question: was Flock considered at a Las Cruces work session and council meeting under Chief Dominguez, with staff notes and a vote? IN THE PUBLISHED RECORD, NO. State it as the bounded negative it is - not found in what was searched, never 'does not exist'. WHAT WOULD STILL EXPLAIN IT, all lawful: purchase off statewide price agreement 30-00000-22-00018, which requires no local procurement and apparently no council vote; execution below a council approval threshold; closed or executive session, which packets do not carry; a body not scanned, such as a committee; or documents the portal does not publish. The 2023 and 2025 packets were also not scanned. DO NOT PRESENT THIS AS CONCEALMENT. The likeliest explanation is the state purchasing channel this dossier documents elsewhere, and the county's own 2024 packet shows how ALPR can ride inside an item about something else entirely.
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
State of New Mexico General Services Department, Purchasing Division · 2026-01-09 · Primary · NM
The mechanism by which any New Mexico public body can buy license plate readers without running its own procurement. A statewide price agreement titled License Plate Recognition, with Flock Group Inc. among the awarded vendors, open to every agency and political subdivision in the state.
- Agreement number 30-00000-22-00018, titled License Plate Recognition, issued by the New Mexico General Services Department Purchasing Division.
- FIVE awarded vendors, of which Flock Group Inc. is one (Supplier ID 0000170812).
- Term: January 13, 2023 through January 12, 2027, extended by Amendment Eight from January 12, 2026 at the same price, terms and conditions.
- Ship To reads: All State of New Mexico agencies, commissions, institutions, political subdivisions and local public bodies allowed by law.
- Amendment Eight signed January 9, 2026 by State Purchasing Agent Dorothy Mendonca; procurement specialist Theresa Mendibles.
- Dona Ana County's June 9, 2026 approval was of USE of this agreement, not a competitive procurement of its own.
OBTAINED FROM PRIMARY SOURCE on 2026-08-30, inside the Dona Ana County BOCC agenda packet for June 9, 2026 (428 pages), retrieved through the county's CivicClerk API. THIS IS THE STRUCTURAL EXPLANATION FOR THE LAS CRUCES GAP and it is entirely lawful: a New Mexico public body does not have to run a procurement, or necessarily hold a council vote, to buy Flock - it can buy off the statewide price agreement. That reframes 'procurement that outruns consent' from a suspicion about one city into a description of how the state set the system up. IT IS ALSO THE MOST DIRECT POLICY LEVER IN THE CORPUS: the agreement is a state instrument, it can be conditioned or allowed to lapse, and IT EXPIRES JANUARY 12, 2027. The full Flock Safety Agreement was listed among the packet's supporting documents but its terms did not appear in the extracted text - retrieve it from GSD directly.
The Las Cruces negative is not an artifact of narrow search terms: the same 96 packets were searched for Vigilant, Genetec, Motorola, Axon, Leonardo, camera, surveillance and real-time crime, and every non-zero result was read and resolved - Motorola is two-way radios, Leonardo is a surname, and the camera hits are body cameras and building security.
Well supported
The case against thisA vendor could still appear under a name not on the list, or an item could describe the function without naming vendor or technology - which is exactly what Dona Ana County's 2024 packet did. That possibility is why the finding is stated as bounded.
1 source
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
The targeted search for the Las Cruces Flock decision in the era it must have happened - 2021, under Chief Miguel Dominguez, in work sessions and council meetings. It is not in the published record.
- SCANNED: 96 agenda packets from the 2021 and 2022 City Council and Work Session folders - 29,404 pages, 52.2 million characters - plus 72 council and work session minutes documents for 2020-2022, 1,398 pages.
- Occurrences of flock, ALPR, license plate reader, plate reader, automated license: ZERO in the packets. One apparent hit in the September 2020 minutes is a resident's letter about unlicensed UTVs and is not ALPR.
- Widened vendor search across the same packets: Vigilant 0, Genetec 0, real-time crime 0. Motorola's 664 mentions in two documents are two-way radio price schedules. Leonardo's 45 mentions are a surname in a payment listing. Camera and surveillance mentions resolve to Axon body cameras, park and City Hall security, and a dam-safety suggestion.
- Controls: 7,994 matches for RESOLUTION, Police or contract across the packets; zero parse failures; the 31 low-character documents are short work session cover sheets with normal density.
- Chief Dominguez is named 375 times across 37 documents; Chief Story zero times - the correct era was searched.
- Las Cruces began operating plate readers in January 2022 per Chief Jeremy Story's own later statement, so the decision falls squarely inside the scanned window.
ORIGINAL RESEARCH, 2026-08-30, answering a specific question: was Flock considered at a Las Cruces work session and council meeting under Chief Dominguez, with staff notes and a vote? IN THE PUBLISHED RECORD, NO. State it as the bounded negative it is - not found in what was searched, never 'does not exist'. WHAT WOULD STILL EXPLAIN IT, all lawful: purchase off statewide price agreement 30-00000-22-00018, which requires no local procurement and apparently no council vote; execution below a council approval threshold; closed or executive session, which packets do not carry; a body not scanned, such as a committee; or documents the portal does not publish. The 2023 and 2025 packets were also not scanned. DO NOT PRESENT THIS AS CONCEALMENT. The likeliest explanation is the state purchasing channel this dossier documents elsewhere, and the county's own 2024 packet shows how ALPR can ride inside an item about something else entirely.
The Las Cruces contract is not missing and never was: it sits in this project's own ALPR procurement database, ingested by another session, readable through the public API with quoted passages and page locators.
Well supported
The case against thisThis dossier reported it as unread for several rounds because I searched the city's portal and the seed files rather than the module's own database. The lesson is procedural: check what the project already holds before searching the world for it.
3 sources
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
Flock Safety / City of Las Cruces · 2025-05-13 · Primary · local:las-cruces
Eight months after the plate-reader agreement, Las Cruces signed a Drone as First Responder contract with the same vendor at more than double the annual value - and the module's comparison finds NO staff report and NO council enactment attached to it.
- Signed 13 May 2025. Recorded as an AMENDMENT to the September 2024 agreement.
- Product line, quoted from page 2: Flock Safety Drone Hardware and Services, Flock Safety DFR 2.0 - 400ft.
- Annual recurring 307,133 dollars; Year 1 one-time fees 150,000 dollars; discounts 157,133 dollars; CONTRACT TOTAL 457,133 dollars, all quoted from page 2.
- RETENTION PERIOD: 30 DAYS.
- Includes a pilot arrangement quoted from page 2: PROJECT PROVE IT. Customer will have a 60 day opt-out period after implementation. Billing frequency is Annual Plan, invoiced at the end of the pilot period.
- AUTOMATIC RENEWAL on the same terms as the 2024 agreement.
- THE COMPARISON FINDS NO PAIRED STAFF REPORT AND NO ENACTMENT for this agreement - both fields are empty.
- Recorded as reviewed: false.
OBTAINED 2026-08-30 via the module's public API. THIS IS THE LAS CRUCES MISSION-CREEP FINDING, and it is stronger than the county's: the city went from a 141,850 dollar plate-reader agreement to a 457,133 dollar drone-as-first-responder agreement with the same vendor in eight months, and the module's own comparison finds nothing in the council record attached to the second one. MY INDEPENDENT SCAN CORROBORATES THAT GAP - 96 packets and 29,404 pages of 2021-2022 material plus the 2022-2026 minutes contain no Flock or ALPR mention at all. Two different methods, same answer. Still a bounded negative: the 2023 and 2025 agenda packets were not scanned by me, and the module's sweep is recorded as covering the council record to date.
Las Cruces went from a 141,850 dollar plate-reader agreement in September 2024 to a 457,133 dollar Drone as First Responder agreement with the same vendor in May 2025 - 307,133 dollars annually recurring, on a 60-day opt-out pilot called PROJECT PROVE IT - and the module's comparison finds no staff report and no council enactment attached to it.
Well supported
The case against thisBoth agreements auto-renew and both carry 30-day retention, so the terms did not loosen; scope and price did. The missing staff report is now confirmed twice - the module records the gap and an independent scan of 24 packets and 9,192 pages of 2025 council and work session material finds nothing. It remains a bounded negative: a DFR authorization could sit in a 2024 packet, a closed session, or a budget line naming neither vendor nor technology, and the state price agreement makes a local vote optional.
4 sources
Flock Safety / City of Las Cruces · 2025-05-13 · Primary · local:las-cruces
Eight months after the plate-reader agreement, Las Cruces signed a Drone as First Responder contract with the same vendor at more than double the annual value - and the module's comparison finds NO staff report and NO council enactment attached to it.
- Signed 13 May 2025. Recorded as an AMENDMENT to the September 2024 agreement.
- Product line, quoted from page 2: Flock Safety Drone Hardware and Services, Flock Safety DFR 2.0 - 400ft.
- Annual recurring 307,133 dollars; Year 1 one-time fees 150,000 dollars; discounts 157,133 dollars; CONTRACT TOTAL 457,133 dollars, all quoted from page 2.
- RETENTION PERIOD: 30 DAYS.
- Includes a pilot arrangement quoted from page 2: PROJECT PROVE IT. Customer will have a 60 day opt-out period after implementation. Billing frequency is Annual Plan, invoiced at the end of the pilot period.
- AUTOMATIC RENEWAL on the same terms as the 2024 agreement.
- THE COMPARISON FINDS NO PAIRED STAFF REPORT AND NO ENACTMENT for this agreement - both fields are empty.
- Recorded as reviewed: false.
OBTAINED 2026-08-30 via the module's public API. THIS IS THE LAS CRUCES MISSION-CREEP FINDING, and it is stronger than the county's: the city went from a 141,850 dollar plate-reader agreement to a 457,133 dollar drone-as-first-responder agreement with the same vendor in eight months, and the module's own comparison finds nothing in the council record attached to the second one. MY INDEPENDENT SCAN CORROBORATES THAT GAP - 96 packets and 29,404 pages of 2021-2022 material plus the 2022-2026 minutes contain no Flock or ALPR mention at all. Two different methods, same answer. Still a bounded negative: the 2023 and 2025 agenda packets were not scanned by me, and the module's sweep is recorded as covering the council record to date.
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
A targeted search for the staff report behind the Flock DFR agreement, in the year it was signed. There isn't one - and this confirms independently the no_staff_report gap the procurement module records for that contract.
- SCANNED: 24 full agenda packets from the 2025 City Council and Work Session folders - 9,192 pages, 18.2 million characters - spanning January through July 2025.
- The Flock Law Enforcement Agreement (DFR) was signed 13 May 2025 for 307,133 dollars annually recurring, 457,133 dollars contract total.
- Occurrences of DFR or 'drone as first responder' across all 24 packets: ZERO.
- Occurrences of Flock: five, all in the 7 July 2025 packet, and all inside the reprinted minutes of the 2 June 2025 meeting - Michael Harris's public comment as a member of the public. Not a staff report, not an agenda item.
- All nine 'drone' mentions resolve to unrelated matters: aviation and drone liability insurance on a landscape architecture contract, a surveyor's CV, drone and aerospace tenants at the industrial park, FAA UAS integration planning at the airport, and the NMSU drone hangar.
- The April, May and June packets specifically - the window bracketing the signature - total 4,421 pages and contain no Flock and no DFR reference at all.
- From Harris's June 2025 comment, a per-unit figure not found elsewhere: each camera costs about 2,500 dollars per year.
ORIGINAL RESEARCH, 2026-08-30. THIS CORROBORATES THE MODULE FROM A DIFFERENT DIRECTION: the procurement database records a no_staff_report gap for this contract, and an independent full-text scan of the year's packets finds nothing either. Two methods, same answer. BOUNDED: 2025 packets only, council and work session bodies only; a DFR authorization could sit in a 2024 packet, in a closed session, in a budget line naming neither the vendor nor the technology, or below a council approval threshold - the state price agreement makes a local vote optional. NOT EVIDENCE OF CONCEALMENT. What it does establish is that the largest single Flock commitment Las Cruces has made reached the council in no document anyone can point to.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
The targeted search for the Las Cruces Flock decision in the era it must have happened - 2021, under Chief Miguel Dominguez, in work sessions and council meetings. It is not in the published record.
- SCANNED: 96 agenda packets from the 2021 and 2022 City Council and Work Session folders - 29,404 pages, 52.2 million characters - plus 72 council and work session minutes documents for 2020-2022, 1,398 pages.
- Occurrences of flock, ALPR, license plate reader, plate reader, automated license: ZERO in the packets. One apparent hit in the September 2020 minutes is a resident's letter about unlicensed UTVs and is not ALPR.
- Widened vendor search across the same packets: Vigilant 0, Genetec 0, real-time crime 0. Motorola's 664 mentions in two documents are two-way radio price schedules. Leonardo's 45 mentions are a surname in a payment listing. Camera and surveillance mentions resolve to Axon body cameras, park and City Hall security, and a dam-safety suggestion.
- Controls: 7,994 matches for RESOLUTION, Police or contract across the packets; zero parse failures; the 31 low-character documents are short work session cover sheets with normal density.
- Chief Dominguez is named 375 times across 37 documents; Chief Story zero times - the correct era was searched.
- Las Cruces began operating plate readers in January 2022 per Chief Jeremy Story's own later statement, so the decision falls squarely inside the scanned window.
ORIGINAL RESEARCH, 2026-08-30, answering a specific question: was Flock considered at a Las Cruces work session and council meeting under Chief Dominguez, with staff notes and a vote? IN THE PUBLISHED RECORD, NO. State it as the bounded negative it is - not found in what was searched, never 'does not exist'. WHAT WOULD STILL EXPLAIN IT, all lawful: purchase off statewide price agreement 30-00000-22-00018, which requires no local procurement and apparently no council vote; execution below a council approval threshold; closed or executive session, which packets do not carry; a body not scanned, such as a committee; or documents the portal does not publish. The 2023 and 2025 packets were also not scanned. DO NOT PRESENT THIS AS CONCEALMENT. The likeliest explanation is the state purchasing channel this dossier documents elsewhere, and the county's own 2024 packet shows how ALPR can ride inside an item about something else entirely.
On the 2024 Las Cruces agreement the written record is silent on camera count, cost and auto-renewal - but not on everything. In the 22 April 2024 work session the police chief stated retention aloud - thirty days for plate readers, seven days for all video - and a councilor raised sharing with ICE by name. What the council never received was any of it in writing, and the vendor is not named once in the 1,732-page packet.
Well supported
The case against thisA work session briefing is real disclosure and should be credited as such - the chief volunteered retention figures unprompted. The narrow claims that survive: it was verbal rather than written, the 7-day video figure has no counterpart in the signed contract, and 'Flock' appears nowhere in the packet.
4 sources
City of Las Cruces · 2024-04-22 · Primary · local:las-cruces
The document the whole Las Cruces comparison hangs on, read in full at last. It is a 1,732-page packet carrying the 22 April 2024 work session minutes - and in them a police chief states the retention periods out loud and a councilor asks twice for a work session she does not get.
- 1,732 pages. Occurrences of 'Flock': ZERO. One license-plate reference in the whole packet. Twelve mentions of a real-time crime center; twenty-three of 'drone', all unrelated - surveying and LiDAR services, an engineering day rate, and a public comment about the Middle East.
- The substance sits in the minutes of the WORK SESSION of 22 April 2024, printed as Agenda Item 5.2 - the procurement module labels this document as a council item of 2024-06-03, which is the packet date, not the meeting where the discussion happened.
- CHIEF JEREMY STORY, stating retention aloud: 'The retention rates that we have set now are thirty days for license plate readers. Which I think is a very reasonable amount and 7 days will be for all video. So a week is what we plan on setting it at.'
- COUNCILOR BENCOMO raised federal sharing directly: 'I particularly have concerns with just sharing data with entities like ICE for example. I have a ton of questions around that.'
- Bencomo asked TWICE for a dedicated public work session on the Real Time Crime Center - 'so the community can ask questions and be involved' and again 'my request would be that we do have a work session.'
- Chief Story's answer: 'I don't have an answer for the work session' - offering a town hall that Thursday instead.
- Story described the safeguards as limiting access to those who need it, auditing procedures to monitor that data is retrieved for proper purposes, an audit trail, and proper policy - 'a lot of good mechanisms in place or will be in place.'
- Bencomo also raised the harms she wanted policy to address, naming racial profiling among them.
READ IN FULL 2026-08-30, only possible after commit f995c38 fixed the 500 that had made this document unfetchable. THREE CONSEQUENCES. (1) The council was NOT told nothing about retention - it was told 30 days for plate readers and 7 days for video, by the chief, in a work session. But that is a verbal statement in minutes, not a written staff analysis, and the 7-day video figure has no counterpart anywhere in the signed contract, whose Retention Period field reads 30 days. (2) FEDERAL ACCESS WAS GENUINELY RAISED, by name, by a councilor - which means the module's 'addresses federal access' row may be defensible in substance even though the passage it quotes, at packet page 51, is a sergeant discussing asset forfeiture. The right passage exists at page 38; the extractor matched the wrong one. (3) The word Flock appears nowhere in 1,732 pages, so the vendor was never named to the council in this material.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
The targeted search for the Las Cruces Flock decision in the era it must have happened - 2021, under Chief Miguel Dominguez, in work sessions and council meetings. It is not in the published record.
- SCANNED: 96 agenda packets from the 2021 and 2022 City Council and Work Session folders - 29,404 pages, 52.2 million characters - plus 72 council and work session minutes documents for 2020-2022, 1,398 pages.
- Occurrences of flock, ALPR, license plate reader, plate reader, automated license: ZERO in the packets. One apparent hit in the September 2020 minutes is a resident's letter about unlicensed UTVs and is not ALPR.
- Widened vendor search across the same packets: Vigilant 0, Genetec 0, real-time crime 0. Motorola's 664 mentions in two documents are two-way radio price schedules. Leonardo's 45 mentions are a surname in a payment listing. Camera and surveillance mentions resolve to Axon body cameras, park and City Hall security, and a dam-safety suggestion.
- Controls: 7,994 matches for RESOLUTION, Police or contract across the packets; zero parse failures; the 31 low-character documents are short work session cover sheets with normal density.
- Chief Dominguez is named 375 times across 37 documents; Chief Story zero times - the correct era was searched.
- Las Cruces began operating plate readers in January 2022 per Chief Jeremy Story's own later statement, so the decision falls squarely inside the scanned window.
ORIGINAL RESEARCH, 2026-08-30, answering a specific question: was Flock considered at a Las Cruces work session and council meeting under Chief Dominguez, with staff notes and a vote? IN THE PUBLISHED RECORD, NO. State it as the bounded negative it is - not found in what was searched, never 'does not exist'. WHAT WOULD STILL EXPLAIN IT, all lawful: purchase off statewide price agreement 30-00000-22-00018, which requires no local procurement and apparently no council vote; execution below a council approval threshold; closed or executive session, which packets do not carry; a body not scanned, such as a committee; or documents the portal does not publish. The 2023 and 2025 packets were also not scanned. DO NOT PRESENT THIS AS CONCEALMENT. The likeliest explanation is the state purchasing channel this dossier documents elsewhere, and the county's own 2024 packet shows how ALPR can ride inside an item about something else entirely.
Las Cruces has a written ALPR policy - LCPD General Order 173, effective 11 September 2025 - and it is genuinely mixed: a mandatory three-step misread-verification protocol and monthly plus annual audits on one side, and a single sentence on data sharing, an optional case number, and no mention of SB 40 on the other.
Well supported
The case against thisThe Active Hit Protocol and the explicit statement that an alert is not probable cause are real safeguards that support the department's claim of protections beyond the minimum. It remains a general order rather than an ordinance - changeable by the department, which is exactly Councilor Harris's point - and its monthly audit is run by the same unit whose queries it examines.
3 sources
Las Cruces Police Department · 2025-09-11 · Primary · local:las-cruces
The city's own written ALPR policy, read in full. Four pages. It contains a real misread-verification protocol and a genuine audit requirement - and says almost nothing about the national network, out-of-state sharing, or federal access.
- Effective 09/11/2025; revised and reviewed 04/30/2025. Four pages. Supersedes all previous versions.
- REFERENCES section names one source: Albuquerque Police Department. The policy is modeled on APD's.
- ACTIVE HIT PROTOCOL, a mandatory three-step check on every stolen-vehicle alert: compare the detection and check for misreads, confirming all characters match; confirm the STATE of the wanted plate matches; and run an NCIC check to confirm the vehicle is still on the hot list.
- Quoted: An ALPR Alert under the ALPR Program does not establish probable cause for enforcement action. Hit information/data must be confirmed before taking any related law enforcement action.
- Query logging: a requestor, case number (IF AVAILABLE), and reason shall be entered with each investigative query. Administrative and auditing queries are exempt from the case-number requirement.
- Quoted, as a stated permitted use: Reasonable suspicion or probable cause is not required before using an ALPR.
- RETENTION: ALPR data shall only be held in the system for thirty (30) days, automatically purged after that unless evidentiary. In-vehicle data must be transferred to the department server at intervals not exceeding thirty days.
- DATA SHARING is one sentence in full: ALPR data shall be considered law enforcement sensitive and can only be shared for valid purposes.
- Audits: sample audits at least MONTHLY by the Intel Unit Section Head or designee, who is also responsible for retaining the audit records; plus an ANNUAL system-integrity audit by the Criminal Investigation Section Lieutenant, reported to the Chief of Police.
- Access: sworn personnel, Police Service Aides and the Crime Analyst Unit, via mobile dispatch terminal, department computer or smartphone, each with an individual username and password. Misuse is subject to discipline.
- Program administration sits with the Investigations and Intelligence Lieutenant or designee.
READ IN FULL 2026-08-30, from the document endpoint that had been returning HTTP 500 until commit f995c38 fixed it. WHAT IT DOES WELL, and the dossier should say so: the Active Hit Protocol is precisely the hot-list verification the Brennan Center recommends and precisely the control whose absence produced the wrong-car-at-gunpoint cases elsewhere in this corpus - Las Cruces has it in writing, along with an explicit statement that an alert is not probable cause. That is a real safeguard and supports LCPD's claim of protections beyond the minimum. FOUR THINGS IT DOES NOT DO. (1) The case number is optional - 'if available' - so this is weaker than the hard case-number rule Dona Ana County's lieutenant describes. (2) Data sharing is a single sentence with no mention of the national lookup network, out-of-state agencies, or federal access - the subjects on which the audit logs in this corpus show the actual risk. (3) It predates SB 40's effective date of 1 July 2026 and has not been revised since, so it carries none of the statute's written-declaration duty. (4) The monthly audit is conducted and retained by the same Intel unit whose queries it examines. This is also the document behind Councilor Harris's point that a departmental policy can be changed by the department - it is a general order, not an ordinance.
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
New Mexico News Port · 2026-08-18 · Secondary · local:las-cruces
Fuller account of the Las Cruces councilors' oversight push, including their reaction after two hours with an LCPD lieutenant.
- Councilors Michael Harris and Johana Bencomo seek a city-level surveillance policy and a public portal showing how police collect, search and share vehicle data.
- They raised the issue after about two hours with an LCPD lieutenant going through the city's use of Flock in detail.
- Harris remains uneasy about what he called creeping surveillance but came away impressed by some of the safeguards LCPD has in place, and wants a citywide policy rather than departmental rules.
- Bencomo continues to oppose mass surveillance but expressed confidence in the LCPD team after the discussion: I have trust in him and the team that we can move forward into this place of being very transparent and honest and responsible with the kind of data that we are collecting from our residents.
IMPORTANT FOR TONE. The two councilors most critical of the technology both came away from a detailed briefing with a measure of confidence in their own department while still wanting a citywide policy. A dossier that renders Las Cruces as a fight between residents and a hostile police department would misdescribe the actual local situation, and would be corrected in the room.
No Flock Wing Gateway purchase has been found by product name in any record searched - but THE FUNCTION IS DOCUMENTED IN THE CITY'S OWN WORDS: a councilor told the Las Cruces council on 1 June 2026 that of 22 cameras, most are Flock-branded but some are the city's own, and THESE ALL GO INTO THE REAL TIME CRIME CENTER, with Flock the vendor that makes the RTCC run.
Well supported
The case against thisThe councilor names no product and no line item, so which contract or bundle carries the integration is unestablished - it may be the six Multi-Purpose LPR and Video Fixed units in the 2024 agreement, a Wing Gateway under a bundle name, or a capability of FlockOS Elite. SCHOOL CAMPUS FEEDS specifically were NOT found in either the city record or the district's published board record.
5 sources
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
Flock Safety · undated · Vendor claim · national
The product that pulls cameras an agency does not own - including school, HOA and business cameras - into the Flock platform and the real-time crime center.
- Wing Gateway 2.0 is described as letting a customer build a community camera program and maximize third-party cameras they already own by integrating them into the Flock platform.
- Wing Gateway Outdoor is described as pulling camera feeds directly into the Flock platform without requiring IT involvement.
- Flock markets integration of public and private cameras from schools, HOAs and businesses into one shared platform, with AI-driven analytics over the combined feeds.
- FlockOS is described as unifying video, LPR, drones, CAD and sensors on one real-time map.
TIERED VENDOR-CLAIM; product descriptions come from Flock's own marketing and have not been verified against a contract. THE NAME MATTERS FOR SEARCHING: the product is Wing Gateway, not simply Gateway, and in a municipal contract it may appear as a line item under Wing, Gateway, Community Network Access or a bundle name rather than any of those. That is why a keyword search for gateway alone is not sufficient evidence of absence - and in Las Cruces it produced only gateway signage, gateway drugs and the southern gateway to downtown.
State of New Mexico Department of Finance and Administration / City of Las Cruces · 2024-10-21 · Primary · local:las-cruces
The state money behind the Las Cruces RTCC, and the statutory language that describes the camera-integration function without naming any product.
- Laws of 2024, Chapter 66, Section 28, Paragraph 294: 650,000 dollars from the General Fund to purchase, equip, install and implement AN INTEGRATED SYSTEM OF CAMERAS, SURVEILLANCE EQUIPMENT AND INFORMATION TECHNOLOGY to develop a real-time crime center for the police department in Las Cruces in Dona Ana county.
- Grant 24-I2936, 650,000 dollars, term 07/01/2024 to 06/30/2026, reversion date June 30 2026, no match required.
- Accepted through the City Council packet of 21 October 2024; project contact Sean Mullen, Office of the Chief.
- The capital improvement plan in the same packet carries a Real Time Crime Center line for the Police Department at 1,750,000 dollars FY2025 and 250,000 dollars FY2026, funded by Grants, shown elsewhere as 1,100,000 dollars plus the 650,000 dollar 2024 legislative appropriation.
ORIGINAL RESEARCH, 2026-08-30, from the city's own 821-page 21 October 2024 agenda packet. THE PHRASE TO SEARCH FOR IN OTHER JURISDICTIONS IS 'INTEGRATED SYSTEM OF CAMERAS' - state appropriation language describes the camera-integration function generically, names no vendor and no product, and would be missed entirely by a keyword search for Flock, ALPR or Gateway. This is also the funding thread connecting the RTCC to the state legislature rather than to the city budget alone.
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
Las Cruces Public Schools via Granicus, scanned by this project · 2026-08-30 · Primary · local:las-cruces
A search of the school district's published board record for any deliberation of Flock, camera integration or a police data-sharing arrangement. Nothing found - but the portal turns out to publish agendas rather than packets, so the district's staff reports have effectively NOT been searched.
- SCANNED: the complete Granicus board record, 216 documents across clip ids 33 to 332 (157 agenda documents and 59 minutes documents), 1,703 pages.
- Occurrences: flock 0, ALPR or license plate 0, surveillance 0, real-time crime 0, Wing Gateway 0.
- One gateway hit is a board member asking whether a firearm detection system would be a daily student walkthrough gateway into the schools. The 13 camera hits are surplus equipment inventory - document cameras and a Sony Mavica - and a parent describing filming a graduation.
- LCPD or police appears in 14 documents; memorandum of understanding or intergovernmental agreement in 23.
- CRITICAL LIMITATION: only TWO of the 216 documents are full agenda packets (1,054 pages and 311 pages). The remaining 214 are two-to-three page agenda cover sheets. Since a staff report IS generally the agenda packet, the district's staff reports are largely absent from this portal.
- Extraction was validated: 1,377 to 2,267 characters per page across the PDFs, zero image-only documents, zero parse failures.
ORIGINAL RESEARCH, 2026-08-30. METHOD FAILURE CAUGHT AND CORRECTED, worth recording because it would have produced a false all-clear: Granicus serves its AgendaViewer output as PDF bytes under a .html URL. A first pass stripped HTML tags from those binary streams and reported 50.9 million characters and zero camera mentions - it was regexing compressed PDF data, not text. Re-run with proper PDF extraction, the corpus is 1,703 pages. THE NEGATIVE HERE IS WEAK AND MUST BE LABELED THAT WAY: the board's actual packets are not on this portal. They are behind a JavaScript-rendered document library at lcps.net/documents/board-documents, which returned only one asset URL to a plain fetch. Retrieving that library is the outstanding task.
Las Cruces Public Schools does not publish its board agenda packets online at all. Its Granicus record carries 216 board documents of which only two are packets, and its own document library - opened in a rendered browser - holds 60 files that are district policy, finance and equity-council material, with no packets among them.
Well supported
The case against thisThis is a limit of publication, not evidence of anything. Many districts never post packets, and nothing here suggests LCPS withholds them improperly. The consequence is procedural: since a staff report is generally the packet, the school-feeds question cannot be closed by scraping and requires a records request to the district.
2 sources
Las Cruces Public Schools via Granicus, scanned by this project · 2026-08-30 · Primary · local:las-cruces
A search of the school district's published board record for any deliberation of Flock, camera integration or a police data-sharing arrangement. Nothing found - but the portal turns out to publish agendas rather than packets, so the district's staff reports have effectively NOT been searched.
- SCANNED: the complete Granicus board record, 216 documents across clip ids 33 to 332 (157 agenda documents and 59 minutes documents), 1,703 pages.
- Occurrences: flock 0, ALPR or license plate 0, surveillance 0, real-time crime 0, Wing Gateway 0.
- One gateway hit is a board member asking whether a firearm detection system would be a daily student walkthrough gateway into the schools. The 13 camera hits are surplus equipment inventory - document cameras and a Sony Mavica - and a parent describing filming a graduation.
- LCPD or police appears in 14 documents; memorandum of understanding or intergovernmental agreement in 23.
- CRITICAL LIMITATION: only TWO of the 216 documents are full agenda packets (1,054 pages and 311 pages). The remaining 214 are two-to-three page agenda cover sheets. Since a staff report IS generally the agenda packet, the district's staff reports are largely absent from this portal.
- Extraction was validated: 1,377 to 2,267 characters per page across the PDFs, zero image-only documents, zero parse failures.
ORIGINAL RESEARCH, 2026-08-30. METHOD FAILURE CAUGHT AND CORRECTED, worth recording because it would have produced a false all-clear: Granicus serves its AgendaViewer output as PDF bytes under a .html URL. A first pass stripped HTML tags from those binary streams and reported 50.9 million characters and zero camera mentions - it was regexing compressed PDF data, not text. Re-run with proper PDF extraction, the corpus is 1,703 pages. THE NEGATIVE HERE IS WEAK AND MUST BE LABELED THAT WAY: the board's actual packets are not on this portal. They are behind a JavaScript-rendered document library at lcps.net/documents/board-documents, which returned only one asset URL to a plain fetch. Retrieving that library is the outstanding task.
Las Cruces Public Schools (Apptegy), examined by this project · 2026-08-30 · Primary · local:las-cruces
The follow-up to the Granicus scan: the district's own document library, opened in a rendered browser rather than a plain fetch, to see whether board agenda packets are published anywhere online. They are not.
- The document library at lcps.net/documents holds 60 unique published files.
- Their subjects are district policy and administration: student discipline and threat-assessment policy series (JI, JK, JFB, JICA, ILBB, JBB), nutrition and free-meal notices, cash reports, high school profile, Equity Council agendas and notes, Finance Subcommittee agendas and schedules, and meeting-schedule notices.
- NO board agenda packets are among them. A single regular-session agenda appears (260324--Regular-Session-Agenda.pdf).
- The folder path /documents/board-documents renders an empty Name/Type/Size table; the files are served from the root /documents index.
- Combined with the Granicus scan of 216 board documents, this means the district publishes agendas and some minutes, and district policy - but not the packets.
ORIGINAL RESEARCH, 2026-08-30, using a rendered browser after a plain fetch returned almost nothing (the site is an Apptegy single-page app; the earlier curl saw one asset URL where the rendered page exposes sixty). CONCLUSION THAT MATTERS FOR METHOD: a staff report is generally the agenda packet, and LCPS DOES NOT PUBLISH ITS BOARD PACKETS ONLINE AT ALL. So the school-feeds question cannot be closed by scraping any public surface - it requires a records request to the district. This is a limit of publication, not evidence of anything: nothing here suggests the district withholds packets improperly, and many districts simply never post them.
Non-Flock, city-owned cameras feed the Las Cruces Real Time Crime Center. In a councilor's words on 1 June 2026: most of the 22 cameras are Flock-branded but some are the city's own, and these all go into the Real Time Crime Center, with Flock the vendor that helps make it run.
Well supported
The case against thisThe same councilor drew a careful line: newly funded capital-improvement cameras for city buildings and public spaces are NOT in the RTCC - they are the city's own system, LCPD must log in separately, and the data is not shared. So integration is selective, not universal, and that distinction should be preserved rather than flattened.
2 sources
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
State of New Mexico Department of Finance and Administration / City of Las Cruces · 2024-10-21 · Primary · local:las-cruces
The state money behind the Las Cruces RTCC, and the statutory language that describes the camera-integration function without naming any product.
- Laws of 2024, Chapter 66, Section 28, Paragraph 294: 650,000 dollars from the General Fund to purchase, equip, install and implement AN INTEGRATED SYSTEM OF CAMERAS, SURVEILLANCE EQUIPMENT AND INFORMATION TECHNOLOGY to develop a real-time crime center for the police department in Las Cruces in Dona Ana county.
- Grant 24-I2936, 650,000 dollars, term 07/01/2024 to 06/30/2026, reversion date June 30 2026, no match required.
- Accepted through the City Council packet of 21 October 2024; project contact Sean Mullen, Office of the Chief.
- The capital improvement plan in the same packet carries a Real Time Crime Center line for the Police Department at 1,750,000 dollars FY2025 and 250,000 dollars FY2026, funded by Grants, shown elsewhere as 1,100,000 dollars plus the 650,000 dollar 2024 legislative appropriation.
ORIGINAL RESEARCH, 2026-08-30, from the city's own 821-page 21 October 2024 agenda packet. THE PHRASE TO SEARCH FOR IN OTHER JURISDICTIONS IS 'INTEGRATED SYSTEM OF CAMERAS' - state appropriation language describes the camera-integration function generically, names no vendor and no product, and would be missed entirely by a keyword search for Flock, ALPR or Gateway. This is also the funding thread connecting the RTCC to the state legislature rather than to the city budget alone.
The camera-integration function appears in public records under generic language, not product names: New Mexico's 2024 appropriation gave Las Cruces 650,000 dollars to implement AN INTEGRATED SYSTEM OF CAMERAS, SURVEILLANCE EQUIPMENT AND INFORMATION TECHNOLOGY for a real-time crime center - naming no vendor and no product.
Well supported
The case against thisAppropriation language is deliberately generic so agencies can procure competitively; it is not evidence of concealment. It is decisive for METHOD: any search for this capability that looks only for Flock, ALPR or Gateway will miss it.
2 sources
State of New Mexico Department of Finance and Administration / City of Las Cruces · 2024-10-21 · Primary · local:las-cruces
The state money behind the Las Cruces RTCC, and the statutory language that describes the camera-integration function without naming any product.
- Laws of 2024, Chapter 66, Section 28, Paragraph 294: 650,000 dollars from the General Fund to purchase, equip, install and implement AN INTEGRATED SYSTEM OF CAMERAS, SURVEILLANCE EQUIPMENT AND INFORMATION TECHNOLOGY to develop a real-time crime center for the police department in Las Cruces in Dona Ana county.
- Grant 24-I2936, 650,000 dollars, term 07/01/2024 to 06/30/2026, reversion date June 30 2026, no match required.
- Accepted through the City Council packet of 21 October 2024; project contact Sean Mullen, Office of the Chief.
- The capital improvement plan in the same packet carries a Real Time Crime Center line for the Police Department at 1,750,000 dollars FY2025 and 250,000 dollars FY2026, funded by Grants, shown elsewhere as 1,100,000 dollars plus the 650,000 dollar 2024 legislative appropriation.
ORIGINAL RESEARCH, 2026-08-30, from the city's own 821-page 21 October 2024 agenda packet. THE PHRASE TO SEARCH FOR IN OTHER JURISDICTIONS IS 'INTEGRATED SYSTEM OF CAMERAS' - state appropriation language describes the camera-integration function generically, names no vendor and no product, and would be missed entirely by a keyword search for Flock, ALPR or Gateway. This is also the funding thread connecting the RTCC to the state legislature rather than to the city budget alone.
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
Las Cruces' legal department is trying to strip from its Flock contract the exact provisions chapter 6b identified: emergency sharing with other agencies, Flock training its own algorithms on city data, and Flock employees reviewing city data and using it in sales demos - the councilor adding, as it has in other cities.
Well supported1 of 4 sources not read at source
The case against thisThis is a councilor's account of an effort in progress, not an executed amendment - the terms may not change. It is nonetheless independent confirmation from a customer city that the training-data license and the vendor-review provision are real and objectionable, and the sales-demo reference points unmistakably at Dunwoody.
4 sources
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
American Civil Liberties Union · 2026-04-16 · Primary · national
ACLU analysis of Flock's revised terms and conditions, identifying four changes that shift control of the data from the customer city to the company.
- The clause Flock does not own and shall not sell Customer Data is absent from the updated terms.
- New terms grant Flock the exclusive right to determine and control the method, timing, format, and medium of a customer's access to its own data - with customers receiving degraded, low-resolution copies lacking metadata such as timestamps.
- Flock gains perpetual rights to use customer data to support and improve its services, retaining access after the customer's contract terminates.
- Expanded liability protections shield Flock even for willful misconduct or gross negligence; disputes go to private arbitration under Georgia law; and termination is made harder, including where cities decline or defund programs.
- ACLU advises municipalities to examine the changes closely, seek legal counsel before entering or renewing, and consider not installing mass surveillance systems at all.
The degraded-copy point deserves emphasis: a city that cannot get full-resolution data with metadata cannot independently audit its own system, which undercuts every locally promised safeguard including case-number verification.
404 Media · 2026-05-01 · Primary · GA
Flock employees live-viewed cameras inside a Jewish Community Center's children's gymnastics room, pool, fitness studios and playground to demonstrate the product to prospective police customers. A resident found it in the access logs.
- Flock staff, including a vice president who pulled up the feed 185 times since early 2025, live-viewed cameras in a JCC children's gymnastics room, pool, fitness studios and a playground, to demonstrate capabilities to prospective police department customers.
- Discovered when Dunwoody, Georgia resident Jason Hunyar filed a public records request for Flock's access logs within the city's camera network, and published his findings.
- The logs showed 1,271 outside agencies had been granted live-view permissions and 358 could record the streams.
- Flock confirmed the access happened as part of sales demonstrations while disputing how residents and activists characterized it.
- CEO Garrett Langley personally apologized to the Jewish community center, acknowledged poor judgement, promised radical transparency, and agreed to stop using Dunwoody footage for demonstrations.
- Dunwoody's city council renewed the contract anyway.
NOT READ at 404 Media (paywalled); assembled from multiple secondary accounts and the resident's own Substack, and should be confirmed. THIS IS THE DOSSIER'S METHOD WORKING AND ITS LIMIT IN ONE STORY: a single resident's records request for the access logs surfaced conduct no oversight body had found - and the council renewed regardless. Cite it when arguing for the audit log, and cite it again when someone assumes disclosure alone decides anything. The 1,271 live-view agencies figure is the most concrete illustration in the corpus of what joining the network actually grants.
Private Flock camera owners in Las Cruces do share with police, and they can be named: asked directly, a councilor said Lowes shares its data with LCPD and Home Depot does not - both now subject to SB 40.
Well supported1 of 3 sources not read at source
The case against thisA councilor's answer in a meeting, not a document; the sharing arrangements themselves have not been obtained. It does establish that the private-camera layer in Las Cruces is real, selective, and knowable by asking.
3 sources
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
DeFlock ILM · undated · Secondary · national
Guide for homeowners association boards on what integrating a Flock system with law enforcement actually does.
- More than 200 HOAs have signed up for Flock services.
- Once an HOA integrates its system with law enforcement, the neighborhood's cameras feed the same nationwide searchable network police use.
- An officer querying the database needs no warrant, named suspect or particular suspicion, and can search by plate, time window, location or vehicle description.
NOT READ in full; undated. An advocacy source, so its characterization of the query interface should be checked against Flock's own documentation and the audit logs. The HOA route matters in New Mexico because SB 40 now defines an ALPR to include non-law-enforcement operated devices.
Las Cruces asked for a 500,000 dollar federal earmark for a gunshot detection system at LCPD's request, submitted by both Rep. Vasquez and Sen. Lujan, mirroring one funded for Bernalillo County - while the councilor tracking it warned about a vendor rolling out a software update that added human-voice detection.
Well supported
The case against thisAn earmark request is not an award, and no vendor has been selected - the councilor noted a bid process would follow. The mission-creep warning is the substantive point, and it matches what Flock actually did with its audio product in 2025.
4 sources
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
Electronic Frontier Foundation · 2026-07-01 · Primary · national
Flock withdrew its plan to use its gunshot-detection microphone network to listen for human screaming and distress, after public pressure. The microphones remain deployed.
- Flock removed the human distress detection element after what it called careful consideration and community consultation.
- The acoustic detectors remain installed and continue listening for gunshots and vehicle crashes.
- Flock says the system cannot understand speech, analyze language or identify voices, and that audio is not recorded by default, with a rolling five-second window continually processed.
- EFF's Matthew Guariglia called gunshot microphones being used to listen for screaming exactly the type of mission creep seen with other surveillance technology.
- Marketing materials originally showed police receiving an alert for screaming; the ad was later amended to say distress.
Important as a counterexample: sustained public pressure reversed a specific rollout. Cite it when someone says opposition changes nothing. Note the microphones themselves stayed - the win was over a feature, not the hardware.
City of Chicago Office of Inspector General / MacArthur Justice Center · 2021-08-01 · Secondary · IL
Analysis of tens of thousands of acoustic gunshot detection alerts finding that the overwhelming majority produced no evidence of a gun crime.
- Chicago's Inspector General analyzed 50,176 alerts and found only 9.1 percent turned up evidence of a gun-related criminal offense.
- A MacArthur Justice Center analysis at Northwestern reached a similar result: nine out of ten times, detected noises led to no evidence of a crime.
- Chicago cancelled its ShotSpotter contract in 2024; other cities including Dayton have cancelled over cost and community backlash.
- SoundThinking claims a 97 percent accuracy rate; critics note the company paid a consultant to audit that figure.
- EFF notes there has been no independent public audit of accuracy, false alerts, response times or policing outcomes.
INGESTED SECOND-HAND from advocacy summaries; the OIG report itself has NOT been read, and the 2021 date is approximate. Relevant here because acoustic gunshot detection is a Flock product line (Raven, later Audio Detection) and because Bernalillo County's cancelled contracts included 116,000 dollars of gunshot detection devices. Accuracy of DETECTION and rate of EVIDENCE FOUND are different measures - the 9.1 percent is the latter.
Albuquerque Journal · 2026-08-27 · Primary · NM
New Mexico's largest county sheriff's office moved to end all three of its Flock contracts, citing loss of confidence in the vendor and out-of-state access to New Mexico data.
- Three contracts ending: 15,000 dollars for 5 ALPR cameras (expiring in October), 56,000 dollars for 16 speed cameras, 116,000 dollars for gunshot detection devices.
- Sheriff John Allen cited insufficient safeguards, cameras destroyed without notification, and out-of-state access to New Mexico data.
- Allen: if I don't have complete confidence in a vendor or company, how am I going to tell another law enforcement entity, yeah, go ahead and go with them.
- Allen barred Torrance and Curry counties from BCSO data over their ICE connections.
- An ACLU records request showed New Mexico cameras were accessed thousands of times by out-of-state law enforcement, including by Texas officers in the self-managed abortion investigation.
Significant because the objection comes from a sitting sheriff, not an advocacy group. Note the tension with the same sheriff's earlier no brainer remark to KOB.
A pattern that holds across every Las Cruces search: product-level detail exists in the contracts and nowhere in the council record. Peregrine, Multi-Purpose LPR, FlockOS Elite and Condor appear zero times across 413 scanned city and district documents, while Peregrine and Multi-Purpose LPR are in the contract and Condor was named by a councilor only in a 2026 verbal update.
Well supported
The case against thisCouncil materials summarize rather than enumerate line items, which is normal practice and not concealment. The consequence for research method is the point: a keyword search of council records will not find the products a jurisdiction actually bought, and the contract must be obtained separately.
4 sources
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
The targeted search for the Las Cruces Flock decision in the era it must have happened - 2021, under Chief Miguel Dominguez, in work sessions and council meetings. It is not in the published record.
- SCANNED: 96 agenda packets from the 2021 and 2022 City Council and Work Session folders - 29,404 pages, 52.2 million characters - plus 72 council and work session minutes documents for 2020-2022, 1,398 pages.
- Occurrences of flock, ALPR, license plate reader, plate reader, automated license: ZERO in the packets. One apparent hit in the September 2020 minutes is a resident's letter about unlicensed UTVs and is not ALPR.
- Widened vendor search across the same packets: Vigilant 0, Genetec 0, real-time crime 0. Motorola's 664 mentions in two documents are two-way radio price schedules. Leonardo's 45 mentions are a surname in a payment listing. Camera and surveillance mentions resolve to Axon body cameras, park and City Hall security, and a dam-safety suggestion.
- Controls: 7,994 matches for RESOLUTION, Police or contract across the packets; zero parse failures; the 31 low-character documents are short work session cover sheets with normal density.
- Chief Dominguez is named 375 times across 37 documents; Chief Story zero times - the correct era was searched.
- Las Cruces began operating plate readers in January 2022 per Chief Jeremy Story's own later statement, so the decision falls squarely inside the scanned window.
ORIGINAL RESEARCH, 2026-08-30, answering a specific question: was Flock considered at a Las Cruces work session and council meeting under Chief Dominguez, with staff notes and a vote? IN THE PUBLISHED RECORD, NO. State it as the bounded negative it is - not found in what was searched, never 'does not exist'. WHAT WOULD STILL EXPLAIN IT, all lawful: purchase off statewide price agreement 30-00000-22-00018, which requires no local procurement and apparently no council vote; execution below a council approval threshold; closed or executive session, which packets do not carry; a body not scanned, such as a committee; or documents the portal does not publish. The 2023 and 2025 packets were also not scanned. DO NOT PRESENT THIS AS CONCEALMENT. The likeliest explanation is the state purchasing channel this dossier documents elsewhere, and the county's own 2024 packet shows how ALPR can ride inside an item about something else entirely.
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
City of Las Cruces · 2026-06-01 · Primary · local:las-cruces
The most detailed public account of what Las Cruces actually operates, given by a councilor on the record - and confirmation that the city's Legal Department is trying to strip from its Flock contract the exact provisions this dossier flagged.
- CONTRACT RENEGOTIATION UNDERWAY: our Legal Department is attempting to work with Flock to change our contract to eliminate provisions for some things that we found objectionable - naming EMERGENCY SHARING WITH OTHER AGENCIES, TRAINING OF THEIR OWN ALGORITHMS, and REVIEW OF OUR DATA AND USE IN SALES DEMOS by Flock's own employees.
- Harris: we definitely do not want that happening with our data as it has in other cities.
- CAMERA INVENTORY: the city operates two Flock models. The Condor is a fixed camera, one direction, fixed focal length, and IT DOES DO A LIVE FEED. 22 cameras in total.
- THE INTEGRATION, in plain words: most of them are Flock branded ones although they do have some of the city's own cameras and THESE ALL GO INTO THE REAL TIME CRIME CENTER... the city does own some cameras, Flock has some cameras, Real Time Crime Center has access to all of these cameras and Flock is a vendor that helps make the Real Time Crime Center run.
- A LINE THE COUNCILOR DRAWS: newly approved capital improvement money for security and surveillance of city buildings and public spaces is NOT integrated into the RTCC - they are not Flock cameras, these are the city's own system, LCPD must log in separately, and the data is not shared.
- PRIVATE PARTICIPANTS NAMED: asked whether private Flock camera owners share data with LCPD - Lowes does, Home Depot does not - and both must comply with SB 40.
- GUNSHOT DETECTION: at LCPD's request the city asked for a 500,000 dollar Department of Justice earmark for a gunshot detection system; Rep. Vasquez and Sen. Lujan both submitted it, similar to a request funded for Bernalillo County Sheriff's Office.
- Harris on audio mission creep: Flock makes their own gunshot detection system and naturally last year they were like hey we are going to roll out a software update and now we can detect human voices which is maybe not great... I do want to make sure we have good policies and oversight into if we install systems to do one thing that they don't start doing another thing later because of a software update.
- Harris noted SB 40 takes effect July 1 with sharing restrictions and reporting requirements.
- Councilor Bencomo, responding: somebody recently said that the only safe data is the data that is not collected.
ORIGINAL RESEARCH, found 2026-08-30 by searching the Las Cruces minutes for GENERIC camera-integration language rather than product names. THIS IS THE ANSWER TO THE GATEWAY QUESTION IN THE CITY'S OWN WORDS: non-Flock, city-owned cameras do feed the Real Time Crime Center, and Flock is the vendor that makes the RTCC run. No product name is used. INDEPENDENT CORROBORATION OF CHAPTER 6B: a customer city's legal department is trying to remove the training-data license and the vendor-reviews-your-data provision - the two terms this dossier identified from Flock's published terms - and the sales-demo reference points unmistakably at the Dunwoody JCC episode. Also note the 22-camera figure against 21 in the September 2024 contract and 45 plus 7 in February 2026 reporting; the counts still need reconciling and each should be printed with its date and its speaker.
Haussamen (haussamen.com) · 2026-02-11 · Primary · local:las-cruces
The most detailed public account of Las Cruces' Flock contract and the council split over it, with statewide deployment figures.
- Las Cruces contract: 737,000 dollars over five years, newest agreement dated September 2024.
- 45 license plate readers in Las Cruces plus 7 on the NMSU campus.
- Cameras are solar powered and capture vehicle rear images; integrated into a 1.8 million dollar real-time crime center with drones and live video.
- Police Chief Jeremy Story supports the program and points to local privacy protections; Councilors Michael Harris, Cassie McClure and Johana Bencomo pressed for local restrictions on third-party sharing.
- Three residents asked for contract cancellation at the January 20 meeting.
- SB 40, sponsored by Sen. Peter Wirth, would bar LPR data for immigration enforcement and for activities legal in New Mexico, with quarterly reporting of out-of-state requests.
- Statewide and national figures cited: about 72,000 Flock cameras nationwide, 332 in greater Albuquerque, 37 near Alamogordo, 22 in Clovis, plus Border Patrol checkpoint locations.
The 72,000 nationwide figure is from February 2026 and is already stale against later counts above 120,000. Always cite this number with its date. Camera counts for Las Cruces differ from the Atlas of Surveillance entry; see atlas-lcpd-alpr.
The school-camera question cannot be answered from any public surface: the district publishes agendas and some minutes but no packets, and its document library carries policy rather than board materials. Closing it requires a records request to LCPS for the 19 August 2025 packet and the LCPS-City of Las Cruces MOU, plus the city's counterpart copy.
Well supported
The case against thisThe city side may answer it sooner and more easily: Las Cruces holds its own copy of any MOU with the district, and the city's records process is already the route being used for the Flock contracts.
3 sources
Las Cruces Public Schools (Apptegy), examined by this project · 2026-08-30 · Primary · local:las-cruces
The follow-up to the Granicus scan: the district's own document library, opened in a rendered browser rather than a plain fetch, to see whether board agenda packets are published anywhere online. They are not.
- The document library at lcps.net/documents holds 60 unique published files.
- Their subjects are district policy and administration: student discipline and threat-assessment policy series (JI, JK, JFB, JICA, ILBB, JBB), nutrition and free-meal notices, cash reports, high school profile, Equity Council agendas and notes, Finance Subcommittee agendas and schedules, and meeting-schedule notices.
- NO board agenda packets are among them. A single regular-session agenda appears (260324--Regular-Session-Agenda.pdf).
- The folder path /documents/board-documents renders an empty Name/Type/Size table; the files are served from the root /documents index.
- Combined with the Granicus scan of 216 board documents, this means the district publishes agendas and some minutes, and district policy - but not the packets.
ORIGINAL RESEARCH, 2026-08-30, using a rendered browser after a plain fetch returned almost nothing (the site is an Apptegy single-page app; the earlier curl saw one asset URL where the rendered page exposes sixty). CONCLUSION THAT MATTERS FOR METHOD: a staff report is generally the agenda packet, and LCPS DOES NOT PUBLISH ITS BOARD PACKETS ONLINE AT ALL. So the school-feeds question cannot be closed by scraping any public surface - it requires a records request to the district. This is a limit of publication, not evidence of anything: nothing here suggests the district withholds packets improperly, and many districts simply never post them.
Las Cruces Public Schools via Granicus, scanned by this project · 2026-08-30 · Primary · local:las-cruces
A search of the school district's published board record for any deliberation of Flock, camera integration or a police data-sharing arrangement. Nothing found - but the portal turns out to publish agendas rather than packets, so the district's staff reports have effectively NOT been searched.
- SCANNED: the complete Granicus board record, 216 documents across clip ids 33 to 332 (157 agenda documents and 59 minutes documents), 1,703 pages.
- Occurrences: flock 0, ALPR or license plate 0, surveillance 0, real-time crime 0, Wing Gateway 0.
- One gateway hit is a board member asking whether a firearm detection system would be a daily student walkthrough gateway into the schools. The 13 camera hits are surplus equipment inventory - document cameras and a Sony Mavica - and a parent describing filming a graduation.
- LCPD or police appears in 14 documents; memorandum of understanding or intergovernmental agreement in 23.
- CRITICAL LIMITATION: only TWO of the 216 documents are full agenda packets (1,054 pages and 311 pages). The remaining 214 are two-to-three page agenda cover sheets. Since a staff report IS generally the agenda packet, the district's staff reports are largely absent from this portal.
- Extraction was validated: 1,377 to 2,267 characters per page across the PDFs, zero image-only documents, zero parse failures.
ORIGINAL RESEARCH, 2026-08-30. METHOD FAILURE CAUGHT AND CORRECTED, worth recording because it would have produced a false all-clear: Granicus serves its AgendaViewer output as PDF bytes under a .html URL. A first pass stripped HTML tags from those binary streams and reported 50.9 million characters and zero camera mentions - it was regexing compressed PDF data, not text. Re-run with proper PDF extraction, the corpus is 1,703 pages. THE NEGATIVE HERE IS WEAK AND MUST BE LABELED THAT WAY: the board's actual packets are not on this portal. They are behind a JavaScript-rendered document library at lcps.net/documents/board-documents, which returned only one asset URL to a plain fetch. Retrieving that library is the outstanding task.
Las Cruces Public Schools Board of Education · 2025-08-19 · Primary · local:las-cruces
The single most promising unretrieved document for the school-camera question: an MOU between the school district and the city, listed under the board's safety goal, whose subject the published agenda does not state.
- Board of Education regular session, 19 August 2025, 5:36 PM, running 3 hours 4 minutes.
- Listed under Las Cruces Public Schools Strategic Plan Benchmarks, Goal 3 Environment - Mental Health & Wellbeing and Goal 4 Environment & Safety: item 2, Discussion and Possible Approval of Memorandum of Understanding between LCPS and City of Las Cruces.
- THE AGENDA DOES NOT SAY WHAT THE MOU COVERS. Only a three-page cover sheet is published for this meeting; no packet and no minutes appear in the Granicus record.
- By contrast, the same board's other city MOU is described in full on a later agenda: a 21 July 2026 Memorandum of Understanding with City of Las Cruces to Authorize Las Cruces Public Schools Staff to Direct Traffic Onto and Off School Property - so the district does normally name the subject.
- The same 2026 agenda also carries School Resource Officer service agreements with the Town of Mesilla and others, showing the district contracts with police agencies routinely.
- Timing: this MOU sits three weeks before LCPD General Order 173 on automated license plate readers, dated 11 September 2025.
IDENTIFIED 2026-08-30 by scanning the district's board record for generic agreement language rather than product names. THIS IS A LEAD, NOT A FINDING - there is no evidence whatever that this MOU concerns cameras, and the district signs many MOUs (autism services, behavioral health, teacher education, traffic direction). It is flagged for one reason: it is a city-district agreement filed under the SAFETY goal whose subject the published agenda uniquely does not state, and it is the only such document in the record. REQUEST IT: the packet or the executed MOU from LCPS, and the city's counterpart copy. Do not characterize it before it is read.
The largest single Flock commitment Las Cruces has made - 457,133 dollars for Drone as First Responder, signed 13 May 2025 - reached the city council in no document anyone can point to. The procurement module records no staff report and no enactment for it, and an independent scan of all 24 available 2025 council and work session packets (9,192 pages) finds zero references to DFR and no Flock item at all.
Well supported
The case against thisA bounded negative confirmed by two independent methods, not an accusation. Lawful explanations remain: purchase off statewide price agreement 30-00000-22-00018 requires no local vote, the authorization could predate 2025 or sit in a closed session, and a budget line naming neither vendor nor technology would not match any search term used.
3 sources
City of Las Cruces Document Center, scanned by this project · 2026-08-30 · Primary · local:las-cruces
A targeted search for the staff report behind the Flock DFR agreement, in the year it was signed. There isn't one - and this confirms independently the no_staff_report gap the procurement module records for that contract.
- SCANNED: 24 full agenda packets from the 2025 City Council and Work Session folders - 9,192 pages, 18.2 million characters - spanning January through July 2025.
- The Flock Law Enforcement Agreement (DFR) was signed 13 May 2025 for 307,133 dollars annually recurring, 457,133 dollars contract total.
- Occurrences of DFR or 'drone as first responder' across all 24 packets: ZERO.
- Occurrences of Flock: five, all in the 7 July 2025 packet, and all inside the reprinted minutes of the 2 June 2025 meeting - Michael Harris's public comment as a member of the public. Not a staff report, not an agenda item.
- All nine 'drone' mentions resolve to unrelated matters: aviation and drone liability insurance on a landscape architecture contract, a surveyor's CV, drone and aerospace tenants at the industrial park, FAA UAS integration planning at the airport, and the NMSU drone hangar.
- The April, May and June packets specifically - the window bracketing the signature - total 4,421 pages and contain no Flock and no DFR reference at all.
- From Harris's June 2025 comment, a per-unit figure not found elsewhere: each camera costs about 2,500 dollars per year.
ORIGINAL RESEARCH, 2026-08-30. THIS CORROBORATES THE MODULE FROM A DIFFERENT DIRECTION: the procurement database records a no_staff_report gap for this contract, and an independent full-text scan of the year's packets finds nothing either. Two methods, same answer. BOUNDED: 2025 packets only, council and work session bodies only; a DFR authorization could sit in a 2024 packet, in a closed session, in a budget line naming neither the vendor nor the technology, or below a council approval threshold - the state price agreement makes a local vote optional. NOT EVIDENCE OF CONCEALMENT. What it does establish is that the largest single Flock commitment Las Cruces has made reached the council in no document anyone can point to.
Flock Safety / City of Las Cruces · 2025-05-13 · Primary · local:las-cruces
Eight months after the plate-reader agreement, Las Cruces signed a Drone as First Responder contract with the same vendor at more than double the annual value - and the module's comparison finds NO staff report and NO council enactment attached to it.
- Signed 13 May 2025. Recorded as an AMENDMENT to the September 2024 agreement.
- Product line, quoted from page 2: Flock Safety Drone Hardware and Services, Flock Safety DFR 2.0 - 400ft.
- Annual recurring 307,133 dollars; Year 1 one-time fees 150,000 dollars; discounts 157,133 dollars; CONTRACT TOTAL 457,133 dollars, all quoted from page 2.
- RETENTION PERIOD: 30 DAYS.
- Includes a pilot arrangement quoted from page 2: PROJECT PROVE IT. Customer will have a 60 day opt-out period after implementation. Billing frequency is Annual Plan, invoiced at the end of the pilot period.
- AUTOMATIC RENEWAL on the same terms as the 2024 agreement.
- THE COMPARISON FINDS NO PAIRED STAFF REPORT AND NO ENACTMENT for this agreement - both fields are empty.
- Recorded as reviewed: false.
OBTAINED 2026-08-30 via the module's public API. THIS IS THE LAS CRUCES MISSION-CREEP FINDING, and it is stronger than the county's: the city went from a 141,850 dollar plate-reader agreement to a 457,133 dollar drone-as-first-responder agreement with the same vendor in eight months, and the module's own comparison finds nothing in the council record attached to the second one. MY INDEPENDENT SCAN CORROBORATES THAT GAP - 96 packets and 29,404 pages of 2021-2022 material plus the 2022-2026 minutes contain no Flock or ALPR mention at all. Two different methods, same answer. Still a bounded negative: the 2023 and 2025 agenda packets were not scanned by me, and the module's sweep is recorded as covering the council record to date.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
The earliest the Las Cruces council record names a license plate reader is 21 December 2020 - more than a year before the city began operating Flock cameras - and it is one of three projects inside a federal HIDTA narcotics grant (License Plate Reader, Money Serialization, Overdose Response) accepted on a routine grant summary at pages 26-27 of a 664-page packet.
Well supported
The case against thisThe council saw the words, so the record is not silent from the beginning. But it saw them once, in a grant acceptance listing several unrelated grants, with no description of what a license plate reader is or does - which is a materially different thing from deliberating a surveillance program.
2 sources
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
City of Alamogordo City Commission · 2024-12-03 · Primary · NM
The clearest window in the corpus into how Flock is sold to a New Mexico city: the local police chief, the LAS CRUCES police chief, and two Flock employees presenting together to a city commission. It also contains the most specific public account of the Las Cruces deployment, given by its own chief.
- Agenda item 7 presenters: Stephanie Hernandez (Acting City Manager), David Kunihiro (Alamogordo Police Chief), JEREMY STORY (LAS CRUCES Police Chief), and Cameron Lewis and Mark Solano of FLOCK SAFETY.
- LAS CRUCES CHIEF JEREMY STORY, in his own words: we were the first in the state to adopt Flock Safety; in January 2022 we started with the license plate readers; we currently have EIGHTEEN of them in a seventy-seven square mile city, meaning that is not a lot.
- Story's efficacy claim: we took our recovery rate for auto theft from fifty to sixty percent up to eighty and ninety percent.
- Story on Las Cruces crime: a 71 percent increase in property crime and 25 percent increase in violent crime from 2019 to 2023; over one thousand stolen vehicles in 2022, ranking the city eighteenth of three hundred ninety cities.
- Story framed the technology as a force multiplier for a short-staffed department, and said the Las Cruces RTCC would probably be operational in February 2025.
- Alamogordo Chief Kunihiro: 42 officers of 56 positions, down 25 percent; calls for service rising from 26,000 in 2021 to a pace of 35,000 in 2024; an average of 83 stolen vehicles a year with a recovery rate around 50 percent.
- Kunihiro: we are in the process of purchasing license plate readers and live-view Pan Tilt Zoom cameras to be strategically placed throughout the city.
- Kunihiro on federal cooperation: in November 2024 we partnered with the Border Patrol regarding two kidnapping suspects; Border Patrol entered it into their license plate reader and got a hit, and a day later we arrested the suspects.
- Kunihiro on the framing: an RTCC is not a big brother or government overreach.
- The packet included three New Mexico State Police stories in which license plate readers helped solve a vehicular homicide, a kidnapping of five children, and a stolen vehicle.
ORIGINAL RESEARCH, 2026-08-30, via the Alamogordo CivicClerk API (file 3600, the December 17 packet carrying the December 3 minutes; the agenda is file 3595). TWO REASONS THIS MATTERS. First, it resolves the Las Cruces camera-count confusion: 18 readers in December 2024 per the chief himself, against 22 devices in July 2025 public records and 45 plus 7 at NMSU in February 2026 reporting. Those sources were never in conflict - the deployment roughly doubled and then doubled again in fourteen months. Print the number WITH its date. Second, it is the pro-camera case at full strength from named officials under their own names, and the dossier is obliged to carry it that way. Note also that Cameron Lewis, presenting for Flock here, is the same name listed as Flock's contact on Amendment Eight of the state price agreement.
The HIDTA license plate reader money is regional, not municipal, and the city's own budget table shows it: in Fund 7492 HIDTA-CLC every city department expenditure line reads zero - the Las Cruces Police Department line included - while the whole fund, the 277,527 dollar LPR-bearing adjustment with it, is booked to a HIDTA line reaching 752,052 dollars.
Well supported
The case against thisA zero LCPD budget line does not prove no Las Cruces officer benefited: Metro Narcotics is a multi-agency task force that includes LCPD personnel, and equipment a regional office buys can be used locally. It does establish that these funds are not police department budget. What the LPR project actually purchased needs the ONDCP grant file, which is not attached to the packet.
1 source
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
The procurement database's HIDTA record carries the wrong dollar figure, and the two are one page apart in the archived document. It records 511,035.12 dollars - which on PAGE 26 is Attachment B, Cinematic Infrastructure Reauthorization, a film and digital media facility grant to Economic Development, agreement 20-E4039. The HIDTA grant is Attachment C on PAGE 27: 277,527 dollars, Metro Narcotics, agreement G20SN0006A.
Well supported
The case against thisThe two attachments are adjacent - pages 25 through 27 of the same grant acceptance summary - which is exactly how an extractor picks up a neighboring figure. The record is nonetheless marked reviewed:true, meaning a wrong number has been promoted past review. Correcting it is a data fix for whoever owns the module, and this dossier should not cite the 511,035 figure for anything.
2 sources
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
The Las Cruces conversation record on ALPR runs across fifteen council meetings from June 2025 to July 2026 - 30 extracted passages - while the procurement database holds eight remarks from one meeting. The discussion is overwhelmingly public comment and councilor debate, not staff material.
Well supported
The case against thisThese are candidates, not ingested rows, and no human has verified each quote against the minutes. The extractor is the module's own, which makes the output consistent with the pipeline but not thereby correct.
3 sources
City of Las Cruces council minutes, extracted by this project · 2026-08-30 · Primary · local:las-cruces
The conversation side of the Las Cruces record - what was actually said out loud about this technology, across fifteen council meetings the procurement database does not yet hold.
- 30 remarks across 15 meetings, June 2025 through July 2026, produced by running the module's own app.alpr_transcript.find_remarks over the council minutes.
- The procurement database currently holds 8 remarks from a single meeting (20 January 2026), so this is fifteen meetings of discussion it does not have.
- Meetings: 2 and 16 June 2025; 20 October; 1 December; 5 and 20 January 2026; 17 February; 2 March; 6 and 20 April; 18 May; 1 and 15 June; 6 and 20 July 2026.
- Topics the extractor assigns, by frequency: sharing (10), cost (7), federal_access (6), policy (6), civil_liberties (5), public_opposition (4), auto_renew (3), retention (2), camera_count (1).
- Matched terms: flock (27), license plate reader (6), alpr (3), flock safety (3), lpr (3), automated license plate (2), automatic license plate (2).
- 14 of 30 remarks carry a speaker guess parsed from the minutes' Name, Role said pattern; recurring names include Derrick Pacheco, Liz Bennett, Juan Garcia, Michael Harris, Lynn Moorer, Connie Chapman, Lucy Silva and Axl Hail, all as members of the public.
- The extractor returns ZERO remarks for the December 2022 minutes - independently agreeing with the manual judgment that its 'we have the license plate' passage is a crime victim's statement and not an ALPR reference.
CANDIDATES, NOT INGESTED, saved at api/seed_data/flock/lc_meeting_remarks_candidates.json. Produced with the module's OWN extractor rather than hand-authored rows, so the output matches what POST /api/alpr/remarks/ingest would create from the same text. It was not ingested because that endpoint reads Document.text_content and requires an archived transcript row plus ADMIN_TOKEN, neither of which this pass had - and manufacturing either would be the wrong way in. A SOURCE DIFFERENCE WORTH FLAGGING TO WHOEVER INGESTS: the table is designed around automatic captions, and its no-numbers rule exists because caption models mishear figures. These are clerk-written MINUTES, which are more reliable - but the rule is kept anyway, topics only. speaker_guess is a regex guess and must be verified before any name is published.
City of Las Cruces Document Center (lascruces.civicweb.net), scanned by this project · 2026-08-30 · Primary · local:las-cruces
An original full-text search of the Las Cruces council record for Flock and ALPR terms, run against the city's own CivicWeb Document Center. It establishes when the cameras entered the public record - and that the contract itself does not appear in it as a vote.
- SCANNED: 95 City Council minutes documents totaling 2,389 pages, plus 200 agenda documents (HTML) spanning council meetings, work sessions and special meetings 2019-2026.
- 16 minutes documents contain Flock, ALPR, license plate or plate reader as whole words.
- The earliest substantive discussion is June 2, 2025, in public comment by Michael Harris - then a member of the public, later a city councilor - who described automated license plate reading cameras appearing on private property and city rights-of-way, naming at least 10 locations including Lohman, University, Missouri, and sites at Lowe's and Home Depot.
- Mentions escalate sharply through 2026: January 5 (11), January 20 (19), February 17 (11), April 6 (11), June 1 (13).
- NOT FOUND ON THE PORTAL: in the documents scanned, no Flock or ALPR mention occurs within 400 characters of a resolution number, ordinance number, contract award, contract amendment, or a carried motion. The searched record contains public comment and councilor discussion, not a procurement vote.
- CONTROL: a comparable police technology procurement IS in the record and IS findable by the same method - the Axon body camera and Taser contract, including Resolution No. 25-057 amending Contract 20-21-054 to increase it by 446,625.57 dollars for a total not to exceed 2,324,799.79 dollars, appears on the November 4, 2024 council agenda.
- AGENDA PACKETS SCANNED: the six full council agenda packets spanning August 5 through October 21, 2024 - the window around the reported September 2024 renewal - total 4,106 pages (960, 891, 634, 215, 585 and 821). They contain ZERO occurrences of Flock, ALPR, license plate, plate reader or automated license. The words surveillance and camera appear at most once across all six.
- EXTRACTION VALIDATED on those packets: 430,000 to 1,112,000 characters extracted per packet, with RESOLUTION appearing 88-146 times, contract 78-379 times and Police 16-97 times - so the zero is a real absence, not a failed parse.
- THE DOMINGUEZ-ERA RECORD WAS SEARCHED AND IS CLEAN. Las Cruces adopted Flock in January 2022 per its own chief, so the decision would fall in 2021 under Chief Miguel Dominguez. Scanned: 96 council and WORK SESSION agenda packets for 2021-2022 (29,404 pages, 52.2 million characters) plus 72 council and work session minutes documents for 2020-2022 (1,398 pages). Occurrences of flock, ALPR, license plate reader, plate reader and automated license: ZERO.
- SEARCH TERMS WERE WIDENED IN CASE THE ITEM WAS NAMED DIFFERENTLY. Across those same 96 packets: flock 0, ALPR 0, plate reader 0, Vigilant 0, Genetec 0, real-time crime 0. Camera appeared in 41 documents and surveillance in 19, but reading the contexts found only Axon body cameras, park and City Hall security cameras, and a resident's suggestion of a camera above a dam. Motorola appeared 664 times in two documents and is two-way radio equipment (MotoTRBO, EVX-S24). Leonardo, the parent of the ELSAG plate-reader line, appeared 45 times and is a person's surname in a payment listing.
- CONTROLS AND EXTRACTION VALIDATED across the 2021-2022 packets: 7,994 matches for RESOLUTION, Police or contract; zero parse failures; and the 31 documents extracting under 5,000 characters are all one-to-five-page work session cover sheets with normal text density of 571 to 1,294 characters per page. Chief Dominguez is named 375 times across 37 documents, confirming the era is well covered. Chief Story appears zero times, consistent with his arriving later.
- February 17, 2026 minutes record a meeting with Flock representatives over Zoom, at which councilors were told, in the speaker's words, that Flock has never and will never integrate facial recognition into its product; the councilor noted they came away not entirely comforted.
- The same February 17, 2026 discussion raised the Mountain View, California incident, where Flock shared city data on the nationwide network and the company's response was that the city was not a client at the time and it was a demo system.
- April 6, 2026 minutes reference an op-ed by Councilors Bencomo and Harris opposing Flock, and record that LCPD invited Las Cruces residents to register their doorbell cameras with Flock.
- January 20, 2026 public comment cited the Aurora, Colorado false-flag stop and its 1.9 million dollar settlement, an approximately 10 percent error rate, Carpenter v. United States, and the assertion that Flock's own patent describes a dynamic surveillance network.
ORIGINAL RESEARCH by this project on 2026-08-30, using the city's own public Document Center - the same portal scripts/alpr/adapters/civicweb.py targets. METHOD AND ITS LIMITS, stated so the finding can be checked or overturned: agendas are published as HTML and minutes as PDF, so both were fetched and searched separately; matching used whole-word regex on extracted text. AN EARLIER PASS OF THIS SCAN PRODUCED NINE FALSE POSITIVES for 'alpr' because the text had been whitespace-stripped before matching, turning 'capital projects', 'biblical principles' and 'real problems' into apparent hits - the space-stripping was unnecessary for these PDFs and was removed. THE NEGATIVE FINDING IS BOUNDED: it means NOT FOUND IN THE DOCUMENTS SCANNED, never that no vote occurred. The six agenda packets for August-October 2024 HAVE now been scanned (4,106 pages, extraction validated against RESOLUTION/contract/Police counts). The 2021-2022 council and work session packets and the 2020-2022 minutes have NOW been scanned as well - see the Dominguez-era findings above. Still not scanned: agenda packets for 2023 and 2025, minutes attachments, and the Utilities and Planning and Zoning bodies. NOTE ON CONTROLS: the Axon control fires on the council AGENDA listing and in three minutes documents, but Axon and Taser appear zero times inside these six packets, so for the packets specifically the positive control is the presence of RESOLUTION, contract and Police text rather than a known police-technology procurement. A contract can also be executed administratively below a council approval threshold, or ride inside a consent-agenda item whose title names neither the vendor nor the technology. Any of those would explain the absence without any impropriety. VERIFY before publishing: pull the September 2024 agenda packet and the city's purchasing records directly.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
What Las Cruces residents and councilors actually raised, by the module's own topic tags: sharing (10 passages), cost (7), federal access (6), policy (6), civil liberties (5), public opposition (4), auto-renewal (3), retention (2), camera count (1) - the same subjects on which the staff report and enactment for the 2024 agreement are silent.
Well supported
The case against thisTopic tags are assigned by keyword matching and are a rough guide to subject, not a measure of how much time the council spent on anything. The overlap with the silent contract terms is nonetheless the point: the room discussed retention, sharing and auto-renewal; the council paperwork did not.
3 sources
City of Las Cruces council minutes, extracted by this project · 2026-08-30 · Primary · local:las-cruces
The conversation side of the Las Cruces record - what was actually said out loud about this technology, across fifteen council meetings the procurement database does not yet hold.
- 30 remarks across 15 meetings, June 2025 through July 2026, produced by running the module's own app.alpr_transcript.find_remarks over the council minutes.
- The procurement database currently holds 8 remarks from a single meeting (20 January 2026), so this is fifteen meetings of discussion it does not have.
- Meetings: 2 and 16 June 2025; 20 October; 1 December; 5 and 20 January 2026; 17 February; 2 March; 6 and 20 April; 18 May; 1 and 15 June; 6 and 20 July 2026.
- Topics the extractor assigns, by frequency: sharing (10), cost (7), federal_access (6), policy (6), civil_liberties (5), public_opposition (4), auto_renew (3), retention (2), camera_count (1).
- Matched terms: flock (27), license plate reader (6), alpr (3), flock safety (3), lpr (3), automated license plate (2), automatic license plate (2).
- 14 of 30 remarks carry a speaker guess parsed from the minutes' Name, Role said pattern; recurring names include Derrick Pacheco, Liz Bennett, Juan Garcia, Michael Harris, Lynn Moorer, Connie Chapman, Lucy Silva and Axl Hail, all as members of the public.
- The extractor returns ZERO remarks for the December 2022 minutes - independently agreeing with the manual judgment that its 'we have the license plate' passage is a crime victim's statement and not an ALPR reference.
CANDIDATES, NOT INGESTED, saved at api/seed_data/flock/lc_meeting_remarks_candidates.json. Produced with the module's OWN extractor rather than hand-authored rows, so the output matches what POST /api/alpr/remarks/ingest would create from the same text. It was not ingested because that endpoint reads Document.text_content and requires an archived transcript row plus ADMIN_TOKEN, neither of which this pass had - and manufacturing either would be the wrong way in. A SOURCE DIFFERENCE WORTH FLAGGING TO WHOEVER INGESTS: the table is designed around automatic captions, and its no-numbers rule exists because caption models mishear figures. These are clerk-written MINUTES, which are more reliable - but the rule is kept anyway, topics only. speaker_guess is a regex guess and must be verified before any name is published.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
Las Cruces has in writing the control whose absence caused the wrong-car-at-gunpoint cases: General Order 173's Active Hit Protocol requires, on every stolen-vehicle alert, a character-by-character misread check, a confirmation that the plate's STATE matches, and an NCIC check that the vehicle is still on the hot list - and states that an ALPR alert does not establish probable cause.
Well supported
The case against thisA written protocol is not a practiced one, and the wrong-car cases elsewhere generally involved officers skipping a verification their department already required. Compliance would show up in the monthly audits, which are not public.
3 sources
Las Cruces Police Department · 2025-09-11 · Primary · local:las-cruces
The city's own written ALPR policy, read in full. Four pages. It contains a real misread-verification protocol and a genuine audit requirement - and says almost nothing about the national network, out-of-state sharing, or federal access.
- Effective 09/11/2025; revised and reviewed 04/30/2025. Four pages. Supersedes all previous versions.
- REFERENCES section names one source: Albuquerque Police Department. The policy is modeled on APD's.
- ACTIVE HIT PROTOCOL, a mandatory three-step check on every stolen-vehicle alert: compare the detection and check for misreads, confirming all characters match; confirm the STATE of the wanted plate matches; and run an NCIC check to confirm the vehicle is still on the hot list.
- Quoted: An ALPR Alert under the ALPR Program does not establish probable cause for enforcement action. Hit information/data must be confirmed before taking any related law enforcement action.
- Query logging: a requestor, case number (IF AVAILABLE), and reason shall be entered with each investigative query. Administrative and auditing queries are exempt from the case-number requirement.
- Quoted, as a stated permitted use: Reasonable suspicion or probable cause is not required before using an ALPR.
- RETENTION: ALPR data shall only be held in the system for thirty (30) days, automatically purged after that unless evidentiary. In-vehicle data must be transferred to the department server at intervals not exceeding thirty days.
- DATA SHARING is one sentence in full: ALPR data shall be considered law enforcement sensitive and can only be shared for valid purposes.
- Audits: sample audits at least MONTHLY by the Intel Unit Section Head or designee, who is also responsible for retaining the audit records; plus an ANNUAL system-integrity audit by the Criminal Investigation Section Lieutenant, reported to the Chief of Police.
- Access: sworn personnel, Police Service Aides and the Crime Analyst Unit, via mobile dispatch terminal, department computer or smartphone, each with an individual username and password. Misuse is subject to discipline.
- Program administration sits with the Investigations and Intelligence Lieutenant or designee.
READ IN FULL 2026-08-30, from the document endpoint that had been returning HTTP 500 until commit f995c38 fixed it. WHAT IT DOES WELL, and the dossier should say so: the Active Hit Protocol is precisely the hot-list verification the Brennan Center recommends and precisely the control whose absence produced the wrong-car-at-gunpoint cases elsewhere in this corpus - Las Cruces has it in writing, along with an explicit statement that an alert is not probable cause. That is a real safeguard and supports LCPD's claim of protections beyond the minimum. FOUR THINGS IT DOES NOT DO. (1) The case number is optional - 'if available' - so this is weaker than the hard case-number rule Dona Ana County's lieutenant describes. (2) Data sharing is a single sentence with no mention of the national lookup network, out-of-state agencies, or federal access - the subjects on which the audit logs in this corpus show the actual risk. (3) It predates SB 40's effective date of 1 July 2026 and has not been revised since, so it carries none of the statute's written-declaration duty. (4) The monthly audit is conducted and retained by the same Intel unit whose queries it examines. This is also the document behind Councilor Harris's point that a departmental policy can be changed by the department - it is a general order, not an ordinance.
Electronic Frontier Foundation · 2024-11-01 · Primary · national
Case-by-case account of innocent drivers stopped at gunpoint after ALPR misreads or stale hot-list entries, with settlement figures.
- Brittney Gilliam, Aurora, Colorado, August 2020: a Colorado SUV matched to a stolen Montana motorcycle plate; family detained at gunpoint with children face-down on pavement; Aurora settled for 1.9 million dollars.
- Denise Green, San Francisco, March 2009: reader misread a 3 as a 7; officers drew guns; city paid 495,000 dollars.
- Jaclynn Gonzales, Espanola, New Mexico: reader mistook a 2 for a 7; detained at gunpoint, her 12-year-old sister placed in a patrol vehicle.
- Jason Burkleo, Atherton, California: misread an H as an M; detained at gunpoint.
- Brian Hofer, Contra Costa County, Thanksgiving 2019: hot list not updated after the vehicle was recovered; 49,500 dollar settlement.
- Isoke Robinson, Detroit: police queried all Dodge Chargers near a shooting; handcuffed at home, 2-year-old placed in a patrol car, car impounded three weeks.
- Cited study: ALPRs misread the state of one in ten plates, before counting other reading errors.
The Espanola case is the New Mexico entry in this list and belongs in the local chapter as well as the harms chapter.
Brennan Center for Justice · 2020-09-10 · Primary · national
Seven concrete policy recommendations for ALPR regulation - the closest thing in the corpus to ready-made ordinance language for a city council.
- Retention and warrants: delete non-matching plate scans immediately; if retained, limit to days rather than months; require a warrant for historical database searches absent emergency.
- Two-step scanning: the first query reveals only registration and hot-list status, and accessing personal information requires a basis for further police action.
- Hot list verification: mandate independent verification of hot-list data and real-time updates to prevent erroneous stops.
- Public transparency and input: communities participate in deployment decisions; policies published; audit results disclosed.
- Audit logs: track automated alerts, officer access to historical data, and all inter-agency data-sharing arrangements.
- Disparate impact audits: evaluate whether deployment disproportionately targets marginalized communities or protected activities.
- Safeguard effectiveness audits: regular review that access controls and retention actually function.
- Legal status as of 2020: no bright-line warrant rule; appeals courts had avoided direct engagement with Carpenter's application to ALPR.
READ on 2026-08-30, closing a gap this dossier had flagged as unread. Published 2020, so its legal-status section is superseded by Rinaldi, Norfolk and Chatrie - but the RECOMMENDATIONS are the durable part and map almost one to one onto what Las Cruces councilors are asking for. Hot-list verification and two-step scanning are the two that directly address the wrong-car gunpoint stops.
General Order 173 devotes a single sentence to data sharing - that ALPR data is law enforcement sensitive and may be shared for valid purposes - with no mention of the national lookup network, out-of-state agencies, or federal access, which are the subjects the audit logs in this corpus show to be the actual risk. It also predates SB 40's effective date and has not been revised since.
Well supported
The case against thisA department policy need not restate a statute that binds the agency regardless, and SB 40 took effect after the last revision. The gap is nonetheless the one that matters: the contract puts the city on the nationwide lookup network, and the policy governing its use does not mention that network exists.
4 sources
Las Cruces Police Department · 2025-09-11 · Primary · local:las-cruces
The city's own written ALPR policy, read in full. Four pages. It contains a real misread-verification protocol and a genuine audit requirement - and says almost nothing about the national network, out-of-state sharing, or federal access.
- Effective 09/11/2025; revised and reviewed 04/30/2025. Four pages. Supersedes all previous versions.
- REFERENCES section names one source: Albuquerque Police Department. The policy is modeled on APD's.
- ACTIVE HIT PROTOCOL, a mandatory three-step check on every stolen-vehicle alert: compare the detection and check for misreads, confirming all characters match; confirm the STATE of the wanted plate matches; and run an NCIC check to confirm the vehicle is still on the hot list.
- Quoted: An ALPR Alert under the ALPR Program does not establish probable cause for enforcement action. Hit information/data must be confirmed before taking any related law enforcement action.
- Query logging: a requestor, case number (IF AVAILABLE), and reason shall be entered with each investigative query. Administrative and auditing queries are exempt from the case-number requirement.
- Quoted, as a stated permitted use: Reasonable suspicion or probable cause is not required before using an ALPR.
- RETENTION: ALPR data shall only be held in the system for thirty (30) days, automatically purged after that unless evidentiary. In-vehicle data must be transferred to the department server at intervals not exceeding thirty days.
- DATA SHARING is one sentence in full: ALPR data shall be considered law enforcement sensitive and can only be shared for valid purposes.
- Audits: sample audits at least MONTHLY by the Intel Unit Section Head or designee, who is also responsible for retaining the audit records; plus an ANNUAL system-integrity audit by the Criminal Investigation Section Lieutenant, reported to the Chief of Police.
- Access: sworn personnel, Police Service Aides and the Crime Analyst Unit, via mobile dispatch terminal, department computer or smartphone, each with an individual username and password. Misuse is subject to discipline.
- Program administration sits with the Investigations and Intelligence Lieutenant or designee.
READ IN FULL 2026-08-30, from the document endpoint that had been returning HTTP 500 until commit f995c38 fixed it. WHAT IT DOES WELL, and the dossier should say so: the Active Hit Protocol is precisely the hot-list verification the Brennan Center recommends and precisely the control whose absence produced the wrong-car-at-gunpoint cases elsewhere in this corpus - Las Cruces has it in writing, along with an explicit statement that an alert is not probable cause. That is a real safeguard and supports LCPD's claim of protections beyond the minimum. FOUR THINGS IT DOES NOT DO. (1) The case number is optional - 'if available' - so this is weaker than the hard case-number rule Dona Ana County's lieutenant describes. (2) Data sharing is a single sentence with no mention of the national lookup network, out-of-state agencies, or federal access - the subjects on which the audit logs in this corpus show the actual risk. (3) It predates SB 40's effective date of 1 July 2026 and has not been revised since, so it carries none of the statute's written-declaration duty. (4) The monthly audit is conducted and retained by the same Intel unit whose queries it examines. This is also the document behind Councilor Harris's point that a departmental policy can be changed by the department - it is a general order, not an ordinance.
New Mexico Legislature · 2026-03-04 · Primary · NM
The enrolled statutory text of New Mexico's first ALPR law, read in full. It restricts sharing, mandates detailed annual agency reporting, and provides real enforcement - but it sets no retention limit, and it makes ALPR information confidential and not a public record under IPRA.
- Section 2 defines an automated license plate reader to include devices owned or operated by persons or entities other than law enforcement, so homeowners associations and businesses are covered.
- Section 3(A) bars a user from selling, sharing, allowing access to or transferring ALPR information where the user has reasonable belief it may be used to investigate or assist immigration enforcement, to investigate or prosecute a protected health care activity, or to impose liability based solely on constitutionally protected activity including assembly, petitioning and speech.
- Protected health care activity is defined to include seeking, providing or receiving reproductive or gender-affirming health care, and assisting someone who is - including by providing information, transportation, lodging or material support.
- Section 3(B) bars access by any out-of-state third party or non-New Mexico law enforcement agency without a prior written declaration expressly affirming the data will not be used in violation of Section 3(A); with no executed declaration, the user shall not share.
- Section 3(C) bars making ALPR information available to non-law-enforcement officers or agencies, excepting the user's own ALPR vendor for service provision.
- Section 3(D) makes ALPR information confidential and not a public record for purposes of the Inspection of Public Records Act.
- Section 4 requires each agency to report to the Department of Public Safety by April 1 each year for the prior calendar year: total cameras owned or leased by mobile or stationary placement; all state and federal databases the data was compared against; total queries INCLUDING THE PURPOSES for them; every other agency granted access; identified instances of unauthorized use or access per the agency's audit policy; subpoenas, warrants and third-party requests for data or audit trails and whether data was provided; the number of out-of-state third-party requests; and a list of all out-of-state agencies that queried the data.
- Section 4(B) requires DPS to aggregate the reporting and make it publicly available by July 1 each year.
- Section 5 authorizes enforcement by the attorney general or a district attorney, and by DPS; courts may grant injunctive relief and assess a civil penalty for an intentional violation of Section 3 of 10,000 dollars or actual damages per violation, whichever is greater.
- Section 5(D) and (E): a non-complying agency may have data-sharing privileges revoked and access to state-managed ALPR systems restricted; a non-complying vendor may face corrective action, suspension of authorization or termination of access.
- Section 6: effective July 1, 2026.
- THE STATUTE CONTAINS NO RETENTION LIMIT. Nothing in it caps how long ALPR information may be kept.
READ IN FULL from the Legislature's own enrolled PDF on 2026-08-30, closing a gap this dossier had flagged. TWO CORRECTIONS to the advocacy summaries previously relied on: (1) the act does not say access requires express consent or a court order - Section 3(D) makes the information confidential and not a public record under IPRA, which is a different thing; (2) reporting is annual to DPS by April 1 with public aggregation by July 1, not quarterly as earlier reporting described the introduced version. First agency reports covering calendar year 2026 are due April 1, 2027; first DPS public aggregation July 1, 2027.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
Flock Group Inc. / Dona Ana County Sheriff's Office · 2026-06-09 · Primary · local:dona-ana-county
AN ACTUAL EXECUTED FLOCK CONTRACT FOR A NEW MEXICO AGENCY, obtained in full from the county's own June 9 2026 agenda packet. It answers the questions the dossier had been asking hypothetically: how many cameras, what retention, which network features, what renewal terms.
- Customer: NM - Dona Ana County SO, 845 N Motel Blvd, Las Cruces. Initial Term 12 months, Renewal Term 12 months, billed annually, Net 30.
- RETENTION PERIOD: 30 DAYS, stated on the face of the Order Form.
- 54 units of Flock Safety LPR, fka Falcon, under a Flock Safety Platform line at 162,000 dollars; Year 1 162,000 at signing and 162,000 annual recurring thereafter.
- AUTOMATIC RENEWAL: the agreement renews for successive terms of the greater of one year or the length on the Order Form unless a party gives notice of non-renewal at least THIRTY DAYS before the end of the current term.
- Special Terms state the agreement is governed by the previously accepted terms of New Mexico Price Agreement 30-00000-22-00018, executed January 12, 2023.
- It supersedes all previously executed agreements between the parties, and prior agreements run coterminous with this Term.
- INCORPORATED BY REFERENCE: the Order Form is governed by the Master Services Agreement or, if none, the Terms of Service at flocksafety.com/legal/terms-and-conditions - terms Flock publishes and revises on its own website.
- Also incorporates state-required provisions at flocksafety.com/legal/state-required-provisions for listed states.
- CONTRACTED FLOCKOS FEATURES INCLUDE: Nationwide Network license plate lookup, described in the contract as leveraging a nationwide system boasting 10 billion additional plate reads per month; State Network lookup across all cameras opted in within the state; Law Enforcement Network Access to request direct access to devices of agencies outside the jurisdiction; and Community Network Access, the ability to request direct access to feeds from privately owned Flock cameras located in neighborhoods, schools and businesses.
- Vehicle Fingerprint search covers vehicle type, make, color, plate state, MISSING OR COVERED PLATES, and features such as bumper stickers, decals and roof racks.
- Insights and Analytics provides device performance data, USER AND NETWORK AUDITS, plate read reports, hot list alert reports, event logs and outcome reports.
- Real-time alerts against FBI NCIC and NCMEC databases; unlimited custom hot lists; unlimited users.
OBTAINED IN FULL on 2026-08-30 from the Dona Ana County agenda packet (pages 285-289 of 428) via the CivicClerk API. THIS IS THE MOST USEFUL SINGLE DOCUMENT IN THE CORPUS for a New Mexico reader, because it is a real New Mexico contract rather than a national description. Note what it settles: retention is 30 days by contract, not the 7 on Flock's policy page or the 30 in its legal-argument page; the county IS contracted onto the nationwide lookup network; and the audit tooling the sheriff relies on is a product feature named in the contract. Note also what it does NOT contain: any term about immigration enforcement, protected health care, or the SB 40 written declaration.
Where Dona Ana County's lieutenant describes a hard rule that every search carry a case number, Las Cruces policy requires a requestor, reason, and case number 'if available' - making the case number optional.
Well supported
The case against thisNot every legitimate query has a case number at the moment it is run - a developing incident or a welfare check may precede one - and the requestor and reason are still mandatory. The national audit logs nonetheless show the reason field being satisfied by whatever an officer types.
3 sources
Las Cruces Police Department · 2025-09-11 · Primary · local:las-cruces
The city's own written ALPR policy, read in full. Four pages. It contains a real misread-verification protocol and a genuine audit requirement - and says almost nothing about the national network, out-of-state sharing, or federal access.
- Effective 09/11/2025; revised and reviewed 04/30/2025. Four pages. Supersedes all previous versions.
- REFERENCES section names one source: Albuquerque Police Department. The policy is modeled on APD's.
- ACTIVE HIT PROTOCOL, a mandatory three-step check on every stolen-vehicle alert: compare the detection and check for misreads, confirming all characters match; confirm the STATE of the wanted plate matches; and run an NCIC check to confirm the vehicle is still on the hot list.
- Quoted: An ALPR Alert under the ALPR Program does not establish probable cause for enforcement action. Hit information/data must be confirmed before taking any related law enforcement action.
- Query logging: a requestor, case number (IF AVAILABLE), and reason shall be entered with each investigative query. Administrative and auditing queries are exempt from the case-number requirement.
- Quoted, as a stated permitted use: Reasonable suspicion or probable cause is not required before using an ALPR.
- RETENTION: ALPR data shall only be held in the system for thirty (30) days, automatically purged after that unless evidentiary. In-vehicle data must be transferred to the department server at intervals not exceeding thirty days.
- DATA SHARING is one sentence in full: ALPR data shall be considered law enforcement sensitive and can only be shared for valid purposes.
- Audits: sample audits at least MONTHLY by the Intel Unit Section Head or designee, who is also responsible for retaining the audit records; plus an ANNUAL system-integrity audit by the Criminal Investigation Section Lieutenant, reported to the Chief of Police.
- Access: sworn personnel, Police Service Aides and the Crime Analyst Unit, via mobile dispatch terminal, department computer or smartphone, each with an individual username and password. Misuse is subject to discipline.
- Program administration sits with the Investigations and Intelligence Lieutenant or designee.
READ IN FULL 2026-08-30, from the document endpoint that had been returning HTTP 500 until commit f995c38 fixed it. WHAT IT DOES WELL, and the dossier should say so: the Active Hit Protocol is precisely the hot-list verification the Brennan Center recommends and precisely the control whose absence produced the wrong-car-at-gunpoint cases elsewhere in this corpus - Las Cruces has it in writing, along with an explicit statement that an alert is not probable cause. That is a real safeguard and supports LCPD's claim of protections beyond the minimum. FOUR THINGS IT DOES NOT DO. (1) The case number is optional - 'if available' - so this is weaker than the hard case-number rule Dona Ana County's lieutenant describes. (2) Data sharing is a single sentence with no mention of the national lookup network, out-of-state agencies, or federal access - the subjects on which the audit logs in this corpus show the actual risk. (3) It predates SB 40's effective date of 1 July 2026 and has not been revised since, so it carries none of the statute's written-declaration duty. (4) The monthly audit is conducted and retained by the same Intel unit whose queries it examines. This is also the document behind Councilor Harris's point that a departmental policy can be changed by the department - it is a general order, not an ordinance.
KFOX 14 · 2026-06-24 · Primary · local:dona-ana-county
The county sheriff's office expanding its Flock deployment, with the clearest statement in the corpus of the safeguards a New Mexico agency claims to apply.
- About 30 cameras currently deployed, with 22 more planned within a year.
- 162,000 dollars approved for the yearly subscription and new cameras, already within the sheriff's approved budget, under one consolidated agreement.
- Lt. Eric Flores: there has to be a case number and therefore a crime associated with that vehicle.
- Flores: the cameras aren't used to surveil just everyday citizens.
- Flores: we've been able to basically solve many many crimes that normally we wouldn't have had leads on.
- Stated safeguards include monthly self-audits verifying that each query has an associated case number.
This is the local case FOR the cameras, and the dossier must carry it at full strength. Two things to test rather than assume: the case-number requirement is exactly the kind of control the national audit logs show being satisfied by free-text entries, and a MONTHLY SELF-AUDIT is the agency checking its own work - the same self-assessment weakness built into SB 40's reporting. Neither observation disproves the claim; both are checkable against the county's own SB 40 report due April 1, 2027.
Electronic Frontier Foundation · 2025-12-30 · Primary · national
EFF's summary of a year of investigations built on Flock's own network audit logs. Establishes the scale of searching across the national network and documents categories of abuse found in the search-reason field itself.
- More than 12 million ALPR searches logged by over 3,900 agencies between December 2024 and October 2025.
- 19 agencies ran searches tied to the No Kings protests; hundreds of searches across multiple protest events.
- More than 80 agencies used stereotyping or slur language against Romani people in search reasons, June 2024 to October 2025.
- A single Texas search reached 6,809 networks and 83,345 cameras.
- San Jose and other California agencies logged 3,965,519 searches between June 5, 2024 and June 17, 2025.
Derived from audit logs obtained by records request, i.e. the system's own record of itself, not an outside estimate. Counts are floors, not ceilings: they cover only agencies whose logs were produced.
The Las Cruces council was told the retention periods - by Chief Jeremy Story, in the 22 April 2024 work session: thirty days for license plate readers and seven days for all video. The signed agreement records a Retention Period of 30 days and carries no seven-day video figure at all.
Well supported
The case against thisLPR data and video may simply be different retention classes, in which case both statements are true of different things - General Order 173 sets thirty days for ALPR data and says nothing about video. That is the checkable question, and it is exactly the kind of divergence a staff-report-versus-contract comparison exists to surface.
3 sources
City of Las Cruces · 2024-04-22 · Primary · local:las-cruces
The document the whole Las Cruces comparison hangs on, read in full at last. It is a 1,732-page packet carrying the 22 April 2024 work session minutes - and in them a police chief states the retention periods out loud and a councilor asks twice for a work session she does not get.
- 1,732 pages. Occurrences of 'Flock': ZERO. One license-plate reference in the whole packet. Twelve mentions of a real-time crime center; twenty-three of 'drone', all unrelated - surveying and LiDAR services, an engineering day rate, and a public comment about the Middle East.
- The substance sits in the minutes of the WORK SESSION of 22 April 2024, printed as Agenda Item 5.2 - the procurement module labels this document as a council item of 2024-06-03, which is the packet date, not the meeting where the discussion happened.
- CHIEF JEREMY STORY, stating retention aloud: 'The retention rates that we have set now are thirty days for license plate readers. Which I think is a very reasonable amount and 7 days will be for all video. So a week is what we plan on setting it at.'
- COUNCILOR BENCOMO raised federal sharing directly: 'I particularly have concerns with just sharing data with entities like ICE for example. I have a ton of questions around that.'
- Bencomo asked TWICE for a dedicated public work session on the Real Time Crime Center - 'so the community can ask questions and be involved' and again 'my request would be that we do have a work session.'
- Chief Story's answer: 'I don't have an answer for the work session' - offering a town hall that Thursday instead.
- Story described the safeguards as limiting access to those who need it, auditing procedures to monitor that data is retrieved for proper purposes, an audit trail, and proper policy - 'a lot of good mechanisms in place or will be in place.'
- Bencomo also raised the harms she wanted policy to address, naming racial profiling among them.
READ IN FULL 2026-08-30, only possible after commit f995c38 fixed the 500 that had made this document unfetchable. THREE CONSEQUENCES. (1) The council was NOT told nothing about retention - it was told 30 days for plate readers and 7 days for video, by the chief, in a work session. But that is a verbal statement in minutes, not a written staff analysis, and the 7-day video figure has no counterpart anywhere in the signed contract, whose Retention Period field reads 30 days. (2) FEDERAL ACCESS WAS GENUINELY RAISED, by name, by a councilor - which means the module's 'addresses federal access' row may be defensible in substance even though the passage it quotes, at packet page 51, is a sergeant discussing asset forfeiture. The right passage exists at page 38; the extractor matched the wrong one. (3) The word Flock appears nowhere in 1,732 pages, so the vendor was never named to the council in this material.
Flock Safety / City of Las Cruces · 2024-09-12 · Primary · local:las-cruces
The Las Cruces Flock contract itself - ingested into this project's own ALPR procurement database by another session, and readable through the public API. It answers the questions this dossier had been asking about Las Cruces specifically.
- Signed 12 September 2024. Vendor Flock Safety. Recorded as the ORIGINAL contract for the jurisdiction.
- RETENTION PERIOD: 30 DAYS, quoted from page 2 of the agreement.
- 21 plate readers, quoted from page 2: Multi-Purpose LPR and Video Fixed w/ LTE Service, quantity 6, and Flock Safety Falcon, quantity 15.
- Total 141,850 dollars, quoted from page 2: Flock Safety Platform 141,850.00, with FlockOS Elite Package included.
- Billing frequency stated as Total Contract Billed at Signing.
- AUTOMATIC RENEWAL, quoted from page 3: This Agreement will automatically renew for successive renewal terms of the greater of one year or the length set forth on the Order Form.
- The agreement addresses data sharing at page 8, describing the Web Interface for automatic license plate detection, alerts, audio detection, searching image records, video and sharing Footage.
- Recorded as reviewed: false - a machine-extracted record that no human has yet promoted.
OBTAINED 2026-08-30 through the module's own public procurement API, not by me. ANOTHER SESSION INGESTED THIS and I had been reporting the Las Cruces contract as unread - it was in production the whole time, in alpr_contracts, and I was searching the city portal and the seed files instead of the module's own database. CORRECTION TO THIS DOSSIER: the widely reported figure of about 737,000 dollars over five years is NOT what this document says. The signed agreement records 141,850 dollars with 21 readers. Both may be true of different things - a not-to-exceed authorization versus an executed order - and the dossier must now print the document's number with the document's date, and treat the press figure as press. NOTE the audio detection reference at page 8: the 2021 Raven audio product was reported as dropped from the September 2024 renewal, and this page-8 language deserves a human read against that.
Las Cruces Police Department · 2025-09-11 · Primary · local:las-cruces
The city's own written ALPR policy, read in full. Four pages. It contains a real misread-verification protocol and a genuine audit requirement - and says almost nothing about the national network, out-of-state sharing, or federal access.
- Effective 09/11/2025; revised and reviewed 04/30/2025. Four pages. Supersedes all previous versions.
- REFERENCES section names one source: Albuquerque Police Department. The policy is modeled on APD's.
- ACTIVE HIT PROTOCOL, a mandatory three-step check on every stolen-vehicle alert: compare the detection and check for misreads, confirming all characters match; confirm the STATE of the wanted plate matches; and run an NCIC check to confirm the vehicle is still on the hot list.
- Quoted: An ALPR Alert under the ALPR Program does not establish probable cause for enforcement action. Hit information/data must be confirmed before taking any related law enforcement action.
- Query logging: a requestor, case number (IF AVAILABLE), and reason shall be entered with each investigative query. Administrative and auditing queries are exempt from the case-number requirement.
- Quoted, as a stated permitted use: Reasonable suspicion or probable cause is not required before using an ALPR.
- RETENTION: ALPR data shall only be held in the system for thirty (30) days, automatically purged after that unless evidentiary. In-vehicle data must be transferred to the department server at intervals not exceeding thirty days.
- DATA SHARING is one sentence in full: ALPR data shall be considered law enforcement sensitive and can only be shared for valid purposes.
- Audits: sample audits at least MONTHLY by the Intel Unit Section Head or designee, who is also responsible for retaining the audit records; plus an ANNUAL system-integrity audit by the Criminal Investigation Section Lieutenant, reported to the Chief of Police.
- Access: sworn personnel, Police Service Aides and the Crime Analyst Unit, via mobile dispatch terminal, department computer or smartphone, each with an individual username and password. Misuse is subject to discipline.
- Program administration sits with the Investigations and Intelligence Lieutenant or designee.
READ IN FULL 2026-08-30, from the document endpoint that had been returning HTTP 500 until commit f995c38 fixed it. WHAT IT DOES WELL, and the dossier should say so: the Active Hit Protocol is precisely the hot-list verification the Brennan Center recommends and precisely the control whose absence produced the wrong-car-at-gunpoint cases elsewhere in this corpus - Las Cruces has it in writing, along with an explicit statement that an alert is not probable cause. That is a real safeguard and supports LCPD's claim of protections beyond the minimum. FOUR THINGS IT DOES NOT DO. (1) The case number is optional - 'if available' - so this is weaker than the hard case-number rule Dona Ana County's lieutenant describes. (2) Data sharing is a single sentence with no mention of the national lookup network, out-of-state agencies, or federal access - the subjects on which the audit logs in this corpus show the actual risk. (3) It predates SB 40's effective date of 1 July 2026 and has not been revised since, so it carries none of the statute's written-declaration duty. (4) The monthly audit is conducted and retained by the same Intel unit whose queries it examines. This is also the document behind Councilor Harris's point that a departmental policy can be changed by the department - it is a general order, not an ordinance.
Federal sharing was raised in Las Cruces by name and early: in April 2024, before the agreement was signed, Councilor Bencomo said she had concerns about sharing data with entities like ICE and 'a ton of questions around that.'
Well supported
The case against thisThis also means the module's 'addresses federal access' comparison row may be right in substance while quoting the wrong passage - the extractor matched a sergeant discussing asset forfeiture at page 51, when the genuine ICE exchange sits at page 38. Reject the quoted candidate; keep the finding.
3 sources
City of Las Cruces · 2024-04-22 · Primary · local:las-cruces
The document the whole Las Cruces comparison hangs on, read in full at last. It is a 1,732-page packet carrying the 22 April 2024 work session minutes - and in them a police chief states the retention periods out loud and a councilor asks twice for a work session she does not get.
- 1,732 pages. Occurrences of 'Flock': ZERO. One license-plate reference in the whole packet. Twelve mentions of a real-time crime center; twenty-three of 'drone', all unrelated - surveying and LiDAR services, an engineering day rate, and a public comment about the Middle East.
- The substance sits in the minutes of the WORK SESSION of 22 April 2024, printed as Agenda Item 5.2 - the procurement module labels this document as a council item of 2024-06-03, which is the packet date, not the meeting where the discussion happened.
- CHIEF JEREMY STORY, stating retention aloud: 'The retention rates that we have set now are thirty days for license plate readers. Which I think is a very reasonable amount and 7 days will be for all video. So a week is what we plan on setting it at.'
- COUNCILOR BENCOMO raised federal sharing directly: 'I particularly have concerns with just sharing data with entities like ICE for example. I have a ton of questions around that.'
- Bencomo asked TWICE for a dedicated public work session on the Real Time Crime Center - 'so the community can ask questions and be involved' and again 'my request would be that we do have a work session.'
- Chief Story's answer: 'I don't have an answer for the work session' - offering a town hall that Thursday instead.
- Story described the safeguards as limiting access to those who need it, auditing procedures to monitor that data is retrieved for proper purposes, an audit trail, and proper policy - 'a lot of good mechanisms in place or will be in place.'
- Bencomo also raised the harms she wanted policy to address, naming racial profiling among them.
READ IN FULL 2026-08-30, only possible after commit f995c38 fixed the 500 that had made this document unfetchable. THREE CONSEQUENCES. (1) The council was NOT told nothing about retention - it was told 30 days for plate readers and 7 days for video, by the chief, in a work session. But that is a verbal statement in minutes, not a written staff analysis, and the 7-day video figure has no counterpart anywhere in the signed contract, whose Retention Period field reads 30 days. (2) FEDERAL ACCESS WAS GENUINELY RAISED, by name, by a councilor - which means the module's 'addresses federal access' row may be defensible in substance even though the passage it quotes, at packet page 51, is a sergeant discussing asset forfeiture. The right passage exists at page 38; the extractor matched the wrong one. (3) The word Flock appears nowhere in 1,732 pages, so the vendor was never named to the council in this material.
Perfect World Project /flock module · 2026-08-30 · Primary · local:las-cruces
The module's own row-by-row comparison of what the council was told against what the agreement says. On every material term of the 2024 agreement, the council record is silent and only the contract speaks.
- The 2024 agreement is paired with a staff report titled RTCC presentation to Council - 2024-06-03, and with Resolution 24-113, a 1,100,000 dollar budget adjustment from the Telshor Fund for Police Department Real Time Crime Center renovations.
- SILENT IN BOTH THE STAFF REPORT AND THE ENACTMENT, stated only in the contract: data retention (30 days), plate readers (21), total cost (141,850 dollars), automatic renewal, and the data-sharing provision.
- Term and annual cost are recorded as unknown - not stated anywhere, including the contract.
- The 2025 DFR agreement has NO paired staff report and NO enactment at all.
- One row runs the other way: Addresses federal access is marked stated in the staff report and enactment at page 51, and silent in the contract.
- Recorded gaps for the jurisdiction: no_staff_report - no staff report accompanying either signed agreement has been located in the council record swept to date; and master_agreement - the signed order form incorporates the previously executed agreement by reference, and that master agreement is not among the documents held, so the terms governing sharing and retention cannot be read in full.
THE FEDERAL-ACCESS ROW IS A FALSE POSITIVE AND SHOULD NOT BE PROMOTED. Its quoted passage at page 51 is Sgt. Gabriel Arenibas discussing where 600,000 dollars of seized funds goes - 'our Federal partners because we are a task force FBI' - which is asset forfeiture, not ALPR federal data sharing. The module's own rule is that a candidate is not a finding until a person reads both documents and promotes it, and every record here is correctly marked reviewed:false. Flagged for whoever reviews. Separately, /api/documents/{id}/file returned HTTP 500 for documents 21537, 21538, 21540 and 21657 on 2026-08-30, so the underlying files could not be read directly - the quotes above come from the compare payload.
KRWG Public Media · 2026-07-06 · Secondary · NM
ACLU of New Mexico's account of misuse of New Mexico ALPR data, including immigration-flagged search reasons, alongside Las Cruces council opposition.
- ACLU-NM reported data misused thousands of times in the prior year, with search reasons including immigration, ICE and HSI.
- A Texas sheriff accessed New Mexico camera data investigating a woman for a self-managed abortion.
- Daniel Williams, Deputy Director of Public Policy, ACLU-NM, is the named speaker.
- Residents have repeatedly opposed the cameras at Las Cruces council meetings; a hit-and-run was also solved with Flock assistance.
- SB 40, the Driver Privacy and Safety Act, passed in 2026.
The hit-and-run detail is included deliberately: the local case for the cameras belongs in the dossier at full strength.
What the 2020 HIDTA License Plate Reader project actually purchased is not knowable from the council record: the packet carries only the one-paragraph grant acceptance summary, and the ONDCP grant agreement is not attached.
Well supported
The case against thisThe grant file is obtainable - from the city as fiscal agent, or from ONDCP - and it is the document that would say whether any of this money became cameras, where they were installed, and for which agencies.
1 source
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
Metro Narcotics is not a police unit. It is a separate governmental entity created by a joint powers agreement dated 1 October 2001 between the City of Las Cruces, Dona Ana County and the New Mexico State Police, governed by an eight-member board drawn from the city, the county, the District Attorney's Office and the State Police, audited annually in its own name, with the City of Las Cruces as fiscal agent accounting for its resources as agency funds.
Well supported
The case against thisLCPD's public page describes Metro as a joint agency of three police forces and says nothing about a board, a JPA or separate financial statements, so a resident starting from the police department's own website would not learn that Metro is a governmental entity with its own budget and its own auditor.
3 sources
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
City of Las Cruces · undated · Primary · local:las-cruces
LCPD's own description of Metro Narcotics: a joint agency of three police forces, with a street address and a phone number, and no description of any technology it uses.
- Quoted: 'The Las Cruces/Dona Ana County Metro Narcotics Agency is the leading organization in combating drug trafficking and dealing in Las Cruces and Dona Ana County, New Mexico.'
- Named member agencies on this page: Las Cruces Police Department, Dona Ana County Sheriff's Office, New Mexico State Police.
- Address 217 E Picacho Avenue, Las Cruces NM 88004; phone (575) 526-0795.
- The page names no technology. HIDTA, license plate readers, ALPR, cameras, intelligence units and any real-time crime center are all absent from it.
Retrieved 2026-08-30. Read in full. The page is the public face of Metro Narcotics and it is three sentences long; every structural fact in this staging file about how Metro is actually governed and funded came from the audits and the board agendas instead, not from here. Undated: the city publishes no revision date on it.
City of Las Cruces · 2026-07-10 · Primary · local:las-cruces
Every Metro Narcotics Board of Supervisors agenda the city has published: quarterly meetings held by Zoom, budgets approved by resolution, equipment disposed of by resolution, and across all eleven agendas not one surveillance item.
- ELEVEN agendas are published, covering meetings on 17 Jan 2024, 17 Apr 2024 (referenced), 17 Jul 2024, 16 Oct 2024, an EMERGENCY meeting 23 Oct 2024, 15 Jan 2025, 16 Apr 2025, 16 Jul 2025, 15 Oct 2025, 21 Jan 2026, 15 Apr 2026 and 15 Jul 2026. Retrieved as the full result set of the city's WordPress agenda archive for the search term 'metro narcotics'.
- The board meets QUARTERLY and by ZOOM WEBINAR.
- BUDGETS, by resolution: Resolution 04-16-252 approved the FY 2025/2026 budget at 819,086 dollars (16 Apr 2025). Resolution 04-15-262 approved the FY 2026/2027 budget at 920,086 dollars (15 Apr 2026) - an increase of 101,000 dollars, 12.3 percent, in one year.
- Resolution 04-15-261 (15 Apr 2026): a 20,000 dollar budget adjustment 'to Increase Overtime for DEA Investigations'. The DEA is not a party to the joint powers agreement but Metro budgets overtime for its investigations.
- Resolution 04-16-251 (16 Apr 2025): 21,794.59 dollars moved in Fund 7420 'to account for and return seized funds to the State of New Mexico'. Fund 7420 is Metro's seized-asset fund and is a different fund from the city's HIDTA fund 7492.
- Resolution 10-16-251 (16 Oct 2024): 25,000 dollars from Metro's fund balance for training/travel, vehicle rentals and overtime. It was carried again at an EMERGENCY meeting a week later, 23 Oct 2024, as the single action item.
- Resolution 07-15-262 (15 Jul 2026): a 25,000 dollar FY2027 adjustment 'to be utilized for cubicles, furniture, possible K9 chemotherapy or the purchase of a new K9'.
- EQUIPMENT DISPOSAL resolutions appear twice: 07-16-251 (16 Jul 2025) and 07-15-261 (15 Jul 2026), each 'authorizing the disposal of obsolete and non-functioning equipment owned by Metro'. Neither agenda lists what the equipment is.
- The standing business every quarter is 'Financial Reports - Finance Department' and 'Recap of Quarterly Activities for Metro - Sgt. Gabriel Arenibas'. The recap is delivered orally; no written recap is attached.
- ACROSS ALL ELEVEN AGENDAS the words license plate, plate reader, ALPR, LPR, Flock, Axon, camera and surveillance do not appear once.
- NO PACKET AND NO MINUTES. Each agenda is a bare list of items with no attachments. Minutes are approved at the following meeting - the agendas prove minutes exist - but the city publishes none of them.
ORIGINAL RESEARCH, 2026-08-30, retrieved through the city's WordPress REST API (lascruces.gov/wp-json/wp/v2/agenda?search=metro%20narcotics) and read in full; all eleven agenda bodies were read, not just titles. The city's WordPress media library returns nothing for 'metro narcotics', so the absence of packets and minutes is an absence in the publishing system, not merely in the page. THE POINT IS NOT THAT THE BOARD HID ANYTHING. It is that a board governing a multi-agency narcotics task force, which sits on 342,808 dollars of HIDTA-funded equipment and approves a 920,086 dollar budget, publishes a one-page agenda per quarter and nothing else - so the only way to learn what Metro buys is the annual audit, which names no individual asset, or a records request.
Metro Narcotics carries 342,808 dollars of HIDTA-funded equipment on its own balance sheet, separately broken out from Metro equipment and seized equipment, and no published document names a single item of it.
Well supported
The case against thisA capital-asset line at historical cost is normal accounting, not concealment; audits do not print asset registers. The point is what follows from it: an inventory exists somewhere for the auditor to have tested, so the question of whether any of the 2020 license plate reader project sits inside that 342,808 dollars is answerable by a records request rather than unknowable.
3 sources
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
Metro Narcotics Agency / City of Las Cruces MuniDocs library · 2024-06-30 · Primary · local:las-cruces
The three earlier Metro audits, read for one purpose: to date the HIDTA equipment line and see whether it ever moves. It does not.
- FY2023 audit, equipment table: Metro equipment 393,620 dollars (2023) against 295,311 (2022); seized equipment 741,560 both years; HIDTA EQUIPMENT 342,808 BOTH YEARS; retirements (229,470); total 1,248,518 against 1,150,209.
- FY2024 audit, equipment table: Metro equipment 448,548 (2024) against 393,620 (2023); seized equipment 741,560 both years; HIDTA EQUIPMENT 342,808 BOTH YEARS; total 1,303,446 against 1,248,518.
- Taken with the FY2025 audit, the HIDTA equipment line reads 342,808 dollars at every one of the four year-ends 30 June 2022, 2023, 2024 and 2025. NO HIDTA-FUNDED EQUIPMENT HAS BEEN CAPITALIZED SINCE FISCAL 2022 AT THE LATEST.
- The seized equipment line is likewise frozen at 741,560 dollars across all four years, and is more than double the HIDTA line.
- FY2022 audit: capital assets net 204,478 dollars at 30 June 2022 against 204,597 at 30 June 2021; additions 76,362, retirements 79,511, a net decrease in total equipment of 3,149 dollars. Quoted: 'No commitments have been made for future capital expenditures.'
- The FY2022 audit's own three-way equipment breakout could not be recovered from the extracted text of that PDF, so the earliest year in which the HIDTA line can be read directly is fiscal 2022 as the comparative column of the FY2023 audit. WHEN THE 342,808 DOLLARS WAS FIRST CAPITALIZED IS NOT FOUND IN THE PUBLISHED AUDITS - which is not the same as saying it is not recorded somewhere.
Retrieved 2026-08-30 from MuniDocs (Metro 2022 nodeId 68755ef7484a0, Metro 2023 nodeId 731ddb9fa0dd6, Metro 2024 nodeId 7aaab2c0eae68). All three PDFs were downloaded and text-extracted; the capital-asset tables, the capital-asset narrative and a full-text term scan for ALPR, license plate, plate reader, Flock, Axon, camera and surveillance were read in each. Those terms return zero hits in all three years. The rest of each document - the investment schedules, the compliance sections - was scanned rather than read line by line, and nothing in this staging file rests on those parts. The URL given is the MuniDocs Metro folder; the three individual documents sit under it.
City of Las Cruces · 2026-07-10 · Primary · local:las-cruces
Every Metro Narcotics Board of Supervisors agenda the city has published: quarterly meetings held by Zoom, budgets approved by resolution, equipment disposed of by resolution, and across all eleven agendas not one surveillance item.
- ELEVEN agendas are published, covering meetings on 17 Jan 2024, 17 Apr 2024 (referenced), 17 Jul 2024, 16 Oct 2024, an EMERGENCY meeting 23 Oct 2024, 15 Jan 2025, 16 Apr 2025, 16 Jul 2025, 15 Oct 2025, 21 Jan 2026, 15 Apr 2026 and 15 Jul 2026. Retrieved as the full result set of the city's WordPress agenda archive for the search term 'metro narcotics'.
- The board meets QUARTERLY and by ZOOM WEBINAR.
- BUDGETS, by resolution: Resolution 04-16-252 approved the FY 2025/2026 budget at 819,086 dollars (16 Apr 2025). Resolution 04-15-262 approved the FY 2026/2027 budget at 920,086 dollars (15 Apr 2026) - an increase of 101,000 dollars, 12.3 percent, in one year.
- Resolution 04-15-261 (15 Apr 2026): a 20,000 dollar budget adjustment 'to Increase Overtime for DEA Investigations'. The DEA is not a party to the joint powers agreement but Metro budgets overtime for its investigations.
- Resolution 04-16-251 (16 Apr 2025): 21,794.59 dollars moved in Fund 7420 'to account for and return seized funds to the State of New Mexico'. Fund 7420 is Metro's seized-asset fund and is a different fund from the city's HIDTA fund 7492.
- Resolution 10-16-251 (16 Oct 2024): 25,000 dollars from Metro's fund balance for training/travel, vehicle rentals and overtime. It was carried again at an EMERGENCY meeting a week later, 23 Oct 2024, as the single action item.
- Resolution 07-15-262 (15 Jul 2026): a 25,000 dollar FY2027 adjustment 'to be utilized for cubicles, furniture, possible K9 chemotherapy or the purchase of a new K9'.
- EQUIPMENT DISPOSAL resolutions appear twice: 07-16-251 (16 Jul 2025) and 07-15-261 (15 Jul 2026), each 'authorizing the disposal of obsolete and non-functioning equipment owned by Metro'. Neither agenda lists what the equipment is.
- The standing business every quarter is 'Financial Reports - Finance Department' and 'Recap of Quarterly Activities for Metro - Sgt. Gabriel Arenibas'. The recap is delivered orally; no written recap is attached.
- ACROSS ALL ELEVEN AGENDAS the words license plate, plate reader, ALPR, LPR, Flock, Axon, camera and surveillance do not appear once.
- NO PACKET AND NO MINUTES. Each agenda is a bare list of items with no attachments. Minutes are approved at the following meeting - the agendas prove minutes exist - but the city publishes none of them.
ORIGINAL RESEARCH, 2026-08-30, retrieved through the city's WordPress REST API (lascruces.gov/wp-json/wp/v2/agenda?search=metro%20narcotics) and read in full; all eleven agenda bodies were read, not just titles. The city's WordPress media library returns nothing for 'metro narcotics', so the absence of packets and minutes is an absence in the publishing system, not merely in the page. THE POINT IS NOT THAT THE BOARD HID ANYTHING. It is that a board governing a multi-agency narcotics task force, which sits on 342,808 dollars of HIDTA-funded equipment and approves a 920,086 dollar budget, publishes a one-page agenda per quarter and nothing else - so the only way to learn what Metro buys is the annual audit, which names no individual asset, or a records request.
The HIDTA equipment line on Metro Narcotics' balance sheet reads exactly 342,808 dollars at all four year-ends from 30 June 2022 through 30 June 2025, so no HIDTA-funded equipment has been capitalized by Metro in at least four years; every dollar of the 78,506 dollars added in fiscal 2025 landed on the ordinary Metro equipment line instead.
Well supported
The case against thisA flat capitalized line does not mean no HIDTA money is being spent. Federal grant money is overwhelmingly spent on overtime, travel, services and consumables, none of which is capitalized, and equipment below the capitalization threshold never reaches the table at all - a subscription license plate reader service, which is what Flock sells, would be an operating expense and would never appear on this line no matter how much of it was bought.
2 sources
Metro Narcotics Agency / City of Las Cruces MuniDocs library · 2024-06-30 · Primary · local:las-cruces
The three earlier Metro audits, read for one purpose: to date the HIDTA equipment line and see whether it ever moves. It does not.
- FY2023 audit, equipment table: Metro equipment 393,620 dollars (2023) against 295,311 (2022); seized equipment 741,560 both years; HIDTA EQUIPMENT 342,808 BOTH YEARS; retirements (229,470); total 1,248,518 against 1,150,209.
- FY2024 audit, equipment table: Metro equipment 448,548 (2024) against 393,620 (2023); seized equipment 741,560 both years; HIDTA EQUIPMENT 342,808 BOTH YEARS; total 1,303,446 against 1,248,518.
- Taken with the FY2025 audit, the HIDTA equipment line reads 342,808 dollars at every one of the four year-ends 30 June 2022, 2023, 2024 and 2025. NO HIDTA-FUNDED EQUIPMENT HAS BEEN CAPITALIZED SINCE FISCAL 2022 AT THE LATEST.
- The seized equipment line is likewise frozen at 741,560 dollars across all four years, and is more than double the HIDTA line.
- FY2022 audit: capital assets net 204,478 dollars at 30 June 2022 against 204,597 at 30 June 2021; additions 76,362, retirements 79,511, a net decrease in total equipment of 3,149 dollars. Quoted: 'No commitments have been made for future capital expenditures.'
- The FY2022 audit's own three-way equipment breakout could not be recovered from the extracted text of that PDF, so the earliest year in which the HIDTA line can be read directly is fiscal 2022 as the comparative column of the FY2023 audit. WHEN THE 342,808 DOLLARS WAS FIRST CAPITALIZED IS NOT FOUND IN THE PUBLISHED AUDITS - which is not the same as saying it is not recorded somewhere.
Retrieved 2026-08-30 from MuniDocs (Metro 2022 nodeId 68755ef7484a0, Metro 2023 nodeId 731ddb9fa0dd6, Metro 2024 nodeId 7aaab2c0eae68). All three PDFs were downloaded and text-extracted; the capital-asset tables, the capital-asset narrative and a full-text term scan for ALPR, license plate, plate reader, Flock, Axon, camera and surveillance were read in each. Those terms return zero hits in all three years. The rest of each document - the investment schedules, the compliance sections - was scanned rather than read line by line, and nothing in this staging file rests on those parts. The URL given is the MuniDocs Metro folder; the three individual documents sit under it.
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
The roughly 900,000 dollars a year of ONDCP HIDTA money the City of Las Cruces receives as fiscal agent does not appear as revenue in Metro Narcotics' audited operating statements: Metro's total fiscal 2025 revenue was 720,484 dollars and its entire operating-grant revenue was 11,054 dollars, all of it from the FBI joint powers agreement.
Well supported
The case against thisThis is the fiscal-agent structure working as designed, not money going missing: the city holds HIDTA funds in agency funds on behalf of the regional office, and agency funds are custodial, so they are not Metro's revenue and should not be in Metro's operating statements. The consequence is still real. A reader who audits Metro Narcotics sees a 720,484 dollar organization; a reader who reads the city's grant packets sees a 1.2 million dollar federal award; and no single published document reconciles the two.
2 sources
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
USAspending.gov (U.S. Department of the Treasury) · 2026-08-30 · Primary · local:las-cruces
The federal side of the grant the Las Cruces council saw once in December 2020 - eleven consecutive annual awards, and a modification record that dates the license plate reader money to the day.
- ELEVEN CONSECUTIVE ANNUAL AWARDS to CITY OF LAS CRUCES from the Office of National Drug Control Policy, Executive Office of the President, award numbers G14SN0006A through G24SN0006A, each a two-calendar-year performance period: FY14 803,673.57; FY15 1,470,894; FY16 1,456,881; FY17 1,424,654.31; FY18 925,605.97; FY19 999,014; FY20 1,242,100.50; FY21 1,259,792; FY22 1,359,950; FY23 1,068,696; FY24 903,130 dollars. Eleven awards totalling 12,914,390.35 dollars.
- MODIFICATION 0002 OF THE FY2020 AWARD IS THE LICENSE PLATE READER MONEY, and the federal record dates it: action date 26 OCTOBER 2020, federal action obligation 277,527.00 dollars. This is an exact match to the figure and the description in the city's 21 December 2020 council packet - independent federal corroboration of the local record, eight weeks earlier.
- The full FY2020 transaction history: base award 9 March 2020, 977,631 dollars; modification 0001, 13 August 2020, +32,200; modification 0002, 26 October 2020, +277,527; modification 0003, 29 July 2021, MINUS 40,270; modification 0004, 20 August 2021, MINUS 4,987.50. Net total obligation 1,242,100.50 dollars, fully outlaid.
- The city's packet gives a 'TOTAL GRANT PROJECT AMOUNT' of 1,287,358 dollars for the same award. The federal record's final obligation is 1,242,100.50 - a difference of 45,257.50 dollars, exactly the sum of the two 2021 deobligations. The packet figure is the award as it stood when the council accepted it; the federal figure is the award as it closed.
- Recipient identity: CITY OF LAS CRUCES, UEI J3ZLWA2K1X47, DUNS 077609279. Place of performance: DONA ANA county, New Mexico, congressional district 02. Awarding and funding office: EOP-OFC OF NATL DRUG CONTROL POLICY, subtier code 1127.
- Non-federal funding on the FY2020 award is 0.00 dollars, matching the packet's 'no match required'.
- FY18 through FY24 awards are recorded as fully outlaid. The FY19 award shows 574,014 dollars outlaid against 999,014 obligated.
- THE SERIES STOPS AT FY2024. No FY2025 or FY2026 ONDCP award to the City of Las Cruces is found in USAspending as of 30 August 2026, although FY2025-numbered ONDCP awards to other New Mexico recipients (for example HID3025G0533 to the Fifth Judicial District Attorney, 287,680 dollars, and HID3025G0460 to Taos Health Systems, 127,000 dollars) are present under a new HID-prefix numbering scheme. NOT FOUND IS NOT DOES NOT EXIST: the city is on its fifteenth year of this money and the likeliest explanation is reporting lag or a renumbered record.
ORIGINAL RESEARCH, 2026-08-30, pulled from the USAspending v2 API: spending_by_award filtered to ONDCP and to the recipient, the award detail endpoint for each generated_internal_id, and the transactions endpoint for the FY2020 award. Every figure above was read from the API response, not from a summary page. WHY THIS MATTERS TO THE DOSSIER: the existing corpus knows about ONE HIDTA document, the December 2020 council item, and treats the 277,527 dollars as an isolated sighting. It is not isolated. It is one modification inside a fifteen-year, roughly 13 million dollar federal funding relationship in which the City of Las Cruces is the fiscal agent, and the council record contains almost none of it. What the federal record still does NOT say is what any of the money bought - USAspending carries obligations, not equipment lists.
The 277,527 dollar license plate reader modification the Las Cruces council saw in December 2020 is not an isolated sighting: it is modification 0002 of the seventh in an unbroken run of eleven annual ONDCP awards to the City of Las Cruces, G14SN0006A through G24SN0006A, totalling 12,914,390.35 dollars from 2014 through 2025.
Well supported
The case against thisSize is not implication: most of that 12.9 million dollars is personnel, overtime and regional office operations for a HIDTA covering 17 counties, and nothing in the federal record attributes any of it beyond the one modification to license plate readers. What the scale establishes is that the council's single December 2020 sighting was a sighting of one modification inside a standing relationship, not of an unusual event.
2 sources
USAspending.gov (U.S. Department of the Treasury) · 2026-08-30 · Primary · local:las-cruces
The federal side of the grant the Las Cruces council saw once in December 2020 - eleven consecutive annual awards, and a modification record that dates the license plate reader money to the day.
- ELEVEN CONSECUTIVE ANNUAL AWARDS to CITY OF LAS CRUCES from the Office of National Drug Control Policy, Executive Office of the President, award numbers G14SN0006A through G24SN0006A, each a two-calendar-year performance period: FY14 803,673.57; FY15 1,470,894; FY16 1,456,881; FY17 1,424,654.31; FY18 925,605.97; FY19 999,014; FY20 1,242,100.50; FY21 1,259,792; FY22 1,359,950; FY23 1,068,696; FY24 903,130 dollars. Eleven awards totalling 12,914,390.35 dollars.
- MODIFICATION 0002 OF THE FY2020 AWARD IS THE LICENSE PLATE READER MONEY, and the federal record dates it: action date 26 OCTOBER 2020, federal action obligation 277,527.00 dollars. This is an exact match to the figure and the description in the city's 21 December 2020 council packet - independent federal corroboration of the local record, eight weeks earlier.
- The full FY2020 transaction history: base award 9 March 2020, 977,631 dollars; modification 0001, 13 August 2020, +32,200; modification 0002, 26 October 2020, +277,527; modification 0003, 29 July 2021, MINUS 40,270; modification 0004, 20 August 2021, MINUS 4,987.50. Net total obligation 1,242,100.50 dollars, fully outlaid.
- The city's packet gives a 'TOTAL GRANT PROJECT AMOUNT' of 1,287,358 dollars for the same award. The federal record's final obligation is 1,242,100.50 - a difference of 45,257.50 dollars, exactly the sum of the two 2021 deobligations. The packet figure is the award as it stood when the council accepted it; the federal figure is the award as it closed.
- Recipient identity: CITY OF LAS CRUCES, UEI J3ZLWA2K1X47, DUNS 077609279. Place of performance: DONA ANA county, New Mexico, congressional district 02. Awarding and funding office: EOP-OFC OF NATL DRUG CONTROL POLICY, subtier code 1127.
- Non-federal funding on the FY2020 award is 0.00 dollars, matching the packet's 'no match required'.
- FY18 through FY24 awards are recorded as fully outlaid. The FY19 award shows 574,014 dollars outlaid against 999,014 obligated.
- THE SERIES STOPS AT FY2024. No FY2025 or FY2026 ONDCP award to the City of Las Cruces is found in USAspending as of 30 August 2026, although FY2025-numbered ONDCP awards to other New Mexico recipients (for example HID3025G0533 to the Fifth Judicial District Attorney, 287,680 dollars, and HID3025G0460 to Taos Health Systems, 127,000 dollars) are present under a new HID-prefix numbering scheme. NOT FOUND IS NOT DOES NOT EXIST: the city is on its fifteenth year of this money and the likeliest explanation is reporting lag or a renumbered record.
ORIGINAL RESEARCH, 2026-08-30, pulled from the USAspending v2 API: spending_by_award filtered to ONDCP and to the recipient, the award detail endpoint for each generated_internal_id, and the transactions endpoint for the FY2020 award. Every figure above was read from the API response, not from a summary page. WHY THIS MATTERS TO THE DOSSIER: the existing corpus knows about ONE HIDTA document, the December 2020 council item, and treats the 277,527 dollars as an isolated sighting. It is not isolated. It is one modification inside a fifteen-year, roughly 13 million dollar federal funding relationship in which the City of Las Cruces is the fiscal agent, and the council record contains almost none of it. What the federal record still does NOT say is what any of the money bought - USAspending carries obligations, not equipment lists.
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
The federal transaction record dates the license plate reader money to 26 October 2020 - modification 0002, 277,527.00 dollars - independently corroborating the figure and description in the city's 21 December 2020 council packet from a second, unrelated system, and showing the council accepted the modification eight weeks after the federal action.
Well supported
The case against thisAn eight-week lag between a federal obligation and a council acceptance item is ordinary grant administration and is not evidence of anything being withheld. The corroboration is what matters: two independent records agree on the amount to the dollar, which puts the 277,527 dollar figure beyond argument and confirms that the procurement database's 511,035.12 dollars is the wrong number.
2 sources
USAspending.gov (U.S. Department of the Treasury) · 2026-08-30 · Primary · local:las-cruces
The federal side of the grant the Las Cruces council saw once in December 2020 - eleven consecutive annual awards, and a modification record that dates the license plate reader money to the day.
- ELEVEN CONSECUTIVE ANNUAL AWARDS to CITY OF LAS CRUCES from the Office of National Drug Control Policy, Executive Office of the President, award numbers G14SN0006A through G24SN0006A, each a two-calendar-year performance period: FY14 803,673.57; FY15 1,470,894; FY16 1,456,881; FY17 1,424,654.31; FY18 925,605.97; FY19 999,014; FY20 1,242,100.50; FY21 1,259,792; FY22 1,359,950; FY23 1,068,696; FY24 903,130 dollars. Eleven awards totalling 12,914,390.35 dollars.
- MODIFICATION 0002 OF THE FY2020 AWARD IS THE LICENSE PLATE READER MONEY, and the federal record dates it: action date 26 OCTOBER 2020, federal action obligation 277,527.00 dollars. This is an exact match to the figure and the description in the city's 21 December 2020 council packet - independent federal corroboration of the local record, eight weeks earlier.
- The full FY2020 transaction history: base award 9 March 2020, 977,631 dollars; modification 0001, 13 August 2020, +32,200; modification 0002, 26 October 2020, +277,527; modification 0003, 29 July 2021, MINUS 40,270; modification 0004, 20 August 2021, MINUS 4,987.50. Net total obligation 1,242,100.50 dollars, fully outlaid.
- The city's packet gives a 'TOTAL GRANT PROJECT AMOUNT' of 1,287,358 dollars for the same award. The federal record's final obligation is 1,242,100.50 - a difference of 45,257.50 dollars, exactly the sum of the two 2021 deobligations. The packet figure is the award as it stood when the council accepted it; the federal figure is the award as it closed.
- Recipient identity: CITY OF LAS CRUCES, UEI J3ZLWA2K1X47, DUNS 077609279. Place of performance: DONA ANA county, New Mexico, congressional district 02. Awarding and funding office: EOP-OFC OF NATL DRUG CONTROL POLICY, subtier code 1127.
- Non-federal funding on the FY2020 award is 0.00 dollars, matching the packet's 'no match required'.
- FY18 through FY24 awards are recorded as fully outlaid. The FY19 award shows 574,014 dollars outlaid against 999,014 obligated.
- THE SERIES STOPS AT FY2024. No FY2025 or FY2026 ONDCP award to the City of Las Cruces is found in USAspending as of 30 August 2026, although FY2025-numbered ONDCP awards to other New Mexico recipients (for example HID3025G0533 to the Fifth Judicial District Attorney, 287,680 dollars, and HID3025G0460 to Taos Health Systems, 127,000 dollars) are present under a new HID-prefix numbering scheme. NOT FOUND IS NOT DOES NOT EXIST: the city is on its fifteenth year of this money and the likeliest explanation is reporting lag or a renumbered record.
ORIGINAL RESEARCH, 2026-08-30, pulled from the USAspending v2 API: spending_by_award filtered to ONDCP and to the recipient, the award detail endpoint for each generated_internal_id, and the transactions endpoint for the FY2020 award. Every figure above was read from the API response, not from a summary page. WHY THIS MATTERS TO THE DOSSIER: the existing corpus knows about ONE HIDTA document, the December 2020 council item, and treats the 277,527 dollars as an isolated sighting. It is not isolated. It is one modification inside a fifteen-year, roughly 13 million dollar federal funding relationship in which the City of Las Cruces is the fiscal agent, and the council record contains almost none of it. What the federal record still does NOT say is what any of the money bought - USAspending carries obligations, not equipment lists.
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
Across all eleven Metro Narcotics Board of Supervisors agendas the city has published, covering every quarterly meeting from January 2024 through July 2026, no agenda item concerns a license plate reader, a camera, or any surveillance technology - the board's published business is budgets, financial reports, an oral quarterly recap, seized-fund transfers, equipment disposal and, in April 2026, overtime for DEA investigations.
Well supported
The case against thisAn agenda line is a title, not a transcript. 'Recap of Quarterly Activities for Metro' appears at every meeting and is delivered orally by a sergeant; anything at all could be said inside it. Since the city publishes no minutes and no packet for this board, the agendas are the entire published record of what it does, and they are the only thing that can be checked.
1 source
City of Las Cruces · 2026-07-10 · Primary · local:las-cruces
Every Metro Narcotics Board of Supervisors agenda the city has published: quarterly meetings held by Zoom, budgets approved by resolution, equipment disposed of by resolution, and across all eleven agendas not one surveillance item.
- ELEVEN agendas are published, covering meetings on 17 Jan 2024, 17 Apr 2024 (referenced), 17 Jul 2024, 16 Oct 2024, an EMERGENCY meeting 23 Oct 2024, 15 Jan 2025, 16 Apr 2025, 16 Jul 2025, 15 Oct 2025, 21 Jan 2026, 15 Apr 2026 and 15 Jul 2026. Retrieved as the full result set of the city's WordPress agenda archive for the search term 'metro narcotics'.
- The board meets QUARTERLY and by ZOOM WEBINAR.
- BUDGETS, by resolution: Resolution 04-16-252 approved the FY 2025/2026 budget at 819,086 dollars (16 Apr 2025). Resolution 04-15-262 approved the FY 2026/2027 budget at 920,086 dollars (15 Apr 2026) - an increase of 101,000 dollars, 12.3 percent, in one year.
- Resolution 04-15-261 (15 Apr 2026): a 20,000 dollar budget adjustment 'to Increase Overtime for DEA Investigations'. The DEA is not a party to the joint powers agreement but Metro budgets overtime for its investigations.
- Resolution 04-16-251 (16 Apr 2025): 21,794.59 dollars moved in Fund 7420 'to account for and return seized funds to the State of New Mexico'. Fund 7420 is Metro's seized-asset fund and is a different fund from the city's HIDTA fund 7492.
- Resolution 10-16-251 (16 Oct 2024): 25,000 dollars from Metro's fund balance for training/travel, vehicle rentals and overtime. It was carried again at an EMERGENCY meeting a week later, 23 Oct 2024, as the single action item.
- Resolution 07-15-262 (15 Jul 2026): a 25,000 dollar FY2027 adjustment 'to be utilized for cubicles, furniture, possible K9 chemotherapy or the purchase of a new K9'.
- EQUIPMENT DISPOSAL resolutions appear twice: 07-16-251 (16 Jul 2025) and 07-15-261 (15 Jul 2026), each 'authorizing the disposal of obsolete and non-functioning equipment owned by Metro'. Neither agenda lists what the equipment is.
- The standing business every quarter is 'Financial Reports - Finance Department' and 'Recap of Quarterly Activities for Metro - Sgt. Gabriel Arenibas'. The recap is delivered orally; no written recap is attached.
- ACROSS ALL ELEVEN AGENDAS the words license plate, plate reader, ALPR, LPR, Flock, Axon, camera and surveillance do not appear once.
- NO PACKET AND NO MINUTES. Each agenda is a bare list of items with no attachments. Minutes are approved at the following meeting - the agendas prove minutes exist - but the city publishes none of them.
ORIGINAL RESEARCH, 2026-08-30, retrieved through the city's WordPress REST API (lascruces.gov/wp-json/wp/v2/agenda?search=metro%20narcotics) and read in full; all eleven agenda bodies were read, not just titles. The city's WordPress media library returns nothing for 'metro narcotics', so the absence of packets and minutes is an absence in the publishing system, not merely in the page. THE POINT IS NOT THAT THE BOARD HID ANYTHING. It is that a board governing a multi-agency narcotics task force, which sits on 342,808 dollars of HIDTA-funded equipment and approves a 920,086 dollar budget, publishes a one-page agenda per quarter and nothing else - so the only way to learn what Metro buys is the annual audit, which names no individual asset, or a records request.
The Metro Narcotics Board of Supervisors publishes a bare agenda per quarter and nothing else: no packet, no attachment, and no minutes - even though the agendas themselves show minutes are drafted and approved at the following meeting.
Well supported
The case against thisNothing in New Mexico law obliges a body to post packets online, and the audits are published in full through the city's MuniDocs library, so this is a thin practice rather than an unlawful one. The effect is still that the only routinely published account of a task force spending 920,086 dollars a year, holding 342,808 dollars of federal equipment and budgeting overtime for DEA investigations is a one-page list of item titles.
2 sources
City of Las Cruces · 2026-07-10 · Primary · local:las-cruces
Every Metro Narcotics Board of Supervisors agenda the city has published: quarterly meetings held by Zoom, budgets approved by resolution, equipment disposed of by resolution, and across all eleven agendas not one surveillance item.
- ELEVEN agendas are published, covering meetings on 17 Jan 2024, 17 Apr 2024 (referenced), 17 Jul 2024, 16 Oct 2024, an EMERGENCY meeting 23 Oct 2024, 15 Jan 2025, 16 Apr 2025, 16 Jul 2025, 15 Oct 2025, 21 Jan 2026, 15 Apr 2026 and 15 Jul 2026. Retrieved as the full result set of the city's WordPress agenda archive for the search term 'metro narcotics'.
- The board meets QUARTERLY and by ZOOM WEBINAR.
- BUDGETS, by resolution: Resolution 04-16-252 approved the FY 2025/2026 budget at 819,086 dollars (16 Apr 2025). Resolution 04-15-262 approved the FY 2026/2027 budget at 920,086 dollars (15 Apr 2026) - an increase of 101,000 dollars, 12.3 percent, in one year.
- Resolution 04-15-261 (15 Apr 2026): a 20,000 dollar budget adjustment 'to Increase Overtime for DEA Investigations'. The DEA is not a party to the joint powers agreement but Metro budgets overtime for its investigations.
- Resolution 04-16-251 (16 Apr 2025): 21,794.59 dollars moved in Fund 7420 'to account for and return seized funds to the State of New Mexico'. Fund 7420 is Metro's seized-asset fund and is a different fund from the city's HIDTA fund 7492.
- Resolution 10-16-251 (16 Oct 2024): 25,000 dollars from Metro's fund balance for training/travel, vehicle rentals and overtime. It was carried again at an EMERGENCY meeting a week later, 23 Oct 2024, as the single action item.
- Resolution 07-15-262 (15 Jul 2026): a 25,000 dollar FY2027 adjustment 'to be utilized for cubicles, furniture, possible K9 chemotherapy or the purchase of a new K9'.
- EQUIPMENT DISPOSAL resolutions appear twice: 07-16-251 (16 Jul 2025) and 07-15-261 (15 Jul 2026), each 'authorizing the disposal of obsolete and non-functioning equipment owned by Metro'. Neither agenda lists what the equipment is.
- The standing business every quarter is 'Financial Reports - Finance Department' and 'Recap of Quarterly Activities for Metro - Sgt. Gabriel Arenibas'. The recap is delivered orally; no written recap is attached.
- ACROSS ALL ELEVEN AGENDAS the words license plate, plate reader, ALPR, LPR, Flock, Axon, camera and surveillance do not appear once.
- NO PACKET AND NO MINUTES. Each agenda is a bare list of items with no attachments. Minutes are approved at the following meeting - the agendas prove minutes exist - but the city publishes none of them.
ORIGINAL RESEARCH, 2026-08-30, retrieved through the city's WordPress REST API (lascruces.gov/wp-json/wp/v2/agenda?search=metro%20narcotics) and read in full; all eleven agenda bodies were read, not just titles. The city's WordPress media library returns nothing for 'metro narcotics', so the absence of packets and minutes is an absence in the publishing system, not merely in the page. THE POINT IS NOT THAT THE BOARD HID ANYTHING. It is that a board governing a multi-agency narcotics task force, which sits on 342,808 dollars of HIDTA-funded equipment and approves a 920,086 dollar budget, publishes a one-page agenda per quarter and nothing else - so the only way to learn what Metro buys is the annual audit, which names no individual asset, or a records request.
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
The FBI is a funding party to Metro Narcotics through a joint powers agreement running since 1 October 2017 with a 30,000 dollar project amount, and its 11,054 dollar fiscal 2025 contribution is the entirety of Metro's operating-grant revenue for the year.
Well supported
The case against this11,054 dollars against a 720,484 dollar budget is one and a half per cent of Metro's money, so this is not federal capture of a local task force. It does mean the federal footprint in Metro's governance is wider than the ONDCP grant alone: an FBI JPA in the audit, DEA overtime in the April 2026 board resolution, and HSI on the HIDTA roster.
1 source
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
The 'HIDTA regional office' the City of Las Cruces says it is fiscal agent for is headquartered in Las Cruces, at 555 South Telshor Suite 200, and it coordinates 43 named federal, state and local agencies across 17 New Mexico counties - so money that passes through the Las Cruces budget can lawfully buy equipment used anywhere in that footprint.
Well supported
The case against thisThe 2020 packet already says the city is fiscal agent for the regional office; locating that office in Las Cruces does not make the money municipal. If anything it sharpens the existing finding that the license plate reader project need not have bought a single Las Cruces camera - the buyer, the banker and the beneficiary can all sit in the same city and still be three different bodies.
3 sources
New Mexico High Intensity Drug Trafficking Area (nmhidta.org) · 2026-08-30 · Primary · NM
The regional office the City of Las Cruces is fiscal agent for, in its own words - headquartered in Las Cruces, with a named roster of federal, state and local member agencies.
- NM HIDTA HEADQUARTERS IS IN LAS CRUCES: 555 South Telshor, Suite 200, Las Cruces NM 88011, phone 575-541-7501. This is the 'HIDTA regional office' the city's 2020 council packet says it acts as fiscal agent for.
- Quoted: the New Mexico HIDTA 'was initially part of the Southwest Border HIDTA, one of the original five HIDTAs created by Congress in 1990, becoming its own separate HIDTA in 2016.' It covers 17 designated counties.
- Mission, quoted: 'To reduce drug availability by supporting multi-agency task forces and facilitating intelligence-driven interdiction and investigation.'
- FEDERAL PARTICIPATING AGENCIES, as listed: Bureau of Alcohol, Tobacco, Firearms and Explosives; Bureau of Indian Affairs; U.S. Border Patrol; Drug Enforcement Administration; Federal Bureau of Investigation; Internal Revenue Service; United States Marshal Service; United States Attorney's Office; Homeland Security Investigations.
- STATE: NM National Guard; NM Department of Public Safety; NM State Police; and the First, Second, Third, Fifth, Sixth, Eleventh and Twelfth Judicial District Attorney's Offices.
- LOCAL, thirty agencies, including LAS CRUCES POLICE DEPARTMENT and DONA ANA COUNTY SHERIFF'S OFFICE, plus Alamogordo PD, Albuquerque PD, Artesia PD, Bernalillo County SO, Bloomfield PD, Carlsbad PD, Chaves County SO, Eddy County SO, Farmington PD, Grant County SO, Lea County SO, Lincoln County SO, Lordsburg PD, Luna County SO, Lovington PD, Otero County SO, Rio Arriba County SO, Rio Rancho PD, Ruidoso Downs PD, Sandoval County SO, San Juan County SO, Santa Fe PD, Santa Fe County SO, Silver City PD, Taos PD, Torrance County SO, Valencia County SO and Western New Mexico University PD.
- ICE IS NOT ON THIS LIST. Homeland Security Investigations is. The ISC page of the same site lists Immigration and Customs Enforcement separately - see the ISC source.
- Stated 2023 figures: 2,630 cases opened; 5,276 drug cases analyzed by NM forensic labs; 22,232 hours of training provided. The 'Participating Agencies' count on the same list renders as '**' rather than a number.
- The site records NM HIDTA as ONDCP's 'Outstanding HIDTA of the Year' for 2024.
Retrieved 2026-08-30 and read in full. This is the HIDTA describing itself, so it is a government source rather than a vendor claim, but the operational numbers on it are self-reported and carry no methodology. What matters here is structural and checkable: the office the city banks for is a Las Cruces office, and the agency roster is the list of bodies that can be in the room when Metro Narcotics or any other New Mexico task force shares information.
City of Las Cruces · 2020-12-21 · Primary · local:las-cruces
The first time 'License Plate Reader' reaches the Las Cruces council record - not as a Flock item, but as one of three projects inside a federal narcotics grant the city accepts as fiscal agent for a regional office.
- Grant Acceptance Summary, council meeting date 12/21/2020, Attachment C: Grant Title FFY21 High Intensity Drug Trafficking Areas (HIDTA) Modification 2.
- Department: Metro Narcotics - HIDTA. Grant/Agreement number G20SN0006A. Grant Type: Federal Operating. Granting Agency: Office of National Drug Control Policy.
- Grant Amount 277,527.00 dollars; cash match 0; TOTAL GRANT PROJECT AMOUNT 1,287,358.00 dollars. Grant period 01/01/2020 to 12/31/2021.
- Use of funds, quoted: Modification 2 for the 2020 grant agreement provides a 277,527 dollar increase in funds for Metro Narcotics' investigation and interdiction expenses, INCLUDING THE LICENSE PLATE READER, MONEY SERIALIZATION, AND OVERDOSE RESPONSE PROJECTS. There is no match required for this modification.
- Quoted: The City of Las Cruces acts as the Fiscal Agent for the HIDTA regional office.
- The item sits at pages 26-27 of a 664-page packet, inside a routine grant acceptance summary listing several unrelated grants.
- A related 16 November 2020 item adjusts the HIDTA-CLC fund (7492) by 18,022.66 dollars to actuals, against total HIDTA expenditures of 1,148,516.66 dollars - fiscal-agent accounting, not an LPR authorization.
- READ FROM THE ARCHIVED DOCUMENT (22330), which is the same 664-page packet: the grant acceptance summary is the ONLY ALPR content in it. The ONDCP grant agreement itself is NOT attached, so what the License Plate Reader project actually purchased cannot be read from the council record.
- THE FUND TABLE ANSWERS WHERE THE MONEY WENT. Fund 7492 HIDTA-CLC, FY2020-21, Exhibit A at page 12: Federal Grants revenue 1,059,024 original, 1,158,970 amended, plus the 277,527 adjustment, giving 1,436,497 adjusted.
- On the expenditure side of that same table EVERY city department line is ZERO - General Government, Legislative, Municipal Court, City Manager, Legal, LAS CRUCES POLICE DEPARTMENT, Fire, Utilities, Economic Development and the rest all read 0 0 0 0. The only non-zero expenditure line is HIDTA itself: 432,909 original, 474,525 amended, plus 277,527, giving 752,052.
- EXACT PAGE LOCATORS FOR THE DATA ERROR: the 511,035.12 figure is on page 26 (Attachment B, Cinematic Infrastructure Reauthorization, Economic Development, agreement 20-E4039). The HIDTA grant is on page 27 (Attachment C, 277,527, Metro Narcotics, agreement G20SN0006A).
ORIGINAL RESEARCH, 2026-08-30, from the city's own 664-page packet. THIS IS THE EARLIEST COUNCIL SIGHT OF THE TECHNOLOGY - more than a year before Las Cruces began operating Flock readers in January 2022 - and it changes the shape of the local story in two ways. First, the council DID see the words License Plate Reader, so the record is not silent from the beginning; it saw them once, as one of three line items in a federal narcotics grant. Second, this is REGIONAL money: the city is fiscal agent for a HIDTA regional office, so LPR funds passing through the Las Cruces budget need not have bought Las Cruces cameras at all. Do not assume they did. What the grant actually purchased, and for whom, is the open question. READ FROM THE ARCHIVE 2026-08-30 after the document endpoint was fixed. THE BUDGET TABLE SETTLES THE REGIONAL QUESTION: the entire HIDTA fund, including the 277,527 that carries the License Plate Reader project, is booked to a HIDTA expenditure line while the Las Cruces Police Department line reads zero across all four columns. This money is not LCPD budget. That does not prove no Las Cruces officer benefited - Metro Narcotics is a multi-agency task force with LCPD personnel in it, and equipment bought by a regional office can be used locally - but the funds do not flow to the police department in the city's own accounting. What the LPR project bought still requires the ONDCP grant file, which is not in the packet.
USAspending.gov (U.S. Department of the Treasury) · 2026-08-30 · Primary · local:las-cruces
The federal side of the grant the Las Cruces council saw once in December 2020 - eleven consecutive annual awards, and a modification record that dates the license plate reader money to the day.
- ELEVEN CONSECUTIVE ANNUAL AWARDS to CITY OF LAS CRUCES from the Office of National Drug Control Policy, Executive Office of the President, award numbers G14SN0006A through G24SN0006A, each a two-calendar-year performance period: FY14 803,673.57; FY15 1,470,894; FY16 1,456,881; FY17 1,424,654.31; FY18 925,605.97; FY19 999,014; FY20 1,242,100.50; FY21 1,259,792; FY22 1,359,950; FY23 1,068,696; FY24 903,130 dollars. Eleven awards totalling 12,914,390.35 dollars.
- MODIFICATION 0002 OF THE FY2020 AWARD IS THE LICENSE PLATE READER MONEY, and the federal record dates it: action date 26 OCTOBER 2020, federal action obligation 277,527.00 dollars. This is an exact match to the figure and the description in the city's 21 December 2020 council packet - independent federal corroboration of the local record, eight weeks earlier.
- The full FY2020 transaction history: base award 9 March 2020, 977,631 dollars; modification 0001, 13 August 2020, +32,200; modification 0002, 26 October 2020, +277,527; modification 0003, 29 July 2021, MINUS 40,270; modification 0004, 20 August 2021, MINUS 4,987.50. Net total obligation 1,242,100.50 dollars, fully outlaid.
- The city's packet gives a 'TOTAL GRANT PROJECT AMOUNT' of 1,287,358 dollars for the same award. The federal record's final obligation is 1,242,100.50 - a difference of 45,257.50 dollars, exactly the sum of the two 2021 deobligations. The packet figure is the award as it stood when the council accepted it; the federal figure is the award as it closed.
- Recipient identity: CITY OF LAS CRUCES, UEI J3ZLWA2K1X47, DUNS 077609279. Place of performance: DONA ANA county, New Mexico, congressional district 02. Awarding and funding office: EOP-OFC OF NATL DRUG CONTROL POLICY, subtier code 1127.
- Non-federal funding on the FY2020 award is 0.00 dollars, matching the packet's 'no match required'.
- FY18 through FY24 awards are recorded as fully outlaid. The FY19 award shows 574,014 dollars outlaid against 999,014 obligated.
- THE SERIES STOPS AT FY2024. No FY2025 or FY2026 ONDCP award to the City of Las Cruces is found in USAspending as of 30 August 2026, although FY2025-numbered ONDCP awards to other New Mexico recipients (for example HID3025G0533 to the Fifth Judicial District Attorney, 287,680 dollars, and HID3025G0460 to Taos Health Systems, 127,000 dollars) are present under a new HID-prefix numbering scheme. NOT FOUND IS NOT DOES NOT EXIST: the city is on its fifteenth year of this money and the likeliest explanation is reporting lag or a renumbered record.
ORIGINAL RESEARCH, 2026-08-30, pulled from the USAspending v2 API: spending_by_award filtered to ONDCP and to the recipient, the award detail endpoint for each generated_internal_id, and the transactions endpoint for the FY2020 award. Every figure above was read from the API response, not from a summary page. WHY THIS MATTERS TO THE DOSSIER: the existing corpus knows about ONE HIDTA document, the December 2020 council item, and treats the 277,527 dollars as an isolated sighting. It is not isolated. It is one modification inside a fifteen-year, roughly 13 million dollar federal funding relationship in which the City of Las Cruces is the fiscal agent, and the council record contains almost none of it. What the federal record still does NOT say is what any of the money bought - USAspending carries obligations, not equipment lists.
A vehicle is an explicitly indexable target in the New Mexico Investigative Support Center's Case Explorer system, which every New Mexico HIDTA participating agency is required to use for event deconfliction and which cross-matches to RISSafe, SafetyNET and the National Virtual Pointer System - a national-reach index run from the same Las Cruces office the city banks for.
Well supported
The case against thisDeconfliction is not surveillance and the ISC's own description sets real limits: a target match returns only agency contact information and what specifically matched, case contents stay with the entering agency, and target deconfliction is encouraged rather than mandatory. But those limits are the operator's account of its own system, published without an audit, and a plate entered as a target still becomes a queryable national index entry.
2 sources
New Mexico High Intensity Drug Trafficking Area (nmhidta.org/isc) · 2026-08-30 · Primary · NM
The intelligence layer under the task forces: a mandatory deconfliction system that indexes vehicles as targets, wired to three national pointer systems, run from the same Las Cruces office - with a phone-extraction request desk and ICE on the partner list.
- The NMISC's stated mission is 'to promote and facilitate the sharing and coordination of criminal intelligence throughout the Southwest Border and the nation', providing 'investigative case support, event and target deconfliction and the development of strategic intelligence products'.
- DECONFLICTION IS MANDATORY, quoted: 'All new Mexico HIDTA participating agencies are required to deconflict all events through Case Explorer'. Target deconfliction is 'encouraged' rather than required.
- CASE EXPLORER DECONFLICTS OUTWARD to three national systems: 'Case Explorer will deconflict Events within the Case Explorer system, and with RISSafe, SafetyNET and NVPS (National Virtual Pointer System).' Target matching runs 'within the Case Explorer system and NVPS only'.
- A TARGET IS EXPLICITLY A VEHICLE AMONG OTHER THINGS, quoted: 'enters a Target (Person, address, phone number, vehicle, etc.)'. A plate or a vehicle entered as a target is matched against every other participating agency's targets.
- The site's own limiting description: a match returns 'only contact information for each agency' and what specifically matched; 'A person cannot go fishing in the system to see if other agencies are investigating a target'. Case Management contents are stated to be visible only to the entering agency.
- FEDERAL PARTNERS LISTED ON THE ISC PAGE: ATF; Bureau of Indian Affairs; BUREAU OF LAND MANAGEMENT; U.S. Border Patrol; DEA; FBI; IMMIGRATION AND CUSTOMS ENFORCEMENT; UNITED STATES FISH AND WILDLIFE SERVICE; IRS; U.S. Marshals Service; U.S. Attorney's Office.
- ICE, BLM AND FISH AND WILDLIFE APPEAR ON THE ISC PARTNER LIST BUT NOT ON THE HIDTA PARTICIPATING-AGENCY LIST on the same website.
- DEVICE EXTRACTION. The page's Important Links are three 2025 'Device Extraction and Analysis Request Form' links - Albuquerque DEX Form 2025, LAS CRUCES DEX FORM 2025, and Roswell DEX Form 2025 - each an external Smartsheet form. Mobile-device extraction is a service the ISC takes requests for from a Las Cruces desk.
- Quoted, and unspecific: 'The ISC supports law enforcement investigations using multiple proprietary and open source tools.' No tool is named anywhere on the page.
Retrieved 2026-08-30 and read in full. THIS IS THE CLOSEST THING FOUND TO A LOCAL ANSWER ON THE NON-ALPR SURVEILLANCE SURFACES, and it is thin by design: the ISC advertises device extraction and unnamed proprietary tools, and names neither. Nothing on the page mentions license plate readers, Bluetooth, cell-site simulators or location data. The deconfliction description is the ISC's own account of its safeguards and should be rendered as such - it is a description of a system, not an audit of one. The value of the page to this dossier is that it establishes, from the program's own publication, that a vehicle is an indexable target in a Las Cruces-run system that reaches RISS, SafetyNET and the National Virtual Pointer System, and that ICE is a listed partner of that center.
New Mexico High Intensity Drug Trafficking Area (nmhidta.org) · 2026-08-30 · Primary · NM
The regional office the City of Las Cruces is fiscal agent for, in its own words - headquartered in Las Cruces, with a named roster of federal, state and local member agencies.
- NM HIDTA HEADQUARTERS IS IN LAS CRUCES: 555 South Telshor, Suite 200, Las Cruces NM 88011, phone 575-541-7501. This is the 'HIDTA regional office' the city's 2020 council packet says it acts as fiscal agent for.
- Quoted: the New Mexico HIDTA 'was initially part of the Southwest Border HIDTA, one of the original five HIDTAs created by Congress in 1990, becoming its own separate HIDTA in 2016.' It covers 17 designated counties.
- Mission, quoted: 'To reduce drug availability by supporting multi-agency task forces and facilitating intelligence-driven interdiction and investigation.'
- FEDERAL PARTICIPATING AGENCIES, as listed: Bureau of Alcohol, Tobacco, Firearms and Explosives; Bureau of Indian Affairs; U.S. Border Patrol; Drug Enforcement Administration; Federal Bureau of Investigation; Internal Revenue Service; United States Marshal Service; United States Attorney's Office; Homeland Security Investigations.
- STATE: NM National Guard; NM Department of Public Safety; NM State Police; and the First, Second, Third, Fifth, Sixth, Eleventh and Twelfth Judicial District Attorney's Offices.
- LOCAL, thirty agencies, including LAS CRUCES POLICE DEPARTMENT and DONA ANA COUNTY SHERIFF'S OFFICE, plus Alamogordo PD, Albuquerque PD, Artesia PD, Bernalillo County SO, Bloomfield PD, Carlsbad PD, Chaves County SO, Eddy County SO, Farmington PD, Grant County SO, Lea County SO, Lincoln County SO, Lordsburg PD, Luna County SO, Lovington PD, Otero County SO, Rio Arriba County SO, Rio Rancho PD, Ruidoso Downs PD, Sandoval County SO, San Juan County SO, Santa Fe PD, Santa Fe County SO, Silver City PD, Taos PD, Torrance County SO, Valencia County SO and Western New Mexico University PD.
- ICE IS NOT ON THIS LIST. Homeland Security Investigations is. The ISC page of the same site lists Immigration and Customs Enforcement separately - see the ISC source.
- Stated 2023 figures: 2,630 cases opened; 5,276 drug cases analyzed by NM forensic labs; 22,232 hours of training provided. The 'Participating Agencies' count on the same list renders as '**' rather than a number.
- The site records NM HIDTA as ONDCP's 'Outstanding HIDTA of the Year' for 2024.
Retrieved 2026-08-30 and read in full. This is the HIDTA describing itself, so it is a government source rather than a vendor claim, but the operational numbers on it are self-reported and carry no methodology. What matters here is structural and checkable: the office the city banks for is a Las Cruces office, and the agency roster is the list of bodies that can be in the room when Metro Narcotics or any other New Mexico task force shares information.
A drug task force or a HIDTA can hold organization-level rights on the Flock network without owning cameras: 'Indiana HIDTA' and 'Midwest HIDTA' appear as sharing partners in the transparency portals of small departments in other states, alongside dozens of named narcotics task forces, and two New Mexico HIDTA member agencies - Bloomfield PD and Lea County SO - already appear as out-of-state sharing partners in the same sample.
Well supported
The case against thisThis says what is possible and what neighbors do; it says nothing about Metro Narcotics or New Mexico HIDTA, neither of which appears in the sample. The sample is 51 portals with no New Mexico portal in it. And the direct test cannot be run yet: as of 18 August 2026 Las Cruces PD was still 'working on a transparency portal provided by Flock', neither LCPD nor Dona Ana County SO links one from its own site, and the sharing lists that would settle the question are therefore not published anywhere.
2 sources
Flock Safety transparency portals, indexed by this project via eyesonflock.com · 2026-08-10 · Primary · national
A structural fact with direct local bearing: a HIDTA can hold data-sharing rights on the Flock network as an organization in its own right, alongside dozens of named drug task forces.
- In the project's index of 51 Flock transparency portals (fetched 10 August 2026), 'Indiana HIDTA' appears in the organizations-shared-with list of 5 separate portals and 'Midwest HIDTA' of 4. A HIDTA IS AN ORGANIZATION ON THE NETWORK, not merely a funding label.
- Named narcotics TASK FORCES appear the same way and widely: Chatham-Savannah Counter Narcotics Team (17 portals), Bowling Green Warren County Drug Task Force KY (13), Kleberg TX County Attorney's Task Force (11), Marshall County Drug Task Force WV (11), SEMO Drug Task Force MO (10), Alabama Drug Enforcement Task Force Region G (8), Mineral Area Drug Task Force MO (8), 18th Judicial District Drug Task Force TN (7), OH U.S.23 Major Crimes Task Force (9), and others. A multi-agency task force with no cameras of its own routinely holds query rights on other agencies' cameras.
- NEW MEXICO AGENCIES ALREADY APPEAR IN THIS SAMPLE as sharing partners of small out-of-state departments: Bloomfield NM PD (9 portals), Clovis NM PD (12), Las Vegas NM PD (12), Lea County NM SO (12), Capitan NM PD (1).
- BLOOMFIELD PD AND LEA COUNTY SO ARE BOTH ON THE NM HIDTA PARTICIPATING-AGENCY ROSTER. Two agencies that share Flock data with departments in Arkansas, Iowa, South Carolina and Georgia are also New Mexico HIDTA member agencies.
- No Las Cruces, Dona Ana County, New Mexico HIDTA or Metro Narcotics organization appears anywhere in this 51-portal sample - which is a sample of 51 portals, not of the network.
- The 50 per-agency search-audit CSVs in the same corpus record searches as id, userId, searchDate, networkCount and offenseType only. THEY CARRY NO REQUESTING-ORGANIZATION NAME, so they cannot be used to show which agency ran a search.
- THE DIRECT LOCAL TEST CANNOT BE RUN, BECAUSE THE LOCAL PORTAL DOES NOT APPEAR TO EXIST YET. Organ Mountain News reported on 18 August 2026 that 'LCPD is working on a transparency portal provided by Flock' and that Councilor Bencomo urged the department to launch it - so as of that date Las Cruces had no published Flock transparency page carrying sharing lists. A site-wide search of lascruces.gov returns exactly one hit for 'flock' and it is an unrelated parks item; the LCPD Transparency page is a weekly arrest blotter and links no portal. A search of donaana.gov returns no Flock content at all.
ORIGINAL RESEARCH, 2026-08-30, computed over api/seed_data/flock/portal_index.json (51 portals, fetched 2026-08-10) and the 50 audit CSVs beside it, cross-referenced by hand against the NM HIDTA participating-agency roster. THE INFERENCE THIS SUPPORTS AND ITS LIMIT. It supports: a HIDTA or a drug task force can be a first-class organization on the Flock network with query rights it did not buy cameras to earn. It does NOT support: any statement that New Mexico HIDTA or Metro Narcotics holds such rights. The 51-portal index is a small, geographically skewed sample and contains no New Mexico portal at all. The direct test would be Las Cruces PD's and Dona Ana County SO's own transparency portals and their sharing lists. GUESSED SLUGS AT transparency.flocksafety.com RETURNED HTTP 403 ON 2026-08-30, BUT SO DID A DELIBERATELY NONSENSE SLUG, so those responses are blanket bot-blocking and are evidence of nothing. Neither agency publishes a portal link on its own website, and reporting from 18 August 2026 has the Las Cruces portal still unlaunched. Treat the local portal as NOT YET PUBLISHED rather than as unread. The URL given is the independent aggregator the portal index was fetched from.
New Mexico High Intensity Drug Trafficking Area (nmhidta.org) · 2026-08-30 · Primary · NM
The regional office the City of Las Cruces is fiscal agent for, in its own words - headquartered in Las Cruces, with a named roster of federal, state and local member agencies.
- NM HIDTA HEADQUARTERS IS IN LAS CRUCES: 555 South Telshor, Suite 200, Las Cruces NM 88011, phone 575-541-7501. This is the 'HIDTA regional office' the city's 2020 council packet says it acts as fiscal agent for.
- Quoted: the New Mexico HIDTA 'was initially part of the Southwest Border HIDTA, one of the original five HIDTAs created by Congress in 1990, becoming its own separate HIDTA in 2016.' It covers 17 designated counties.
- Mission, quoted: 'To reduce drug availability by supporting multi-agency task forces and facilitating intelligence-driven interdiction and investigation.'
- FEDERAL PARTICIPATING AGENCIES, as listed: Bureau of Alcohol, Tobacco, Firearms and Explosives; Bureau of Indian Affairs; U.S. Border Patrol; Drug Enforcement Administration; Federal Bureau of Investigation; Internal Revenue Service; United States Marshal Service; United States Attorney's Office; Homeland Security Investigations.
- STATE: NM National Guard; NM Department of Public Safety; NM State Police; and the First, Second, Third, Fifth, Sixth, Eleventh and Twelfth Judicial District Attorney's Offices.
- LOCAL, thirty agencies, including LAS CRUCES POLICE DEPARTMENT and DONA ANA COUNTY SHERIFF'S OFFICE, plus Alamogordo PD, Albuquerque PD, Artesia PD, Bernalillo County SO, Bloomfield PD, Carlsbad PD, Chaves County SO, Eddy County SO, Farmington PD, Grant County SO, Lea County SO, Lincoln County SO, Lordsburg PD, Luna County SO, Lovington PD, Otero County SO, Rio Arriba County SO, Rio Rancho PD, Ruidoso Downs PD, Sandoval County SO, San Juan County SO, Santa Fe PD, Santa Fe County SO, Silver City PD, Taos PD, Torrance County SO, Valencia County SO and Western New Mexico University PD.
- ICE IS NOT ON THIS LIST. Homeland Security Investigations is. The ISC page of the same site lists Immigration and Customs Enforcement separately - see the ISC source.
- Stated 2023 figures: 2,630 cases opened; 5,276 drug cases analyzed by NM forensic labs; 22,232 hours of training provided. The 'Participating Agencies' count on the same list renders as '**' rather than a number.
- The site records NM HIDTA as ONDCP's 'Outstanding HIDTA of the Year' for 2024.
Retrieved 2026-08-30 and read in full. This is the HIDTA describing itself, so it is a government source rather than a vendor claim, but the operational numbers on it are self-reported and carry no methodology. What matters here is structural and checkable: the office the city banks for is a Las Cruces office, and the agency roster is the list of bodies that can be in the room when Metro Narcotics or any other New Mexico task force shares information.
Whether Metro Narcotics uses any surveillance technology of its own cannot be answered from the published record: four annual audits, eleven board agendas, the LCPD unit page, the federal award record, the CourtListener opinion database and the ALPR corpus together name not one plate reader, camera, tracker, cell-site simulator or Bluetooth device in Metro's hands.
Well supported
The case against thisA gap is not a finding of absence, and the shape of this gap is informative: the one federal modification that names a License Plate Reader project is on Metro's own grant, and Metro's balance sheet carries a HIDTA equipment line. The unread surfaces that would settle it are the Metro equipment inventory, the ONDCP grant file, the Metro board minutes, and the Metro Narcotics ALPR policy - or a statement that none exists. The local Flock transparency portals are not on that list: as of 18 August 2026 Las Cruces PD had not launched one and Dona Ana County SO publishes none.
5 sources
Perfect World Project, original research · 2026-08-30 · Primary · local:las-cruces
A negative result, recorded so it is not searched for twice: nothing in the published record names a cell-site simulator, a Bluetooth tracker, a GPS tracker or a pole camera in Metro Narcotics' hands.
- CourtListener opinion search for '"Metro Narcotics" Las Cruces' returns 7 opinions, of which one is a District of New Mexico case, United States v. Ibarra-Sandoval (26 September 2017). The other six are New Mexico Court of Appeals, New Mexico Supreme Court and Tenth Circuit decisions from 1979 to 2005. NONE WAS READ IN FULL - the CourtListener text endpoint returned empty bodies for this project on 2026-08-30.
- A CourtListener search for '"Metro Narcotics" "license plate"' returns 30 opinions, all of them Tennessee, Fifth Circuit or other out-of-state matters involving differently named Metro Narcotics units. None is a New Mexico case.
- Search for '"Metro Narcotics Agency" tracker' returns zero opinions.
- Web searches for Metro Narcotics with cell-site simulator, stingray, GPS tracker and suppression-motion terms return only national explainer material and no Las Cruces matter.
- The four published Metro Narcotics audits (FY2022 to FY2025) contain no instance of tracker, Bluetooth, GPS, camera or surveillance.
- The eleven published Metro Narcotics Board agendas (2024 to 2026) contain no surveillance item of any kind.
- The only device-level capability found anywhere in the local HIDTA structure is the New Mexico Investigative Support Center's Las Cruces Device Extraction and Analysis request desk - see the ISC source. It is mobile-device forensics, which is a different surface from live location tracking.
ORIGINAL RESEARCH, 2026-08-30. THIS IS A GAP RECORD AND MUST BE RENDERED AS ONE: it says these searches did not find the record, and says nothing about whether the technology exists or is used. Opinion databases only reach matters that produced a written opinion, which is a small fraction of drug prosecutions and skews to appeals; a suppression fight settled at the district-court docket level never appears. The unsearched surfaces that would actually answer this are the New Mexico Third Judicial District Court docket, the D.N.M. PACER docket, and the Metro Narcotics equipment inventory - none of which was reached in this pass. The corpus had no Bluetooth, cell-site or covert-tracking content before this record and still has none; what it now has is a written account of where that hole was looked for. The URL given is the one District of New Mexico opinion the search surfaced; the CourtListener search page itself refuses automated fetches.
Metro Narcotics Agency / State of New Mexico Office of the State Auditor · 2025-11-17 · Primary · local:las-cruces
The one document that says what Metro Narcotics is, who governs it, who pays for it and what it owns - including a capital-asset table with a separate line for HIDTA-funded equipment.
- WHAT METRO IS, quoted: 'Metro Narcotics Agency (Metro) is an organization formed by a joint powers agreement (JPA) between the City of Las Cruces, the County of Dona Ana, and the New Mexico State Police Department.'
- GOVERNANCE, quoted: 'The Agency is governed by an eight-member board comprised of members from the City of Las Cruces, Dona Ana County, the District Attorney's Office, and the New Mexico State Police.' The District Attorney's Office is a fourth constituency on the board but not a party to the JPA as described in the same note.
- Quoted: 'The City of Las Cruces is the fiscal agent for Metro and accounts for its resources as agency funds.'
- OFFICIAL ROSTER at 30 June 2025, none of whom are employed by Metro: Jeremy Story (Chairman), Scott McFaul (Vice Chairman), Eric Enriquez, Ikani Taumoepeau, Kim Stewart, Scott Andrews, Susana Chaparro, Fernando Macias.
- CAPITAL ASSETS - THE HIDTA LINE. The equipment table breaks Metro's equipment into three funding origins: Metro equipment 527,054 dollars (2025) against 448,548 (2024); SEIZED EQUIPMENT 741,560 dollars, unchanged; HIDTA EQUIPMENT 342,808 dollars, unchanged; retirements (229,470); total equipment 1,381,952 dollars against 1,303,446; accumulated depreciation (1,221,637); capital assets net 160,315 dollars.
- The whole of fiscal 2025's 78,506 dollars of additions therefore landed on the Metro equipment line. THE HIDTA EQUIPMENT LINE DID NOT MOVE.
- NO ASSET IS NAMED ANYWHERE IN THE AUDIT. The words license plate, plate reader, ALPR, LPR, Flock, Axon, camera, surveillance, tracker, Bluetooth and GPS do not appear in the document at all.
- REVENUE, year ended 30 June 2025: operating grants 11,054 dollars; charges for services 325,543; investment income 35,025; other revenues 348,862; total 720,484 dollars. Expenditures 587,714 dollars, of which capital outlay 78,506. Fund balance ended at 908,869 dollars.
- Depreciation for the year was 96,855 dollars, charged to law enforcement activities. Depreciation exceeded additions, so Metro's net capital assets FELL from 178,664 to 160,315 dollars.
- SCHEDULE OF JOINT POWERS AGREEMENTS names three, all with the City of Las Cruces as audit-responsible party: City of Las Cruces, from 1 October 2001, perpetual, 325,543 dollars contributed in the year; Dona Ana County, from 1 October 2001, perpetual, 325,543 dollars; and the FEDERAL BUREAU OF INVESTIGATION, from 1 OCTOBER 2017, perpetual, project amount 30,000 dollars, 11,054 dollars contributed in the year.
- The FBI agreement's stated purpose is quoted as: 'Investigate/Prosecute avenues by which to convict and incarcerate dangerous offenders'. The 11,054 dollars it paid is the entire 'operating grants' revenue line.
- NOTE 3: 'Metro receives funding from several governmental agencies including Federal Bureau of Investigation, The County of Dona Ana, and the City of Las Cruces.' Due from federal at year end: 27,129 dollars.
- NOTE 6 describes a fund for 'the disposition of all seized property, including illegal narcotics, as well as to account for all federal or state reimbursements for services rendered, commonly referred to as seized asset funds'. It also states the City and County fund Metro's operating expenses 'proportionate to their respective share of the task force, which is the total number of law enforcement agencies assigned to Metro for each fiscal year', and that 'The number of participating agencies in the task force can vary from year to year.'
- NO ONDCP OR HIDTA GRANT REVENUE APPEARS IN METRO'S OPERATING STATEMENTS. The only grant revenue is the FBI's 11,054 dollars.
Retrieved 2026-08-30 from the City of Las Cruces MuniDocs library (Audits > JPA Audits > Metro), 41 pages, downloaded and text-extracted. Read: the official roster, the management discussion and analysis, the statement of activities, the budgetary comparison, Notes 1 through 7, the Schedule of Joint Powers Agreements and the compliance section. THIS AUDIT IS THE PIVOT OF THE WHOLE HIDTA QUESTION. It proves Metro holds 342,808 dollars of HIDTA-funded equipment at historical cost, and it names none of it. It also shows that the ONDCP money the city receives as fiscal agent does not pass through Metro's audited operating statements at all - so a reader auditing Metro's books would never see the roughly 900,000 dollars a year of federal HIDTA funding described in the city's own council packets.
City of Las Cruces · 2026-07-10 · Primary · local:las-cruces
Every Metro Narcotics Board of Supervisors agenda the city has published: quarterly meetings held by Zoom, budgets approved by resolution, equipment disposed of by resolution, and across all eleven agendas not one surveillance item.
- ELEVEN agendas are published, covering meetings on 17 Jan 2024, 17 Apr 2024 (referenced), 17 Jul 2024, 16 Oct 2024, an EMERGENCY meeting 23 Oct 2024, 15 Jan 2025, 16 Apr 2025, 16 Jul 2025, 15 Oct 2025, 21 Jan 2026, 15 Apr 2026 and 15 Jul 2026. Retrieved as the full result set of the city's WordPress agenda archive for the search term 'metro narcotics'.
- The board meets QUARTERLY and by ZOOM WEBINAR.
- BUDGETS, by resolution: Resolution 04-16-252 approved the FY 2025/2026 budget at 819,086 dollars (16 Apr 2025). Resolution 04-15-262 approved the FY 2026/2027 budget at 920,086 dollars (15 Apr 2026) - an increase of 101,000 dollars, 12.3 percent, in one year.
- Resolution 04-15-261 (15 Apr 2026): a 20,000 dollar budget adjustment 'to Increase Overtime for DEA Investigations'. The DEA is not a party to the joint powers agreement but Metro budgets overtime for its investigations.
- Resolution 04-16-251 (16 Apr 2025): 21,794.59 dollars moved in Fund 7420 'to account for and return seized funds to the State of New Mexico'. Fund 7420 is Metro's seized-asset fund and is a different fund from the city's HIDTA fund 7492.
- Resolution 10-16-251 (16 Oct 2024): 25,000 dollars from Metro's fund balance for training/travel, vehicle rentals and overtime. It was carried again at an EMERGENCY meeting a week later, 23 Oct 2024, as the single action item.
- Resolution 07-15-262 (15 Jul 2026): a 25,000 dollar FY2027 adjustment 'to be utilized for cubicles, furniture, possible K9 chemotherapy or the purchase of a new K9'.
- EQUIPMENT DISPOSAL resolutions appear twice: 07-16-251 (16 Jul 2025) and 07-15-261 (15 Jul 2026), each 'authorizing the disposal of obsolete and non-functioning equipment owned by Metro'. Neither agenda lists what the equipment is.
- The standing business every quarter is 'Financial Reports - Finance Department' and 'Recap of Quarterly Activities for Metro - Sgt. Gabriel Arenibas'. The recap is delivered orally; no written recap is attached.
- ACROSS ALL ELEVEN AGENDAS the words license plate, plate reader, ALPR, LPR, Flock, Axon, camera and surveillance do not appear once.
- NO PACKET AND NO MINUTES. Each agenda is a bare list of items with no attachments. Minutes are approved at the following meeting - the agendas prove minutes exist - but the city publishes none of them.
ORIGINAL RESEARCH, 2026-08-30, retrieved through the city's WordPress REST API (lascruces.gov/wp-json/wp/v2/agenda?search=metro%20narcotics) and read in full; all eleven agenda bodies were read, not just titles. The city's WordPress media library returns nothing for 'metro narcotics', so the absence of packets and minutes is an absence in the publishing system, not merely in the page. THE POINT IS NOT THAT THE BOARD HID ANYTHING. It is that a board governing a multi-agency narcotics task force, which sits on 342,808 dollars of HIDTA-funded equipment and approves a 920,086 dollar budget, publishes a one-page agenda per quarter and nothing else - so the only way to learn what Metro buys is the annual audit, which names no individual asset, or a records request.
City of Las Cruces · undated · Primary · local:las-cruces
LCPD's own description of Metro Narcotics: a joint agency of three police forces, with a street address and a phone number, and no description of any technology it uses.
- Quoted: 'The Las Cruces/Dona Ana County Metro Narcotics Agency is the leading organization in combating drug trafficking and dealing in Las Cruces and Dona Ana County, New Mexico.'
- Named member agencies on this page: Las Cruces Police Department, Dona Ana County Sheriff's Office, New Mexico State Police.
- Address 217 E Picacho Avenue, Las Cruces NM 88004; phone (575) 526-0795.
- The page names no technology. HIDTA, license plate readers, ALPR, cameras, intelligence units and any real-time crime center are all absent from it.
Retrieved 2026-08-30. Read in full. The page is the public face of Metro Narcotics and it is three sentences long; every structural fact in this staging file about how Metro is actually governed and funded came from the audits and the board agendas instead, not from here. Undated: the city publishes no revision date on it.
USAspending.gov (U.S. Department of the Treasury) · 2026-08-30 · Primary · local:las-cruces
The federal side of the grant the Las Cruces council saw once in December 2020 - eleven consecutive annual awards, and a modification record that dates the license plate reader money to the day.
- ELEVEN CONSECUTIVE ANNUAL AWARDS to CITY OF LAS CRUCES from the Office of National Drug Control Policy, Executive Office of the President, award numbers G14SN0006A through G24SN0006A, each a two-calendar-year performance period: FY14 803,673.57; FY15 1,470,894; FY16 1,456,881; FY17 1,424,654.31; FY18 925,605.97; FY19 999,014; FY20 1,242,100.50; FY21 1,259,792; FY22 1,359,950; FY23 1,068,696; FY24 903,130 dollars. Eleven awards totalling 12,914,390.35 dollars.
- MODIFICATION 0002 OF THE FY2020 AWARD IS THE LICENSE PLATE READER MONEY, and the federal record dates it: action date 26 OCTOBER 2020, federal action obligation 277,527.00 dollars. This is an exact match to the figure and the description in the city's 21 December 2020 council packet - independent federal corroboration of the local record, eight weeks earlier.
- The full FY2020 transaction history: base award 9 March 2020, 977,631 dollars; modification 0001, 13 August 2020, +32,200; modification 0002, 26 October 2020, +277,527; modification 0003, 29 July 2021, MINUS 40,270; modification 0004, 20 August 2021, MINUS 4,987.50. Net total obligation 1,242,100.50 dollars, fully outlaid.
- The city's packet gives a 'TOTAL GRANT PROJECT AMOUNT' of 1,287,358 dollars for the same award. The federal record's final obligation is 1,242,100.50 - a difference of 45,257.50 dollars, exactly the sum of the two 2021 deobligations. The packet figure is the award as it stood when the council accepted it; the federal figure is the award as it closed.
- Recipient identity: CITY OF LAS CRUCES, UEI J3ZLWA2K1X47, DUNS 077609279. Place of performance: DONA ANA county, New Mexico, congressional district 02. Awarding and funding office: EOP-OFC OF NATL DRUG CONTROL POLICY, subtier code 1127.
- Non-federal funding on the FY2020 award is 0.00 dollars, matching the packet's 'no match required'.
- FY18 through FY24 awards are recorded as fully outlaid. The FY19 award shows 574,014 dollars outlaid against 999,014 obligated.
- THE SERIES STOPS AT FY2024. No FY2025 or FY2026 ONDCP award to the City of Las Cruces is found in USAspending as of 30 August 2026, although FY2025-numbered ONDCP awards to other New Mexico recipients (for example HID3025G0533 to the Fifth Judicial District Attorney, 287,680 dollars, and HID3025G0460 to Taos Health Systems, 127,000 dollars) are present under a new HID-prefix numbering scheme. NOT FOUND IS NOT DOES NOT EXIST: the city is on its fifteenth year of this money and the likeliest explanation is reporting lag or a renumbered record.
ORIGINAL RESEARCH, 2026-08-30, pulled from the USAspending v2 API: spending_by_award filtered to ONDCP and to the recipient, the award detail endpoint for each generated_internal_id, and the transactions endpoint for the FY2020 award. Every figure above was read from the API response, not from a summary page. WHY THIS MATTERS TO THE DOSSIER: the existing corpus knows about ONE HIDTA document, the December 2020 council item, and treats the 277,527 dollars as an isolated sighting. It is not isolated. It is one modification inside a fifteen-year, roughly 13 million dollar federal funding relationship in which the City of Las Cruces is the fiscal agent, and the council record contains almost none of it. What the federal record still does NOT say is what any of the money bought - USAspending carries obligations, not equipment lists.
The recipient NAME field on New Mexico HIDTA awards in USAspending cannot be relied upon: the largest New Mexico series, roughly two million dollars a year with a Dona Ana County place of performance, is recorded to the Lower Rio Grande Public Water Works Authority in Anthony, New Mexico, and for the 2021 award year the same slot is recorded to 'County of Monroe' while keeping the Anthony address.
Well supported
The case against thisThis is almost certainly a registration artifact rather than a water authority running narcotics money, and it does not touch the City of Las Cruces series, whose UEI is stable at J3ZLWA2K1X47 across all eleven awards. It is recorded so that the dollar figures in this file are cited with their award numbers, dates and places of performance rather than with recipient names.
1 source
USAspending.gov (U.S. Department of the Treasury) · 2026-08-30 · Primary · NM
A caution about the federal data the rest of this file relies on: the biggest New Mexico HIDTA award series carries a recipient name that changes between years and does not obviously belong to law enforcement.
- The ONDCP award series G19SN0020A through G24SN0020A - the largest New Mexico HIDTA series, 1,984,357 to 2,425,425.77 dollars a year - is recorded to LOWER RIO GRANDE PUBLIC WATER WORKS AUTHORITY, UEI RNDLY765B5M5, PO Box 2646, Anthony NM 88021, Dona Ana County.
- In one year the recipient name on the same slot flips: G21SN0020A (2021, 2,425,425.77 dollars) is recorded to COUNTY OF MONROE, UEI L9K8WTB2DCR3 - with the recipient city still given as ANTHONY, NEW MEXICO.
- Every award in the series has a place of performance of Dona Ana County, New Mexico, congressional district 02 - the same county as the City of Las Cruces series.
- WHAT THIS DOES NOT ESTABLISH: nothing here shows a water authority spending narcotics money. The name flip to a county on the far side of the country, with the New Mexico address retained, is the signature of a recipient-registration artifact rather than a real change of grantee.
- WHAT IT DOES ESTABLISH: the recipient NAME field on New Mexico HIDTA awards cannot be relied on by itself. Amounts, dates, award numbers and place of performance are the fields to cite.
ORIGINAL RESEARCH, 2026-08-30, from the USAspending award detail endpoint for each year of the series. The recipient names, UEIs, cities and obligations above were read directly from those responses. WHO ACTUALLY RECEIVES THE SN0020A SERIES IS NOT RESOLVED HERE and is worth resolving, because it is roughly twice the size of the Las Cruces series and lands in the same county. It is recorded so that no one later cites the Las Cruces figures without knowing the same dataset has a visible name-integrity problem two award slots away.
Neither Las Cruces PD nor the Dona Ana County Sheriff's Office publishes a Flock transparency portal: as of 18 August 2026 LCPD was reported to be 'working on a transparency portal provided by Flock' and had not launched it, a site-wide search of lascruces.gov returns one unrelated hit for 'flock', the page LCPD titles Transparency is a weekly arrest blotter, and donaana.gov returns no Flock content at all - so the sharing lists that would show whether a task force organization sits on the local network are not published by anyone.
Well supported
The case against thisA portal is a vendor-supplied page, not a legal obligation, and LCPD says one is coming; agencies elsewhere took months to stand theirs up. What the delay costs is specific and dated: every other Flock agency in the project's index publishes camera counts, retention, search totals and both sharing directions, and for Las Cruces and Dona Ana County none of that is checkable from any published source today.
3 sources
Organ Mountain News · 2026-08-18 · Primary · local:las-cruces
Las Cruces councilors pressing for a city-level surveillance policy, regular audits, and an independent public transparency portal rather than relying on the vendor's own.
- Councilors seek a city surveillance policy, a public data transparency portal, and regular audits.
- Councilor Michael Harris argues for citywide rules because departmental policies are subject to change.
- Councilor Johana Bencomo: I will just not ever be someone who is supportive or excited about mass surveillance; she urged disclosure of camera counts, scan numbers, retention periods, search volumes and inter-agency sharing.
- Lt. Peter Bradley of LCPD is developing a transparency portal through Flock and says the department applies safeguards exceeding state requirements.
- No formal council action had been taken as of publication.
The live local ask, as of two weeks before this dossier. Harris's point - that a departmental policy is not a law - is the argument for a city ordinance, and it is the specific hook this project's audit data can serve. Note the portal is being built through Flock; a vendor-supplied portal is not an independent audit.
Flock Safety transparency portals, indexed by this project via eyesonflock.com · 2026-08-10 · Primary · national
A structural fact with direct local bearing: a HIDTA can hold data-sharing rights on the Flock network as an organization in its own right, alongside dozens of named drug task forces.
- In the project's index of 51 Flock transparency portals (fetched 10 August 2026), 'Indiana HIDTA' appears in the organizations-shared-with list of 5 separate portals and 'Midwest HIDTA' of 4. A HIDTA IS AN ORGANIZATION ON THE NETWORK, not merely a funding label.
- Named narcotics TASK FORCES appear the same way and widely: Chatham-Savannah Counter Narcotics Team (17 portals), Bowling Green Warren County Drug Task Force KY (13), Kleberg TX County Attorney's Task Force (11), Marshall County Drug Task Force WV (11), SEMO Drug Task Force MO (10), Alabama Drug Enforcement Task Force Region G (8), Mineral Area Drug Task Force MO (8), 18th Judicial District Drug Task Force TN (7), OH U.S.23 Major Crimes Task Force (9), and others. A multi-agency task force with no cameras of its own routinely holds query rights on other agencies' cameras.
- NEW MEXICO AGENCIES ALREADY APPEAR IN THIS SAMPLE as sharing partners of small out-of-state departments: Bloomfield NM PD (9 portals), Clovis NM PD (12), Las Vegas NM PD (12), Lea County NM SO (12), Capitan NM PD (1).
- BLOOMFIELD PD AND LEA COUNTY SO ARE BOTH ON THE NM HIDTA PARTICIPATING-AGENCY ROSTER. Two agencies that share Flock data with departments in Arkansas, Iowa, South Carolina and Georgia are also New Mexico HIDTA member agencies.
- No Las Cruces, Dona Ana County, New Mexico HIDTA or Metro Narcotics organization appears anywhere in this 51-portal sample - which is a sample of 51 portals, not of the network.
- The 50 per-agency search-audit CSVs in the same corpus record searches as id, userId, searchDate, networkCount and offenseType only. THEY CARRY NO REQUESTING-ORGANIZATION NAME, so they cannot be used to show which agency ran a search.
- THE DIRECT LOCAL TEST CANNOT BE RUN, BECAUSE THE LOCAL PORTAL DOES NOT APPEAR TO EXIST YET. Organ Mountain News reported on 18 August 2026 that 'LCPD is working on a transparency portal provided by Flock' and that Councilor Bencomo urged the department to launch it - so as of that date Las Cruces had no published Flock transparency page carrying sharing lists. A site-wide search of lascruces.gov returns exactly one hit for 'flock' and it is an unrelated parks item; the LCPD Transparency page is a weekly arrest blotter and links no portal. A search of donaana.gov returns no Flock content at all.
ORIGINAL RESEARCH, 2026-08-30, computed over api/seed_data/flock/portal_index.json (51 portals, fetched 2026-08-10) and the 50 audit CSVs beside it, cross-referenced by hand against the NM HIDTA participating-agency roster. THE INFERENCE THIS SUPPORTS AND ITS LIMIT. It supports: a HIDTA or a drug task force can be a first-class organization on the Flock network with query rights it did not buy cameras to earn. It does NOT support: any statement that New Mexico HIDTA or Metro Narcotics holds such rights. The 51-portal index is a small, geographically skewed sample and contains no New Mexico portal at all. The direct test would be Las Cruces PD's and Dona Ana County SO's own transparency portals and their sharing lists. GUESSED SLUGS AT transparency.flocksafety.com RETURNED HTTP 403 ON 2026-08-30, BUT SO DID A DELIBERATELY NONSENSE SLUG, so those responses are blanket bot-blocking and are evidence of nothing. Neither agency publishes a portal link on its own website, and reporting from 18 August 2026 has the Las Cruces portal still unlaunched. Treat the local portal as NOT YET PUBLISHED rather than as unread. The URL given is the independent aggregator the portal index was fetched from.
New Mexico News Port · 2026-08-18 · Secondary · local:las-cruces
Fuller account of the Las Cruces councilors' oversight push, including their reaction after two hours with an LCPD lieutenant.
- Councilors Michael Harris and Johana Bencomo seek a city-level surveillance policy and a public portal showing how police collect, search and share vehicle data.
- They raised the issue after about two hours with an LCPD lieutenant going through the city's use of Flock in detail.
- Harris remains uneasy about what he called creeping surveillance but came away impressed by some of the safeguards LCPD has in place, and wants a citywide policy rather than departmental rules.
- Bencomo continues to oppose mass surveillance but expressed confidence in the LCPD team after the discussion: I have trust in him and the team that we can move forward into this place of being very transparent and honest and responsible with the kind of data that we are collecting from our residents.
IMPORTANT FOR TONE. The two councilors most critical of the technology both came away from a detailed briefing with a measure of confidence in their own department while still wanting a citywide policy. A dossier that renders Las Cruces as a fight between residents and a hostile police department would misdescribe the actual local situation, and would be corrected in the room.