Last updated: September 21, 2026 — applies to the Mova Flow desktop app and the Mova Flow Meet Recorder Chrome extension.
Short version: Mova Flow does not have a backend, an account system, or any analytics. Audio you record or upload is sent only to the Mova Flow host you configure, over your own local network. Nothing is sent to us or to any third party, because there is no "us" in the data path at all — the code runs entirely on your machines.
config.json or chrome.storage for the extension).Audio and transcripts travel only between devices you control, over your own local network:
whisper-cli.exe — recognition never calls out to any external API.No audio, transcript, or setting is ever sent to Mova Flow's developer, to any analytics service, or to any third party. There are no ads, no trackers, and no telemetry.
Mova Flow Meet Recorder requests the following, each used only for the purpose below:
tabCapture / offscreen — capture the Meet tab's audio and mix it with your microphone into one recording.storage — remember your configured host address and secret, and in-progress recording status, locally in the browser.activeTab — identify the current Meet call's tab when you press Record.downloads — save the recording as a .wav file when your host can't be reached.host_permissions (the address you configure) — send the recording to your own Mova Flow host for transcription.Audio and transcripts are stored only on the host and/or client devices you run Mova Flow on. Delete an entry from the History tab (or delete the underlying files/folder) to remove it — there is no remote copy to also delete, since none exists.
If this policy changes, the "Last updated" date above will change and the new version will be published at this same URL.
Questions about this policy or the project: open an issue on github.com/f3an/Mova-Flow.