Amazon Drops Government NDAs. Communities Still Need the Project File.

Amazon says it has stopped using nondisclosure agreements with the government agencies involved in its data-center projects. That is a useful concession to communities being asked to accommodate the infrastructure. It is also narrower than a promise that everyone can now see everything that matters. A ban on one kind of agreement does not, by itself, identify the end customer, publish a water forecast, explain a utility contract or release an older file. The significant question is whether residents receive usable information while decisions are still open, rather than after the project has become difficult to change.

The company's published Data Center Commitment pairs the NDA statement with promises of earlier community engagement and annual reporting of energy use, water use, efficiency and carbon-free energy. Those are statements of company practice and intended disclosure, not an independent audit of compliance at every site. The document does not establish a project-by-project public register or explain how every existing agreement will be treated. For a town evaluating a proposal, that leaves an immediate distinction to preserve: a portfolio-level commitment can support a conversation, but it cannot answer all the questions about the facility next door.

WIRED's October 2 reporting identifies a particularly important unresolved boundary. Amazon did not answer the publication's question about whether its promise also covers contractors. This matters because a developer or intermediary can be the party dealing with public officials even when a larger technology company is the eventual customer. The unanswered question is not proof that Amazon is evading its commitment. It is a reason to ask for the policy's reach in writing, including who is bound by it and who is responsible for communicating it to project partners.

The historical record in Arizona shows why knowing the customer's identity is more than curiosity. In July 2025, Arizona Luminaria obtained a county document naming Amazon Web Services in connection with Tucson's proposed Project Blue. County officials cited confidentiality restrictions, while some city officials told the publication they did not know which company was involved. The reporting exposed a basic mismatch: people participating in public decisions did not necessarily possess the same information about the proposed development. This is a historical account, not a claim that the project's ownership or customer arrangements remain unchanged today.

A subsequent Arizona Luminaria report, published in October 2025, described the NDA itself. The agreement named AWS and protected its identity for five years or until project completion, whichever came first. The reporting also described advance notice allowing the business to seek a protective order before a records disclosure. It included contrary current-position statements: developer Beale Infrastructure said it had no agreement with AWS, and Amazon described earlier due diligence. Those distinctions prevent an old document from becoming a false claim about a present deal. They also illustrate why a public-record trail needs dates and parties, not just a company name. That October report described Pima County's adoption of a requirement to disclose company names before a requested public-body approval or vote. Publishing a name eventually is different from publishing it before elected officials must commit land or approve a proposal. Our recommendation is to apply the same timing test to the information residents need to evaluate resource demands. Put an identifiable disclosure milestone ahead of the relevant decision. An open house held after the consequential choices have been made can inform people, but it cannot give them the same opportunity to influence those choices.

The dispute is not always as simple as a document legally prohibiting disclosure. ABC57 reported in September that South Bend council member Sherry Bolden-Simpson said questions about wastewater from the New Carlisle Amazon facility had gone unanswered because of NDAs. Councilman and chief of staff Troy Warner disputed that account's implication, saying no NDA prevented disclosure of public data and that utility information had been presented publicly. ABC57 also reported a proposed transparency ordinance. This report does not establish its later adoption or resolve the officials' disagreement. It preserves both positions because a claimed restriction and a legally effective restriction are different things.

For an operator, that disagreement is a practical warning even without a court ruling. If one official believes information cannot be discussed and another says it is already public, the communication process is not self-explanatory. A useful disclosure package should identify where the records are available, which information remains withheld and the reason for withholding it. It should also separate permission to answer an ordinary question from the process of making a formal records request. These are recommendations for making the commitment observable, not a legal opinion about the South Bend agreement or any particular public-records exemption.

Pennsylvania supplies a more specific governmental model. Its August 18 executive order makes data-center NDAs impermissible for agencies under the governor's jurisdiction and directs creation of a public permitting map. It also directs notification of annual energy-and-water reporting requirements beginning July 1, 2027. The listed information includes facility and parent-company identity, monthly energy consumption and sources, water consumption and maximum-day demand, and projected demand for the following year. The jurisdictional boundary matters: this is not a statement that every public official everywhere is covered. Nor does the order's publication prove that every directed implementation step is already complete.

