ABOUT PROTECT OUR POCONOS
Local Decisions Deserve Local Attention.
Protect Our Poconos is an independent, community-focused information and advocacy project tracking data center development, infrastructure and land-use decisions across Pennsylvania’s Pocono region.
This site exists to make it easier for residents to understand what is actually being proposed, what remains uncertain and when public decisions are being made.
WHY WE’RE HERE
Making local development easier to follow
Data center proposals, transmission projects and zoning decisions are moving across the Poconos, but the information behind them is often scattered across township agendas, utility filings, state records and local reporting.
Protect Our Poconos brings that information together so residents can follow projects as they develop, understand what stage they have reached and find the original records behind the facts.
We believe communities deserve clear information and a meaningful opportunity to participate before decisions with long-term local impacts are made.
HOW WE WORK
Follow the record
We rely first on official municipal records, government filings, project applications and utility documents, with reputable reporting used for additional context.
A proposal is not the same as an approval. Related infrastructure is not automatically evidence of a data center. A community report is not treated as confirmed simply because it is circulating locally.
When the public record changes, we update the site to reflect it.
INDEPENDENT & COMMUNITY-FOCUSED
No developer. No utility. No government agency.
Protect Our Poconos is not affiliated with the developers, utilities or government bodies whose projects and decisions appear on this site.
Our focus is the Pocono community, particularly Pike County and Monroe County, and the land-use and infrastructure decisions that may shape the region in the years ahead.
CORRECTIONS & UPDATES
Found something we should review?
Public records change, and we can get things wrong. If you find outdated information, a broken source or a new official document that changes something published here, please let us know.