Connect with us

NEWS

OpenAI Drops Data Center NDAs After the Midterm Rebuke

OpenAI will stop using NDAs with public officials at campuses it owns, two days after voters limited data centers in 40 of 41 local contests.

Published

on

OpenAI said on November 5 it will stop using non-disclosure agreements with public officials at future compute campuses it owns and operates. The ChatGPT maker bundled that pledge with a National Community Compact and a policy blueprint aimed at the rest of the industry.

The package landed two days after voters backed limits in 40 of 41 local contests on November 3. It covers a narrower slice of OpenAI’s computing footprint than the headline suggests.

What the Compact Leaves to Partners

OpenAI’s National Community Compact for future campuses is the baseline for sites the company both owns and runs. Each of those sites is supposed to get a local compact shaped by residents early enough to change the plans, a local contact for the life of the campus, and a public report every year.

The shared list is broader than the NDA line. OpenAI says it will cover electricity and the grid gear needed to serve a campus, put money aside so other utility customers are not stuck if a project shrinks or dies, publish water and power use, post construction and noise studies, and list the jobs it expects to create. It also says it will put money into priorities residents help pick.

The owned-and-operated limit is the hinge. A large share of the computing OpenAI uses is built and held by partners. Those halls can still be negotiated the old way unless those firms copy the compact, or unless lawmakers force them to.

WHAT WE KNOW

  • Who is bound: Future compute campuses OpenAI owns and operates, each with its own local compact.
  • NDA rule: No non-disclosure agreements with public officials, except narrow protections for security, trade secrets, and competitively sensitive information.
  • Already tested: OpenAI says it voided NDAs in Effingham County, Georgia, in July.

WHAT IS UNCONFIRMED

  • Partner sites: The documents do not put leased or partner-run capacity under the same compact.
  • Older paper: Outside Effingham, OpenAI has not published a full list of official NDAs it has torn up.

OpenAI calls the buildings “compute campuses,” a rename that does not change the load on the grid. Residents still meet a warehouse of servers, a substation, and a water plan. The compact is the process wrapper around that hardware, not a smaller machine.

Microsoft Ended Government NDAs in March

OpenAI is the third large operator this year to give ground on official secrecy, not the first. On March 18, Microsoft said it would end nondisclosure agreements with local governments and work through existing ones worldwide so they can be terminated. The firm still shields trade secrets and design details, and it still uses NDAs on private land deals.

Amazon followed on October 2. AWS chief Matt Garman wrote that the company will no longer use nondisclosure agreements with government agencies on its projects. He tied the line to a claim that more than 100 data center moratoriums were under consideration, and he rolled out community spending the same day. Rep. Jamie Raskin had just sent letters to Amazon, Google, Meta, and Oracle asking how they used these agreements with public officials.

We no longer use nondisclosure agreements with the government agencies we work with on our projects.

Matt Garman, CEO of Amazon Web Services, Amazon Data Center Commitment

Microsoft’s March note said it was hunting down active NDAs so local governments could be released. Amazon’s October line is written in the present tense and does not describe a clean sweep of older contracts. OpenAI’s November compact is written for future campuses it owns, with one named void in Effingham last summer. Three policies, three clocks.

THE NDA RETREAT THIS YEAR

  1. January 2026: OpenAI publishes Stargate community pledges to pay its own way on energy and to shape plans with local priorities.
  2. March 4, 2026: OpenAI signs the White House Ratepayer Protection Pledge with six other large tech firms.
  3. March 18, 2026: Microsoft ends NDAs with local governments and starts terminating existing ones.
  4. July 2026: OpenAI voids NDAs in Effingham County, Georgia.
  5. October 2, 2026: Amazon says it no longer uses NDAs with government agencies on data center projects.
  6. November 2, 2026: OpenAI launches its Grid Protectors Program, one day before Election Day.
  7. November 5, 2026: OpenAI publishes the National Community Compact and the Compute Campus Policy Blueprint.

The November wrap arrived after Microsoft had already moved, after Amazon had already moved, and after OpenAI had already cut the Effingham paper. Branding it as a new standard papers over that order.

The Power Pledge Is Eight Months Old

