A major company wants hundreds of acres, enormous electrical capacity, access to water, infrastructure assistance, and possibly years of tax relief.
Local officials begin meeting with the developer. Utility representatives calculate what the project will require. Economic-development staff discuss incentives. Lawyers exchange proposed agreements.
The residents who will live with the decision may know none of this.
They hear only a project name: “Project Delta.” “Project West.” “Project Tango.” The company behind it may be represented by a recently created limited liability corporation with no employees, public history, or recognizable connection to the eventual operator.
When residents ask questions, officials say they cannot answer because they signed a nondisclosure agreement.
By the time the company’s identity and the project’s full scale become public, land may already be under contract, infrastructure planning may be underway, and the government may have invested months of work in advancing the deal.
The public hearing still happens. But the public enters the process late.
This is becoming a defining problem in the nationwide expansion of artificial-intelligence infrastructure: communities are being asked to approve data centers before they are allowed to understand them.
The secrecy playbook
Large economic-development projects have used confidential negotiations for decades. Companies argue that secrecy prevents competitors from interfering, protects trade secrets, and stops land prices from rising before a site can be assembled.
Some confidentiality is legitimate. A government does not need to disclose proprietary server designs, cybersecurity systems, private land-negotiation strategies, or legally protected trade secrets.
But data-center secrecy often extends beyond those narrow concerns.
Developers may use:
Code names that conceal the nature or owner of a project
Shell companies that acquire land or submit applications
Nondisclosure agreements covering communications with public officials
Land options that secure control before public review
Redactions that conceal financial and infrastructure commitments
Closed economic-development negotiations
Claims of competitive sensitivity involving information with direct public consequences
The result is an information imbalance.
The developer knows what it wants. Government officials may know what it wants. Residents know only what the parties decide to reveal.
These are not ordinary warehouses
A data center can resemble an industrial warehouse from the outside, but its public effects are different.
Hyperscale facilities can require extraordinary and continuous electrical loads. They may need new substations, transmission lines, water systems, roads, emergency-response capacity, and large banks of backup generators.
The permanent workforce can be modest compared with the project’s construction cost and physical footprint.
That makes several facts essential before approval:
Maximum electrical demand
Expected water consumption
Source of the water
Responsibility for grid and utility upgrades
Effect on residential utility rates
Number and type of permanent jobs
Property and sales-tax exemptions
Emergency-generation capacity and emissions
Noise levels at neighboring properties
Plans for expansion
Decommissioning obligations
Financial guarantees if the project is abandoned
These are not trade secrets. They are the basic terms residents need to evaluate whether a project benefits their community.
Officials may be negotiating with a company they cannot name
In Norwalk, Iowa, officials worked with an unidentified national technology developer on a proposed 300-acre data-center district known as “Project West.” Local officials had signed a nondisclosure agreement while working with the developer and utility providers.
The public was asked to consider creating an overlay district intended to streamline approvals for a project that could take years to develop.
Residents could evaluate the proposed zoning language. They could not initially evaluate the company seeking its benefit.
Similar patterns have appeared across the country. A 2026 review described developers using newly created or obscure corporate entities to acquire property and submit applications while the ultimate company remained hidden.
In Arkansas, entities named Willowbend Capital and Forgelight Ventures reportedly represented projects later connected to Google. In Wisconsin, local governments negotiated data-center developments involving limited liability companies before the technology companies behind them were publicly identified.
The shell company may be perfectly legal. The question is whether government should make consequential public decisions without disclosing who will receive the benefit.
Nondisclosure agreements can distort public service
A private landowner can decide whether to sign a confidentiality agreement.
A public official has a different obligation.
Government officials hold information on behalf of the public and operate under open-meetings and public-records laws. They should not contract away transparency merely because secrecy is convenient to a prospective developer.
Some agreements reportedly require public entities to assert available records exemptions when responding to information requests. Others restrict elected officials from discussing a proposal while legislative or land-use decisions move forward.
That places officials in an impossible position. They are expected to represent residents while being contractually restricted from telling residents what they know.
It also damages public trust.
When officials finally announce a project, they may believe they are presenting an economic opportunity. Residents may see a decision that has already been made.
Microsoft’s reversal proves secrecy is a choice
In March 2026, Microsoft announced that it would stop using nondisclosure agreements with local governments for data-center development and work to terminate existing agreements.
The company acknowledged that it had used NDAs to protect commercial information and address security concerns during early project development. It then reached a more important conclusion: transparency with affected communities was more important.
Microsoft will continue protecting legitimate trade secrets and using confidentiality in private land transactions. It will no longer treat broad secrecy agreements with governments as the default.
That distinction matters.
Protecting a private negotiation is not the same as concealing a public commitment. A company can protect server-security specifications without hiding how much electricity it wants, whether residents will subsidize infrastructure, or how much tax revenue the community will forgo.
If one of the world’s largest data-center operators can abandon local-government NDAs, other developers can do the same.
Some governments are beginning to push back
Cuyahoga County, Ohio, released a Data Center Development Guide in June 2026 to help municipalities evaluate proposals before committing public resources.
County Executive Chris Ronayne warned that poorly structured projects can consume local power, water, and tax capacity without producing adequate jobs or revenue.
The guide encourages communities to investigate energy use, infrastructure costs, environmental effects, employment, and long-term public benefits. It also warns local officials against signing nondisclosure agreements, relying solely on developer-generated projections, or accepting verbal assurances about significant impacts.
That approach reverses the usual power relationship.
Instead of competing to offer the fastest approval and largest incentive, a local government defines its requirements before a developer arrives.
It decides what information must be public, what costs the developer must bear, and which promises must become enforceable obligations.
That is economic development conducted as public administration—not salesmanship.
Secrecy can produce worse deals
Officials sometimes argue that confidentiality is necessary to compete with other communities.
That argument assumes landing the project is the goal.
It is not.
The goal is securing a project whose public benefits exceed its public costs.
Competition can pressure local governments to accept the developer’s assumptions, shorten review periods, conceal negotiations, and offer incentives without independent analysis. Officials may fear that asking difficult questions will cause the company to choose another location.
But a project that cannot withstand public scrutiny may not be a project worth winning.
Secrecy can prevent residents, independent engineers, utility experts, environmental specialists, and financial analysts from identifying weaknesses before an agreement becomes difficult to reverse.
It can also protect exaggerated claims.
A developer may emphasize total investment and construction employment while saying less about permanent jobs, equipment-tax exemptions, transmission costs, water infrastructure, or the project’s effect on other customers.
The bigger the promised investment, the more scrutiny—not less—the public agreement deserves.
What should be public before a vote?
Before a governing body approves zoning, incentives, public financing, annexation, utility service, or a development agreement for a major data center, residents should receive:
The identity of the developer, landowner, operator, and parent company.
All corporate entities involved in acquiring land or requesting approvals.
The anticipated electrical demand at each phase of development.
Estimated daily and peak water use.
Every proposed tax exemption, rebate, credit, or public subsidy.
The expected number of construction and permanent jobs.
All publicly funded infrastructure obligations.
The method used to prevent costs from shifting to other utility customers.
Noise, air-emission, and emergency-generation studies.
Draft development, utility, and community-benefit agreements.
Independent fiscal and environmental analyses.
The identities of lobbyists, consultants, and law firms representing the project.
Any nondisclosure agreement signed by the government or its representatives.
A record of campaign contributions and gifts involving relevant officials, where required by law.
Sufficient time for public review before the final vote.
Documents should be published in a searchable format. Material redactions should identify the legal basis for withholding information.
“This is confidential” is not an adequate explanation.
Public hearings should occur before commitment
A legally compliant public hearing is not necessarily meaningful public participation.
If officials have already spent months advancing a project, negotiated key terms, directed staff resources, and publicly celebrated the investment, the final hearing may function as procedural closure rather than deliberation.
Meaningful participation begins before the government becomes committed to an outcome.
Residents should have an opportunity to shape:
The location
Project scale
Water and energy limits
Required setbacks
Noise standards
Tax terms
Infrastructure responsibilities
Monitoring and enforcement
Community benefits
Expansion conditions
Public participation does not mean every project must be rejected. It means approval must be informed and legitimate.
AI infrastructure needs public legitimacy
The country will build more data centers. Artificial intelligence, cloud computing, financial systems, hospitals, government agencies, and ordinary digital services depend on them.
The choice is not between technology and no technology.
The choice is between infrastructure developed with communities and infrastructure imposed on them through secrecy, urgency, and institutional momentum.
Local officials are not real-estate brokers for multinational corporations. They are fiduciaries for the public.
Their responsibility is not to land every deal. It is to ask whether the community can support the project, whether the promised benefits are real, whether the costs are fairly allocated, and whether residents had a genuine opportunity to influence the decision.
A company may need to protect a trade secret.
A government should never treat the public interest as one.
Sources: Microsoft’s decision to end local-government NDAs, Cuyahoga County’s Data Center Development Guide announcement, reporting on shell companies and secrecy in data-center land deals, and analysis of confidential data-center agreements.