Flock Gives Law Enforcement All Over the Country Access to Your Location

Police in Texas, Florida, and thousands of departments nationwide can track Massachusetts drivers in real-time — without a warrant, probable cause, or even reasonable suspicion of wrongdoing. Documents obtained by the ACLU of Massachusetts reveal that police across the state are collecting detailed information about the locations of Massachusetts drivers and sharing that information with a network of over 7,000 agencies and organizations all over the country — including in states that have passed laws banning abortion and gender-affirming healthcare for minors, and laws requiring police to conduct civil immigration enforcement operations.  

The records and other publicly available information confirm that over 80 Massachusetts police departments have entered into contracts to deploy Flock Safety’s automatic license plate reader (LPR) technology to surveil drivers when they pass one of Flock’s cameras on the roads. Over the past three years, Massachusetts police have spent over $2 million in taxpayer funds on this technology. Many of these departments have been sharing LPR data collected in their jurisdiction with Flock to be entered into its national database, where it can be accessed by thousands of out-of-state police departments and even federal agencies.  

At minimum, this dragnet surveillance means warrantless tracking of everyone on the road. At worst, it means a digital police state wherein law enforcement officials in far-flung jurisdictions outside of Massachusetts can track protesters, political opponents, immigrants, patients, and others not suspected of any crime and use the information to hurt them. 

What Is Flock and How Does It Work? 

Flock Safety is a major player in the LPR industry, contracting with thousands of law enforcement agencies, running LPR surveillance across nearly 7,000 networks, and deploying nearly 90,000 cameras nationwide as of July 2025. The company's CEO claims their technology can eradicate all crime in America — though that's more marketing hype than reality. 

License plate readers are cameras that automatically capture and record license plates, locations, and timestamps as vehicles pass by. These AI-enabled systems allow police to instantly track where motorists are now and where they've been. 

At the crux of the problems with Flock is their nationwide data sharing model. Police departments that contract with Flock can choose to share the LPR data they collect with no other departments, with specific named departments, with all departments in their state, or with the entire Flock network nationwide. But Flock has designed its system to incentivize maximum sharing: if a police department chooses to share their data with the entire nationwide network, that department can also search the entire nationwide network. In effect: “You show me yours, I'll show you mine.” This Flock training video received in response to public records requests demonstrates how seamless and unrestricted data sharing operates within Flock’s system. To share their data with police nationwide, all an administrator needs to do is click a button: 

This screenshot from Flock’s training materials shows that simply by selecting “Enable National Lookup[,]” agencies contracted with Flock can give their staff access to Flock’s national database and, in turn, share their data with agencies nationwide.
While departments contracted with Flock can opt to only accept specific data sharing requests, departments also have the option of automatically accepting sharing requests from other agencies.

We know many Massachusetts police departments are taking part in this nationwide network because, after submitting public records requests with nearly 80 departments, we received numerous records called “Flock Network Audits[.]” These network audits document searches conducted by police across the country of approximately 7,000 agencies and organizations’ LPR data, including data on Massachusetts drivers collected by dozens of Massachusetts police departments. What this means in practice is that officers with the Florida Highway Patrol and those in Dallas, TX, Jacksonville, FL, Columbus, OH, and thousands of other locations can track where and when Massachusetts residents are driving, even when they are in Massachusetts — all without demonstrating any probable cause or even reasonable suspicion that those people have committed a crime.  

Even some federal law enforcement agencies may have access to Flock’s database, despite Flock’s recent assertion that it ended its pilot program with the Department of Homeland Security’s Customs and Border Protection (CBP). News reports indicate local police have conducted searches on behalf of ICE agents.  

And that’s not all. Flock isn’t the only license plate reader company with a large presence in Massachusetts. The Massachusetts State Police (MSP) and some local departments also have contracts with Vigilant Solutions, a company that maintains its own national database and has contracts with agencies nationwide — including those in states that have passed extreme restrictions on abortion and gender affirming healthcare access. Vigilant also has contracts with federal agencies, including ICE. Indeed, records obtained through a public records request to the town of Auburn, Massachusetts show ICE agents have direct access to query the Vigilant database. The ACLU of Massachusetts is currently involved in public records litigation to learn more about the MSP’s license plate reader surveillance network and its statewide LPR tracking database. Stay tuned for more details as that litigation progresses. 

ICE staff and agents have access to search Vigilant's nationwide database, as shown in the above screenshot from public records shared by the Auburn, MA police department.

