Privacy Policy

Last updated: June 15, 2026

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 activeTab permission. 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.
• Saved redactions (optional, off by default): in the live editor you can choose to save the redactions you place on a page so Snappy reapplies them automatically when you revisit it. Snappy stores the rules — the page address and which elements you hid, plus the style (blackout, pixelate, or blur) — in local browser storage on your device only. They are never uploaded. You can review or remove saved pages anytime from the gallery's "Saved redactions" tab, remove individual redactions in the live editor, or turn the whole feature off in settings.
• Images you save are written to your Downloads folder and are entirely under your control.

Settings

Your editor preferences (watermark text, colors, export format), your gallery choice, and any saved redactions 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, performs full-page auto-scroll, and opens the on-page live editor, only on the tab you acted on.
• 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 navigation items to the toolbar icon's right-click menu, plus one page item ("Snappy: edit this page live") that opens the live editor on the current tab. The item reads nothing from the page.
• 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.
• favicon: shows each site's icon next to your saved redactions in the gallery, read from Chrome's local icon cache. No network request — nothing is fetched from any server.

Optional permission: saved redactions

The saved redactions feature is the one optional thing that asks for broader access, and only if you turn it on. To reapply your redactions when you revisit a page, Snappy needs permission to run on the sites you visit (Chrome phrases this as "read and change your data on all websites"). Snappy requests this only when you first turn the feature on, uses it solely to reapply the redactions you saved, and still sends nothing anywhere. You can turn it off at any time in settings, which revokes the access; your saved rules stay on your device until you delete them.

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.