Contact us
Corrections, permissions, advertising questions or just a fact we got wrong - this is where it goes.
The fastest way to reach us is by email:
We read everything and reply to most things within a few working days.
There is no contact form, and there is no newsletter sign-up hiding behind this page. One address, read by the person who writes the site.
What to include
- Corrections - the entry number (shown as #123 on each card), the page it appears on, and ideally a source we can check.
- Permissions - which text you want to reuse, where, and whether it is commercial. See the terms of use first, because short quoted excerpts with a link back are already allowed.
- Privacy requests - access, deletion or objection requests under GDPR, UK GDPR or CCPA. Put "Privacy request" in the subject line.
- Advertising - we serve ads through Google AdSense and do not sell direct placements, but we are happy to answer questions.
- Suggestions - a fact, a story or a quote you think belongs here. Tell us where it comes from.
Response times
We are a small team and this is not a 24-hour help desk. Confirmed factual errors are prioritised and usually corrected within a week. Everything else gets answered in the order it arrives.
If a correction is straightforward and you have given us a source, the page itself is usually updated before the reply is sent - so you may see the fix land first.
Reporting a copyright concern
If you believe something on this site infringes your rights, email us with the exact URL, the entry number, a description of the work concerned and your contact details. We investigate every notice and remove material where a claim is substantiated.
Photographs are used under the licences recorded on the photo credits page, which names the source and licence for every image. If an attribution there is wrong or incomplete, that is worth an email too, and it is quick to fix.
Reporting a security issue
If you have found a security problem with the site itself, email us with the URL and the steps to reproduce it, and please give us a reasonable chance to fix it before publishing anything. Machine-readable contact details are published at /.well-known/security.txt following RFC 9116.
For context: this is a static site. There is no login, no database and no account data, so there is nothing here holding personal information about you beyond the emails you choose to send us.
Writing for the site
Reader submissions have their own route: the propose a story page explains what makes a good entry, how long it should be, and what happens after you send it. Sending a story to the address above still works, but the guidelines there will save you a round trip.
Before you write
A quick look at the FAQ answers most questions about how the site works, where the content comes from and what you may reuse. How we source, check and correct entries is set out in the editorial policy.