Is Warrantless, Dragnet Surveillance of Motorists Legal? 

In 2014, in Commonwealth v. Augustine, the Massachusetts Supreme Judicial Court held that police are required to obtain a search warrant to access cell site location information under the Massachusetts Constitution, the Declaration of Rights. Four years later, the Supreme Court applied similar protections nationwide in Carpenter v. United States. The Court reasoned that technology enabling the government to track everyone, to monitor all our public movements, and to do so both in real time and retroactively, posed a significant threat to our Fourth Amendment rights.  

LPRs are analogous to cellphone tracking. These AI-enabled cameras track motorists in real-time and historically, giving the government the means to track people's locations in a manner similar to the cell site location information at issue in Augustine and Carpenter. 

The Massachusetts Supreme Judicial Court recognized this in 2020, holding in Commonwealth v. McCarthy that “[w]ith enough cameras in enough locations, the historic location data from an [LPR] system in Massachusetts would invade a reasonable expectation of privacy and would constitute a search for constitutional purposes.” Yet today, police in Massachusetts are subject to no state or federal statute governing their use of automatic license plate readers. In the absence of a state statute, police are engaged in mass surveillance of all drivers. 

Flock's Data Sharing Model vs. the Massachusetts Shield Law 

In August 2024, Massachusetts strengthened its Shield Law, which prohibits Massachusetts law enforcement from providing information or assistance to any other state's law enforcement agency in relation to investigations into reproductive healthcare or gender-affirming healthcare that is lawful in the Commonwealth. The Shield Law was designed to protect people from other states’ laws that criminalize abortion and restrict access to gender-affirming care, ensuring that people who receive and provide protected healthcare that is lawful in Massachusetts can do so without fear of retribution from out-of-state actors.  

But Massachusetts law enforcement's use of Flock's nationwide data sharing undermines the effectiveness of the Shield Law. Out-of-state officers from thousands of agencies across the country can and do access information about where and when people are driving in Massachusetts, and there is nothing stopping them from using that information to track the movements of people in Massachusetts who are seeking or providing protected healthcare. 

These concerns are not hypothetical. Earlier this year, police in Johnson County, Texas performed a nationwide search in Flock's database to find a woman who they believed had a self-administered abortion — searching LPR data from many states where abortion is legal and protected, including Massachusetts. We know about this investigation because the Texas officer entered “had an abortion, search for female” in the “Reason” field in Flock’s database. Initially, Flock tried to dismiss criticism stemming from the negative press, suggesting that the woman's “family feared she was hurt” and that police merely sought to make sure that she was alright. But subsequent reporting from 404 Media based on public records obtained by the Electronic Frontier Foundation show the police who made this search were pursuing the woman as part of a “death investigation” into the abortion. As 404 Media reporters put it: “In documents created prior to the publication of our article, there is zero mention of concern about the woman’s safety. The records show that the police retroactively created a separate document about the Flock search a week after our article was published, in which they justify the search by saying they were concerned for her safety.” 

Flock claims it protects people's privacy and legal rights by requiring all law enforcement officers to enter a “search reason” before accessing database results. According to Flock’s recent response to similar data sharing concerns in other states, if an out-of-state officer enters a reason that would violate a state law that protects access to reproductive and gender-affirming healthcare (for example, Massachusetts’ Shield Law), that state’s LPR data would be excluded from the search results. But the Flock network audits obtained by the ACLU of Massachusetts demonstrate that the company’s measures are woefully inadequate. 

The network audits show police frequently enter vague, tautological terms like “investigation” or “susp” instead of information about the substance of the investigation. But even if Flock were to prohibit officers from accessing search data unless they provide a substantive reason, police could evade the system’s guardrails. As Flock's technology attracts more negative media attention and scrutiny from public officials concerned about its data sharing practices, officers in states that criminalize abortion and gender-affirming healthcare could simply decline to provide specific details about their investigations or use terms like “homicide” or “suspicious death” when investigating an abortion case. The scale of the nationwide searches makes case-by-case oversight impossible. For example, a Flock network audit provided to the ACLU of Massachusetts in response to a July 2025 public records request documents over 450,000 searches of the nationwide database in just a 30-day period in the spring of 2025. 

The above screenshot shows an actual Massachusetts police department’s Flock network audit, with personally identifiable information redacted.

