screencappy privacy policy

Last updated: August 15, 2026

The short version

screencappy collects nothing. There is no network code in the extension at all: no analytics, no telemetry, no accounts, no cloud storage, and no third-party services.

What happens to your screenshots

Your screenshots stay on your computer and are never sent anywhere. Captures, annotations, and capture history are stored locally in your browser (IndexedDB) on your own device. They are deleted when you delete them, when history pruning removes old captures, or when you uninstall the extension.

Settings

Your preferences (output format, filename template, and similar) are stored with your browser profile using your browser's extension storage. If you have browser sync enabled, your browser may sync these preferences between your own devices. This is browser functionality under your control; screencappy has no server involved.

Permissions

• activeTab, scripting: lets screencappy see and capture the page in the current tab, only after you click the button, press the shortcut, or use the context menu.
• downloads: saves exported images and PDFs to your computer.
• storage, unlimitedStorage: stores settings and local capture history.
• contextMenus: adds the right-click capture options.
• debugger (power build only): the version downloaded from GitHub declares this permission for its advanced captures. It attaches only while one of those captures runs, and your browser shows a banner the whole time. The store version does not include this permission at all, and requests only the six above.

screencappy asks for no access to any website. It cannot see any web page until the moment you ask it to take a screenshot, and that access covers only the tab you are looking at, only at that moment.

Changes

Any change to this policy will be published at this address, with the source history visible in the public repository.