Together AI inference

Provider: Together AI

The company offering the API, as named on its own page.

Together AI supports zero data retention (ZDR) at the organization level.

Source: https://docs.together.ai/docs/zero-data-retention. Read 2026-11-01. Checked by a second reader.

Offering: Together's inference services

The API, tier or platform the row covers, in the provider's words.

the content you submit to Together’s inference services, including text, images, and prompts, and any outputs returned to you are not stored, retained, or used for model training

Source: https://docs.together.ai/docs/zero-data-retention. Read 2026-11-01. Checked by a second reader.

Trains on API data by default: No

True or false only where the text plainly says what happens to this offering's API data with no opt-in or opt-out by the customer. An opt-out with no stated default is left blank. Where pages differ: legal or privacy page first, then help or trust pages, then developer docs, with the other in conflicts.

We do not use any data collected from you to train our models without your explicit opt-in and consent.

Source: https://www.together.ai/privacy. Read 2026-11-01. Checked by a second reader.

Default retention: Together stores the prompts you send and the responses models return, and may use them for product improvements

How long prompts and outputs are kept by default, in the provider's words. Where pages differ: legal or privacy page first, then help or trust pages, then developer docs, with the other in conflicts. A page that's only less specific isn't a conflict: the more specific statement is the value.

Unless your organization enables ZDR, Together stores the prompts you send and the responses models return, and may use them for product improvements.

Source: https://docs.together.ai/docs/zero-data-retention. Read 2026-11-01. Checked by a second reader.

Exceptions: Passthrough models: data sent to them is handled under that provider's own policy

The main case with different retention, in the provider's words: first a model carved out of the general promise, then a feature, then a case such as flagged content. Pages rank as for Default retention; between pages of equal rank, the one naming the models. One passage only, so others may exist.

Passthrough models: Models that forward requests to a third-party provider are allowed by default. Data sent to them is handled under that provider’s own policy.

Source: https://docs.together.ai/docs/zero-data-retention. Read 2026-11-01. Checked by a second reader.

Zero retention offered: Yes

True only where the provider plainly offers zero data retention by that name for this offering; false only where it plainly excludes it. A similar control under another name is left blank here and described in How to get it.

Together AI supports zero data retention (ZDR) at the organization level.

Source: https://docs.together.ai/docs/zero-data-retention. Read 2026-11-01. Checked by a second reader.

How to get it: Open the Privacy section of organization settings. Set Store prompts and model responses to No

What the provider says is needed for zero retention. Where it has no offer by that name, its nearest named control or pointer, in its own words. Where pages differ: legal or privacy page first, then help or trust pages, then developer docs, with the other in conflicts.

ZDR is not enabled by default. To enable it: Open the Privacy section of Organization Settings. Set Store prompts and model responses to No.

Source: https://docs.together.ai/docs/zero-data-retention. Read 2026-11-01. Checked by a second reader.

BAA available: Not found

True where the provider says it signs or offers a HIPAA Business Associate Agreement, or sets terms for use under one, for this offering. A general cloud BAA that the page doesn't tie to this offering, or an invitation to ask, is left blank.

No source we could use stated this. A blank never means no.

Data location: Geo-specific inference keeps inference processing in the United States for select serverless models. It covers only where those requests are processed, not where data is stored, logged, or routed

Where the provider states data is processed or stored, in its words. Where pages differ: legal or privacy page first, then help or trust pages, then developer docs, with the other in conflicts.

For select serverless models, geo-specific inference keeps inference processing in the United States, with no GPUs to provision. The guarantee applies to requests sent to us-api.together.ai. It covers only where those requests are processed, not where data is stored, logged, or routed.

Source: https://docs.together.ai/docs/privacy-and-security. Read 2026-11-01. Checked by a second reader.