The compact’s loudest money line is that OpenAI will pay the full cost of electricity it uses and the infrastructure needed to serve its campuses, and that it will post financial assurances before major spending so other customers are protected if a project is delayed, reduced, or canceled. That is close to language OpenAI already signed in March.

The Ratepayer Protection Pledge, announced at the White House on March 4, is a voluntary promise by Amazon, Google, Meta, Microsoft, OpenAI, Oracle, and xAI to cover the generation and grid upgrades their data centers need instead of pushing those costs onto other customers. OpenAI’s compact says it signed that pledge and will pay incremental infrastructure costs plus the full cost of the electricity it uses.

So the November document is not the first time OpenAI promised not to stick households with its power bill. It is the first time that promise is bolted to a no-NDA rule, annual public reports, and a request that state utility commissions make the same math mandatory for every large customer. A voluntary pledge does not override a utility tariff. The blueprint is the attempt to put the pledge into a bill.

Before major spending, OpenAI says, it will post financial assurances so other customers are protected if a campus is delayed, cut, or killed. That stranded-asset piece is the part March’s one-page pledge did not spell out in public as a site-level insurance step. It is also the part local officials can test, because a bond or a parent guarantee either exists on a docket or it does not.

How 40 of 41 Local Fights Ended

The compact’s timing is not subtle. On November 3, voters favored limits on data center development in 40 of 41 local ballot measure contests, according to Ballotpedia, an elections tracker. The one exception was Harwood, North Dakota, where a proposal for extra review of industrial projects, data centers included, failed 325 to 105.

Ballotpedia counted at least 50 data center-related local measures in 2026 across 13 states, with 41 of those 50 set for November 3. Ohio alone accounted for 21 of the 50. Voters approved 27 measures that limited development or stated opposition, including five full bans, and they defeated 13 measures that would have helped projects or signaled support.

NOVEMBER 3 DATA CENTER VOTES

Place Question Result
Alhambra, California Prohibit data centers 84% yes (18,823 to 3,609)
Edgewater, Florida Prohibit new data centers 77% yes (7,784 to 2,328)
Wells, Maine 180-day moratorium 82% yes (5,818 to 1,282)
Granville, Ohio Prohibit data centers 82% yes (2,015 to 429)
Grove City, Ohio Voter approval for large loads 55% yes (11,317 to 9,411)
Harwood, North Dakota Extra industrial review 24% yes (105 to 325), failed

Grove City was the close one. Most of the rest were not. In Ashville, Ohio, a term summary meant to guide talks with EdgeConneX on two data centers was rejected 1,469 to 331. OpenAI’s Grid Protectors note went up on November 2, the day before those results. The compact went up two days after.

Paying the power bill and dropping official NDAs is the minimum a developer now has to put on the table in a town that just watched its neighbors ban the product. It does not rewind a ban, and it does not bind a partner who still wants a quiet docket.

The Carve-Out Covers Security and Trade Secrets

OpenAI’s NDA sentence is one clause with a hole in the middle. The company will not use non-disclosure agreements with public officials, it says, while still allowing “only narrow protections covering legitimate security information, trade secrets, or proprietary or competitively sensitive information.”

And we will not use non-disclosure agreements (NDAs) with public officials, allowing only narrow protections covering legitimate security information, trade secrets, or proprietary or competitively sensitive information.

OpenAI, National Community Compact, November 2026

Security and trade secrets are the easy cases. Building plans, camera layouts, and cooling design are not town-meeting material. “Competitively sensitive” is the phrase that can still swallow the numbers people show up to hear: peak load, water draw, tax abatements, and the date a campus actually connects. If a utility filing is sealed because a developer calls the megawatt figure sensitive, the compact’s transparency promise is a press release with a lock on the appendix.

Microsoft kept a similar pocket. It said it may still share confidential trade secrets or competitively sensitive information with local governments in limited cases, such as detailed design and security controls for permits, and still try to keep that material out of open records. Amazon’s one-line NDA drop does not define the leftover confidential bucket at all. The industry is converging on “no NDA” as a slogan and on “sensitive” as the working file.

The compact does require OpenAI to publish site-level water and electricity use, construction plans, and independent noise studies before operations begin and every year after. Those reports are the test. If the public tables show load and gallons, the carve-out is actually narrow. If they show indexes and ranges, the exception won.

