Byte BungalowByte Bungalow

← Stories

Who's Really Behind 'Project Whisper LLC'? The Paper Trail Is Public If You Know Where to Pull

Updated September 4, 2026

A company nobody's ever heard of just asked your county for a tax break on a project it won't describe. The application says something like Project Whisper LLC, and the people presenting it won't say who they work for. So I went digging into how every recent one of these actually got unmasked. And the surprise is that the shell company was never a locked door — it's a paper trail with a silly name on it.

The name on the application is your first clue

I assumed a trillion-dollar company trying to stay invisible would pick something forgettable. Regional Infrastructure Partners. Midwest Land Holdings. Something beige.

Nope. Google showed up in West Memphis, Arkansas as Groot LLC. Meta was Balloonist LLC in Wisconsin, Winner LLC in Fort Worth, Wurldwide LLC in El Paso, and Greater Kudu LLC in New Mexico. These shells get named like teams in somebody's fantasy football league.

And that's the assumption worth breaking. A shell company feels like a vault. It isn't. An LLC can't exist without filing paperwork with a state, and filed paperwork is public. The whole disguise depends on you never going to look. Which, fair — most people don't. But when reporters and county clerks did look, the same trick fell apart the same way, over and over.

Because a data center can't stay abstract. It has to buy actual land, ask an actual utility for power, and stand in front of an actual county commission asking for a tax deal. Every one of those touches leaves a record with a name or an address on it. The company controls one name — its own. It can't control the fingerprints.

Pull the thread: one name always shows up twice

Here's the method, and it's less forensic accounting than it sounds.

Start with the Secretary of State's business search in your own state — that's where the LLC had to register to do business. Write down everything on the filing: the registered agent, any manager or organizer named, every address, the formation date. Any one of those can be the thread.

In Arkansas, three separate shells were buying land for data centers in three different cities. Groot LLC, Willowbend Capital LLC, Forgelight Ventures LLC — different names, different towns. But state filings showed the same individual listed as manager on all three. Once reporting tied Groot to Google, the other two came with it. One name, three masks.

In South Carolina, Google slipped by letting two of its anonymous LLCs share an address on their filings. In Ohio, a mystery LLC proposing a data center turned out to have been incorporated by the same person — on the same day — as a confirmed Meta subsidiary building in Wisconsin. Same lawyer, same morning, two states apart. That's not a coincidence, that's a batch job.

Then widen out. County property records show who actually bought the land and for how much. Tax abatement paperwork gets filed with real signatures. Utility interconnection requests, water permits, even job postings for the site — each one adds a name or an address to your pile. You're not looking for a confession. You're looking for overlap.

And I'll be straight about the limit: if the trail dead-ends inside Delaware, you can stall. Delaware doesn't make LLC owners public, which is exactly why these shells are formed there. Sometimes the best you get from pure paperwork is 'probably.' The confirmed unmaskings almost always needed that second layer — the local records the project can't avoid touching.

If it's nothing bad, why the disguise?

This is the question under every comment section on every data center video, usually phrased with more teeth: they tell us we have nothing to fear if we have nothing to hide, then they sign NDAs.

The companies' stated logic, when they say anything at all, goes like this: if a buyer with more money than the state budget walks into a rural land market under its own name, every seller triples their price, and competitors learn where the next AI campus is going. When Texas reporters asked Meta directly why it uses shell companies, Meta declined to comment. So the official answer is mostly silence, and we're left judging the behavior.

And the behavior goes further than hiding a name. In Beaver Dam, Wisconsin, city officials signed a nondisclosure agreement that barred them from revealing their talks with Balloonist LLC — or even that the project existed. In Pine Island, Minnesota, city officials knew a data center was coming for two years before their own residents did. Two years of council members sitting across from their neighbors at church and the gas station, legally unable to say what was about to land next door.

That's where this stops being a corporate trivia game for me. The secrecy isn't aimed at Google's competitors. Functionally, it lands on the person whose well and power bill sit downstream of the decision, who finds out at the groundbreaking.

