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

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

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.

Screencappy requests no host permissions and cannot read any page until you invoke it.

Changes

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