Why Your Browser Extension Should Never Collect Your Data
Browser extensions have a unique position in the privacy landscape. They run on every page you visit, see every request your browser makes, and can access sensitive data. That's why we built FlowPick with a strict zero-data-collection policy from day one.
The Problem with Extension Privacy
Browser extensions often request broad permissions. Some legitimately need them — a media sniffer needs to monitor network requests. But what happens with that data?
Common Privacy Concerns
- Analytics tracking: Many extensions embed Google Analytics or similar tools
- Data harvesting: Some extensions collect browsing history and sell it
- Third-party scripts: Ad SDKs and tracking pixels embedded in extensions
- Remote code execution: Extensions that load code from external servers
A 2020 study by Princeton University found that hundreds of Chrome extensions were harvesting browsing data and sending it to third-party servers. Users had no idea this was happening.
Our Approach: Privacy by Design
FlowPick is built differently. Here's what "zero data collection" actually means in practice:
No Analytics
We don't track how you use the extension. No event logging, no session tracking, no funnel analysis. We improve FlowPick based on GitHub issues and community feedback — not by surveilling users.
No External Connections
FlowPick makes zero network requests to our servers. The only network activity is:
- Downloading media segments from the website you're browsing (that's the whole point)
- Browser extension update checks (handled by the browser itself)
No Data Storage on Servers
Since we don't collect data, there's nothing to store. We have no databases, no logs, no user accounts. Your download history exists only in your browser's local storage and is cleared when you close the tab.
Open Source Verification
Don't take our word for it — verify it yourself:
- Review the source code on GitHub
- Monitor network activity using browser DevTools (Network tab)
- Check permissions in your browser's extension management page
- Use a firewall to confirm no unexpected connections
Why This Matters for a Media Downloader
A media downloader is particularly sensitive because it knows:
- What videos you watch: The URLs and titles of detected media
- What you download: Your download choices and history
- When you're active: Timestamps of your activity
Imagine if this data were collected and correlated. It would create a detailed profile of your media consumption habits. We believe no extension should have that kind of insight into your life.
The Technical Implementation
Here's how we ensure privacy at the code level:
Local-Only Processing
Media Detection → Browser Memory
Fragment Merging → WebAssembly (Browser)
File Saving → Download API (Browser)
Settings → Local Storage (Browser)
Every step happens on your machine. No data crosses the network.
Minimal Permissions
| Permission | Why We Need It | What We Don't Do |
|---|---|---|
activeTab | Detect media on current page | Read page content or DOM |
webRequest | Monitor network for streams | Log or store request data |
downloads | Save files to your device | Track download history |
storage | Save your preferences | Transmit settings anywhere |
The Bigger Picture
We believe privacy isn't a feature — it's a fundamental right. As browser extensions become more powerful, developers have a responsibility to minimize data collection. FlowPick proves that a fully functional media downloader can work without collecting a single byte of user data.
If you care about your privacy, we encourage you to:
- Review permissions before installing any extension
- Check for open source alternatives
- Monitor network activity of your extensions
- Support developers who prioritize privacy
Your data belongs to you. Period.