The Pennsylvania reporting categories expose a weakness in arguments built only around national or companywide averages. A community needs to understand the proposed facility's demand and timing, not merely whether its operator is efficient across a larger portfolio. Maximum-day water demand and monthly consumption ask different questions. A projection for next year is also not a measurement of last year. Keeping those fields separate makes later comparison possible. For builders, the opportunity is to make the information understandable enough that a forecast can be checked against subsequent operation, rather than replaced with a new presentation when conditions change.

Delaware's legislative record provides another concrete comparison. Senate Bill 312 was signed and became effective on August 26, 2026. Its text covers state agencies, counties and municipalities in relation to data centers using, or capable of using, at least 100 megawatts. The definition of an NDA reaches beyond a document with that title to verbal or written understandings and confidentiality provisions. Prohibited contractual provisions are described as void and unenforceable. That is materially different from a voluntary corporate statement. It also has a defined size threshold, so it should not be summarized as a universal ban covering every computing facility.

At the federal level, Representatives Tom Barrett, Greg Landsman and Jamie Raskin announced introduction of the No Secrets for Data Centers Act on September 24. Introduction is not enactment. The sponsor-posted proposal reviewed here would make covered predispute nondisclosure clauses unenforceable in judicial and arbitration proceedings and restrict public incentives conditioned on secrecy. Its definition reaches facilities, or groups of facilities in aggregate, above 50 megawatts of rated capacity or projected peak load. Covered agreements include those involving a public official in that capacity or provisions concerning public funds, land or incentives. The document is a legislative proposal, not an existing nationwide rule.

The federal draft also preserves a route for confidential filings with utility regulators when the filing is not for receiving a public incentive. That qualification is worth reading alongside the headline. The policy problem is not solved by pretending that all information has the same sensitivity or purpose. Commercial confidentiality and public accountability can be addressed separately, with the protected category and decision-maker made explicit. The exception distinguishes regulatory submissions from other agreements. Whether that balance is the right one is a policy judgment, not something the bill's title establishes. The public-finance connection predates this week's announcement. A December 2025 review from the National Conference of State Legislatures described states pairing data-center incentives with employment, wage and energy-related conditions while debating restrictions on NDAs. That is historical context, not a current inventory of enacted laws. It helps explain why transparency is a business issue rather than merely a public-relations preference. When a project seeks public support, the relevant comparison includes the conditions attached to that support and the obligations being accepted. A promise of economic activity does not tell residents which commitments are measurable or what happens if they are missed.

Amazon is offering more than a change in confidentiality practice. Matt Garman's announcement says its Built Together framework will add more than $1 billion in community investment over five years. The described education component would cover financial gaps after other aid, with agreements being established and launch planned in the coming months. These are announced commitments and program plans, not a report that the full amount has already been spent or that every resident can enroll today. The commercial logic is understandable: a company seeking permission to expand has an interest in making the benefits visible where the infrastructure sits.

The strongest version of that bargain would let residents distinguish an investment announcement from delivery. For an education program, publish the participating institutions, eligibility, opening dates and actual participation. For efficiency assistance, distinguish promised funding from completed work and measured results. Those are suggested accountability tests, not claims about outcomes Amazon has already achieved. They also give the company a better way to demonstrate progress than treating every objection as a misunderstanding. Community benefits can be valuable in their own right while leaving legitimate questions about a particular site's water, power, land use or confidentiality unresolved.

Ending government NDAs is therefore a meaningful starting point, provided the practice matches the statement. The next useful evidence is quite specific: a clear contractor policy, an account of existing agreements, timely project-level disclosures and a record of delivered benefits. None requires residents to endorse every project in advance, and none requires a builder to abandon every legitimate confidential discussion. It requires putting public decisions on an intelligible record. For Amazon and its peers, a community should be able to assess the proposed bargain without first having to investigate who is making it.

LaunchPad positionJudge the new commitment by its contractor coverage, project-level disclosures and delivered community benefits, not by the announcement alone.