Privacy Policy

Last updated: 2026-05-11

Meeting Recorder is a native macOS app that records meeting audio and video, transcribes recordings, and lets you search across your meeting history. This document explains what data the app handles and where it goes.

The short version: we don't collect, transmit, or store any of your recordings, transcripts, or settings on our servers. Everything stays on your Mac unless you explicitly configure a third-party provider, and even then the configuration is yours to control.

Who runs this app

Meeting Recorder is developed and distributed by Infopeak. There is no analytics backend, no telemetry, and no marketing pipeline that ever sees your data.

Contact: hej@infopeak.se

What the app records

When you start a recording, the app captures:

• Audio from the microphone you select in Settings → Audio.
• System audio (the audio coming out of your speakers — i.e. the other meeting participants) when you enable that option, via Apple's ScreenCaptureKit framework. This requires your explicit Screen Recording permission grant in System Settings → Privacy & Security.
• Video of a specific window (or the whole screen) when you start an "Audio + Video" recording. Captured via ScreenCaptureKit with the same permission grant as above.
• Snapshots (single-image captures of the meeting window) when you trigger them with Cmd+Shift+S.

Recordings are written as files (.m4a, .mp4, .png) into a folder on your Mac that you choose in Settings → Storage. The default is ~/Documents/MeetingRecorder/.

These files never leave your Mac unless you copy or share them yourself, or until you explicitly send them to a transcription provider you've configured.

What the app transcribes — and where

After a recording, the app can transcribe the audio. You choose the provider in Settings → Transcription. Each option has a different data-handling profile:

Local-only providers (nothing leaves your Mac)

• WhisperKit — runs OpenAI's Whisper model directly on your Mac via Core ML. Model weights are downloaded once from Hugging Face on first use, then cached locally. Your audio is processed on-device with no network round-trips.
• MLX (built-in LLM) — runs Qwen models directly on your Mac via Apple's MLX framework. Same as above: weights download once, then inference is fully local.
• Apple's NLEmbedding — used when you choose "Local" embeddings for meeting search. Runs entirely on-device.

Third-party cloud providers (you opt in, you bring your own key)

• OpenAI — when you configure your own OpenAI API key in Settings → Advanced, the app sends recording audio to OpenAI's /v1/audio/transcriptions endpoint and (if you choose OpenAI for structuring) the transcript text to /v1/chat/completions. Your audio and text are processed under OpenAI's privacy policy and their API data usage policy. As of writing, OpenAI does not train on data sent through the API. Meeting Recorder pays nothing to OpenAI on your behalf — you are billed directly by them.
• OpenAI-compatible local servers (LM Studio, Ollama, llama.cpp, LocalAI, etc.) — when you point the app at a server you run yourself, audio and text go to that server's URL. Whether any of that data leaves your machine depends on what you've configured the server to do. Meeting Recorder is not in that loop.

The provider for each step (transcription, structuring, search, chat) is shown in Settings and is the source of truth. Changing providers takes effect on the next recording.

Where API keys and other secrets are stored

API keys you enter (OpenAI, OpenAI-compatible servers) are stored in your Mac's system Keychain, in an entry tagged with the provider name. They are not persisted in plaintext anywhere else and never transmitted off your Mac except as part of an authorised request to the configured provider.

What's stored in app settings

Settings (chosen device, provider preferences, video resolution, storage paths, monthly usage counters for the freemium tier, etc.) live in macOS UserDefaults — a per-user, per-app preferences store. They never leave your Mac.

When you upgrade to Pro, the purchase receipt is stored by Apple's StoreKit framework on your Mac and reflected back to Apple's servers under Apple's privacy policy. We do not see your Apple ID; StoreKit returns only an entitlement status (Free / Pro Subscription / Pro Lifetime) to the app.

What we do NOT do

• We do not run any analytics, telemetry, or crash-reporting service that phones home.
• We do not collect your name, email, IP address, or device identifier.
• We do not sell, share, or rent any data — there is no data on our side to sell.
• We do not use third-party tracking SDKs.
• We do not send recordings or transcripts anywhere unless you configured a third-party provider yourself.

Third-party services you might trigger

Depending on the providers you configure, your data may be processed by:

You can avoid all three by using only WhisperKit + MLX (both local) and not upgrading to Pro.

Children's privacy

Meeting Recorder is not directed at children under 13 and does not knowingly process data about them.

Changes to this policy

If we ever change how the app handles data, this document will be updated and the "Last updated" date at the top will change. Significant changes will also be flagged in the app's release notes and in App Store version descriptions.

Your rights

Because no data leaves your Mac under default operation, there is nothing for us to provide, correct, or delete. Your recordings, transcripts, and settings are entirely under your control:

• Delete a recording: in the History view's row overflow menu, or by removing the session folder from your storage directory.
• Delete all data: uninstall the app and delete its storage directory and the app's UserDefaults (defaults delete com.tho-sil.MeetingRecorder AppSettings.v1).
• Revoke API keys: Settings → Advanced → Remove API key, or delete the corresponding Keychain entry directly.