Comment by catoc
2 days ago
That an LLM needs input tokens to produce output was understood. That is not what the privacy policy is about. To me the policy reads Anthropic also subsequently persists (“collects”) your data. That is the point I was hoping to get clarified.
The only thing Anthropic receives is the chat session. Files only ever get sent when they are included in the session - they are never sent to Anthropic otherwise.
Note that I am talking about this product where the Claude session is running locally (remote LLM of course, but local Claude Code). They also have a "Claude Code on the Web" thing where the Claude instance is running on their server. In principle, they could be collecting and training on that data even if it never enters a session. But this product is running on your computer, and Anthropic only sees files pulled in by tool calls.
So when using Cowork on a local folder and asking it to "create a new spreadsheet with a list of expenses from a pile of screenshots", those screenshots may[*] become part of the "collected Inputs" kept by Anthropic.
[*]"may" because depending on the execution, instead of directly uploading the screenshots, a (python) script may be created that does local processing and only upload derived output
Yes, in general. I think in your specific example it is more likely to ingest the screenshots (upload to Anthropic) and use its built-in vision model to extract the relevant information. But if you had like a million screenshots, it might choose to run some Python OCR software locally instead.
In either case though, all the tool calls and output are part of the session and therefore Input. Even if it called a local OCR application to extract the info, it would probably then ingest that info to act on it (e.g. rename files). So the content is still being uploaded to Anthropic.
Note that you can opt-out of training in your profile settings. Now whether they continue to respect that into the future...
1 reply →