Amazon Drops Data Center NDAs, October 9, 2026: Notes for Corporate Governance

TechCrunch’s Equity podcast reported on October 9, 2026 that Amazon will stop using NDAs when negotiating data center deals with local governments. The report notes that Microsoft made a similar move earlier this year, and that secrecy has fuelled community backlash against AI infrastructure. Opposition has led to hundreds of proposed and enacted moratoriums, from New York to San Francisco. This note looks at what changed, why directors should care, and which controls and disclosures boards should consider.

What was announced

• Amazon says it will stop using NDAs in negotiations with local governments over data center projects.
• Microsoft made a comparable commitment earlier in 2026.
• The stated backdrop is community backlash against AI infrastructure, with hundreds of moratoriums proposed or enacted in places ranging from New York to San Francisco.

The Equity hosts discussed whether ending NDAs will really change how data center deals get done. That question is still open, and the report does not describe the details of Amazon’s policy, such as whether it covers confidentiality about the end customer, power arrangements or tax incentives. Readers should look for the company’s own statement for precise terms.

Why NDAs became a governance problem

Developers often use confidentiality agreements in early site selection to protect commercial plans and avoid land-price speculation. The difficulty is that data centers draw on shared public resources: electricity, water, land and tax incentives. When officials sign confidentiality agreements and residents learn of a project only after terms are set, the process looks like a closed bargain even if the project is lawful and beneficial.

Two related pieces of recent coverage on kurums.com illustrate how the issue is moving through legal channels. In our notes, we covered letters from Representative Raskin on data-center NDAs on September 30 and San Francisco’s data center moratorium on October 7. Together with Amazon’s and Microsoft’s decisions, they suggest that confidentiality in public-sector infrastructure deals is under scrutiny from companies, legislators and local governments alike.

What this means for boards and governance teams

Licence to operate is a board-level risk

A project that stalls because of a moratorium or a community campaign carries real financial cost: delayed capacity, stranded land and equipment commitments, and reputational damage. Directors overseeing capital-intensive businesses, whether they are cloud providers, utilities, landlords or large customers dependent on new capacity, should ask management how community acceptance is assessed before a site is committed.

Disclosure policy should be deliberate, not ad hoc

Amazon’s move shows that a blanket practice can be changed. Boards should know what their company’s default is for confidentiality in dealings with public bodies, who may approve exceptions, and what is disclosed to whom and when. A clear policy distinguishes legitimately sensitive commercial information from facts the public has a reasonable interest in knowing, such as expected power and water use.

Align public statements with contract practice

A company that announces community-friendly principles while still using broad confidentiality clauses invites criticism. Legal, government-affairs and communications teams should review how contracts, lobbying and public commitments fit together.

Consider supply chain and customer exposure

Companies that rely on third-party data centers or that fund them may be indirectly exposed. If a key provider’s expansion is delayed, your own AI or cloud roadmap may slip. Risk committees should include infrastructure permitting risk in scenario analysis.

A checklist for directors

1. Ask management to describe how confidentiality agreements with public bodies are approved and recorded.
2. Request a map of planned or pending sites facing moratoriums, hearings or organised opposition.
3. Check that public-facing sustainability and community commitments are consistent with what contracts permit.
4. Confirm that the legal team has reviewed local open-records laws, which can override or limit what an NDA can protect.
5. Make sure the audit or risk committee receives periodic updates on permitting risk and community engagement.
6. Ensure there is a plan for communicating with residents early, in plain language, when a project becomes public.

Counter-arguments and limits

It would be wrong to treat NDAs as simply illegitimate. Developers have genuine interests in protecting competitive information, and officials may themselves prefer confidentiality in early talks to avoid speculation. Ending NDAs does not by itself guarantee openness, and it does not resolve the underlying concerns about energy demand, water and local benefits that drive opposition. The Equity hosts’ question, whether this changes how deals are done, is a fair one. We would expect the effect to depend on what replaces the NDA: earlier public meetings, published impact assessments and community benefit agreements would be substantive; a change in paperwork alone would not.

The broader AI infrastructure backdrop

The same Equity episode covered several adjacent stories that show why infrastructure is under pressure. Lambda was reported to be raising $4 billion ahead of a planned IPO, with a single customer behind $35 billion of its backlog. The White House’s plans for a new “Super Intelligence Force” were discussed. And startups are pitching AI agents that would manage consumers’ inboxes and credit cards. Each depends on physical capacity that must be sited somewhere, and local acceptance is part of the cost of capital for all of them. The concentration of one customer behind a large share of a provider’s backlog is a reminder that demand and approvals both carry concentration risk, a point audit committees should note.

What to watch

• The published text of Amazon’s policy and whether it applies globally or only to U.S. local governments.
• Whether other large developers follow Amazon and Microsoft.
• State or local legislation that restricts confidentiality in economic-development agreements.
• Whether moratoriums are lifted, reshaped or extended in cities that have adopted them.

Bottom line

Amazon’s decision, following Microsoft’s, marks a shift in how the largest infrastructure builders handle their relationship with the public sector. For boards, the lesson is broader than data centers: secrecy that was once routine can become a source of regulatory and reputational risk when a technology’s footprint becomes politically visible. Directors should ensure their companies have a clear, consistently applied approach to confidentiality, a credible plan for community engagement, and reporting that lets the board see permitting and acceptance risk before it becomes a headline.

Questions shareholders and stakeholders may ask

Investors increasingly read environmental and community risk as part of the quality of governance. Large buyers of cloud capacity, insurers and lenders financing data center construction may ask whether a developer has a record of local opposition, whether approvals were obtained through transparent processes, and whether the project depends on incentives that could be challenged. A company that can show a clear engagement process and a consistent confidentiality policy is better placed to answer those questions credibly.

Employees and customers are another audience. Staff in sustainability, government affairs and legal teams are often the ones fielding questions from residents and journalists, and they need a defined position. Customers with their own climate or community commitments may also ask providers to explain how sites were chosen. Having documentation ready, including summaries of community meetings held and commitments made, shortens those conversations.

How the board agenda can reflect this

Practically, this does not require a new committee. It can be handled by adding a standing item to the risk or sustainability committee agenda: a short quarterly dashboard covering sites in development, the stage of local approvals, any organised opposition, and any confidentiality arrangements in force with public bodies. The aim is for directors to see problems early, when they can still be addressed by changing the engagement approach, rather than after a moratorium has been enacted. Where management proposes a new site, the board paper should state plainly what has been disclosed to the community and what has not, and why.

Lessons for companies outside the technology sector

Although the headlines concern hyperscale cloud providers, the governance lesson applies to any company that negotiates with public bodies: retailers seeking tax incentives, manufacturers asking for infrastructure upgrades, and logistics firms planning large facilities. In each case, agreements that are confidential by default can later be portrayed as backroom deals. Companies should review which of their public-sector agreements contain confidentiality terms, confirm that those terms are compatible with local public-records rules, and decide in advance what they would be comfortable publishing. Doing that review now is far cheaper than doing it under media pressure, and it gives the board evidence that the company manages this exposure deliberately.

Sources

• TechCrunch Equity podcast, “Amazon drops data center NDAs, and AI agents want your credit card,” Oct. 9, 2026.
• Kurums.com notes on San Francisco’s data center moratorium (Oct. 7, 2026) and Raskin letters on data-center NDAs (Sept. 30, 2026).

This note is general information for governance professionals and not legal advice.