Flock’s purported solution to comply with state laws that restrict the sharing of information related to investigations of protected healthcare services is no solution at all. Today, out-of-state officers continue to have effectively unrestricted access to Flock’s nationwide database, including data about Massachusetts residents and visitors. 

Flock's Contract Problem 

Police departments that use Flock and seek to protect the rights of Massachusetts residents from out-of-state or federal scrutiny must turn off information sharing settings authorizing those entities from searching the data they collect. But even when departments opt to restrict sharing in Flock’s system settings, they may not actually be protecting people’s privacy. According to public records reviewed by the ACLU of Massachusetts, the template user agreement many law enforcement agencies sign gives Flock “a non-exclusive, worldwide, perpetual, royalty-free right and license (during and after the Service Term hereof) to (i) use and distribute [] Aggregated Data to improve and enhance the Services and for other development, diagnostic and corrective purposes, other Flock offerings, and crime prevention efforts, and (ii) disclose the Agency Data (both inclusive of any Footage) to enable law enforcement monitoring against law enforcement hotlists as well as provide Footage search access to law enforcement for investigative purposes only” [italics added for emphasis].

The above screenshot shows an excerpt of Flock’s template user agreement, which grants Flock the license to use, distribute, and disclose data collected by a given agency.

What this means in practice is troubling: even when a police department chooses in Flock's application to restrict data access to its own officers, the template agreement gives Flock the right to disclose the local police department's data both to law enforcement nationwide and federal agencies for “investigative purposes.” 

Individual police departments can, and sometimes have, addressed this problem by amending Flock’s contract language. For example, when the Boston Police Department (BPD) conducted a pilot of Flock’s technology earlier this year, the department elected in its sharing settings not to share data outside the department — but the BPD also appears to have rewritten Flock's template contract. Unlike the template contract language that many police departments have agreed to, the Boston Police Department's agreement does not give Flock the right to disclose its LPR data. 

The above screenshot shows an excerpt of the Boston Police Department’s user agreement with Flock, which notably differs from Flock’s standard template user agreement in that the Boston Police Department’s agreement does not give Flock the right to disclose agency data.

But the vast majority of police departments in Massachusetts lack the legal resources and sophistication of Boston's department, putting them at a serious disadvantage. Flock, which recently received a large investment from Andreessen Horowitz, has been engaged in an aggressive marketing campaign to win more contracts and secure more taxpayer dollars. This campaign includes potent sales tactics, such as invitations to participate in a free TopGolf event and an opportunity for agencies to participate in Flock's “Project Prove It[,]” in which Flock installs LPR cameras on the roads and the agency can back out at no cost within 45 days. Flock sales staff also offer to work with local Massachusetts departments and other municipal leaders to identify and apply for grant funding for Flock LPR systems. 

Flock draws police departments into its nationwide data sharing network by offering officers and other staff the opportunity to participate in free events, like at TopGolf.
The above screenshot of an email from a Flock salesperson to the Waltham police department shows Flock’s typical sales tactics used to convince even departments that are hesitant to invest in its LPR technology to adopt it through Flock’s “Project Prove It.”
Flock sales staff even offer to help local police departments obtain funding to contract with Flock.

Faced with this onslaught from a company with seemingly endless resources at its disposal, small- and medium-sized police departments across the country are falling prey to aggressive marketing and sales pitches. Individual action by sophisticated departments like Boston’s isn't enough. Residents in communities with less well-resourced departments deserve protection too.  

How Lawmakers and Law Enforcement Can Address Issues with LPRs 

The scope and severity of this dragnet surveillance make clear that both legislative action and individual police department changes are needed to achieve statewide protections from unrestricted LPR use. 

First, state lawmakers must pass comprehensive LPR legislation. H.3755 strikes the right balance, protecting civil rights and civil liberties while allowing police to use LPRs for legitimate investigations. The bill prohibits law enforcement from using LPRs to monitor individuals based on First Amendment-protected activities, including political protests or religious gatherings. It requires that LPR data be deleted within 14 days unless a record is tied to a specific, ongoing criminal investigation supported by articulable facts. Access to LPR data would be limited to law enforcement for investigative purposes and could not be disclosed outside judicial proceedings. The bill also prohibits buying, selling, renting, or sharing LPR and related location data unless required by judicial process, and bars law enforcement from accessing LPR data collected by another entity without a valid search warrant. These provisions prevent the accumulation and sharing of data on millions of people not suspected of any wrongdoing, while allowing law enforcement to use LPRs in legitimate criminal investigations. This legislation would ensure consistent protections apply for all Massachusetts residents. 

