OpenAI's API training default
OpenAI's enterprise privacy page commits that data submitted through the OpenAI API, ChatGPT Enterprise, and ChatGPT Team is not used to train OpenAI's models. The consumer ChatGPT free and Plus tiers default differently and are out of scope for this page.
When Meetily users select OpenAI as their summary provider via BYOK, the request hits api.openai.com under your API key and your account's contract. The defaults on this page apply unless you have a separate enterprise arrangement.
Retention
OpenAI's documented default for API inputs and outputs is short-term retention for abuse monitoring (up to 30 days as published by OpenAI), after which the data is deleted unless legal obligations require longer retention. Specific endpoints such as fine-tuning, Assistants, and Stored Completions have their own retention semantics that you opt into when you use those features.
For exact retention windows, consult OpenAI's enterprise privacy documentation and your Business Associate Agreement (if applicable). Reviewing those before deployment is recommended for regulated workloads.
Zero data retention
OpenAI offers zero data retention for eligible enterprise customers on supported endpoints. With ZDR, prompts and outputs are processed in memory and not retained after the request completes. ZDR is not a self-serve toggle - eligibility and supported endpoints are listed in OpenAI's enterprise documentation, and your account team must enable it.
How Meetily uses OpenAI
Meetily routes OpenAI traffic through your own API key. Your account's contract terms apply. The transcript text is sent over TLS to api.openai.com for summarization, and the response is returned to Meetily and stored locally on your device. Audio is never transmitted to OpenAI 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.