Editorial team
Alexander W.
My job is to translate the EPA's PFAS testing dataset into something a household can actually use — without alarmism, without oversimplification, and without claiming medical authority I don't have.
01What I do here
I write and review the editorial content on CheckPFAS — the explanatory articles, the per-page "what this means" copy on ZIP results, the FAQ, the methodology page, and the filter reviews. I don't generate the underlying water-quality numbers. Those come straight from the EPA's Fifth Unregulated Contaminant Monitoring Rule (UCMR 5) dataset, ingested unchanged, and reformatted for ZIP-code lookup.
When a reader sees a HIGH-risk verdict on their ZIP, the verdict is the EPA's; my job is making sure the plain-English explanation underneath accurately reflects what's in the data and what the science actually supports.
02What I don't claim
I don't hold a medical degree, a public-health credential, or a toxicology background. CheckPFAS isn't a medical resource — nothing here constitutes diagnosis, prescription, or treatment advice. If you've been drinking water with PFAS above the EPA limit for years and want a clinical evaluation, the right source is the ATSDR's PFAS clinical guidance and a conversation with your doctor.
What I do bring is editorial process: every claim about health effects is anchored to a primary source (EPA, NIH/NTP, ATSDR, IARC, or peer-reviewed journals), every regulatory claim is anchored to the EPA's published rulemaking text, and every filter recommendation is anchored to NSF/ANSI certification documentation. The process is documented in full on the editorial standards page.
03Corrections & contact
If you think a factual claim on the site is wrong, email me directly at [email protected]. Include the page URL and the specific claim. I review every correction request against the EPA source data and respond within 5 business days; confirmed corrections get a dated correction line on the affected page.
For general questions about the site or the methodology, use [email protected].