Climate ErrataIndependent, reproducible checks of climate papers, datasets and code

Policies and privacy

How Climate Errata handles findings, responses, corrections, personal data and requests. Last updated 22 November 2026.

Contents: Contact first · Author and producer responses · Corrections to our entries · Papers that use affected data · Discussion and moderation · Code of conduct · Funding and conflicts of interest · Use of AI · Privacy · Takedown and legal requests · Licence

Contact first

Author and producer responses

Corrections to our entries

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

Code of conduct

Funding and conflicts of interest

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.

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.