Amazon Drops Data Center NDAs With Governments: What Changed and What It Does Not Cover

Short answer: Amazon says it no longer signs nondisclosure agreements with the government agencies it works with on data center projects. AWS CEO Matt Garman announced the change on October 2, 2026, in a post that also pledged more than $1 billion over five years to host communities under a program called Built Together, per Implicator's report. TechCrunch's Equity podcast picked the NDA line up on October 11, noting it was "buried in the blog post" even though it goes to the root of the backlash.

The change is real but narrow: it applies going forward, and key questions about contractors and past deals are open. This guide lays out what is confirmed, what is not, and why secrecy became the weak point of the AI build-out. For the wider political fight, see our coverage of the Senate investigation into hyperscaler data center costs.

TL;DR: what Amazon said and what is still open

What the post actually says

According to Implicator, Garman's post said Amazon no longer uses nondisclosure agreements with government agencies on its projects, and framed the community pledge as a response to the wave of local opposition. He wrote that the moratoriums could threaten the US lead in artificial intelligence. I could not retrieve Amazon's original post directly, so these details come from press coverage. Check the aboutamazon.com page for exact wording.

The money side, as reported: Built Together would cover remaining community college costs after financial aid for an estimated 300,000 students, add 16 training centers on or near data center sites beyond the three operating and six in development, fund energy-efficiency upgrades for more than 300 schools and community buildings and more than 30,000 homes, and give flexible grants to local nonprofits and foundations. Garman wrote, "This is not Amazon deciding what communities need, it is Amazon providing resources and letting communities decide."

Fortune covered the community college piece separately, and the pledge also included annual energy and water reporting and cleaner backup generators at new sites, which Implicator notes are self-reported figures.

Why NDAs became the pressure point

A data center needs land, tax treatment, power and water. Developers often negotiate those with local officials under confidentiality, sometimes before the public knows who the tenant is. The argument for it is commercial: site searches are competitive and a leaked name can move land prices.

The argument against, made by TechCrunch's Sean O'Kane on Equity, is that "a lot of these projects are being negotiated essentially in secret," which feeds distrust about property values, electricity bills and water use whether or not those fears are justified. He compared it to Uber's mid-2010s habit of negotiating with cities privately. TechCrunch's Anthony Ha added that removing NDAs will not instantly turn opponents into supporters, but "the beginning of that conversation" is that people do not know what the company is doing.

The Senate side sharpened it. All four large tech companies in that probe routinely sought NDAs during development, per the report we summarized in the Senate hyperscaler investigation post, and some asked government officials to sign them. Implicator adds that Rep. Jamie Raskin sent letters to Amazon, Google, Meta and Oracle demanding information about their data center NDAs just days before Garman's post.

Amazon versus Microsoft: not the same promise

Microsoft moved first. Implicator reports Microsoft said in March it would terminate its existing NDAs with local governments, which goes further than Amazon's forward-only stance. Our Senate coverage records a narrower version: Microsoft told investigators it would stop seeking NDAs with local governments but keep using them with state agencies, public utility commissions and utilities. Those two descriptions are not identical, so read each company's exact wording before treating them as equivalent.

Google and Meta declined to commit to ending NDAs, per that same report. So the industry is split: two of four named giants have changed policy in some form, and the details differ.

What the Amazon change leaves out

Several gaps matter to anyone reading a local data center proposal:

• Past agreements. Amazon says most old NDAs no longer apply once a project becomes public, but it does not plan to revisit them.- Contractors and intermediaries. In Wharton County, Texas, Implicator reports an official signed an NDA with a contractor, VisionFirst Advisors, that stopped him from sharing details of an Amazon project. A pledge covering government agencies may not reach third parties acting for the company.
• State agencies and utilities. Whether the policy covers state-level bodies is not specified in the coverage I found.
• Timing. The announcement gives no date for when the policy actually began, per one report.

Is the $1 billion meaningful?

Implicator calculates the pledge at roughly $200 million a year, about one-tenth of 1 percent of Amazon's projected $220 billion in 2026 capital spending. Amazon itemized only about $200 million so far: more than $100 million for community college endowments and roughly $100 million for training centers. Amazon also says it gave more than $1 billion to data center communities in the past three years.

Stand.Earth called the funding "a drop in the bucket" and a "flailing attempt at damage control," while saying ending NDAs would likely improve transparency. The group also pointed to a power plant Amazon is building in Pecos, Texas, which it says is permitted to emit 33 million tons of CO2 annually and is not mentioned in the commitments. These are the group's claims, reported by Implicator.

The moratorium backdrop

Garman's figure of more than 100 moratoriums under consideration is his own count. Independent trackers show the pressure is real: Implicator cites Data Center Watch counting at least 75 projects worth about $130 billion blocked or delayed in the first quarter of 2026, and an Economist/YouGov poll in late August finding 63 percent of Americans would oppose a data center in their community.

Cluster of houses with a blank sign, illustrating local opposition to a data center project

We have followed the specific fights as they land. San Francisco's moratorium is ironic given the city's tech roots, the New York pause tied to Hochul and Ocasio-Cortez is framed as a study period, and protests against an Amazon site in Thane, India show the same dynamic abroad. State legislatures are acting too, as in our summary of the California data center and AI infrastructure bills.

TechCrunch's Rebecca Bellan was skeptical that moratoriums will have lasting effect, since many last one or two years and the facilities would not come online for years anyway. Ha countered that backers clearly look worried. Both readings can be true: delay raises cost even if it does not kill projects.

What this means for builders and buyers

You may not site data centers, but their availability sets what you pay and wait for.

• Capacity risk is rising. More moratoriums and more scrutiny mean slower, costlier compute. Our look at China's 24 GW versus the US 56 GW of compute shows why labs argue speed matters.
• Expect more disclosure. If you follow a local project, expect energy and water reporting and public meetings to become standard asks.
• Watch for contractor loopholes. If a project in your area is being discussed, ask who has signed what, not only whether the company has a policy.

How to check a local data center proposal

A practical checklist for residents, journalists and officials:

1. Ask the county or city clerk whether any confidentiality agreement exists for the project and who signed it.
2. Request the public-records trail for tax abatements, utility service agreements and zoning applications.
3. Check whether the developer is a contractor or shell entity rather than the eventual tenant.
4. Compare the company's published commitments, such as water reporting, against what the permit actually requires.
5. Note which claims are self-reported, as Amazon's water use and generator run time figures are.

Limits of this report

This post relies on press coverage rather than Amazon's original text. Implicator describes its summary as AI-generated and editor-reviewed. The Equity discussion is opinion by journalists, not new reporting. Where outlets differ, such as on exactly what Microsoft agreed to, we have shown both versions rather than choosing one.

Related reading

• Senate investigation: hyperscalers and AI data center costs
• San Francisco's data center moratorium
• New York data center moratorium explained
• Amazon data center protests in Thane, India
• California data center and AI infrastructure bills
• China 24 GW versus US 56 GW compute
• Sources: TechCrunch, Implicator, Fortune

Details reflect press coverage as of October 11, 2026 and may change as Amazon, Microsoft and lawmakers publish more.