Contact UsefulSpot

Use this page to get in touch about anything on the site. The messages that are most useful, roughly in order:

A tool giving a wrong result. This is the one worth writing in about. Include the input you entered, what the tool returned, and what you expected instead.
A bug. Something that doesn't load, a chart that renders off-screen, a button that does nothing, a layout that breaks on your phone. Naming your browser helps.
A suggestion for a new tool. Especially if it's something that can run entirely in the browser, the way everything here already does.
Press or business enquiries. Advertising, partnerships, and similar.

A note on what to send: because every tool on this site runs on your own device and nothing you type is transmitted to us, there is no log of your session to look up. That means a report needs to carry enough detail to reproduce the problem. A small, invented example that produces the same wrong answer is ideal — please don't send real spreadsheets, client data, or anything you'd rather keep private.

What Happens Next

Messages go to a single inbox that is checked in batches rather than watched continuously, so a realistic expectation is days rather than hours — longer over holidays. There is no support desk behind this form and no ticket number will come back to you.

Bug reports jump the queue. A clear report of a wrong result gets checked against the tool's own tests first, because a counting or charting error affects everyone using that page, not just the person who reported it. Feature suggestions are kept and revisited when new tools are planned, but many more arrive than can be built.

Not every message receives an individual reply. Every one is read.

If your question is about how the site handles data, cookies, or advertising, the Privacy Policy and Cookie Policy probably answer it faster than a message would. For background on how the tools work and why they run in your browser, see the about page.

Frequently Asked Questions

What should I include in a bug report?

The tool you were using, the exact input you entered, the result you got, and the result you expected. If it only happens in one browser, say which. Reproducible reports get fixed; 'the chart is broken' usually can't be acted on.

Will you build a tool I suggest?

Sometimes. Suggestions that fit the site — something that can run entirely in the browser and that people search for by name — are the ones most likely to get built. Requests arrive faster than tools can be written, so no promises.

Do you need my data to investigate a problem?

Usually not, and please don't send anything sensitive. A short, made-up example that reproduces the same wrong result is more useful than a real spreadsheet, and it keeps your data on your device where it belongs.

How long does a reply take?

Messages are read in batches rather than continuously, so expect days rather than hours. Bug reports are prioritised over everything else. Not every message gets an individual reply, but every one is read.

Is there an email address instead of a form?

The form is the way in. It routes messages to one place and cuts out the spam that a published address attracts, which means genuine reports actually get seen.