By This Hour AI Desk

Amazon says it will stop using nondisclosure agreements when negotiating data-center deals with local governments, a reported change that goes to the heart of a growing dispute over how AI infrastructure is built and who gets to scrutinize it before commitments are made.

The significance lies less in the legal instrument itself than in the process it can shape. When a company and a public body negotiate behind confidentiality restrictions, residents may have limited visibility into proposals that could affect their community. Removing those restrictions could give local officials more room to discuss a project openly. It could also make it easier for people to ask questions before a deal is settled rather than after its essential terms have already been decided.

TechCrunch has reported that Microsoft made a similar change earlier in 2026. If both companies follow through consistently, the shift would mark a notable response from major technology groups whose data-center ambitions are closely connected to the expansion of AI services. Yet a pledge not to use NDAs is not, by itself, a guarantee that the most consequential details of a project will be clear, timely or understandable to the public.

Secrecy became part of the argument over infrastructure

The reported Amazon policy addresses a source of friction that has been attached to data-center proposals: the perception that negotiations have proceeded out of public view. Data centers are physical projects, often involving public agencies and local decisions. That puts the terms of disclosure at the center of the argument, not at its edges. For communities, the question is not simply whether a facility will be built, but what information is available while local governments weigh it.

TechCrunch describes secrecy as a contributor to backlash against AI infrastructure and says opposition has helped produce hundreds of proposed and enacted moratoriums in places ranging from New York to San Francisco. The supplied reporting does not identify each moratorium, distinguish proposals from enacted measures, or explain the individual factors involved in every case. The broad point, however, is that resistance has moved beyond isolated complaints and into formal debates over whether construction should pause or be constrained.

That context helps explain why companies may see confidentiality practices as a business issue rather than merely a legal preference. A project can require a sequence of permissions and local decisions. Public confidence in that sequence can influence its pace and its political durability. An agreement reached with limited public visibility may still be valid, but it can face a harder reception if residents conclude that key choices were made before they had a meaningful opportunity to understand or challenge them.

Conversely, openness does not require communities to accept a proposed facility. It changes the terms on which an argument happens. Residents who oppose a project may still object after receiving more information; supporters may still regard it as desirable. But a more visible process can make the grounds for disagreement clearer and force companies and officials to confront objections directly rather than treating disclosure as an afterthought.

What Amazon’s reported commitment appears to cover

The available account is narrowly framed: Amazon says it will no longer use NDAs in negotiations with local governments over data-center deals. That wording matters. It describes a policy regarding negotiations with public authorities, not a complete inventory of all documents, commercial arrangements or discussions connected to a project. It also does not specify how Amazon defines the covered negotiations, whether the practice applies everywhere, or how it will operate when multiple public bodies and private parties are involved.

Nor does the supplied material set out a publication standard. A company can refrain from asking a local government to sign an NDA without committing to release every document proactively, publish agreements at a particular point, or provide plain-language explanations of technical or financial terms. The practical value of the reported shift will therefore depend on implementation: what becomes public, when it becomes public, and whether the information is sufficiently complete for residents and elected officials to assess the proposal.

Amazon’s change should also be read as a response to an approval environment, not as proof that every concern surrounding data centers has been resolved. An approved contextual report describes Amazon’s position as part of a broader effort to answer objections over transparency, water, power costs and emissions. Those subjects point to the distinction between process and substance. Ending NDAs may address the process of disclosure; it does not itself answer disputes over the effects of a particular project or the commitments attached to it.

For that reason, the policy could become most meaningful in the mundane parts of local decision-making: when a proposal is announced, what documents can be reviewed, what officials can discuss publicly, and whether questions receive specific answers. Trust is unlikely to be restored by a declaration alone. It is more likely to be shaped by whether communities can see a proposal early enough to matter and test the claims made for it.

Microsoft’s similar reported step raises the stakes

Microsoft’s reported earlier move provides an important comparison. Two prominent companies dropping or declining to use NDAs in this context could signal that secrecy has become a liability in negotiations involving AI-related computing infrastructure. The supplied reporting does not provide details of Microsoft’s policy, its scope, or how closely it matches Amazon’s approach. It would be premature to treat the two measures as identical.

Still, parallel moves matter because local governments do not approach these negotiations in a vacuum. A practice adopted by one large company can influence what officials and residents come to expect from another. If non-disclosure restrictions cease to be routine in data-center talks, companies that continue to rely on them may face tougher questions about why. The comparison may also give local authorities more leverage to seek clearer terms from prospective developers.

There is a separate risk in presenting the change as an industry-wide transformation. The available material identifies Amazon and refers to Microsoft; it does not establish what other companies do, whether either policy is legally binding, or whether they will remain in place over time. “Others” in the broader discussion should not be mistaken for evidence that the entire sector has adopted a common disclosure rule.

The timing is also consequential. AI has raised the strategic importance of the computing facilities that support it, while concentrating attention on the local approvals required to build them. Companies can argue for the economic or security value of infrastructure, as Amazon has reportedly done in urging communities to support AI data centers. Local governments, meanwhile, must consider their own processes and public obligations. A less secretive negotiation model may reduce one source of conflict, but it cannot eliminate the underlying contest between corporate plans and local consent.

Transparency will be measured in records, not rhetoric

The next test is straightforward: whether the reported policy produces a materially more visible public record. Residents will be able to judge openness by what they can learn before decisions are finalized, not by whether a company says it has changed a negotiating practice. The relevant evidence would include the availability of terms, the clarity of commitments, and the opportunity for local debate while choices can still be influenced.

Local governments also have a role that Amazon’s policy cannot replace. Public agencies decide how to conduct meetings, release records and explain decisions. A company’s refusal to use an NDA may widen the space for disclosure, but it does not determine how an authority uses that space. The difference between a formally open process and an intelligible one can be large, particularly when the subject is technical infrastructure and negotiations may involve many moving parts.

For Amazon, the policy may be an acknowledgement that public legitimacy has become central to the buildout of AI infrastructure. For communities, it is an opening to press for more than a general assurance. They can seek the practical information needed to evaluate a specific proposal. For critics of secrecy, the key question is whether eliminating a barrier to discussion turns into a durable norm of earlier, fuller disclosure.

The report has not been independently corroborated. The available account comes from two TechCrunch pages that present the same core summary, one of them tied to a podcast episode, and neither supplied record includes the underlying Amazon policy language or details of Microsoft’s earlier action. As a result, the reported change should be treated as a significant claim about Amazon’s approach, but not as a complete account of how future data-center negotiations will proceed.

That uncertainty is not a minor qualification. It defines the story’s central limit. Amazon’s stated break with NDAs could improve the conditions for local trust, particularly if it results in earlier access to meaningful records. Whether it does so will depend on the policy’s scope, consistency and use in actual negotiations—and on whether the resulting transparency gives communities a real voice before data-center decisions harden into commitments.

For further context on this subject, see Amazon says it has stopped using NDAs in data-center approvals.

Reporting notes

What is confirmed: The supplied reporting identifies Amazon’s stated NDA policy and describes a comparable Microsoft action. It does not provide the policy text or implementation details.

Why this matters: The reported policy could make local AI-infrastructure negotiations more visible, but it does not by itself resolve objections to projects.

What remains unclear: The scope, geographic application and practical disclosure rules are not established by the available material, nor is the reported change independently corroborated. This report is based on one source and has not been independently corroborated.

Sources