MediaFlowSwift

Privacy

Last updated 22 September 2026. This page describes the app; it says the same as Settings › Privacy inside MediaFlowSwift, which is the authoritative list and changes with the app.

The short version

MediaFlowSwift works on your Mac and your own network. It has no account, collects no usage data or analytics, and contacts no server of ours. Your media, projects and database stay on your Mac and on your network.

A few features need a service run by another company. Each one is off until you turn it on in Settings › Privacy, which shows what is sent, to whom, and what for. You can turn any of them off again at any time.

Services you can turn on

ServiceGoes toWhat is sent
Online speech recognitionAppleThe audio of the clip being transcribed, only when your Mac has no on-device speech model for its language.
Historical weather lookupOpen-MeteoEach clip’s GPS coordinates, rounded to about 100 m, and the date it was shot.
Place names for GPS coordinatesAppleEach clip’s coordinates, rounded to about 100 m.
Maps of where you shotAppleThe area of the map being shown, so that the map images can be supplied.
Writing your YouTube title, description and tagsThe model provider you chose (Anthropic, OpenAI or Google), or a model on your own computerThe transcript of the finished video you chose, its length, the brief you typed, and the drafts for revision. Never the video or its file name. With a model on your own Mac or network, nothing leaves your network.
Suggesting categoriesThe model provider you chose, or a model on your own computerThree frames from each clip, your category list, the clip’s camera, duration and place name, the opening words of any speech, and your recent corrections. Set up in Settings › Analysis and ticked per import.
Uploading to YouTubeGoogle, in a Google Cloud project you ownThe finished video you chose and the details you entered for it, and the thumbnail if you chose to send it. Sign-in opens your browser at Google; MediaFlowSwift never sees your Google password. Nothing is uploaded until you click Upload and confirm.
Reading your videos’ statisticsGoogle (YouTube and YouTube Analytics)The YouTube IDs of videos uploaded by MediaFlowSwift and a date span; Google answers with views, likes, comments, watch time and the like. Only when you click Read from YouTube Now.
Sending problem reportsThe report relay whose address you entered (for reports to us, see below)A problem report, only when you click Send on one you have read in full: its text exactly as shown, a title, a random identifier for your copy of the app, and a crash signature if there is one. Names, drives, folders and file names are taken out before you see it.

What stays on your network

Problem reports sent to us

If you send a problem report to us, it is filed as an issue in our development tracker so that we can fix the fault. It contains only what the app showed you before you clicked Send. If you chose to include an email address for a reply, we use it for that reply and nothing else. We keep reports for as long as the fault is being worked on and for our release records afterwards.

This website

This site is static pages served by GitHub Pages. We run no analytics and set no cookies. GitHub, as the host, keeps ordinary server logs of requests (IP address, page requested, time) under GitHub’s privacy statement. Fonts are loaded from Google Fonts, which receives the request for the font files.

Purchases

When plans go on sale, payment will be handled by a payment provider; the checkout page will say which, and their privacy policy covers the card and billing details you enter there. MediaFlowSwift itself never sees card numbers.

Questions

Write to support@mediaflowswift.com.