HushshotPrivacy policy
In short: Hushshot collects nothing. It has no account, no analytics, no crash reporting and no servers. Your captures stay on your computer.
What the extension does with your data
- Captures (images of the pages you choose to capture) and the text read from them are stored in the extension's own storage inside your Chrome profile. They are never sent anywhere. Delete a capture from its result page, or remove the extension to delete them all.
- Settings are stored in the same place.
- Files you download (PNG, PDF, JPEG, WebP, text) are saved by Chrome to your Downloads folder.
- Text recognition runs on your computer with a model that ships inside the extension.
Network requests
The extension makes no network requests. Its code, libraries and the text-recognition model are all bundled. It cannot load code from the internet: its Content Security Policy only allows its own files. Automated tests record every request made by every part of the extension and fail if any request leaves the computer.
Chrome itself may contact Google to keep extensions up to date. That is Chrome's behaviour, covered by Google's privacy policy, and not something the extension controls.
Permissions
Each permission and why it's needed is explained in PERMISSIONS.md. The extension has no access to any website until you click its icon or press one of its shortcuts on that tab. Sharp mode uses Chrome's debugger permission; Chrome's install dialog describes it broadly, but the extension only attaches it to the tab you're capturing, during the capture.
This website
This site is a set of static pages hosted on GitHub Pages. It uses no cookies, no analytics and no third-party scripts or fonts. GitHub, as the host, may keep standard server logs; see GitHub's privacy statement.
Changes and contact
If this policy changes, the new version will be published here and in the repository's history. Questions can be raised as an issue on GitHub.