Answer: If your organization signed a BAA for Claude API usage before December 2, 2025, that agreement only covers API usage and does not extend to the HIPAA-ready Enterprise plan, so you'll need to sign a new BAA with your account team to add Enterprise plan access. Status: Confirmed Entry: tool/claude-apps/privacy-and-data/existing-api-baa Revision: 1 Digest: sha256:3ac132a6da4cff02 (changes whenever the content changes) Timeline: Created: 2026-11-13T02:58:40Z Last changed: 2026-11-13T02:58:40Z Last verified: 2026-11-20T12:03:58Z Next check: 2026-11-21T12:03:58Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Action required | sign a new BAA with your account team | [1] | 2026-11-20 BAA cutoff date | December 2, 2025 | [1] | 2026-11-20 Coverage of existing BAA | only covers API usage | [1] | 2026-11-20 Coverage of new BAAs | both API usage and the Enterprise plan under a single agreement | [1] | 2026-11-20 Sources: [1] Anthropic. "HIPAA-ready Enterprise plans | Claude Help Center". https://support.claude.com/en/articles/13296973-hipaa-ready-enterprise-plans Role: primary. Accessed: 2026-11-20T12:03:58Z Quote: "To add this Enterprise plan access, you'll need to sign a new BAA with your account team." (Supports: Action required) Quote: "If your organization signed a BAA for Claude API usage before December 2, 2025" (Supports: BAA cutoff date) Quote: "that agreement only covers API usage—it does not extend to the HIPAA-ready Enterprise plan" (Supports: Coverage of existing BAA) Quote: "BAAs signed after December 2, 2025 can cover both API usage and the Enterprise plan under a single agreement." (Supports: Coverage of new BAAs) Snapshot SHA-256: ce92b1406ab5c083d15ca413e66e9973c2cc13ee2fdb468ab72dcbc08feb1e92 (captured 2026-11-20T12:03:56Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:03:58Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:03:58Z Last attempt: 2026-11-20T12:03:58Z Notes and limitations: Extracted automatically from a single official source (section "If you have an existing API BAA"). Related: https://latestn.com/tool/claude-apps/privacy-and-data/export-claude-data How do I export my Claude data? https://latestn.com/tool/claude-apps/privacy-and-data/export-data-delete-banned-account How do I export my data or delete my Claude account if it has been banned? https://latestn.com/tool/claude-apps/privacy-and-data/google-data-processing-maps What information does Claude share with Google when using maps and weather content? https://latestn.com/tool/claude-apps/privacy-and-data/enterprise-search-privacy-permissions What data can Claude access in my enterprise search project, and who can see my search history? https://latestn.com/tool/claude-apps/privacy-and-data/eu-dsa-support-contact How do EU users contact Claude support under the DSA? https://latestn.com/tool/claude-apps/privacy-and-data/eu-monthly-active-recipients How many monthly active recipients does Claude have in the European Union? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T02:58:40Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/privacy-and-data/existing-api-baa/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/privacy-and-data/existing-api-baa POST: https://latestn.com/dispute/tool/claude-apps/privacy-and-data/existing-api-baa with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/privacy-and-data/existing-api-baa?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What should I do if I already have an existing API BAA with Claude? Revision 1, last verified 2026-11-20T12:03:58Z. https://latestn.com/tool/claude-apps/privacy-and-data/existing-api-baa (accessed 2026-11-21T09:58:14Z). @misc{LatestN_tool_claude_apps_privacy_and_data_existing_api_baa_r1, title = {What should I do if I already have an existing API BAA with Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/privacy-and-data/existing-api-baa}}, note = {Revision 1; digest sha256:3ac132a6da4cff02; last verified 2026-11-20T12:03:58Z; accessed 2026-11-21T09:58:14Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/privacy-and-data/existing-api-baa