Screenshot to Webhook Privacy Policy

Last updated: 2026-08-28

Screenshot to Webhook is a Chrome extension that captures a screenshot, lets you annotate it, and sends the result to a webhook URL that you configure. This policy explains what data the extension handles and where it goes.

Summary

Screenshot to Webhook has no accounts, no sign-in, and no servers of its own.
Screenshot to Webhook does not collect analytics, telemetry, or usage data.
Data leaves your browser only when you press "Send" or "Send test", and only to the webhook URL you entered.
Screenshot to Webhook never reads, modifies, or monitors the content of web pages. The only page information it reads is the URL and title of the active tab at the moment you click the toolbar icon (the activeTab permission), which is included in the webhook payload.

Data the extension handles

Data	When	Where it is stored	Where it is sent
Screenshot image	When you start a capture	`chrome.storage.session` on your device (memory only), removed as soon as the editor tab picks it up	Your webhook URL, only when you press Send
Annotations and notes	While you edit	In memory on your device	Merged into the image and JSON metadata sent to your webhook
Active tab URL and title	At capture time	In memory on your device	Your webhook URL, as `page.url` and `page.title`
Browser, OS, screen and viewport size	At capture time	In memory on your device	Your webhook URL, as `environment`
Webhook destinations: name, URL, payload format, authentication (token, API key or Basic credentials), custom headers	When you change Settings	`chrome.storage.local` on your device only; never synced	Authentication and custom headers are attached only to requests to that destination
Sent history: the annotated screenshot, note, pin notes, page URL and title, environment, destination name and the delivery result of each send	When you press Send (successful or failed)	IndexedDB on your device only; never synced; the newest 50 entries are kept. No authentication values or headers are stored	Nowhere, unless you choose Resend in the History tab, which posts that entry to the destination you pick

What we do not do

We do not operate any backend. There is no Screenshot to Webhook server that receives your data.
We do not sell, share, or transfer any data to third parties.
We do not use data for advertising, profiling, or creditworthiness.
We do not load remote code.

Third parties

The only third parties that receive data are the webhook endpoints you configure (for example Zapier, Make, n8n, or your own server). Each report goes to the one destination selected in the editor when you press Send. That service's privacy policy governs what happens to the data after delivery. Authentication values and custom headers you enter (such as API tokens) are stored on your device only and sent only to the destination they belong to.

Permissions

storage: save your settings and hold the screenshot while the editor opens.
activeTab: capture the tab you are looking at, and read its URL and title, only when you click the toolbar icon.
Host access to all URLs: required because your webhook can be on any domain. It is used solely for the outgoing request to that webhook.

Data retention and deletion

All data stays on your device. Remove individual sends or the whole log from the History tab in the options page, clear settings in the Destinations tab, or uninstall the extension, which deletes the chrome.storage.local, chrome.storage.session and IndexedDB data for Screenshot to Webhook. Data already delivered to your webhook is under the control of that service.

Children

Screenshot to Webhook is not directed at children under 13 and does not knowingly handle their data.

Changes

Changes to this policy are published at this URL with an updated date.

Contact

Questions about this policy: contact@megedit.com