Snapshot Studio
Privacy Policy
Last updated: 24 July 2026
All processing happens on your device. No data is transmitted or stored on our servers. Snapshot Studio has no backend, no user accounts, and no sign-in. It is completely free — there is no paid tier, no license check, and no payment of any kind — so it collects no personal information and makes no network requests at all.
What Snapshot Studio does
Snapshot Studio captures a screenshot of the page you choose — the visible tab, a region you drag, a full page (scroll and stitch), a device-size viewport (phone / tablet / laptop), or an image you paste or upload — then lets you redact sensitive information (blur, pixelate, solid block, or a freehand blur brush), annotate it (arrows, lines, boxes, text, numbered steps, spotlight, and more), beautify it (backgrounds, padding, rounded corners, shadow, a browser frame), and export it (PNG / JPG / WebP / PDF, or copy to the clipboard). Every one of these steps runs entirely in your browser. Redaction is flattened into the exported image, so the original pixels cannot be recovered from the saved file.
What we collect
Nothing. Snapshot Studio does not send any data off your device — not the images you capture, not your browsing history, and no analytics of page content. There are no accounts to create, nothing to sign in to, and nothing to pay for.
What is stored locally
Stored only on your device via the browser's local extension storage, never sent anywhere:
- Presets & templates — your saved beautify / watermark configurations and annotation templates.
- Preferences — your chosen language and light/dark theme.
- Screenshot history — the screenshots you capture are saved on your device (in the browser's local IndexedDB) so you can reopen, download, or delete them later. The newest 50 (up to 500 MB) are kept; older ones are removed automatically, and you can clear the whole history at any time from the editor. These images are never uploaded and never leave your device.
Nothing above is transmitted anywhere. Everything can be deleted from within the extension.
Permissions and why they are needed
activeTab— capture and read the current tab, and only after you click the toolbar icon or press the capture shortcut. It grants no standing access to your browsing.chrome.tabs.captureVisibleTabruns under this grant.scripting— inject Snapshot Studio's on-demand helper (region selection and full-page scroll-and-stitch capture) into the current tab when you invoke it.storage— save the local presets, templates, and your language / theme preferences above. (Screenshot history uses the browser's local IndexedDB, also on-device only.)debugger— used only for the optional "device viewport" capture, to reflow the current tab to a phone / tablet / laptop layout via the Chrome DevTools Protocol and screenshot it. It is attached briefly, only during an explicit device capture you start, and detached immediately afterward (Chrome shows a "started debugging" banner while it is attached). It is never used to read or transmit page data.
Snapshot Studio requests no host permissions at install time, so it cannot read or capture any site until you explicitly invoke it.
Third parties
Snapshot Studio shares no data with any third party, because it collects none. There are no analytics, advertising, or tracking services of any kind.
Children's privacy
Snapshot Studio collects no personal information from anyone, including children.
Changes
If this policy changes, the "Last updated" date changes and the new version ships with the extension update.
Contact
Questions about privacy: mahmoud.i.a1993@gmail.com