We'd love to hear from you.
Whether you've found a bug, want to report a problem with an ad, or have a question about our privacy practices, the best way to reach us is by email.
If you can think of a free browser tool you would like on ToolsAre.Us, use the suggestion form. Include your name, email, and what the tool should do — we will try to build useful ideas and get back to you.
To help us respond quickly, it's useful to mention:
We read every message and aim to reply within a few business days.
This is a small independent site run by one person, not a support department, so please read the following as a description of what actually happens rather than a service-level promise. Every message is read. Most get a reply within a few business days, and messages that arrive over a weekend or a holiday will naturally take longer.
Messages are worked through roughly in this order: anything that looks like a security problem, then clear reproducible bugs in a named tool, then questions about privacy and data, then feature ideas and general correspondence. A well-described bug in a specific tool tends to get answered quickly because it is actionable; a message saying only that something “does not work” usually needs a round of questions first, which is slower for both of us.
Almost every bug report that gets fixed the same day contains the same handful of details. If you can include these, you will save a round trip:
toolsare.us/imgcompress/. Several tools do overlapping jobs, and the URL removes any ambiguity about which one you mean.F12, choose the Console tab, reload, and copy any red text. This is optional and often decisive.Please do not attach the file that caused the problem unless you are comfortable sharing it. In most cases the file is not needed — a description of its type, rough size and origin is usually enough, and if the actual file turns out to be necessary we will ask.
If you believe you have found a security issue — a way to read data belonging to someone else, a cross-site scripting hole, an exposed endpoint, anything of that kind — please email rather than posting publicly, and say clearly in the subject line that it is a security report. Include enough detail to reproduce it. Reports of this kind go to the front of the queue.
Please do not run automated vulnerability scanners against the site. They generate a great deal of traffic on a small server, they are indistinguishable from an attack in the logs, and they rarely find anything a careful manual look would not.
Most tools here process everything on your own device and never send your content anywhere, so in the majority of cases there is simply no personal data held about you to request or delete. The exceptions are the tools that create share links — shared countdowns, RSVP lists and Watch Together rooms — which necessarily store something on a server so that other people can open the link.
If you want data associated with one of those removed, email with the share link or room identifier and it will be deleted. The privacy policy sets out in more detail what is collected, what advertising partners receive, and how the cookie consent choice works.
If an advert looks inappropriate, broken, or misleading, please email the page address and a screenshot if you can capture one. Adverts are served by a third-party network rather than chosen individually here, so a specific report is the only practical way to get one investigated. You can also change your cookie consent choice and use your browser’s own controls, both described in the privacy policy.
Email sent to the address above is read by one person and is not added to a mailing list, sold, or shared with anyone. It is kept only for as long as it is useful to keep — typically until the issue is resolved, and longer for bug reports that describe a problem still on the list to fix. If you would like your message deleted after it has been dealt with, just say so in it.