Privacy Policy
Last Updated: July 2026
Privacy in one line
MediaFlow is local-first. Your media files and capture history stay on your PC. We do not run a cloud library of your videos.
1. Local-first processing
Capture, conversion, compression, local transcription, and most AI enhance steps run on your machine and write to folders you choose.
We do not receive or store:
- Your media files (video, audio, images)
- Your transcripts, subtitles, or project timelines
- A remote log of what you archive or open
2. Data that may leave your device
Only limited, optional, or necessary network activity:
- License activation (Pro): license key, hardware ID (HWID hash), and device name may be checked with our payment/license provider (e.g. Lemon Squeezy) to prevent abuse.
- App updates: the desktop app may contact our release CDN to check for a newer installer.
- Payments: card data is handled by Lemon Squeezy; we do not store full card numbers.
- Optional APIs you configure: if you paste your own cloud TTS/AI API keys, those providers process only what you send through those features.
- Optional error reports: if you enable error reporting in Settings, anonymized diagnostics may be sent. Media files and download URLs are not intentionally included.
3. Clipboard watch (optional, off by default)
If you enable clipboard link detection in Settings, MediaFlow reads clipboard text only on your PC to detect capturable media URLs. Clipboard content is not uploaded. A system notification appears first; the app focuses only if you click it. You can change detection range or turn it off anytime.
4. Local network features (optional)
Mobile / LAN helpers and the browser extension helper listen on localhost or your local network only when you enable them. They are not auto-started for everyone. Use a PIN when offered. Traffic is for your devices, not a MediaFlow media cloud.
5. Browser extension (optional)
The optional extension talks to your local desktop app. It does not send your media library to MediaFlow servers. Host/cookie permissions exist so you can send public or session-backed links you already can access into the local app — use only content you have the right to save.
6. Logs on your device
The desktop app may write local log files under your user data folder for troubleshooting. You can open or clear them from Settings. Temp files from processing are cleaned on exit or via cleanup tools.
7. Third-party platforms
When you capture from a website, your computer connects to that platform directly (via tools such as yt-dlp). Those sessions follow that platform’s terms and privacy rules.
8. Contact
Privacy questions: mediaflow.service@gmail.com