AI vendors and your data

Vendors146Answers427

146 vendors · 427 answers

API and data retention changed Anthropic, Oct 26, 2026

Anthropic · Oct 26, 2026 · 20 added, 18 removed · seen by the weekly check

The pageAll Anthropic terms
  1. Added: 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. On Amazon Bedrock and Claude Models on Google Cloud (Google managed), the cloud provider is the data processor; refer to those platforms' data retention and compliance documentation for their equivalent controls.
  2. Removed: This page covers the Claude API ( api.anthropic.com ), Claude Platform on AWS, and Claude in Microsoft Foundry , where Anthropic is the data processor. On Amazon Bedrock and Google Cloud's Agent Platform, the cloud provider is the data processor; refer to those platforms' data retention and compliance documentation for their equivalent controls.
  3. Added: Different APIs and features have different storage needs. Where a feature does not require storage of customer prompts or responses, it might be eligible for ZDR. Where a feature necessarily requires storage, Anthropic designs for the smallest possible retention footprint under the following commitments:
  4. Removed: Different APIs and features have different storage needs. Where a feature does not require storage of customer prompts or responses, it may be eligible for ZDR. Where a feature necessarily requires storage, Anthropic designs for the smallest possible retention footprint under the following commitments:
  5. Added: Claude Messages and Token Counting APIs: ZDR applies to these endpoints for eligible features listed in the feature eligibility table . Features that use /v1/messages but are marked "No" in the table (such as code execution) are not covered.
  6. Removed: Claude Messages and Token Counting APIs: ZDR applies to these endpoints for eligible features listed in the feature eligibility table . Features that ride on /v1/messages but are marked "No" in the table (such as code execution) are not covered.
  7. Added: Claude Models on Google Cloud (Anthropic managed): Claude Models on Google Cloud (Anthropic managed) follows the same data retention policy as the first-party Claude API. ZDR is available on request; contact your Anthropic account representative to enable it.
  8. Added: Skill data retained according to standard policy. See Agent Skills data retention .
  9. Added: Client-side tool run in your environment.
  10. Added: 29-day retention; async storage required. See Batch processing data retention .
  11. Added: Client-side tool. Anthropic does not run browser actions or retain page content beyond standard API handling. Not covered under HIPAA readiness; requests that include the browser use tool are not blocked. See Browser use data retention .
  12. Added: Your prompts and Claude's outputs are not stored. A fingerprint of cryptographic hashes and token-count estimates is retained briefly to allow comparison against the next request. See Cache diagnostics data retention .
  13. Removed: Skill data retained per standard policy. See Agent skills .
  14. Removed: Client-side tool executed in your environment.
  15. Removed: 29-day retention; async storage required. See Batch processing .
  16. Removed: Client-side tool. Anthropic does not run browser actions or retain page content beyond standard API handling. Not covered under HIPAA readiness; requests that include the browser use tool are not blocked. See Browser use .
  17. Removed: Your prompts and Claude's outputs are not stored. A fingerprint of cryptographic hashes and token-count estimates is retained briefly to enable comparison against the next request. See Cache diagnostics .
  18. Added: Container data retained up to 30 days. See Code execution data retention .
  19. Added: Client-side tool where screenshots and files are captured and stored in your environment, not by Anthropic. See Computer use data retention .
  20. Removed: Container data retained up to 30 days. See Code execution .
  21. Removed: Client-side tool where screenshots and files are captured and stored in your environment, not by Anthropic. See Computer use .
  22. Added: Files retained until explicitly deleted or they reach their configured expiration. See Files API file lifecycle .
  23. Added: Data retained according to standard policy. See MCP connector data retention .
  24. Removed: Files retained until explicitly deleted or they reach their configured expiration. See Files API .
  25. Removed: Data retained per standard policy. See MCP connector .
  26. Added: Built on code execution containers; data retained up to 30 days. See Programmatic tool calling data retention .
  27. Removed: Built on code execution containers; data retained up to 30 days. See Programmatic tool calling .
  28. Added: Your prompts and Claude's outputs are not stored. Only the JSON schema is cached, for up to 24 hours since last use. This also covers strict tool use ( strict: true on tools), which uses the same grammar pipeline. PHI must not be included in JSON schema definitions; see PHI handling guidelines . See Structured outputs data retention .
  29. Added: Server-side tool run by Anthropic; the tool definitions in the request are searched in memory per call and nothing is stored after the response.
  30. Added: Profiles are metadata about your end customers and don't contain prompts or outputs. The profile data you send is retained according to standard policy until you delete the profile. HIPAA-enabled organizations can use user profiles, but the user profiles API is not a HIPAA-eligible service and PHI must not be included in the profile data you send. See What a profile contains and how Anthropic uses it .
  31. Added: Fetched web content returned in the API response. Dynamic filtering for web fetch is not eligible for ZDR or HIPAA. Website publishers might retain request data (such as fetched URLs and request metadata) according to their own policies.
  32. Added: Real-time web search results returned in the API response. Dynamic filtering for web search is not eligible for ZDR or HIPAA.
  33. Removed: Your prompts and Claude's outputs are not stored. Only the JSON schema is cached, for up to 24 hours since last use. This also covers strict tool use ( strict: true on tools), which uses the same grammar pipeline. PHI must not be included in JSON schema definitions; see PHI handling guidelines . See Structured outputs .
  34. Removed: Server-side tool executed by Anthropic; the tool definitions in the request are searched in memory per call and nothing is stored after the response.
  35. Removed: Fetched web content returned in the API response. Dynamic filtering is not eligible for ZDR or HIPAA. Website publishers may retain request data (such as fetched URLs and request metadata) according to their own policies.
  36. Removed: Real-time web search results returned in the API response. Dynamic filtering is not eligible for ZDR or HIPAA.
  37. Added: Claude Models on Google Cloud (Anthropic managed) follows the same data retention policy as the first-party Claude API, and Anthropic is the data processor. ZDR is available there on request. On Amazon Bedrock and Claude Models on Google Cloud (Google managed), the cloud provider is the data processor; refer to those platforms' data retention and compliance policies for their equivalent controls.
  38. Removed: No. The ZDR and HIPAA arrangements described on this page apply to the Claude API, where Anthropic is the data processor. On Bedrock and Google Cloud, the cloud provider is the data processor; refer to those platforms' data retention and compliance policies for their equivalent controls.
About this change
Page
platform.claude.com/docs/en/manage-claude/api-and-data-retention
Kind
Documentation
Text hash
554f4d4a2940 to 3ae15f07b24c
Dated by
the weekly check that first read the new text