Client dashboards, under NDA, on your own machine.
If your screenshots hold other people's data, most of this category is off-limits to you. This one was built for that constraint first.
The question your client's security review will ask
You screenshot a billing screen, an internal admin tool, a staging environment with real customer records in it. Then you need to find one of those again next month.
Every cloud screenshot tool solves that by uploading the images. That is not a trade you're permitted to make, and "their privacy policy says it's fine" is not an answer that survives a security questionnaire.
Screenshot Inbox makes no network calls in its capture, recognition and search loop at all. Not fewer, not encrypted, not anonymised — none. You can prove that from outside the app with Little Snitch in about five minutes, which is a much better answer than a policy document.
What you get
"How do I know the next version won't start uploading things?"
Fair, and the honest answer isn't a promise — it's that the commit gate rejects any change adding a network call to the core module, and rejects adding a third dependency. It fails the build rather than relying on anyone remembering. You can also simply not update: updates are user-initiated, never automatic, and an activated licence is perpetual, so a version you've audited keeps working indefinitely.
Before you evaluate anything else
Install the trial with a network monitor running and watch it do nothing. That takes five minutes and settles the only question that matters for your work — see Privacy for what to look for.
Try it on your own screenshots
Fourteen days, everything unlocked, no account and no card. Import the folder you already have on day one — that's what makes the trial a fair test rather than a demo.