Last updated: June 15, 2026

💡 Privacy Commitment: SnapFlow Studio is designed to respect your data. The extension operates completely offline. All image processing, canvas operations, crops, and annotations occur directly on your local device. We never collect, store, or transmit your screenshots or personal data.

1. Overview of Data Practices

Unlike traditional screenshot extensions that upload your images to third-party cloud servers for rendering or sharing, SnapFlow Studio uses a local-first architecture.

• No Screen Capture Uploads: Your screenshots never leave your browser. All canvas styling (window mockups, shadows, mesh gradients, cropping, and annotations) is rendered locally on your machine using the HTML5 Canvas API.
• No Personal Data Harvesting: We do not collect, capture, or transmit personal details, email addresses, passwords, IP addresses, or browsing history.
• Local Workspace Settings: Any configurations you set (such as backdrop selections, custom padding size, or brand watermark text) and your license activation key are saved directly on your device using chrome.storage.local.

2. Browser Permissions We Request & Why

To operate as a screen capture and annotation suite, SnapFlow Studio requests specific permissions from your browser. Each permission is strictly used to fulfill this single purpose:

• activeTab Allows the extension to capture the visible viewport image of the page you are currently viewing when you click the capture button.
• tabs Allows the extension to read basic tab details (e.g., page title and tab dimensions) to coordinate canvas sizing and full-page scrolling.
• scripting Allows the extension to inject a temporary helper script into the active page to coordinate automatic scrolling. This scrolling is required to stitch multiple segments together into a single, high-resolution full-page screenshot.
• downloads Allows you to export your finalized mockups, annotated images, or batch ZIP archives directly to your system's default local Downloads folder.
• storage & unlimitedStorage Used to save your design preferences locally on your browser and cache high-resolution captures in IndexedDB to prevent memory leaks and browser crashes during multi-page capture sessions.
• notifications Sends a brief browser notification to alert you when a long full-page stitch or bulk URL capture has finished processing in the background.
• <all_urls> (Host Permissions) Needed to inject the scrolling script and execute viewport capturing on user-specified websites.

3. Third-Party Data Disclosures