In mid-2024, Adobe prompted users to accept revised terms of service. Most people clicked through. A few read closely — and what they found sparked a panic that spread across creative communities worldwide.
One clause, in particular: “We may access your content through both automated and manual methods, such as for content review.”
Within days, the backlash was severe enough that Adobe’s CEO felt compelled to publicly respond. A tweet highlighting the clause received over five million views. Photographers, illustrators, video editors, and designers started asking a question they’d never thought to ask before: what exactly does Adobe do with the files I store in Creative Cloud?
The panic was partially overblown. But the underlying concern was legitimate. And what it exposed about the nature of creative cloud storage goes beyond Adobe.
What Adobe’s Terms Actually Said
Adobe walked back the controversy quickly, clarifying that they do not train generative AI models on user content without consent. The clause about accessing content was described as necessary for content moderation — specifically, scanning for illegal content like child sexual abuse material — which is a standard (and legally required) practice for cloud storage providers in many jurisdictions.
The specific clarifications Adobe provided:
- Adobe does not train generative AI models on user or customer content unless the content has been submitted to the Adobe Stock marketplace with permission
- Adobe will not have third parties train generative AI models on user content
- Content stored locally is not scanned; cloud-synced content may be automatically scanned for illegal material
- Human review of content can occur only in specific, limited circumstances — CSAM detection, safety flags, legal requests
These clarifications substantially addressed the specific fear that drove the panic: that Adobe might use Creative Cloud files as training data for Firefly, Adobe’s generative AI image tool. That’s not what the terms permitted, Adobe said, and the company subsequently added summaries to each ToS section to make this clearer.
So What Was the Real Problem?
The panic revealed something more fundamental than a single terms-of-service clause.
Millions of creative professionals had been storing their most commercially and personally valuable work in Creative Cloud — client files, portfolio work, personal projects, unreleased work — without having read, or having reason to think about, the terms governing that storage. The files were there because Creative Cloud is where the tools live. The storage was a convenient byproduct of the software subscription.
The 2024 controversy made people realize that “we store your files as part of the software service” and “we have terms that govern what we can do with those files” are not the same thing, and that the second part had always been true — they’d just never thought to look at it.
Creative Cloud’s Specific Access Model
Adobe is a software company, not a privacy-first storage company. Its cloud services exist to support its software products, not as a standalone storage offering. This shapes what the terms are written to accommodate.
Adobe maintains the right to access cloud-synced content for:
Content moderation and safety: Scanning for illegal content, as described above. This applies to cloud-synced files and is conducted through automated systems.
Product improvement: Adobe uses aggregated, anonymized usage data and technical file data to improve its products. The terms describe how “usage information” — which can include metadata about files and how they’re processed — may be used to improve AI and machine learning features.
Legal compliance: Adobe can and must respond to valid legal requests, including subpoenas and court orders, which may require disclosing user content.
Feature integration: When you use Creative Cloud features that process your files — AI-powered editing in Photoshop, background removal in Express, auto-tagging in Lightroom — that processing often involves sending content to Adobe’s servers even if you don’t think of yourself as “uploading to the cloud.”
None of this is extraordinary for a cloud software platform. The issue is the mismatch between what users assumed (“my files are stored, unread, like a file cabinet”) and what the actual model is (“files are stored in a service environment where various operational and safety processes run”).
The AI Training Question: Current State
Adobe has staked out a clear position on generative AI training: no user content is used to train AI models without consent, unless that content was specifically submitted to Adobe Stock.
Adobe’s Firefly generative AI is, according to the company, trained on Adobe Stock images and other licensed datasets, not on the Creative Cloud libraries of paying subscribers.
The key caveat: Adobe uses AI and machine learning extensively within its products — for content-aware fill, background removal, subject selection, auto-tagging, and dozens of other features. The model used to detect a person in your photo for background removal is AI, and AI requires training data. Adobe’s stated position is that this training uses different data sources than customer Creative Cloud libraries, but the terms don’t make this distinction crystal-clear to a casual reader.
What This Means for Your Creative Work
The practical implications differ depending on what you store and why.
Client work and commercial projects: If you’re a professional photographer, designer, or video editor storing client work in Creative Cloud, the reputational and legal stakes of unintended disclosure or access are real. The question isn’t whether Adobe is likely to misuse client files — it’s whether the terms you accepted are compatible with the confidentiality agreements you’ve made with clients. Many professional service agreements require reasonable safeguards for client materials; worth checking whether Creative Cloud meets those requirements in your context.
Personal creative work and private photos: Creative Cloud isn’t optimized as a personal photo archive or private creative journal. The service is built around the tools, not around providing private storage as a primary value. Files stored there are subject to terms written to support the software product, not to provide storage privacy guarantees.
Unreleased work: Photographers storing images before release, musicians storing unreleased tracks, designers storing concepts before pitching — the risk isn’t that Adobe will leak this content. The risk is that the storage terms and scanning practices are designed around Creative Cloud’s needs, not around pre-release confidentiality.
The Broader Lesson About Creative Platform Storage
The Adobe situation exposed a pattern that applies beyond Adobe:
When you use a software platform’s cloud storage because it’s bundled with the tools you use, you’re making a storage decision by default rather than by choice. The storage terms are written to serve the platform’s needs, not to optimize for your storage privacy.
This is particularly worth examining for creative professionals who store their most valuable work — portfolios, client projects, personal archives — inside tool-bundled cloud services. The tools are excellent. The storage, from a terms and privacy perspective, is the terms that the tool company needed to write, not the terms a privacy-focused storage service would offer.
Storage and tools don’t have to live in the same place. Lightroom can edit a photo that’s stored in daftei. Final Cut Pro can work with files that aren’t in iCloud Drive. Separating the tool from the storage means you can choose each based on what it’s designed for.
What to Look for in Storage for Creative Work
If you’re evaluating where to store creative work — especially personal photos, archival files, or client materials — the questions worth asking:
What can the provider access, and for what purposes? Content moderation scanning (for illegal content) is standard practice for cloud providers. AI training on your content without opt-in is a different category. The distinction matters.
Are the terms written for storage or for software? Terms bundled with software products are designed to support that software’s operations. Terms for a storage service are written specifically to govern storage.
What happens to your files if you stop paying? Creative Cloud accounts deactivate and files may become inaccessible after a grace period. If you store personal archives in a tool-bundled service, the storage is tied to the subscription.
What does deletion mean? As with any cloud service, “deleted” is the beginning of a process, not the end of it. Understanding the deletion timeline and what “permanent” means for a specific service matters for work you genuinely want gone.
Adobe’s 2024 terms controversy didn’t reveal a conspiracy. It revealed that millions of professionals had stored their most valuable work in a cloud service without thinking about the storage terms, because the cloud was there and convenient and they were there for the tools.
That’s a reasonable way to have ended up in that situation. It’s also worth correcting, deliberately, once you know it’s the situation you’re in.