Verify it. Don't take our word for it.
If you screenshot client dashboards, internal tools or anything under NDA, a privacy policy is not evidence. Here is what you can actually check.
The test that matters
Install the trial with Little Snitch or LuLu running. Take twenty screenshots. Search them, copy from them, export them. You will not see a single outbound connection, because there is no code on that path that could make one.
The only two network operations that exist anywhere in the app are Check for Updates and licence activation. Both are buttons. Neither runs on a schedule, neither runs in the background, and both live on the same settings screen so you can see the entire network surface at a glance.
Run it yourself, in about ten minutes
- Install Little Snitch or the free LuLu, and let it start monitoring.
- Download the trial and open it. Grant the folder access it asks for and nothing else.
- Take twenty screenshots of whatever you like. Wait for text recognition to finish.
- Search them, open the overlay, copy text and images, redact one, export the library.
- Read the monitor's log, filtered to
Screenshot Inbox.
The log will be empty. The only entries you can produce are the two you have to press a button to trigger: Check for Updates, which reaches the update feed, and Activate, which reaches the licence API once. Both are named on the status page and neither has a background schedule to catch you out later.
If you run this and see anything else, that is a bug of the most serious kind we have — tell us and it will be the next thing fixed.
What this means in practice
| Your screenshots | Cloud capture tools | Screenshot Inbox |
|---|---|---|
| Text recognition | Uploaded to a server | Apple Vision, on your Mac |
| When recognition is imperfect | Retried in the cloud | Stays local. No fallback, ever. |
| Sharing links | Images live on their servers | No sharing service exists |
| Analytics & crash reporting | Usually on by default | None. Not even opt-in. |
| Where your library lives | Their format, their cloud | Image files in a folder, plus SQLite |
| Getting your data out | Export tool, if there is one | One click: images, text, metadata |
What data exists, and where
Enforced by the build, not by intention
The commit gate rejects any change that adds a network call to the core module, adds a third dependency, or introduces a force-unwrap that could crash on your library. The whole app depends on exactly two outside packages, and neither talks to a network. That is not a policy somebody could quietly relax — it fails the build.
If plaintext on disk is still too much
There's an optional setting that encrypts the recognized text and word boxes with AES-GCM, keyed to your Mac's Keychain. Searchable prefixes are stored only as keyed hashes, so search keeps working.
It's off by default, and the settings screen tells you what you give up: an encrypted index is no longer the inspectable SQLite file described above. If the key is ever lost, your images are untouched and the app offers to rebuild recognition rather than silently writing fresh plaintext next to the encrypted rows.
What is not covered. The encryption option is narrowly scoped to the recognized-text index. Your screenshot images and the derived type and entity metadata sit outside it. We would rather say that here than let you discover it later.
About this page
This page loads no webfonts, no analytics, no embedded video and nothing from a CDN. A privacy page that phones out to a font host would undermine the only claim it exists to make. Nor is that special treatment for this page: no page on this site runs analytics or sets a cookie, which is why you have not been shown a consent banner. The cookie policy says how to verify that in your own browser, and the privacy policy covers the rest.