Privacy Policy

This policy covers the SnapFlow extension for Google Chrome and Microsoft Edge and the SnapFlow official website. The extension and website have different data practices, described below.

SnapFlow stores screenshot records in the extension’s local IndexedDB. A record can include the screenshot image and thumbnail, capture type, source URL, page title, capture time, image format, dimensions, and file size. This information supports local history, preview, copy, download, and deletion.

• The selected interface language is stored in chrome.storage.local.
• Analytics consent and a random installation identifier are stored in chrome.storage.local only after analytics is enabled.
• Temporary capture-task state is stored in chrome.storage.session while SnapFlow coordinates a requested capture.

Screenshot content is processed locally for the capture requested by the user. The source URL, page title, and capture time are stored with the screenshot to provide source context and make local history easier to revisit and manage. SnapFlow does not continuously monitor browsing activity or collect browsing history in the background.

Anonymous product analytics are disabled by default. If the user actively enables them and grants optional access to the Mixpanel endpoint, SnapFlow sends only allowlisted events: feature event type; capture type; a coarse duration range; a standardized error code; screenshot action type; interface language; extension version; browser type; event time; and random installation and event identifiers.

Analytics does not include screenshots, thumbnails, URLs, domains, page titles, webpage content, clipboard content, downloaded files, user input, raw error messages, or stack traces. Disabling analytics stops future events, removes the local installation identifier, and removes the optional Mixpanel host permission.

SnapFlow uses browser permissions only for its current features.

• activeTab temporarily accesses the active tab after a user action to capture the page and read its URL and title.
• scripting injects packaged capture code when full-page or selected-area capture requires page interaction.
• offscreen performs local Canvas, Blob, cropping, stitching, thumbnail, PNG encoding, and IndexedDB work.
• sidePanel displays local screenshot history and actions.
• storage saves language, consent, and temporary task state.
• Optional https://api.mixpanel.com/* access is requested only after the user enables analytics and is not required for screenshots.

SnapFlow does not upload screenshots, thumbnails, source URLs, domains, page titles, webpage content, or local screenshot history to a SnapFlow cloud service. No account is required for screenshot functionality, and SnapFlow has no developer-operated backend for screenshot storage.

When analytics is enabled, Mixpanel receives only the allowlisted analytics data described above through its HTTPS Track API with IP enrichment disabled. Mixpanel may still process network information needed to receive and secure requests under its own policies. SnapFlow does not use Mixpanel Autocapture or Session Replay and does not sell or rent user data.

Local screenshots remain until the user deletes them or the browser removes extension storage, including when the user clears extension data, resets the browser profile, or uninstalls SnapFlow. Deleting a screenshot through SnapFlow removes that record, including its image, thumbnail, and metadata, from the local IndexedDB. SnapFlow does not provide cloud backup or remote recovery.

Analytics data already received by Mixpanel may remain according to the configured Mixpanel project settings and Mixpanel’s retention practices; SnapFlow does not state a fixed retention period that has not been configured and verified.

The current SnapFlow website is a static marketing and legal-information website. It has no account, contact form, website analytics, tracking pixels, advertising scripts, or embedded third-party content, and the site code does not set cookies. The hosting service may process ordinary connection and service logs as part of delivering the website; SnapFlow does not make unverified claims about those logs or their retention.

SnapFlow minimizes permissions and keeps screenshot processing within the browser extension environment. Optional analytics is sent to Mixpanel over HTTPS only after consent. No local storage method can be guaranteed to protect data from a person who already has access to the user’s device or browser profile.

This policy may be updated when SnapFlow’s features or data practices change. The date above will be revised when an update is published. Materially different processing will require updated disclosure and any consent required before it begins.

For questions about this policy or SnapFlow’s data practices, contact: