> 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 ge

> 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. 100%. The thing is, I've seen in B2B sales, one business handling another's data will have to very explicitly say who will be acting as subprocessors and storage of data. You might have to disclose that you're using AWS and Snowflake to store and process data. Maybe it's time for B2C to start doing that, too. Instead of "We may send your data to 3rd parties for processing", say WHICH 3rd parties and WHY. > legal brevity An exceptionally rare thing to see. "Legalese" exists because people create loopholes by exploiting the slightest ambiguity. I invented a story of a mom telling her kid to stop jumping on the bed, and the kid says "I'm not jumping, I'm hopping!" and goes into a diatribe on the difference between jumping and hopping, the mom says "well quit it!" and leaves, only to come back later and the kid is still jumping, the mom is angry, and the kid says "I'm not jumping or hopping, I'm bouncing!" and eventually the mom has to say something like "Do not jump, hop, bounce, spring, leap, or otherwise use your feet or any other body part, nor any object, to propel yourself upwards or laterally from the bed". And then later, the mom checks on the kid, and he has removed the mattress from the bed and is still jumping on it.