Anthropic Claude API

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: Anthropic

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

This page covers the Claude API (api.anthropic.com), Claude Platform on AWS, Claude in Microsoft Foundry, and Claude Models on Google Cloud (Anthropic managed), where Anthropic is the data processor.

Source: https://platform.claude.com/docs/en/manage-claude/api-and-data-retention. Read 2026-11-01. Checked by a second reader.

Offering: Claude API

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

This page covers the Claude API (api.anthropic.com), Claude Platform on AWS, Claude in Microsoft Foundry, and Claude Models on Google Cloud (Anthropic managed), where Anthropic is the data processor.

Source: https://platform.claude.com/docs/en/manage-claude/api-and-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.

By default, we will not use your inputs or outputs from our commercial products (e.g. Claude for Work, Anthropic API, Claude Gov, etc.) to train our models.

Source: https://privacy.claude.com/en/articles/7996868-is-my-data-used-for-model-training. Read 2026-11-01. Checked by a second reader.

Default retention: Automatically delete inputs and outputs on our backend within 30 days of receipt or generation

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.

For Anthropic API users, we automatically delete inputs and outputs on our backend within 30 days of receipt or generation, except:

Source: https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data. Read 2026-11-01. Checked by a second reader.

Exceptions: Claude Fable 5.1, Claude Mythos 5.1, Claude Fable 5, and Claude Mythos 5: these models require 30-day data retention and are not available under ZDR unless expressly authorized by Anthropic

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.

Claude Fable 5.1, Claude Mythos 5.1, Claude Fable 5, and Claude Mythos 5: These models require 30-day data retention and are not available under ZDR unless expressly authorized by Anthropic.

Source: https://platform.claude.com/docs/en/manage-claude/api-and-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.

Some Claude Platform (Claude API) and Claude Code for Enterprise customers, subject to Anthropic’s approval, may have arrangements under which Anthropic does not store their inputs or outputs except where needed to comply with law or combat misuse or harm.

Source: https://privacy.claude.com/en/articles/8956058-i-have-a-zero-data-retention-agreement-with-anthropic-what-products-does-it-apply-to. Read 2026-11-01. Checked by a second reader.

How to get it: Reach out to our sales team; requests are reviewed and applied on a per-organization basis

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.

please reach out to our Sales Team. Note that zero data retention requests are reviewed and applied on a per-organization basis

Source: https://privacy.claude.com/en/articles/8956058-i-have-a-zero-data-retention-agreement-with-anthropic-what-products-does-it-apply-to. Read 2026-11-01. Checked by a second reader.

BAA available: Yes

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.

Anthropic provides a BAA covering our HIPAA-ready services, such as use of our first-party API, Claude in Microsoft Foundry, or Enterprise plans.

Source: https://privacy.claude.com/en/articles/8114513-business-associate-agreements-baa-for-commercial-customers. Read 2026-11-01. Checked by a second reader.

Data location: Inference geo: only "us" and "global" are available. Workspace geo: only "us" is currently available

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.

Inference geo: Only "us" and "global" are available. Workspace geo: Only "us" is currently available.

Source: https://platform.claude.com/docs/en/build-with-claude/data-residency. Read 2026-11-01. Checked by a second reader.