It is shifting, slowly. Microsoft announced this spring it would stop using NDAs with local governments on data center projects — though it kept them for land purchases. Public Citizen published a whole playbook urging states to ban officials from signing these agreements at all. But as of right now, in most places, the disguise is still legal, still standard, and still beatable by anyone with a laptop and a county records login.

The LLC is chapter one of a much deeper rabbit hole

Unmasking the shell answers who. It doesn't answer the questions that actually decide what your town just signed up for. Where do the gigawatts come from? Who builds the substation? What happens to everyone else's electric bill when the biggest customer in the state's history plugs in?

That's the rabbit hole Byte Bungalow lives in — following the wire from the anonymous application all the way back through the transformers, the turbines, and the rate cases nobody reads.

So if a Project Whisper just showed up in your county, or you just want to understand the machine being built around all of us: watch the video, and subscribe to Byte Bungalow on YouTube so the next one finds you.

Common questions

If these companies aren't doing anything wrong, why all the shell companies and NDAs?
Their stated reasons are land speculation and competitors — announce yourself as Google and every acre triples in price. But the NDAs go well past that: in Beaver Dam, Wisconsin, officials couldn't even confirm a project existed. And when Texas reporters asked Meta directly why it uses shells, the company declined to comment. Make of that what you will.
Where do I actually search to find out who owns an LLC?
Start with your state's Secretary of State business search — the LLC had to register there to operate. Note the registered agent, any named manager or organizer, every address, and the formation date. Then check county property records for who bought the land, and any tax abatement filings. You're hunting for overlap: a name or address that also appears on an entity already tied to a known company.
The LLC is registered in Delaware. Is that a dead end?
Delaware itself mostly is — the state doesn't make LLC owners public, which is why these shells form there. But the project can't stay in Delaware. It has to file locally for permits, power, and tax deals, and those local records carry names and addresses you can cross-reference. In Arkansas, one manager's name on three different shells connected all of them to Google.
Can town officials really be blocked from telling residents what's coming?
Yes. NDAs signed with shell companies have barred officials from discussing projects — in Pine Island, Minnesota, city officials knew about a data center for two years before residents did. Microsoft has since pledged to stop using NDAs with local governments, and groups like Public Citizen are pushing states to ban the practice, but in most places it's still legal.
Does it really matter which tech giant is behind it?
It changes everything downstream. Who's on the hook for grid upgrades, what water commitments mean, whether promises will be kept — a shell LLC with no assets is a very different negotiating partner than a company with one of the largest balance sheets on Earth. Communities that knew who they were dealing with negotiated differently than ones kept in the dark.
What are the early warning signs before anyone confirms a data center?
A vague code name on a rezoning or tax abatement application, a Delaware LLC nobody's heard of buying large acreage near transmission lines or a substation, officials suddenly going quiet citing confidentiality, and outsized requests for power or water capacity. Any two of those together are worth a records search.

Keep reading

Sources

  • isconsinwatch.org — Balloonist LLC = Meta in Beaver Dam (NDA signed Dec 2023 barred officials from revealing talks "or even the existence of the project"); Balloonist also in Menomonie (Feb 2024); Deg
  • hntrbrk.com — (fetch 403'd; facts taken from search-result summary) DB Stu LLC, proposing a data center in Mount Orab, Ohio, was incorporated by the same person (Gregorski) and on the exact same
  • arkansasonline.com — Google confirmed behind the West Memphis project originally developed by Groot LLC; ~$10B, ~920 acres, five large-scale buildings.
  • datacenterdynamics.com — Meta disclosed at an El Paso city council meeting as the company behind WurldWide LLC seeking ~1,000 acres of city land; ~$800M first phase; 35-year agreements, 80% city+county pro
  • tomsguide.com — Pine Island, Minnesota: city officials knew about a proposed data center for two years before residents, due to NDAs; Mason County, Kentucky: $10M offer for a doctor's 250-acre far

Byte Bungalow

I do the homework out loud.

If this is the kind of thing you want checked against the documents instead of the hype, the video's above — and there's a new one every week.

Subscribe on YouTube →

By Byte Bungalow. Home power and home tech, checked against the documents instead of the hype. Independent commentary; not affiliated with any manufacturer, utility, or builder named here. Not professional electrical advice.