Second, police departments must take immediate action. Individual departments should stop voluntarily sharing data with out-of-state and federal agencies. They should redraft contracts with Flock to ensure their department retains full control of all data they collect. Finally, police departments must adopt internal policies requiring that every Flock network search be justified by a specific, documented reason for the inquiry, clarifying to all officers and staff that a non-descriptive entry like “investigation” will not suffice. 

Take Action 

Right now, your movements on Massachusetts roads are being tracked and shared with thousands of agencies nationwide. No warrant, no suspicion, no safeguards. 

Join us in calling on the Massachusetts Legislature to pass common sense checks and balances on police use of license plate readers, to ensure that you retain basic civil liberties on the road.  

Email your state legislators today to show your support for H.3755, An Act Establishing Driver Privacy Protections.

This post was updated on February 26, 2026, to reflect that more than 80 police departments across Massachusetts have contracts with Flock Safety.


Fact check: In Boston, pro-immigrant policies coexist with lower crime rates, not higher ones

Trump administration officials claim that state and local laws preventing police from participating in federal civil immigration enforcement (sometimes referred to as “sanctuary” policies) make communities more dangerous. But these claims don’t fit the facts.  

The Center for American Progress conducted a nationwide analysis of over 2,000 counties in 2017, finding that crime per capita is significantly lower in sanctuary counties compared to similar non-sanctuary counties. On average, there were 35 fewer crimes committed per 10,000 people in sanctuary counties. These results accord with many other peer-reviewed studies. What’s more, the Center for American Progress report found that sanctuary counties are also more economically prosperous. A 2020 study published by researchers at UC San Diego found that immigrants are less likely to trust local law enforcement if they work with ICE. These studies support the view, long espoused by the ACLU and other supporters of welcoming city policies, that creating a clear boundary between policing and immigration enforcement enhances rather than diminishes community safety. 

In Boston, the city’s Trust Act was signed in August 2014 and amended in 2019. The law prohibits City of Boston officials from using city resources to assist with federal civil immigration enforcement. Recently, the Trump administration and Congressional Republicans have taken aim at Boston and Mayor Michelle Wu, demanding that the city assist with Trump’s plans for mass deportations. Underlying these demands are claims that policies such as Boston’s harm public safety. 

But the facts tell a very different story: FBI and BPD data show crime rates, already declining when the Trust Act passed in 2014, have continued to decline in the nearly 11 years since the legislation became law. Indeed, Boston has reported historic lows in the number of homicides and shootings over the last few years. Both property crime and violent crime, according to FBI Uniform Crime Reporting statistics, have been on the decline since 2005, a decline that continued following the enactment of the Trust Act.  

The data from Boston reflects a trend observed in peer-reviewed studies, with some finding that sanctuary laws actually result in a decrease in crime. Contrary to claims from anti-immigrant officials in Washington, cities across the country would do well to consider Boston a model. 


We saved hundreds of Biden-era AI documents, so you don't have to

Image credit: Adapted from Anton Grabolle / Better Images of AI / Classification Cupboard / CC-BY 4.0


On January 20th, Trump will begin his second term in office.

If Trump and his administration follow through on their campaign promises, the transition of power will bring devasting consequences for our fundamental rights and freedoms, particularly for immigrants, reproductive health care seekers, people of color, poor people, and queer and trans communities.

Among the many anticipated impacts, the new administration has signaled it intends to reverse Biden-era progress related to protecting our civil rights and civil liberties in the realms of privacy and artificial intelligence.

The day after the election, Trump announced his intention to repeal a Biden era executive order regulating AI. Since then, Trump has granted Elon Musk unprecedented influence over government affairs, and hosted scores of tech leaders at Mar-a-Lago. Tech CEOs have in turn donated millions to Trump’s inauguration, with contributions from Apple, Meta, Amazon, and OpenAI far outpacing their donations to Biden in 2020.

These and other developments foreshadow an incoming administration that is going to take a lax approach toward regulating technology companies.

Over the last four years, the Biden administration made important strides in this area, including a directive increasing transparency into government use of AI, FTC enforcement against location data brokers, and a DOJ lawsuit challenging the legality of RealPage’s rent price-fixing algorithm.

These efforts were buttressed by legal documents, reports, blogs, and other records laying out the administration’s efforts to protect consumers and hold Big Tech accountable. But once administrative agencies change hands under Trump, there is no guarantee that documentation of these and other initiatives will remain accessible to advocates, journalists, and interested members of the public.

So, we saved them.

Below, you can view archived copies of over 250 documents and webpages on topics like algorithmic discrimination, generative AI, and biometric surveillance. Try filtering by agency (e.g., DHS, FTC) or keywords (e.g., AI use case inventory, Kochava, risk). Use the drop-down menu to change how many rows you can see at a time.

No matter what happens, the ACLU of Massachusetts remains committed to fighting for law reforms to protect the public interest, civil rights, and civil liberties. Click here to find out ways you can get involved.


AgencyDocumentSource
Administrative ConferenceAI and regulatory enforcementOriginal source
Administrative ConferenceGuidance on agency use of AI (2020)Original source
Administrative ConferenceReport on automated legal guidance at federal agenciesOriginal source
ANSIPublic private partnershipsOriginal source
CFPBAdverse action notification on credit algorithmsOriginal source
CFPBAI in financial services - commentOriginal source
CFPBAI in home appraisals - blogpostOriginal source
CFPBAI in home appraisals - ruleOriginal source
CFPBBackground dossiers and AI in employmentOriginal source
CFPBCall to action for tech whistleblowingOriginal source
CFPBFair Credit Reporting and Name-Only Matching ProceduresOriginal source
CFPBGuidance on black box algorithmsOriginal source
CFPBGuidance on credit denials using AIOriginal source
CFPBNo-action letter to Upstart - blogpostOriginal source
CFPBNo-action letter to Upstart (credit lender)Original source
CFPBOn false matches in tenant and employment screeningOriginal source
CFPBProposed registry for AI harm repeat offendersOriginal source
CFPBRights for job seekers on background screeningOriginal source
CFPBRights for tenants on rental application denialsOriginal source
CFPBTenant screening - consumer snapshotOriginal source
CFPBTenant screening - market reportOriginal source
Chief Information Officers CouncilGuidance for federal agencies on AI use case inventory (2024)Original source
CommerceDepartment of Commerce AI use case inventory (2023)Original source
CongressAdvancing American AI actOriginal source
Copyright OfficeCopyright and AI: Digital ReplicasOriginal source
Department of StateDepartment of State AI use case inventory (2024)Original source
Department of StateDepartment of State use of AI compliance planOriginal source
DHSDHS AI roadmap (2024)Original source
DHSDHS AI use case inventory - blog post Original source
DHSDHS AI use case inventory - landing pageOriginal source
DHSDHS AI use case inventory (2022)Original source
DHSDHS AI use case inventory (2023)Original source
DHSDHS AI use case inventory (2024)Original source
DHSDHS playbook for GenAI in the public sectorOriginal source
DHSDHS Simplified AI use case inventory landing pageOriginal source
DHSDHS use of AI compliance planOriginal source
DHSPress release on DHS playbook on GenAI in the public sectorOriginal source
DODDOD use of AI compliance planOriginal source
DOJAI and disability discrimination in hiringOriginal source
DOJDOJ AI use case inventoryOriginal source
DOJDOJ Sues RealPage for Algorithmic Pricing Scheme Original source
DOJDOJ Sues Six Large Landlords for Algorithmic Pricing Scheme Original source
DOJUS et al. v. RealPage - proposed final judgmentOriginal source
DOJUS vs RealPageOriginal source
DOJUS vs RealPage - amended compliantOriginal source
DOLAI and ADS under Fair Labor Standards ActOriginal source
DOLAI and worker well-being principlesOriginal source
DOLFederal contractors use of AIOriginal source
StateRisk Management Profile for AI and Human RightsOriginal source
DOTDOT AI use case inventoryOriginal source
DOTDOT use of AI compliance planOriginal source
EducationAI Discrimination in EducationOriginal source
EducationDepartment of Education AI use case inventoryOriginal source
EducationDepartment of Education use of AI compliance planOriginal source
Election Assistance CommissionElection Assistance Commission use of AI compliance planOriginal source
EnergyDepartment of Energy AI use case inventory (2023)Original source
EnergyDepartment of Energy GenAI Reference GuideOriginal source
EnergyDepartment of Energy use of AI compliance planOriginal source
EOCCAddressing adverse impact of AI in employment under CRAOriginal source
EOCCArtificial Intelligence and Algorithmic Fairness InitiativeOriginal source
EOCCEOCC use of AI compliance plan (2024)Original source
EOCCGuidance on AI in employment and ADA Original source
EOCCImplications of big data for equal employment opportunity lawOriginal source
EOCCiTutorGroup age discrimination lawsuitOriginal source
EOCCiTutorGroup settlementOriginal source
EOCCPress release on guidance on AI in employment and ADA Original source
EOCCTips for workers on AI and ADAOriginal source
EOCCVisual Disabilities in the Workplace and ADAOriginal source
EOCCWearables in the workplace under federal discrimination lawsOriginal source
EOTAI and future of teaching and learningOriginal source
EPAEPA use of AI compliance planOriginal source
Executive Office of PresidentPromoting the Use of Trustworthy Artificial Intelligence in the Federal GovernmentOriginal source
FCCAI in robocalls and proposed rule on robotextsOriginal source
Federal Housing Finance AgencyFederal Housing Finance Agency use of AI compliance plan (2024)Original source
FTCAI and the risk of consumer harmOriginal source
FTCApproaches to Address AI-enabled Voice CloningOriginal source
FTCBest practices for use of FRTOriginal source
FTCBlogpost on location data casesOriginal source
FTCExplainer on proposed settlements with Avast, X-Mode, and InMarketOriginal source
FTCExplainer on real-time biddingOriginal source
FTCExplainer on surveillance pricingOriginal source
FTCFRT vs Facebook (2012) settlementOriginal source
FTCFTC on deceptive AI claimsOriginal source
FTCFTC vs Ascend Ecom deceptive claim lawsuitOriginal source
FTCFTC vs DoNotPay "AI lawyer" deceptive claim - agreed consent orderOriginal source
FTCFTC vs DoNotPay "AI lawyer" deceptive claim - complaintOriginal source
FTCFTC vs Ecommerce Empire deceptive claim complaintOriginal source
FTCFTC vs Everalbum Photo App complaintOriginal source
FTCFTC vs Everalbum Photo App press releaseOriginal source
FTCFTC vs Everalbum settlementOriginal source
FTCFTC vs Facebook (2012) settlement order press releaseOriginal source
FTCFTC vs Facebook settlement orderOriginal source
FTCFTC vs Facebook settlement order press releaseOriginal source
FTCFTC vs FBA machine deceptive claimOriginal source
FTCFTC vs FBA machine orderOriginal source
FTCFTC vs Flo Health press releaseOriginal source
FTCFTC vs Flo Health statement on settlementOriginal source
FTCFTC vs GravyAnalytics complaintOriginal source
FTCFTC vs GravyAnalytics concurring statement (1 of 3)Original source
FTCFTC vs GravyAnalytics concurring statement (2 of 3)Original source
FTCFTC vs GravyAnalytics concurring/dissenting statement (3 of 3)Original source
FTCFTC vs GravyAnalytics press releaseOriginal source
FTCFTC vs GravyAnalytics proposed orderOriginal source
FTCFTC vs InMarket complaintOriginal source
FTCFTC vs InMarket press releaseOriginal source
FTCFTC vs InMarket press release on finalized orderOriginal source
FTCFTC vs Inmarket proposed orderOriginal source
FTCFTC vs Intellivision (unsupported claims about FRT) complaintOriginal source
FTCFTC vs Intellivision blogpostOriginal source
FTCFTC vs Intellivision press releaseOriginal source
FTCFTC vs Intellivision proposed consent orderOriginal source
FTCFTC vs Kochava amended complaintOriginal source
FTCFTC vs Kochava case pageOriginal source
FTCFTC vs Kochava complaintOriginal source
FTCFTC vs Kochava concurring statementOriginal source
FTCFTC vs Kochava memorandum decision 02/2024Original source
FTCFTC vs Kochava press releaseOriginal source
FTCFTC vs MobileWalla complaintOriginal source
FTCFTC vs MobileWalla complaintOriginal source
FTCFTC vs MobileWalla proposed settlement orderOriginal source
FTCFTC vs RiteAid complaintOriginal source
FTCFTC vs RiteAid concurring statementOriginal source
FTCFTC vs RiteAid press releaseOriginal source
FTCFTC vs RiteAid proposed orderOriginal source
FTCFTC vs Rytr (writing assistant) deceptive claim complaintOriginal source
FTCFTC vs Rytr proposed orderOriginal source
FTCFTC vs X-mode agreement with consent order (Jan 2024)Original source
FTCFTC vs X-mode analysis of proposed consent orderOriginal source
FTCFTC vs X-Mode and Outlogic press release on finalized orderOriginal source
FTCFTC vs X-mode and Outlogic press release on outcomeOriginal source
FTCFTC vs X-mode complaint (April 2024)Original source
FTCFTC vs X-mode complaint (Jan 2024)Original source
FTCFTC vs X-mode decision and order (April 2024)Original source
FTCFTC vs X-mode proposed order (Jan 2024)Original source
FTCHealth app breach notification rule Original source
FTCImpersonation rule press releaseOriginal source
FTCOperation AI ComplyOriginal source
FTCPolicy statement on use of biometric informationOriginal source
FTCPress release on health app breach notification rule Original source
FTCStatement by FTC commissioner on health app breachesOriginal source
FTCSurveillance pricing order press releaseOriginal source
FTCSurveillance pricing order to file reportOriginal source
FTCWarning about biometric surveillanceOriginal source
GAOGov AI accountability highlightsOriginal source
GAOGov AI accountability reportOriginal source
General Services AdministrationGSA use case inventory Original source
General Services AdministrationGSA use of AI compliance plan - governanceOriginal source
General Services AdministrationGSA use of AI compliance plan - responsible innovationOriginal source
General Services AdministrationGSA use of AI compliance plan - risksOriginal source
HealthDepartment of Health AI use case inventory (2024)Original source
HHSU.S. Department of Health and Human Services use of AI compliance planOriginal source
HUDFair Housing Act and use of criminal records in housing transactionsOriginal source
HUDFair Housing Act guidance on AIOriginal source
HUDGuidance on AI in advertising of housing, credit and real estateOriginal source
HUDGuidance on AI in tenant screeningOriginal source
HUDHUD AI use case inventory (2023)Original source
HUDHUD AI use case inventory (2024)Original source
HUDHUD use of AI compliance plan (2024)Original source
Industry and Security BureauProposed rule for mandatory AI reportingOriginal source
InteriorDepartment of Interior AI use case inventory (2024)Original source
InteriorDepartment of Interior use of AI compliance planOriginal source
IRSIRS transitions away from FRT for third-party verificationOriginal source
LaborDOL AI use case inventoryOriginal source
LaborDOL use of AI compliance planOriginal source
Library Of CongressAI and copyrightOriginal source
Multi-agency2023 Joint Statement on Enforcement of Civil Rights, Fair Competition, Consumer Protection, and Equal Opportunity Laws in Automated SystemsOriginal source
Multi-agency2024 Joint Statement on Enforcement of Civil Rights, Fair Competition, Consumer Protection, and Equal Opportunity Laws in Automated SystemsOriginal source
Multi-agency2024 use case inventory reporting instructionsOriginal source
Multi-agencyCFPB and Federal Partners on ADSOriginal source
Multi-agencyCFPB and NLRB Announce Information Sharing Agreement Original source
Multi-agencyFederal Agency AI Use Case Inventory (2023)Original source
Multi-agencyFederal Agency AI Use Case Inventory (2024)Original source
Multi-agencyFederal Agency AI Use Case Inventory READMEOriginal source
Multi-agencyJoint statement against AI biasOriginal source
Multi-agencyJoint statement on ADS enforcementOriginal source
NAIACAI literaryOriginal source
NAIACAI positive impact on science and medicineOriginal source
NAIACAI's Procurement ChallengeOriginal source
NAIACData Challenges and Privacy Protections for Safeguarding Civil Rights in GovernmentOriginal source
NAIACExpand the AI Use Case Inventory by Limiting the ‘Common Commercial Products’ ExceptionOriginal source
NAIACExpand the AI Use Case Inventory by Limiting the ‘Sensitive Law Enforcement’ ExceptionOriginal source
NAIACFAQs on Foundation Models and GenAIOriginal source
NAIACFindings and recommendations on AI SafetyOriginal source
NAIACFindings on The Potential Future Risks of AIOriginal source
NAIACGenAI risksOriginal source
NAIACHarnessing AI for Scientific ProgressOriginal source
NAIACImplementing the NIST AI Rights Management FrameworkOriginal source
NAIACInstitutional Structures to Support Safer AI SystemsOriginal source
NAIACNAIAC webpagesOriginal source
NAIACNational Artificial Intelligence Advisory Committee: Year 1 ReportOriginal source
NAIACNational Artificial Intelligence Advisory Committee: Year 2 ReportOriginal source
NAIACNational Campaign on Lifelong AI Career SuccessOriginal source
NAIACOn adverse event reporting of emerging risks from AI Original source
NAIACOn field testing of law enforcement AI toolsOriginal source
NAIACOn implementing the NIST AI Safety InstituteOriginal source
NAIACPublic Summary Reporting on Use of High-Risk AIOriginal source
NAIACPublic Use Policies for High-Risk AIOriginal source
NAIACRationales, Mechanisms, and Challenges to Regulating AIOriginal source
NAIACReport on impact of AIOriginal source
NAIACReport on law enforcement use of AIOriginal source
NAIACResponsible Procurement Innovation for AI at Government AgenciesOriginal source
NAIACStatement of support on Safe, Secure and Trustworthy AI EOOriginal source
NAIACStatement on AI and Existential RiskOriginal source
NAIACTowards Standards for Data Transparency for AI ModelsOriginal source
NAIACWorking Group on Rights-Respecting AIOriginal source
NAIRRNAIRR task force final reportOriginal source
NAIRRNAIRR task force interim reportOriginal source
NAIRRNational AI Research Resource pilot launchOriginal source
NASANASA use of AI compliance planOriginal source
NISTAI risk management frameworkOriginal source
NISTAI risk management playbookOriginal source
NISTAI technical standardsOriginal source
NISTGenAI risk managementOriginal source
NISTGenAI software development practicesOriginal source
NISTNIST landing post on Safe, Secure, Trustworthy AI EOOriginal source
NISTOne-pager on carrying out Safe, Secure, Trustworthy AI EOOriginal source
NISTRisks of foundation modelsOriginal source
NISTSecure Software Development FrameworkOriginal source
NISTStandards for identifying biasOriginal source
NSFNSF 2023/2024 AI use case inventoryOriginal source
NSFNSF use of AI compliance planOriginal source
NSSCETNational Standards Strategy for Critical and Emerging Technology roadmapOriginal source
NSTTrustworthy AI R&DOriginal source
Nuclear Regulatory CommissionNuclear Regulatory Commission use of AI compliance planOriginal source
OETGuidance for developers on AI in EducationOriginal source
Office of Personnel ManagementOffice of Personnel management use of AI compliance planOriginal source
OMBBlogpost on responsible acquisition of AIOriginal source
OMBMemo on AI governanceOriginal source
OMBMemo on responsible acquisition of AIOriginal source
OSTPBlueprint for AI Bill Of RightsOriginal source
SECSEC AI use case inventory 2024Original source
SECSEC use of AI compliance planOriginal source
SSASSA use of AI compliance planOriginal source
TreasuryAI use case inventory May 2023Original source
TreasuryTreasury use of AI compliance planOriginal source
US Commission on Civil RightsAI in K-12 educationOriginal source
US Commission on Civil RightsCivil rights implications of algorithmsOriginal source
US Commission on Civil RightsCivil rights implications of FRTOriginal source
US Commission on Civil RightsCivil rights implications of FRT factsheetOriginal source
US Commission on Civil RightsUSCCR use of AI compliance planOriginal source
USAIDUSAID use of AI compliance planOriginal source
USDAUSDA AI strategyOriginal source
USDAUSDA AI use case inventory (2024)Original source
USDAUSDA use of AI compliance planOriginal source
VeteransDepartment of Veterans Affairs use of AI compliance planOriginal source
White HouseEO on Safe, Secure and Trustworthy AIOriginal source
White House EO on Safe, Secure and Trustworthy AI - press releaseOriginal source
White HouseDelivering on the Promise of AI to Improve Health OutcomesOriginal source
White HouseEO on Responsible AIOriginal source
White HouseFramework on AI governance in national securityOriginal source
White HouseNational Standards Strategy for Critical and Emerging Technology - press releaseOriginal source
White HouseThe Cost of Anticompetitive Pricing Algorithms in Rental HousingOriginal source
White HouseVoluntary Commitment on AI - press releaseOriginal source

Can’t find what you’re looking for? It may be available on the Internet Archive.


Join the ACLU

find out about upcoming events and follow our latest reports.

Privacy Preference Center