Cohere SaaS platform

From AI API data terms: training, retention and zero retention: What does each AI provider say happens to data sent to its commercial API: is it used for training, how long is it kept, and can zero retention be had?

Provider: Cohere

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

If you have been approved for zero data retention, Cohere does not log any customer prompts or generations.

Source: https://cohere.com/enterprise-data-commitments. Read 2026-11-01. Checked by a second reader.

Offering: Cohere SaaS platform

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

You can also use the Cohere SaaS Platform to leverage Cohere-managed infrastructure.

Source: https://cohere.com/enterprise-data-commitments. Read 2026-11-01. Checked by a second reader.

Trains on API data by default: Not found

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.

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

Default retention: We automatically delete logged prompts and generations after 30 days

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.

We automatically delete logged prompts and generations after 30 days, unless we need it to comply with a legal requirement or customer contract, or unless your usage is flagged as potentially violating our terms, including our Usage Policy (e.g. abuse or misuse of our services).

Source: https://cohere.com/enterprise-data-commitments. Read 2026-11-01. Checked by a second reader.

Exceptions: Data you allow us to use for training purposes may be retained separately

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.

Data you allow us to use for training purposes may be retained separately in accordance with our agreement with you.

Source: https://cohere.com/enterprise-data-commitments. Read 2026-11-01. Read once.

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.

Zero data retention (ZDR) means we do not log any prompts or generations.

Source: https://cohere.com/enterprise-data-commitments. Read 2026-11-01. Checked by a second reader.

How to get it: We only allow ZDR for enterprise customers who can make additional commitments about their usage

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.

Because of this, we only allow ZDR for enterprise customers who can make additional commitments about their usage of the Cohere Services.

Source: https://cohere.com/enterprise-data-commitments. 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: Not found

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.

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