Security & trust
Here's what MEETO AI can access, where your data goes, and how you stay in control of it.
MEETO AI asks for read-only Google scopes: calendar events, Meet conference records and Meet-created Drive files. It can't edit your calendar, send invites or read other Drive files.
Auto-join can be turned off for the whole workspace, and the notetaker can be removed from any single meeting before it starts. The bot joins under a clearly visible display name.
Meeting-bot status events are checked against their Svix signature, and Stripe events against the Stripe signature. Anything unsigned or stale is rejected before it's processed.
All traffic to Google, Recall.ai, OpenAI Whisper, Anthropic Claude, Notion, Slack and Stripe goes over TLS. Session cookies are HTTP-only, signed and sent over HTTPS only in production.
Deleting a meeting removes its transcript, analysis, decisions and action items. Raw recordings are only needed until the transcript is stored, and you can purge them right after.
Transcription and extraction go through the OpenAI and Anthropic business APIs. Under their terms, customer API data isn't used to train their models by default.
Each provider gets only what its step needs. Audio goes to the transcription service and text goes to the AI service. Notion and Slack only receive the finished notes.
| Provider | Purpose |
|---|---|
| Sign-in, calendar sync, native Meet recordings | |
| Recall.ai | Meeting bot: joins calls and records audio |
| OpenAI | Whisper speech-to-text |
| Anthropic | Claude: summary, decision and action item extraction |
| Notion | Delivery of meeting notes (when connected) |
| Slack | Delivery of meeting recaps (when connected) |
| Stripe | Subscription billing |
Enterprise customers can run MEETO AI on their own infrastructure and Postgres database, with their own provider keys. Transcripts never pass through our servers.