Is a PFAS Reckoning Coming to Big Tech?

For years, conversations in Wisconsin regarding per- and poly-fluoroalkyl substances (PFAS) mostly centered on firefighting foam at airports, biosolids spread on farm fields, and legacy industrial sites in places like Marinette and Peshtigo. This spring, that conversation changed shape. With the signing of 2025 Wisconsin Act 200 and Act 201 on April 6, 2026, the state didn't just release long-delayed cleanup money; it fundamentally reset the liability and oversight landscape that any new industrial water user, including every hyperscale data center, now has to build into their planning from day one. If you work with a town board, a developer, or a community group weighing a proposed data center, here's what actually changed, and why it matters more than it might first appear.

What the new law does

Act 200 and Act 201 together direct roughly $125 million toward PFAS remediation and grant programs, and hand over expanded authority to the Wisconsin DNR. Three elements of that authority are worth watching closely if a data center is headed to your community:

The DNR can now sample more broadly. The new funding supports testing of wastewater, sludge, biosolids, and landfill leachate for PFAS; not just drinking water. Hyperscale data center facilities are often heavy water users, use PFAS-containing coolants or water-treatment chemicals, and operate cooling systems that discharge wastewater. Expanded state sampling authority means the wastewater leaving a data center campus, or the biosolids from a treatment plant that accepts it, is now directly within the state agency's monitoring reach in a way it wasn't a year ago.

Liability exemptions now protect passive receivers - but only some of them. The new law creates narrow exemptions from Wisconsin's Spills Law for municipalities, water utilities, farmers, airports, and fire departments who receive PFAS contamination passively (meaning they didn't cause it, but end up with it). This matters significantly to any town that is considering a data center's wastewater agreement, because it draws a line between the passive municipal receiver, who may now have some protection, and the active industrial discharger, who does not. A city counsel or town board needs to understand which side of that line their proposed agreement puts them on before a contract is signed.

The DNR has new capacity to investigate and remediate. Ten new positions and a functioning grant program mean the agency finally has the staff and the money to act on this authority. Enforcement that was theoretical is now becoming operational.

Why this is a reckoning, not just a regulation

Data center developers have spent the last several years trying to build a public narrative around efficiency: power usage effectiveness (PUE- measured by dividing total facility power by IT equipment energy), water usage effectiveness, and the incorporation of closed-loop systems. Those metrics matter, but they were never designed to answer the PFAS question, and until this spring, Wisconsin didn't have the regulatory infrastructure to ask it.

This has changed. A facility's cooling technology, its wastewater discharge permit, and its relationship with the local treatment plant are no longer operational details buried in a site plan. They are now the points where DNR's sampling authority, the state's Spills Law liability, and the newly-funded grant programs intersect. For a project sited near a karst aquifer, a shared municipal wastewater system, or agricultural land that receives biosolids, this intersection is not hypothetical.

What this means for the stakeholders

For town and municipal officials: Before signing a wastewater service agreement or development agreement with a data center operator, officials should gain an understanding of whether their community's status as a "passive receiver" actually applies to what they're agreeing to. An agreement that makes a municipality an active party to disposal decisions may forfeit the protections that Act 200 was designed to offer.

For developers: The era of treating PFAS as someone else's regulatory problem is over. The sampling data associated with cooling system chemistry, wastewater discharge, and any biosolids pathway should be part of the disclosure package you bring to a community, not something produced only after a regulatory inquiry.

For community groups and residents: The right questions to ask at a public hearing have shifted. It's no longer only the question "how much water will this use." It's also "where does the wastewater go, who tests it, and who is liable if PFAS shows up downstream."

For attorneys and consultants advising any of the above: This is a genuinely new area of practice risk and practice opportunity. The liability lines that Act 200 draws are narrow and specific. Getting a client positioned on the right side of them, before a facility is built rather than after offsite contamination is detected, is where the real value gets delivered.

The bottom line

Wisconsin didn't pass this legislation with hyperscale data centers in mind; this law was passed because communities like Marinette and Peshtigo spent years waiting for help that a locked trust fund couldn't provide. With the implementation of Act 200/201, the new authority and funding that the state now has applies to every industrial water user going forward, and hyperscale data centers are arriving in Wisconsin at the exact moment that this authority came online. Any stakeholder at the table, whether representing a town, a developer, or a group of concerned residents, should treat that timing as more than a coincidence.

This piece reflects legislative and regulatory developments through August 2026. As DNR rulemaking and enforcement practices develop under Act 200 and Act 201, the specific implications for data center wastewater and cooling system permitting are likely to continue evolving.