Privacy Policy
Last updated: June 11, 2026
The short version: Snappy collects nothing. It has no servers, no analytics, no accounts, and makes zero network requests. Everything happens on your device.
What Snappy collects
Nothing. Snappy does not collect, transmit, sell, or share any data of any kind.
How your screenshots are handled
-
Screenshots are captured only when you explicitly trigger a
capture (toolbar click or keyboard shortcut), using Chrome's
activeTabpermission. Snappy cannot see any tab at any other time and has no access to your browsing history. - All captures are processed entirely on your device.
- By default, only your most recent capture is retained, in local browser storage, so the editor can display it. Each new capture overwrites the previous one. Quitting Chrome clears the most recent visible capture; the most recent full-page capture is overwritten by the next one or removed when you clear browsing data.
- Gallery (optional, off by default): if you turn on the gallery, Snappy keeps your recent captures (10, 25, or 50, your choice) in local browser storage (IndexedDB) on your device only. The gallery is never uploaded anywhere. You can turn it off, delete individual captures, or clear everything at any time from the gallery page or Snappy's settings.
- Evidence mode (optional, off by default): if you turn on evidence mode, Snappy draws a stamp on your captures showing the page URL, the capture date and time, and a "captured by" name you type in yourself. That name is a setting stored locally, the stamp is part of the image on your device, and nothing about it is transmitted anywhere. The optional integrity manifest bundles each download into a single .zip file in your Downloads folder, containing the image and a small text manifest.
- Verified "captured by" (optional): if you click Verify in Snappy's settings, the email address of the Google account your browser is signed in with is read locally through Chrome's identity API and used as the "captured by" value. This happens only when you click Verify, involves no network request by Snappy, and the email is stored locally with your other settings. It appears only on the stamps and manifests of your own captures and is never transmitted anywhere by Snappy.
- Images you save are written to your Downloads folder and are entirely under your control.
Settings
Your editor preferences (watermark text, colors, export format) and
your gallery choice are stored locally in your browser via
chrome.storage.local and never leave your device.
Permissions, explained
- activeTab: temporary access to the current tab, granted only at the moment you trigger a capture.
- scripting: shows the quick-actions card and performs full-page auto-scroll, only on the tab you captured.
- storage: keeps your preferences and your latest capture, locally.
- unlimitedStorage: lets the optional gallery hold full-resolution screenshots locally without hitting browser quota limits. Used only on your device.
- contextMenus: adds "Open Gallery" and "Open Editor" to the toolbar icon's right-click menu. Nothing is added to web pages.
- identity, identity.email: reads your browser profile's Google account email, locally and only when you click Verify in settings, so evidence stamps can carry a verified "captured by". No network request, no account access beyond the email address.
Changes
If this policy ever changes (for example, if a future feature requires new permissions), the change will be reflected here and in the Chrome Web Store listing before release.
Contact
Questions? Contact the developer through the Chrome Web Store listing's support tab.