Amazon Says It Has Stopped Using NDAs in Data Center Talks

Amazon says it has stopped using nondisclosure agreements in its outreach to residents about data centers. For a community weighing one of these projects, that removes a potential obstacle to talking openly about the plans. It does not yet tell residents how much electricity a proposed facility would need, what water demands to expect, or whether public money would help pay for the deal.

Those questions reach well beyond the property line. A data center can bring construction work and local revenue, while also requiring land, utility service and infrastructure that other people depend on. Residents need a chance to examine those trade-offs before officials commit to a project. Amazon’s announcement gives them a clearer opening to talk; the next test is what they can learn, and when.

What Amazon Has Said, and What Remains Unclear

A nondisclosure agreement, or NDA, restricts what the people who sign it can share. In a data center discussion, that restriction could prevent a resident or local official from bringing details to neighbors, comparing notes or seeking outside advice. Dropping NDAs from resident outreach makes those conversations easier.

Amazon’s statement has a defined scope: NDAs in its data center engagement. It should not be read as a promise that every document connected to a site search, land negotiation or commercial contract will become public. The available account also does not establish how Amazon is handling any earlier agreements, or how consistently the change applies across projects. Those are questions for the company to answer, rather than gaps to fill with guesses.

Companies have reasons to protect some project information. Early site discussions may involve landowners, contractors and negotiations whose terms are unsettled. Publishing every preliminary number could make bargaining harder or leave residents arguing over a design that later changes. That is the strongest case for some confidentiality, and it deserves a hearing.

It also has limits. A proposed facility’s expected demand for power and water, its likely effects on local infrastructure, and any requested public incentives are central to the community’s decision. A resident cannot evaluate those costs and benefits from a promise that details will arrive after negotiations conclude. The practical question is where Amazon draws the line between information it protects while planning a project and information the public needs while it can still influence one.

The Questions a Community Can Actually Check

Start with electricity. A useful public forecast would explain the facility’s expected demand, how that demand might change as the site develops, and what work the utility expects to do to serve it. Peak demand and long-term growth are more useful to a household than a general assurance that power will be available. If upgrades are needed, residents and businesses will want to know who is expected to pay.

That last question cannot be answered by Amazon alone. A utility may have its own planning and approval process, and the details will depend on the proposed site. Residents would need to hear from the utility as well as the developer before judging possible effects on the grid or future costs. Amazon can disclose what it has requested and forecast; it should also identify which answers rest with someone else.

Water needs the same plain-language treatment. A projected annual total is useful, but it may conceal when demand would be highest. Residents would also need to know where the water would come from and whether the plan could change as the facility expands. It is to get a forecast for the project people are being asked to live beside, with its assumptions attached.

Then comes the public-money question. If a company seeks tax breaks, infrastructure spending or other incentives, officials should be able to put a value on the proposal and explain what the community expects in return. Amazon can make a case for jobs, investment and future revenue. Residents can ask how firm those projections are, when benefits would arrive and what happens if the project changes size. An open meeting helps only if the terms under discussion are available before the decision.

Pledges Need Addresses and Timelines

Amazon is also pledging $1 billion to host communities, Tom’s Hardware reports. That figure puts a sizable number beside the NDA announcement, but it gives an individual town little to budget around without further detail. Which communities qualify? Over what period would the money be committed? What would it fund, and who would decide?

A pledge can support work that residents value. It can also sit beside requests for incentives or infrastructure commitments whose local price tags have yet to be settled. Communities need the terms of both sets of commitments to compare them. The same scrutiny applies to promised jobs or other benefits: a forecast should say what it counts, when those benefits are expected and whether anyone will check later.

Timing makes every disclosure more useful. Consider two towns receiving identical estimates for power, water and public costs. One gets them while a project’s footprint and terms are still under discussion. The other gets them after the principal agreements are in place. The second town has information it can debate, but fewer opportunities to change the plan. Ending NDAs helps people speak; early disclosure helps them participate.

What Happens When the Forecast Changes?

Data center proposals can evolve between an initial pitch and a finished facility. That creates a straightforward accountability problem: residents may debate one set of estimates while officials eventually approve, or the company eventually builds, something different. A useful disclosure process would preserve the original forecast, publish updates and explain substantial changes. Otherwise, everyone can point to a number that was available at some stage, without agreeing on which number guided the decision.

That is also a fairer standard for the company than treating every early estimate as a guarantee. Forecasts have uncertainty. Labeling assumptions and updating them gives Amazon room to revise a plan while letting residents track the consequences. It gives local officials a record they can use when weighing a proposed benefit against a possible public cost.

For people who mainly encounter Amazon through a shopping app or cloud-backed services, the siting debate can feel remote. For a host community, it may involve the utility system, local land and public finances. Residents do not need access to every commercial negotiation to take part. They need the project-specific information that bears on their own costs and benefits, delivered while their questions can still change an outcome.

Amazon says residents can now discuss its data center outreach without an NDA standing in the way. At the next proposed site, the clearest measure of that change will be what they can discuss before anyone signs off.