YOUR DATA / CURRENT BETA
Know where
your context goes.
mter keeps its project library on your Mac and uses external services for live transcription and AI assistance. Here’s the distinction.
Planned included-AI service
The public release will use a mter account and a subscription allowance. Provider API keys will stay on our servers, not inside the Mac app. The service will authenticate requests, check remaining usage, and forward relevant meeting and project context to AI providers. Audio will use authorized transcription sessions.
Account identifiers, subscription state, and usage totals will need server storage. Payment details will be handled by Stripe. This service is not live yet; its hosting, retention, deletion controls, and formal privacy notice must be finalized before paid access opens.
Current internal test build
The sections below describe the existing local build, which still connects directly to user-configured providers. They should not be read as a privacy promise for the planned server-backed release.
What is stored on your Mac
mter stores your settings, project names and selected paths, imported document text, prepared code context, and saved meeting history in its local application data directory. This includes working context used to answer project questions.
Meeting text, document text, and project context are not encrypted by mter. API keys are encrypted through Electron’s macOS-backed secure storage. The protection of other local data depends on your Mac’s account and disk security.
Saved meeting content is retained locally; do not assume it disappears when you stop a call or quit the app. The current beta does not provide a complete in-app data-deletion flow. This is a release limitation to consider before adding sensitive material.
What is sent to providers
- Live audio: microphone and captured system audio are sent to AssemblyAI for transcription during an active capture session.
- AI assistance: requests may include your question, the current transcript, summaries of earlier discussion, relevant project and document excerpts, tool results, and selected file paths. These go to your configured AI endpoint; the default uses OpenAI.
- Project discovery: candidate names and paths from search locations you choose are sent to the configured AI provider. Discovery does not send candidate file contents. You review its picks before creating the project.
- Links and evidence: when you add a public link or request external evidence, mter may contact the relevant site or search service to retrieve information.
Provider retention, data processing, and usage charges are governed by your provider’s terms and account settings. mter does not promise zero retention or offline processing.
What you control
You choose the project folders and documents, configure provider credentials, grant macOS permissions, and explicitly start or stop capture. Optional calendar access requires permission. A visible recording state indicates an active session.
Select project material carefully, including when a folder contains confidential files. Let meeting participants know when you record and follow the requirements that apply to your conversation.
About this website
The interactive product examples are fictional and run in your browser. They do not record audio or send example interactions to an AI provider. The setup-prompt customizer also runs in your browser; it does not submit your project name or language choice to an agent. Copying the prompt puts it on your clipboard, and you choose where to paste it. This website is hosted through Sites. Its fonts are requested from Google Fonts, so those hosting and font services receive the network information needed to deliver the page.