🔒 Your Privacy Matters

Privacy Policy

We built SnapFlow to be powerful and private. Here’s exactly what we do and don’t do with your data.

📅 Last Updated: April 3, 2026

🌍 Applies to all users

📌 Chrome Extension v3.0.0

🛡️

Overview

The short version of everything below

✅ SnapFlow does not collect, transmit, or sell any personal data to any server or third party. All captures, recordings, and edits stay on your own device unless you explicitly choose to upload them to your own Google Drive account.

SnapFlow (“the Extension”) is a Chrome browser extension developed for screen capture, screen recording, image annotation, and Google Drive integration. This Privacy Policy explains how the Extension handles information in connection with your use of its features.

By installing or using SnapFlow, you agree to the practices described in this policy.

📦

Data We Collect

What information the extension touches and why

Data Type	Collected?	Where It Goes
Screenshots	Local only	Saved to your device or uploaded to your Drive on request
Screen Recordings	Local only	Saved to your device or uploaded to your Drive on request
Annotations / Edits	Local only	Processed in-browser memory only, not persisted externally
Extension Preferences (format, FPS, folder, toggles)	Local only	Stored in Chrome’s local storage on your device
Google Account Info (name, email)	Drive only	Only if you connect Drive. Displayed in the popup. Never sent to us.
Browsing History / Visited URLs	Not collected	Never accessed or stored
Personal / Financial / Health Data	Not collected	Never accessed or stored
Analytics / Crash Reports	Not collected	We have no analytics or telemetry whatsoever

🔑

Chrome Permissions

Why each permission is requested and how it is used

SnapFlow requests only the permissions it genuinely needs. Below is a plain-English explanation for every permission in the manifest:

activeTab Capture a screenshot of the currently visible tab when you click a capture button. Only triggered by your explicit action.

scripting Inject the annotation overlay and area-selection tool into the current page. Nothing is injected passively only when you use those features.

desktopCapture Required by Chrome to show the screen/window/tab picker when you start a screen recording.

tabCapture Capture the audio stream from the current tab when “Tab Audio” is enabled during recording.

downloads Save screenshots and recordings to your Downloads folder using Chrome’s built-in download API.

storage Save your preferences locally (e.g. chosen format, FPS, Drive folder). This data never leaves your device.

identity Handle the Google OAuth2 sign-in flow for Drive integration. Your credentials are managed entirely by Google we never see your password.

offscreen Process and mix video/audio streams (MediaRecorder) in a hidden background document. Required by Chrome MV3 for recording tasks.

notifications Show brief system notifications (e.g. “Recording saved”, “Upload complete”) as feedback for background actions.

debugger Used exclusively for the Full-Page screenshot feature it programmatically scrolls the page and stitches sections together. It is not used for any debugging or monitoring of your activity.

contextMenus Add a right-click menu shortcut so you can trigger captures faster without opening the popup.

clipboardWrite Copy a captured screenshot to your clipboard when “Auto copy to clipboard” is enabled. We only write to your clipboard we never read it.

ℹ️ All permissions are used only when you explicitly trigger a feature. The extension does not run background scripts that passively monitor your browsing, keystrokes, or any page content.

☁️

Google Drive Integration

How OAuth and Drive upload works

The Drive feature is completely optional. You can use all capture and recording features without ever touching the Drive tab.

When you choose to connect Google Drive:

You are redirected to Google’s standard OAuth2 consent screen.
We request only the drive.file scope the most restricted drive scope available. This means SnapFlow can only access files it created itself. It cannot read, browse, or modify any of your existing Drive files or folders.
We also request userinfo.email and userinfo.profile scopes solely to display your name and email inside the extension popup for confirmation that you are signed in.
Your Google OAuth token is stored locally by Chrome’s identity API. We do not store it on any server.
Files are uploaded directly from your browser to Google’s servers using the Drive REST API. The data does not pass through any intermediate server operated by us.
You can disconnect your Drive account at any time from the Drive tab in the extension popup.

⚠️ Google’s own Privacy Policy and API Services User Data Policy govern how Google handles data during the Drive upload process. Please review them separately.

🚫

Third-Party Sharing

We do not share your data with anyone

✅ We do not sell, share, rent, or transfer any user data to any third party for any purpose not for advertising, analytics, AI training, or otherwise.

The only external service SnapFlow communicates with is Google (for Drive uploads and OAuth and only if you explicitly choose to use the Drive feature). No analytics SDK, crash-reporting library, or marketing pixel is bundled in the extension.

The bundled jsPDF library is used locally for PDF export. It runs entirely in your browser and makes no network requests.

💾

Data Storage & Retention

Where your data lives and for how long

Extension preferences are stored in Chrome’s local extension storage (chrome.storage.local) on your own machine and are never synced to external servers.
Screenshots and recordings are either downloaded directly to your device or uploaded to your own Google Drive. Neither copy is retained by us.
In-memory data (annotation canvas, recording stream buffers) exists only for the duration of your session and is discarded when the tab or popup is closed.
Uninstalling SnapFlow from Chrome will remove all locally stored preferences. Any files already saved to your Drive or Downloads remain under your own control.

⚖️

Your Rights & Choices

You are always in control

Access & deletion: All data is on your device. You can clear extension storage via Chrome Settings → Extensions → SnapFlow → Clear storage. You can also simply uninstall the extension.
Drive disconnect: Open the Drive tab in the popup and click “Disconnect” to revoke access. You can also revoke access anytime via Google Account Permissions.
Permissions: You can disable specific Chrome permissions for this extension via Chrome → Extensions → SnapFlow → Details. Some features may stop working if a required permission is revoked.
Opt-out at any time: Simply uninstall SnapFlow from Chrome. This removes all local data the extension stored.

👶

Children’s Privacy

COPPA compliance statement

SnapFlow is not directed at children under the age of 13, and we do not knowingly collect any personal information from children. Since we do not collect personal data from anyone, this applies by default.

If you are a parent or guardian and believe your child has used the extension in a way that concerns you, please contact us using the information below.

📋

Changes to This Policy

How we notify you of updates

We may update this Privacy Policy from time to time to reflect changes in the extension’s functionality or applicable laws. When we make material changes, we will update the “Last Updated” date at the top of this page and may note changes in the Chrome Web Store listing or extension update notes.

Continued use of SnapFlow after a policy update constitutes acceptance of the revised policy. We encourage you to review this page periodically.

📬

Questions, concerns, or data requests

If you have any questions, concerns, or requests regarding this Privacy Policy or how SnapFlow handles data, please reach out. We aim to respond within 48 hours.

✉️

SnapFlow Support

Email: medkonxapps@gmail.com
Chrome Web Store listing: SnapFlow on Chrome Web Store