Are Confidentiality Agreements Limiting Data Center Growth?

When local officials sign non-disclosure agreements before discussing a proposed data center with their constituents, something fundamental about democratic accountability is at stake. That tension—between the legitimate business interests of hyperscalers and tech giants on one side and the public's right to know what's being built in their backyard on the other—is now landing in state legislatures across the country.

The outcome of those debates will shape where data centers get built, how fast, and at what political cost.

Why Confidentiality Agreements Became Standard Practice

Data center development moves fast and involves information that competitors would love to get their hands on. Site selection criteria, power consumption requirements, tax incentive thresholds, and even the identity of the end tenant—all of it can move markets, tip off rivals, or complicate negotiations if it leaks too early.

The NDA became a standard tool in the data center developer's kit not out of secrecy for its own sake, but because the economics of large-scale infrastructure deals are genuinely sensitive. A hyperscaler evaluating ten potential sites simultaneously can't afford to have a county commissioner casually mentioning to a local reporter that Amazon is looking at a parcel outside of town. Land prices spike. Competing jurisdictions poach the deal. Years of site work evaporate.

For their part, economic development agencies have long operated with a degree of confidentiality around major industrial recruitment efforts. This isn't unique to data centers—auto plants, semiconductor fabs, and logistics hubs have all landed under similar secrecy arrangements. The difference is scale and frequency. A state might land one auto plant a decade. Right now, data center proposals are arriving in waves, and the NDAs are coming with them.

When Secrecy Meets Public Infrastructure

Here's where it gets complicated. A data center isn't just a private building. It requires massive public infrastructure commitments—transmission upgrades, new substations, road improvements, and water access for cooling systems. In some cases, these facilities consume as much electricity as a small city. Dominion Energy has reported that data center load growth in Northern Virginia alone is adding gigawatts of demand to a grid that wasn't built for it.

When local officials sign confidentiality agreements before approving zoning variances, utility easements, or tax abatements, they're making consequential public decisions with information the public can't access. That's not just a transparency problem—it's a governance problem. Residents can't meaningfully weigh in on infrastructure that will shape their community's power grid, water supply, and tax base if the details are sealed behind an NDA.

The specific trigger for recent legislative attention has been proposals where elected officials—not just appointed economic development staff—were asked to sign binding confidentiality agreements. That crosses a line for many lawmakers. An appointed bureaucrat operating under confidentiality during recruitment negotiations is one thing. An elected representative being legally prevented from discussing a public matter with constituents is another.

What Legislators Are Actually Proposing

Several states are now considering bills that would limit when and how confidentiality agreements can be used in data center proposals. The approaches vary, but a few common threads are emerging.

Some proposals would prohibit elected officials from signing NDAs entirely, leaving confidentiality obligations to appointed economic development staff who can manage sensitive negotiations without compromising the accountability of elected representatives. Others would establish mandatory disclosure timelines—a project can remain confidential during active negotiation, but once a formal application for public permits or incentives is filed, the details become public record.

There's also growing interest in carve-outs: allowing confidentiality around genuinely proprietary information (the tenant's identity, specific technical specifications) while requiring disclosure of the material public commitments—how much power the facility will draw, what infrastructure investments the locality will need to make, and the full value of any tax incentives being offered.

The legislative instinct here is sound, but the execution matters enormously. Overly broad transparency requirements applied too early in the process would kill deals. A developer who has to publicly disclose a site before land acquisition is complete is a developer who will move to a more accommodating jurisdiction. That's not a hypothetical—it's happened.

The risk of poorly drafted legislation is that it doesn't actually increase accountability. It just relocates data center investment to states with fewer disclosure requirements, leaving communities with neither the transparency nor the economic development they were hoping for.

The Stakeholder Math

Understanding who wins and loses in this debate requires looking past the obvious positions.

Data center developers and their hyperscaler tenants have the most obvious interest in preserving broad confidentiality protections. But even within the industry, there's nuance. Established players with deep relationships in mature markets like Northern Virginia, Phoenix, and Dallas are less dependent on secrecy—their deals are often practically closed before a formal process begins. It's newer entrants and secondary markets where NDA protections matter more for competitive positioning.

Local officials are genuinely caught in the middle. They want the economic development—the jobs, the tax revenue, the infrastructure investment. But they're also accountable to constituents who are increasingly sophisticated about what large data center clusters mean for their power bills and grid reliability. Signing an NDA that prevents them from answering constituent questions about a 500 MW facility coming to town is politically untenable, regardless of the legal justification.

Community and ratepayer advocates have arguably the strongest substantive case for reform. When a data center secures favorable utility rates or drives transmission upgrades that get socialized across the rate base, those are real costs that real people pay—and they're being decided, at least in part, behind sealed agreements.

Utilities occupy interesting territory here. They need to plan for load growth years in advance, which requires early information sharing with developers. But they also operate under public utility commission oversight that has its own transparency requirements. The intersection of confidential data center development agreements and regulated utility planning processes is an area where current rules were not designed to handle this volume or velocity of development.

How the Industry Should Be Thinking About This

The instinct to defend existing confidentiality practices as broadly as possible is understandable but strategically shortsighted. Legislative backlash driven by high-profile cases where elected officials felt muzzled is a much worse outcome for the industry than proactively engaging on what reasonable disclosure frameworks should look like.

Several things are worth considering for developers and their public affairs teams operating in this environment.

Distinguish between negotiation-phase confidentiality and decision-phase confidentiality. The former is defensible and has clear precedent in economic development practice. The latter—where binding NDAs restrict elected officials during formal public decision-making—is the exposure point and the legitimate target of reform legislation.

Engage proactively with economic development agencies and legislative staff on what disclosure frameworks would actually work. The industry has real expertise on what information is genuinely competitively sensitive and what isn't. That knowledge should inform legislation rather than simply opposing it.

Recognize that community trust is becoming a material development factor. Markets where data center growth has outpaced community engagement—certain Virginia counties come to mind—are now generating the political friction that produces restrictive legislation. Front-loading community transparency, even voluntarily, is cheaper than managing a legislative fight.

The regulatory environment around data center development is tightening across multiple dimensions simultaneously: power procurement, water use, land use, and now information disclosure. Developers who build organizational capacity to navigate that complexity—rather than treating each new requirement as an obstacle—are the ones who will move faster in the markets that matter.

The confidentiality agreement debate is, at its core, a maturity test for an industry that has grown faster than the governance frameworks designed to manage it. Getting ahead of that curve is both the right call and the smart one.

[INTERNAL LINK: confidentiality agreements] [INTERNAL LINK: data center development] [INTERNAL LINK: community engagement]

For more insights on navigating the complexities of data center development, visit our marketplace at InfraSale Marketplace.

EDITOR NOTES

• Consider cutting the paragraph discussing the differences between auto plants and data centers, as it may feel like filler.
• Ensure that the internal links are relevant to the content and lead to appropriate pages.