Tell us what we got wrong

“A guide says X, but the rule changed”

This is the most useful message we get, and we would rather hear it from you than discover it six months later. Include the page, the sentence, and a link to the current source if you have one. We correct genuine errors quickly and update the review date on the page so readers can see it has been checked. Our editorial policy sets out how corrections are handled.

“A tool did not work in my browser”

Tell us the browser and version, the operating system, and what you were doing. If a file failed to process, its approximate size and format helps a great deal — very large images can exceed what a phone can decode, which produces a different failure from a genuine bug. We cannot see any error on our end, because the tools do not run on our servers, so your description is all we have to work from.

“Can you recover my invoice / my compressed image?”

We cannot, and it is worth explaining why rather than just declining. Every tool on this site runs entirely inside your browser. Your invoice draft is stored in your own browser’s local storage; your images are read into your device’s memory and never uploaded. We hold no copy of any of it. That is the point of building the tools this way, and the trade-off is that there is no backup on our side. Clearing your browser data deletes a draft permanently.

“What personal data do you hold about me?”

Almost certainly none, unless you have emailed us before. Send a request with “Privacy” in the subject line and we will confirm what we hold, correct it, or delete it. Requests under the GDPR or CCPA are answered within one month, as the law requires. The full picture is in our privacy policy.

“Can I write a guest post / buy a link?”

No, and this saves us both time. We do not publish guest posts, sponsored articles or paid links, and we do not use affiliate links. Everything on the site is written by the people who build the tools. Advertising enquiries about display inventory are welcome; enquiries about editorial placement are not.

“Will you build a tool that does Y?”

Possibly. The bar is whether it can run entirely in the browser without uploading anything, and whether it is something we would use ourselves. Tell us what you are actually trying to accomplish rather than the feature you have in mind — the underlying problem is often solvable in a way neither of us had thought of.