Lawmakers Are Asked to Make the Rest Follow

The companion Compute Campus Policy Blueprint is the piece that treats the compact as a floor for everyone else. OpenAI says families should be able to count on basic protections whoever builds a campus, and that voluntary company pledges are only a starting point. The ask is for federal, state, and local rules.

WHAT THE BLUEPRINT WANTS WRITTEN INTO LAW

  • Who pays: State utility commissions would require large electricity customers to cover the grid costs they add and protect other customers if a project falls through.
  • Who can connect: Utilities would make it easier to hook up campuses that can safely cut demand when power is scarce.
  • What is public: Water, energy, noise, and hiring would be reported, and NDAs with public officials would face narrow limits.
  • Tax deals: Incentive terms would be public, with measurable commitments and a way to claw money back if a developer misses them.
  • Local work: Purchasing plans would go out early enough for local suppliers to bid, and hiring forecasts would feed trades and community colleges.

That list is how a company that has already promised to pay full freight tries not to be the only one doing it. If OpenAI’s owned campuses carry stranded-asset insurance and published water use while a rival still hides load behind an NDA and a cheap industrial rate, the rival wins the next county board vote on price and speed. OpenAI’s own language is that new policy is required to establish trust among communities, elected officials, and companies. Trust, in this draft, looks a lot like a mandate.

Congress is also asked to speed transmission upgrades and to restore and expand tax incentives for clean electricity. Those are builder requests, sitting in the same packet as the community ones. The compact is the neighbor-facing cover. The blueprint is the industry-facing ask.

School Meals for 14,000 Students in Effingham

OpenAI is already spending in two counties it uses as proof of the model. The compact cites $80 million for community priorities in Effingham County, Georgia, and $40 million in Pike County, Ohio. In Effingham, residents helped shape a $4.8 million grant for free school meals for all 14,000 students in the county, plus $2 million for a local park. In Pike County, families named childcare, and OpenAI and SB Energy, the energy firm on the project, made a joint $6 million pledge.

THE TWO COUNTIES OPENAI IS USING AS PROOF

  • Effingham County, Georgia: $80 million in community priorities, including $4.8 million for school meals and $2 million for a park; NDAs voided in July; Georgia Power can cut delivery by up to 1,000 megawatts at peak.
  • Pike County, Ohio: $40 million from OpenAI on top of an earlier SB Energy community agreement, including $6 million jointly for childcare.
  • Grid Protectors: A national program, launched November 2, for campuses to drop demand when the grid is tight, with batteries and on-site supply where the equipment exists.

The 1,000-megawatt Georgia Power arrangement is the compact in hardware form. The utility can take power back from the campus during high demand so homes keep air conditioning. OpenAI floated the same idea as national policy: connect faster if you can shut off when the system is stressed. That is a more concrete concession than a renamed campus.

Amazon’s parallel check is larger and thinner per site. Garman announced a $1 billion Built Together community program over five years for towns that host Amazon data centers, aimed at education, job training, energy bills, and water. OpenAI is writing smaller, named checks in the counties where it wants a local compact to look real. Neither pile of money moves a town that just banned the building.

The next test is not another press kit. It is whether the first annual reports show megawatts and gallons, whether partner-built halls stay off the compact, and whether a state commission takes OpenAI up on the offer to make full-freight power the rule for every large load, not only the campuses with the company’s name on the gate.

Harry is the editor of COVER 365, an independent publication he owns and runs, and a journalist of ten years who moved from reporting into editing. Anything the site reviews has been used before it is judged. A phone, a car, a game or a piece of travel gear is tested in ordinary conditions, its measured results are set against the maker's specification sheet, and where the two disagree the article says which one to trust and why. No product gets a verdict Harry has not earned by using it. Off the test bench, the same rule of primary evidence applies: business stories come from filings and results, science from the published paper, sports from the governing body's records, and news from statements and transcripts rather than second hand accounts. Coverage runs across technology, auto, gaming, lifestyle and travel as well as news, business, science, sports and entertainment, for readers in every part of the world. Every figure is checked before publication and corrected publicly under a stated policy when wrong. Reader mail is answered at support@cover365.in.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending