Anthropic's API training default
Anthropic's Commercial Services Agreement is explicit: customer content from commercial products is not used to train Anthropic models. That covers the Anthropic API, Claude for Work, and Claude Gov. The Consumer Terms that govern free Claude.ai conversations are separate, and the privacy posture there is different.
When Meetily users select Claude as their summary provider via BYOK, the request hits api.anthropic.com under your API key and your workspace's contract. The defaults on this page apply unless you have a separate commercial arrangement that overrides them.
Retention
For commercial API traffic, Anthropic operates with a short default retention window for inputs and outputs sufficient for service operation and abuse monitoring. Feedback submitted through the thumbs-up or thumbs-down button retains the related conversation for up to 5 years per Anthropic's privacy article, but no feedback is sent by Meetily's default integration - only the prompt and response.
For exact retention windows, the authoritative source is the current Anthropic Data Processing Addendum referenced from the Commercial Terms. Reviewing the DPA before deployment is recommended for any regulated workload.
Zero data retention
Anthropic offers zero data retention for eligible enterprise customers through their commercial agreement. Under ZDR, prompts and outputs are processed in memory and not retained after the request completes. To enable this, contact Anthropic sales; it is not a self-serve toggle in the public dashboard.
How Meetily uses Anthropic
Meetily routes Anthropic traffic through your own API key. Your workspace's contract terms apply. The transcript text is sent over TLS to api.anthropic.com for summarization, and the response is returned to Meetily and stored locally on your device. Audio is never transmitted to Anthropic at any point.
If you want stronger guarantees than the cloud-default offers, switch your summary model to a local provider (Ollama). Meetily's transcription path is already local, so the local-summary path keeps the entire pipeline on-device.