Why your input matters more than usual

Tidy Receipts runs entirely in your browser. Your receipts never reach our servers, which is exactly the point. The trade-off is that we cannot see what happened. We do not know whether the edge detection found your receipt, whether the contrast pass made faded thermal print legible, or whether the PDF that landed on your machine looked the way you needed it to.

For a normal web app, the people building it can lean on analytics, error logs, and session recordings to spot problems. For a privacy-first tool like this one, none of that exists. The only way we learn what is and is not working is by asking.

A short form, two clicks away

There are now two ways to reach the feedback form. A Feedback link sits in the navigation at the top right of every page. A Share feedback button also sits next to Download PDF in the result view, so it is visible the moment you have something to react to.

Both open the same short form. It takes under a minute and asks three things:

Did the tool successfully process your receipts?
What kind of receipts were they (thermal, printed, mixed)?
Anything that did not work, or that you would like to see added?

No account, no sign-in, and the contact field is optional. If you would rather not say who you are, leave it blank.

What we find most useful

If you do fill it in, the most useful things to mention are:

Receipt types that came out poorly (faded thermal, foreign currency, very crumpled)
Features you reached for and could not find
Anything that broke, with whatever detail you remember at the time

Bug reports that include the device and browser you were using are gold. Feature ideas are equally welcome, even if they sound far-fetched.

Thanks in advance for taking the time. Every reply genuinely shapes what gets built next.