The simplest way to reach us is email: [email protected]
There’s no contact form and nothing to sign up for. Write the way you’d write to a colleague.
What to write about
Bug reports. Tell us which tool, what you did, what you expected and what happened instead. Please include your browser and device — for example “Chrome on Windows 11” or “Safari on an iPhone 13” — because many problems only appear on one of them. A screenshot helps a lot. If the problem involves a file you opened in a tool, describe it (format, rough size in pixels or megabytes) rather than attaching it, unless you’re happy to share it.
Corrections. If a number, a formula or a statement in one of our guides looks wrong, send us the page and what you believe is correct, ideally with a source. We check every correction and update the page when it holds up.
Tool ideas. Describe the task you keep doing by hand or in a spreadsheet and what a useful answer would look like. That is usually enough for us to judge whether it would make a good tool.
Partnerships and press. For collaborations, workshop or classroom use, or press questions, tell us briefly who you are and what you have in mind.
When to expect a reply
We read everything and usually reply within two or three working days. Bug reports that stop a tool from working get looked at first. We can’t promise to build every suggested tool, but every suggestion is read.
Please don’t send passwords, payment details or other sensitive personal information by email. We will never ask for them.