Even if this is not what Adobe are doing, the author of the tweet is not incorrect to make such an interpretation from the terms.<p>Now would be a good time for Adobe to do away with vague "catch all" language, because we now live in an era where user data is being swept up for AI model generation and governments are leaning heavily into tech companies for policing.<p>However to play the devil's advocate we can see how these terms have come about without rounding up to tweeter's interpretation.<p><i>Note: There is also good reasoning to believe this interpretation because using software that collects data indiscriminately would significantly impact the ability of Adobe's large customers to use their software. Since service agreements and various compliance standards forbid as such.</i><p>First up are Adobe's online terms that relate to CSAM, abiding by subpoenas, security, and feedback/bug support. Those are all pretty standard for hosted services. So while some may not like that, this is a "nothing to see here" clause.<p>However the "gotcha" for users comes about because <i>a lot</i> of Adobe's features rely on their cloud infrastructure which they may use unintentionally. This extends beyond using their cloud storage allowance or the Behance social network. Here are some examples:<p>- Generative AI: in & out painting will send image data to Adobe for matching.<p>- Farm rendering: Some apps, such as Dimension, feature off-site processing options. These of course mean that your content, textures, logos, etc are then on Adobe's servers for processing.<p>- Forms dissemination: Hosting forms means that Adobe will have not just your content, but also that of people that fill out the form.<p>- Review features: Review features are all performed through the cloud.<p>- Moving documents between devices: Using the app's built into tools to move a document/graphic between devices is performed via the cloud.<p>There are many more scenarios, but I've tried to choose a range to demonstrate variety, and how that extends beyond actions where the user is deliberately using online storage.<p>The next part of Adobe's terms is noting that they don't specifically call out online versus offline processing, rather they use the terms "Services" and "Products". This would appear to be explainable as Adobe's apps include algorithms that enforce certain types of document security, such as anti-counterfeiting measures, watermarking, Content Credentials and copyright embedding. The vague language of this clause is the source of the problem, as Adobe don't demarcate where and why the processing is performed.<p>So in summary the overly vague language can be chalked up to legal brevity, but in this era that is insufficient for peace of mind.