Anthropic rebuilt its enterprise data policy after regulated customers pushed back — what it signals for compliance-heavy builds

Anthropic announced Enterprise Frontier Safeguards on 1 September 2026, replacing its prior data retention approach after complaints from financial services, healthcare and public sector customers, storing activity data in infrastructure the customer controls rather than Anthropic's own — a direct response to the compliance concerns that have been the biggest brake on AI coding tool adoption in regulated industries.

Anthropic announced Enterprise Frontier Safeguards (EFS) on 1 September 2026, developed with more than 100 customers across financial services, healthcare, manufacturing, telecom, law, retail and the public sector — including CISOs from Goldman Sachs, Morgan Stanley, Citi and Bank of America, and organisations like Comcast, Mastercard and Visa. EFS combines zero data retention with automated misuse detection, but the structural change is what matters most: activity data now sits in cloud infrastructure the customer controls, not Anthropic’s, with businesses able to run automated safety monitoring without any Anthropic human review of their data. It’s supported on Claude Code, Claude Enterprise and the Claude Platform across AWS, Google Cloud and Microsoft Foundry, rolling out in phases from this autumn, at no additional charge.

The detail worth reading closely is why this happened: it’s a direct response to pushback, not a proactive feature launch. Regulated organisations have spent 2026 raising the same objection to AI coding tools — that they can’t verify what happens to their data, and can’t satisfy an auditor or regulator with “trust us.” Anthropic building customer-controlled infrastructure into its core enterprise offering, at the request of banks and healthcare organisations specifically, is a concrete signal that the compliance gap around AI-assisted development is closing, not just being talked about.

Why this matters beyond Anthropic’s own customers

If data governance has been the reason your organisation held off on AI-assisted development — a common and reasonable position in healthcare, financial services or any NHS-adjacent work — this is evidence the vendor landscape is starting to build for that requirement rather than asking regulated buyers to accept generic terms. It doesn’t remove the need to check EFS’s actual guarantees against your specific compliance obligations once it’s live, but it changes the starting conversation from “can we use this at all” to “how do we configure it correctly.”

So what

If you’re planning a build in a regulated space — healthcare, finance, or anywhere with strict data handling requirements — the AI tooling question and the compliance question are no longer separate conversations, and treating them separately is how projects get stuck late. See our healthcare software development work, or get in touch to talk through how AI-assisted delivery fits a project with real compliance constraints.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work