Security

The simplest way to protect your meetings is not to collect them. MeetInk has no server that receives or stores your recordings, transcripts or notes. They live on your Mac, protected by your Mac. This page explains how that works, and what’s left that you should know about.

Local-first by design

• On your Mac: audio capture, transcription, speaker separation, the search index for Ask, and the library itself. Transcription and speaker separation use models that run on the Mac’s Neural Engine.
• Never uploaded: audio. Not to us, and not to any AI provider.
• Only if you choose it: transcript text goes to the cloud notes engine you picked, directly from your Mac with your own key. With Ollama, notes are written on your Mac too. The privacy policy lists everything that can leave your Mac.

Where your data lives

Everything is in ~/Library/Application Support/MeetInk: a SQLite database (notes.db) with transcripts, notes, Ask conversations and the search index, and one folder per meeting with its audio. The folder is protected by macOS file permissions for your user account. MeetInk doesn’t add its own encryption to the library, so we recommend turning on FileVault (System Settings → Privacy & Security), which encrypts the whole disk.

You can free the original audio of meetings in Settings → Storage, and delete any meeting at any time.

Secrets

API keys, Slack and webhook links (which contain access tokens), Google Calendar sign-in tokens and the optional account session are encrypted before they are saved, using Electron’s safeStorage. The encryption key is held in your macOS Keychain, so the saved values can’t be read by copying the database to another Mac. Secrets are never included in exports, usage statistics or anything sent to us.

Google sign-in and calendars

Google sign-in opens in your own browser, never inside the app, so MeetInk never sees your Google password. It uses the standard flow for desktop apps (PKCE with a one-time local redirect). Google Calendar access is read-only.

AI-app connector

The connector for Claude Desktop, Claude Code and Cursor runs on your Mac and talks to those apps over a local pipe, not a network port. It opens your library read-only, so it cannot change or delete anything. What those apps do with the answers is up to them and their AI provider.

Signed releases and updates

• Release builds are signed with an Apple Developer ID, use Apple’s hardened runtime and are notarized by Apple, so macOS checks them before they open. The bundled transcription engine is signed the same way.
• Updates are downloaded over HTTPS from GitHub Releases. Before installing, macOS checks that an update is signed by the same developer as the app you have.
• The remote configuration file the app may fetch carries only announcements and on/off switches. It cannot run code.

Certifications

MeetInk has no SOC 2 report, ISO 27001 certificate, HIPAA attestation or third-party audit. Those programs assess companies that hold customer data on their servers. We don’t have a server holding your meetings, so there is nothing of that kind to certify. If your organisation has rules about meeting data, the useful question is how your Macs are managed, because that’s where the data is.

Reporting a vulnerability

If you find a security problem in MeetInk or this website, please email hello@dataotto.com with the details and steps to reproduce it. Please give us a reasonable time to fix it before you publish anything, and don’t access other people’s data while testing. We’ll acknowledge your report, keep you updated, and credit you if you’d like. We don’t currently run a paid bug bounty.