Together AI's API training default
Together AI's privacy policy is explicit that it does not train on your data without your consent: "We do not use any data collected from you to train our models without your explicit opt-in and consent. You may revoke that consent at any time and request deletion." [1] Together's privacy and security documentation reinforces this, stating that data sharing for training other models is opt-in and not enabled by default. [2]
When Meetily users select Together AI as their summary provider via BYOK, the request hits Together's OpenAI-compatible API under your own API key and your account's settings. The opt-in-only training default applies unless you have separately enabled data sharing for training in your Privacy & Security controls.
Retention
Together AI's developer documentation states that Together does not store inputs or outputs by default and that the platform supports zero data retention, while temporary caching may occur for performance unless configured otherwise. [2] Together's customer-facing privacy policy, separately, describes retained prompt and response history that you can view and delete through account settings. [1] Because these two surfaces frame the default differently, this page does not assert a single fixed retention window in days; the authoritative posture for your specific account is the Privacy & Security configuration at api.together.ai/settings/profile read together with the current privacy policy. Reviewing both before deployment is recommended for any regulated workload.
Zero data retention
Zero data retention is available on Together AI and is documented as a self-serve control rather than an enterprise-only contract item. You enable it in Privacy & Security under your account profile by declining to store prompts or to allow data for model training. [1][2] Under ZDR, the content you submit and the outputs returned are not stored, retained, or used for model training, product improvements, or any secondary purposes except as needed to provide the service. [1]
Two operational notes matter. First, ZDR applies only from the moment you enable it and does not affect any data processed before that point, so enable it before sending traffic. [1] Second, for organizations the organization-level setting governs all traffic made under that organization's projects and API keys, regardless of which member sends the request. [2]
How Meetily uses Together AI
Meetily routes Together AI traffic through your own API key. Together exposes an OpenAI-compatible API at https://api.together.xyz/v1, which is the base URL you enter in Meetily's BYOK summary configuration. [3] Your account's contract and privacy settings apply to that traffic. The transcript text is sent over TLS to Together for summarization, and the response is returned to Meetily and stored locally on your device. Audio is never transmitted to Together at any point.
If you want stronger guarantees than the cloud default offers, enable zero data retention in your Together account before use, or switch your summary model to a local provider such as Ollama. Meetily's transcription path is already local, so the local-summary route keeps the entire pipeline on your device.
References
- Privacy Policy, Together AI, updated December 17, 2025, https://www.together.ai/privacy (accessed 2026-06-29).
- Privacy and security, Together AI developer documentation, https://docs.together.ai/docs/privacy-and-security (accessed 2026-06-29).
- OpenAI compatibility, Together AI developer documentation, https://docs.together.ai/docs/openai-api-compatibility (accessed 2026-06-29).