Policies and privacy
How Climate Errata handles findings, responses, corrections, personal data and requests. Last updated 22 November 2026.
Contact first
- Every finding is sent privately to the authors, data producers or developers before it appears here.
- An entry is published only after they reply, the issue is already public (an erratum, a known-issues page, an open GitHub issue), or three weeks pass without a reply.
- If they ask for more time to check, we give it within reason and say so on the entry.
- Findings sent to us by others follow the same rule: we reproduce them first, then contact the responsible party.
Author and producer responses
- The responsible party's reply is recorded on the entry. We quote it with permission or summarise it, and send the summary to them to check before posting.
- If they disagree, the entry is marked Disputed and shows both views side by side. We do not remove a finding because it is disputed, and we do not keep a finding that the evidence no longer supports.
- Authors can reply on the entry's discussion thread at any time, or send a response for the entry itself through Write to us. We aim to acknowledge messages within a week.
- When a problem is fixed (a new version, an erratum, a release), the entry's status changes to Fixed with a link to the fix. Credit goes to the people who fixed it.
Corrections to our entries
- If we get something wrong, we correct the entry openly. The change and its date are shown on the entry; entries are never silently edited or deleted.
- If a finding turns out to be wrong as a whole, the entry is marked as withdrawn and stays visible with an explanation.
- Anyone can point out an error in an entry, publicly on its thread or privately through Write to us.
- Earlier versions of every page are kept in the public change history.
Papers that use affected data
For a problem in a dataset, an entry may list papers whose abstract or text shows they use the affected data for the affected region and period. The list is a pointer for readers and authors, not a finding about those papers: the effect on each paper is not assessed, and many conclusions will hold. Papers whose authors we are in contact with are not listed until that exchange has had its three weeks. Authors can ask for a listing to be corrected or explained, and we do so promptly.
Discussion and moderation
- Questions, answers and discussion about any dataset, paper or entry are welcome.
- New error claims about someone's work go to the responsible party first, or to us privately. Comments that make a new, unreported error claim may be hidden until the responsible party has been contacted; they are restored afterwards.
- Comments that break the code of conduct, are off-topic or promotional, or share someone else's private information are hidden or removed. The maintainer makes moderation decisions; you can ask for one to be reviewed through Write to us.
Code of conduct
- Discuss methods and data, never people or motives. Assume good faith: errors are normal in science, and finding them is part of the work.
- Be specific: name the dataset version, the region, the period and what you did, so others can check it.
- No harassment, insults, threats or demeaning language about anyone, including authors who are not present.
- Do not post private correspondence without the sender's permission, or anyone's personal information.
- Disclose relevant interests when you comment on your own work or a competitor's.
Funding and conflicts of interest
- Climate Errata is run by Mark L. Morrissey, Ph.D., Professor Emeritus of Meteorology, School of Meteorology, University of Oklahoma (previously also at the University of Hawaiʻi). It has no funding and no sponsors, carries no advertising and earns no income.
- Over a long career the maintainer has worked with scientists at data centres whose products appear here, including NOAA's Climate Prediction Center and the GPCP and GPM teams at NASA. Entries about those products follow exactly the same process as all others.
- The maintainer writes books and a Substack on weather and climate, some of which discuss findings listed here. Entries are never held back or published to suit them.
- When an entry concerns work by a past collaborator, the entry says so.
Use of AI
The analyses behind the entries are carried out with an AI system (Claude, by Anthropic) under the maintainer's direction. The maintainer checks the methods and results and is responsible for every entry. Code and data needed to reproduce a finding are linked from the entry wherever possible.
Privacy
What we collect.
- Write to us form: what you enter (name, email, affiliation, message and the other fields). Submissions are stored by Netlify, which hosts the site, and emailed to the maintainer. Your email is used only to reply to you; it is never published or shared. A question you send is posted publicly only if you tick the box allowing it, and then without your name or email. You are credited by name on an entry only if you ask to be.
- Comments: comment threads are GitHub Discussions, shown on the site through giscus. To comment you sign in with GitHub, and your comment is public under your GitHub name. GitHub's privacy policy applies to that account and its data.
- Server logs: Netlify keeps standard web server logs (such as IP address and pages requested) to run the site. We do not use these to identify visitors.
What we do not do. No advertising, no tracking or analytics cookies, no selling or sharing of data. The site itself sets no cookies. The giscus comment box may store a sign-in token in your browser when you choose to sign in.
Services your browser contacts. The DOI pages look up paper and dataset details from Crossref and DataCite directly from your browser, so those services see the request. Comment threads load from giscus and GitHub.
Keeping and deleting. Form messages are kept as long as needed to handle them and the entry they concern. To see or delete what you sent us, ask through Write to us and we will delete it from the Netlify form store and the maintainer's mailbox. Your own GitHub comments can be edited or deleted by you at any time on GitHub.
Takedown and legal requests
Send any request to correct, remove or restrict content, including copyright or legal concerns, through Write to us and choose "A takedown or legal request". Say which page and which content, and why. We respond as quickly as we can and record the outcome on the page where appropriate. Requests to remove an accurate finding because it is unwelcome are not grounds for removal, but we will always add the requester's response.
Licence
Entries and site content are licensed CC BY 4.0; site code is MIT-licensed (see LICENSE.md). Comments remain their authors' own, under GitHub's terms.