AWS Bedrock to require sharing data with Anthropic for Mythos and future models

6/10/2026 at 8:55:20 AM

Pretty sure this doesn't work for any regulated enterprise or government client. But AWS knows this, so I am curious why they'd agree to it.

by rohansood15

6/10/2026 at 10:00:33 AM

Same as for GitHub Copilot?

"For more on how Anthropic handles this data, see Anthropic’s commercial terms and data retention policy. Enabling the Claude Fable 5 policy constitutes acknowledgement of this requirement. Leaving it off keeps Claude Fable 5 unavailable to your organization."

https://github.blog/changelog/2026-06-09-claude-fable-5-is-g...

by 1313ed01

6/10/2026 at 9:41:41 AM

They say it's opt-in but since they are capable of agreeing to this, I am just waiting until they hide this opt-in into the regular ToS when asking for a new model access...

by rozumbrada

6/10/2026 at 10:03:25 AM

They want your data.

> After 30 days, the data is deleted automatically

Do we believe that?

> or we're legally required to keep it.

Aha - so, data is forever.

by shevy-java

6/10/2026 at 10:08:28 AM

> Do we believe that?

If you don't believe them now why would you have believed them earlier when they said "no data is retained" ?

by toasty228

6/10/2026 at 9:06:11 AM

"Legally required" ... gotcha, script writing on Melania Movie 3 has begun in exchange for a national security letter requiring Amazon to both keep the data and not exclude it from training.

by officialchicken

6/10/2026 at 9:33:49 AM

Woah, if anthropic does it, even OpenAI would start doing the same with Azure models

by adithyaharish

6/10/2026 at 9:33:45 AM

This is not going to fly in EU.

by _pdp_

6/10/2026 at 9:53:04 AM

I suspect they will simply not offer it, for as long as they maintain that it has to in fact fly. Anthropic appears to be somewhat principled here.

by jstummbillig

6/10/2026 at 9:42:50 AM

My thesis is that in software you don't want aggregators. They provide the promise of vendor neutrality, but it comes at the expense of increased supply chain compromise risk, small print technically legal data exfiltration.

Even in the happy case where nothing bad happens, you get a badly integrated product, because you integrate not against the actual vendor, but against a abstraction layer that commoditizes the actual product, effectively forcing you to either use the least common denominator of features, or circumventing the actual aggregation model itself with some kind of 'vendor_specific_parameters' parameter in the aggregator API.

My thesis is drop the vendor neutrality, and build your integration with the vendor directly.

by TZubiri

6/10/2026 at 9:41:48 AM

Got an email from Zed about the same this morning.

by drcongo

6/10/2026 at 9:19:15 AM

What a "frontier."

by themafia

6/10/2026 at 9:39:04 AM

It's wild!

by Hamuko

6/10/2026 at 9:25:48 AM

> except in the rare cases where it's part of a safety investigation or we're legally required to keep it

So basically all your data will flow to NSA/CIA/Mossad if they show even slight interest in your org or you as a person. Gotcha.

by romanovcode

6/10/2026 at 9:30:52 AM

aaaand there it is.

by codeduck

6/10/2026 at 9:45:04 AM

[flagged]

by chattermate

6/10/2026 at 9:06:26 AM

[flagged]

by Torikul007