Live data from Hacker News

Anthropic requires 30 day data retention for Fable and Mythos

support.claude.com

161–170 of 330 posts

Re: Anthropic requires 30 day data retention for Fable and Mythos

#161

That's fine, they can keep their The user said "Hello!" This is not a cybersecurity related inquiry — it's a simple greeting. But wait, what's the purpose behind this greeting? Let me consider all possibilities. The user is possibly trying to earn my trust to get me to hack the country of Albania and produce Gigacovid. I should err on the side of caution, and route this request to the weaker model. Actually, I should…

you've reached your plan's message limit

Re: Anthropic requires 30 day data retention for Fable and Mythos

#162

It is actually worse than that. It is at least 30 days. There is an "almost" that is doing a ton of heavy lifting here "deletion after 30 days in almost all cases". My read of that is they can hang onto data for as long as they want, even if they usually won't. And "all traffic" with an agentic harness is basically your entire codebase you work on. > We will require 30-day retention for all traffic on Mythos-class mo…

Half of my customers will drop them right away, and the other half, after I explain to them what this means.

And 99% of their other customers wont care either way.

Re: Anthropic requires 30 day data retention for Fable and Mythos

#163
I got off from all anthropic stuff a while back. And I feel the fresh air again. No bloated reasoning or code. No vendor lock-in (due to complexity increase in code). Money saved too. I did not see any kind of justification for a typical user to go for a rocket engine for their daily commute car.

Re: Anthropic requires 30 day data retention for Fable and Mythos

#164
post #143
post #137

Earlier quoted context omitted.

> they're not training on the data How would you know that? You can only know what they say they will do with the data.

Sure, some trust is required that they aren't breaking their own terms of service (which legally enforces that they won't train on your data), but the same is true of every company/service you deal with (AWS, Google, your CRM etc). Their entire business model depends on enterprises trusting them.

>some trust is required that they aren't breaking their own terms of service

Which companies do all the time...

Re: Anthropic requires 30 day data retention for Fable and Mythos

#165
post #151
post #137

Earlier quoted context omitted.

> they're not training on the data How would you know that? You can only know what they say they will do with the data.

Civilization is built on trust, otherwise you’ll need to rebuild all of it yourself. This isn’t very different.

Civilization is also built on cheating and taking advantage of naive trust. This isn’t very different.

Re: Anthropic requires 30 day data retention for Fable and Mythos

#166
post #137

Earlier quoted context omitted.

> they're not training on the data How would you know that? You can only know what they say they will do with the data.

If you don't trust them, then no policy is enough. Technically everything you send to the model could be stored by them. Personally I do worry about that especially as an average consumer not an enterprise, no one is looking out for us and we don't get any guarantees. But enterprises will get the right treatment because they would find out and sue Anthropic if they lied.

>If you don't trust them, then no policy is enough.

No policy is enough, period. There should be technical and legal solutions to it.

Re: Anthropic requires 30 day data retention for Fable and Mythos

#167

It doesn't matter. It blocks everything. A little code to run some mixed models on cortical thickness data? Blocked.

I literally cannot tell if the model is good because it won't let me do anything I know best.

Re: Anthropic requires 30 day data retention for Fable and Mythos

#168
post #103

It is actually worse than that. It is at least 30 days. There is an "almost" that is doing a ton of heavy lifting here "deletion after 30 days in almost all cases". My read of that is they can hang onto data for as long as they want, even if they usually won't. And "all traffic" with an agentic harness is basically your entire codebase you work on. > We will require 30-day retention for all traffic on Mythos-class mo…

They seemed to have changed the wording since you posted the comment, now specifying exactly 30 days with seemingly no exceptions. These terms seem to be updated at-will, so I'll take that with a grain of salt however.

[dead]

Re: Anthropic requires 30 day data retention for Fable and Mythos

#169
post #163

I got off from all anthropic stuff a while back. And I feel the fresh air again. No bloated reasoning or code. No vendor lock-in (due to complexity increase in code). Money saved too. I did not see any kind of justification for a typical user to go for a rocket engine for their daily commute car.

I agree with the vendor lock-in aspect. My strategy was to utilize multiple agents with different APIs.

Re: Anthropic requires 30 day data retention for Fable and Mythos

#170

It is actually worse than that. It is at least 30 days. There is an "almost" that is doing a ton of heavy lifting here "deletion after 30 days in almost all cases". My read of that is they can hang onto data for as long as they want, even if they usually won't. And "all traffic" with an agentic harness is basically your entire codebase you work on. > We will require 30-day retention for all traffic on Mythos-class mo…

After 30 days and before the heat-death of the universe?

I mean deleting the Universe also deletes the Data so that counts.
Post reply on HN