Google Nebraska Data Centers Water and Electricity Use Exposed by Improper Redaction

Bottom‑line: leaked figures show Google’s Lincoln data center draws 52.65 MW at peak and 13.3 million gallons of water per year, and the state’s redaction rules are being questioned.

What the leaked numbers actually are

  • Electricity: Agate LLC (Google’s Lincoln data center) reported 52.65 megawatts of peak electrical demand.
  • Water: The same report listed 13.299 megagallons of water used for cooling towers, evaporative systems and site operations – roughly 13 million gallons per year.
  • Contextual scale: 13 million gallons equals about 20 Olympic‑size swimming pools and is under half of the total water the City of Lincoln reported using on September 29, 2026.
  • Statewide totals: Six Nebraska data centers together reported 765 million gallons of water last year, enough for 1,159.93 Olympic‑size pools.
  • Largest consumer: Fireball Group LLC (Google’s Papillion site) reported 547.88 megagallons for 2025, dwarfing the Lincoln facility.
  • Tax refunds: Agate LLC expects a $55,822,472 tax refund for 2025; Fireball LLC expects $39,171,573.39; Westwood Solutions LLC (Omaha) expects $22,558,881.
  • Physical size: Agate LLC’s gross floor area is 288,530 sq ft – about five football fields.

"Using a computer cursor to highlight the redacted text box in the report to DWEE, then copying and pasting it into a separate document reveals the numbers." — Madison Pitsch, 1011 NOW

Why the redaction matters

  • Statutory basis: Google cited Nebraska statutes 81‑1527, 84‑712.05, and NAC Title 115, Ch. 2 to claim electricity and water usage were trade secrets.
  • Public‑record law: Nebraska’s Department of Water, Energy, and Environment (DWEE) requires annual reporting, but the statutes allow companies to withhold “trade‑secret” data, creating a loophole for opaque disclosures.
  • Governor’s executive order: Gov. Jim Pillen’s July 20 2026 order mandates self‑reporting of power‑grid and water impacts, yet the redaction defeats the order’s transparency intent.
  • Redaction failure: The incident shows that visual redaction (black boxes) without proper data sanitization can be reversed by simple copy‑paste, violating basic records‑management best practices.

"If copy‑and‑paste, a PDF parser, or OCR can recover the content, the document was never redacted." – @soltanov (HN comment)

How the numbers compare to other uses

Resource Google Lincoln DC City of Lincoln (Sept 2026) Typical Nebraska farm (average)
Water (annual) 13 M gal (≈20 pools) > 26 M gal (≈½ of city use) ~390 M gal (≈30× Lincoln DC)
Electricity (peak) 52.65 MW ~30 MW (city peak) —
  • Electricity footprint: @se4u estimated Google’s three Nebraska sites could power ≈290,000 homes, roughly one‑third of Nebraska’s residential demand.
  • Water footprint: @strstr noted 13 M gal ≈ 40 acre‑feet, comparable to irrigating ≈26 acres of corn – a tiny slice of the state’s agricultural water use.

Community reactions on Hacker News

  • Skepticism about significance: Several commenters (e.g., @tptacek, @pavel_lishin) argued the water amount is modest when framed against city or agricultural consumption.
  • Concern over transparency: @jimjimjim highlighted the procedural failure of redaction and suggested better records‑handling policies.
  • Broader environmental critique: @_heimdall and @fasterik warned that focusing on water or electricity alone distracts from the larger issue of AI‑driven data‑center expansion.
  • Comparative analogies: Users offered analogies ranging from Olympic pools to the water needs of a small town (~25,000 people) to illustrate scale.
  • Policy suggestions: @VikingCoder called for mandatory public reporting of Power Utilization Effectiveness (PUE) and water metrics for cloud providers.

What this reveals about Nebraska’s reporting regime

  1. Statutory trade‑secret carve‑outs enable companies to withhold data that is arguably of public interest.
  2. Improper redaction techniques (visual black boxes) are insufficient for protecting confidential information and can backfire, exposing the very data meant to be hidden.
  3. Public‑record requests remain a viable tool; 10/11 filed a request on Sept 30, 2026, prompting the leak.
  4. Executive‑order compliance is undermined when agencies accept redacted submissions without verification.

Implications for data‑center transparency

  • Regulatory reform: Tightening the definition of “trade secret” in the context of utility usage could force full disclosure.
  • Technical safeguards: Agencies should employ redaction tools that remove underlying text data, not just overlay black boxes.
  • Benchmarking standards: Industry‑wide metrics (e.g., PUE, water‑use intensity) would allow stakeholders to compare facilities objectively.
  • Public awareness: Clear, relatable analogies (Olympic pools, farm acreage) help the public gauge impact without sensationalism.

Takeaway for policymakers and the public

Improper redaction of Google’s Nebraska data‑center reports unintentionally disclosed concrete electricity and water usage figures, exposing gaps in state transparency laws and prompting a broader conversation about the environmental footprint of AI‑driven infrastructure.

Sources

Related