Cease and Desist Over AI-Generated Content 2026: The First 72 Hours

Read the Letter Before You Answer It

Identify which instrument arrived

A lawyer's demand letter, a platform takedown notice and a marketplace policy strike are three different machines with three different clocks. The letter asks you to act and threatens a court. The takedown has already acted — the asset is down, and the only lever is a counter-notice. The policy strike is decided by a private appeals process where statutory arguments carry little weight. Work out which one you are holding before anyone drafts a reply.

Find the specific right being asserted

Copyright in a particular work, a registered trademark, a person's name or likeness, a database or licence term, or a contract you signed — each has different elements and different defences, and a single letter often gestures at several. If the letter never identifies the protected work with any specificity, that is both a weakness in the claim and the first thing to ask about.

Separate the training-data argument from your problem

Whether a model was lawfully trained is a fight between rightsholders and model vendors. A claim against your business is about the asset you published and the use you made of it. You can lose that claim regardless of how the model was built, and you can win it while the training question stays unresolved. Do not let your reply adopt the vendor's litigation posture as your own.

Check whether the asset is still live anywhere

Website, ads, app stores, packaging, decks, partner sites, syndicated feeds, the CDN cache and the print run in a warehouse. Continuing to publish after notice is the fact that turns an argument about similarity into an argument about willfulness, and it is decided by inventory rather than by intention.

Five Things to Freeze Today

Everything that makes this defensible is metadata, and most of it expires on someone else's retention schedule.

The generation record

Prompt text, negative prompt, model and version, any seed, sampler or style settings, and every reference image or file uploaded. This is the closest thing to a provenance chain you will ever have for the asset, and the version that matters is the one from the day it was generated — not what the account shows after the tool updated.

Who generated it, when, and in which account

Timestamps and identity, including whether it happened in a corporate seat or in an employee's personal account. The latter changes the ownership question, the contract question and the indemnity question at the same time, and it is discovered at the worst moment in about a third of these files.

What happened to the output afterwards

Human editing, compositing, retouching, the versions that were rejected and the version that shipped. Human contribution is relevant to what you can claim to own and to how far the published asset sits from the work being asserted.

The licence and the settings in force

The tool's terms on the generation date, the plan you were on, the commercial-use grant, any indemnity offered, and whether content filters or opt-outs were enabled. Vendor indemnities are usually conditioned on the settings — one disabled filter can void the protection you are about to rely on.

A litigation hold, issued in writing

Named custodians, the systems in scope, and an instruction to suspend normal deletion in the design tool, the asset manager, chat and the vendor account. Quietly deleting the file is the single worst move available: it does not remove the copy in the claimant's exhibit, and it converts a defensible dispute into an argument about your conduct.

The Clocks Nobody Diarised

Prompt-notice conditions expire in days

Where a vendor offers copyright indemnity, it almost always requires prompt written notice of the claim through a specified channel. The condition is measured from when you learned of the claim, so the clock started on the day the letter arrived and is running while your team debates the merits. Send the notice first; you can withdraw a notice and you cannot resurrect a lapsed condition.

Indemnity is conditioned on how you used the tool

Typical carve-outs: prompts that named a protected work, artist or brand; disabled filters or safety settings; use of an output the vendor flagged; modification of the output; use on a plan without the commercial grant. Establish which of these is true from your own records before you assert coverage to anyone.

They will want control of the defence

Indemnities usually carry a right to assume and control the defence, and sometimes a bar on settling without consent. That can be exactly what you want, or it can mean a vendor with portfolio-wide incentives running a fight you would rather settle quietly. Read the clause now so the decision is informed rather than reflexive.

Your own downstream promises may be worse

If you delivered the asset to a client, the warranty in your services agreement probably says the deliverable does not infringe, with your own indemnity behind it. Agencies routinely carry an obligation upward that is broader than anything they hold from their tool vendor. Find that mismatch on day one, because your client will find it by day ten.

Insurance has its own notice condition

Media liability, professional liability and some cyber policies respond to intellectual-property claims, and all of them are claims-made with notice conditions. Notify in writing on the policy's schedule even if you expect to handle the matter yourself — late notice is the way a covered claim becomes an uncovered one.

The Answers Available in Week One

Take it down without conceding, where it is cheap

For a marketing asset with no strategic value, removing it while stating that you take third-party rights seriously and are reviewing the claim resolves a large share of these letters at a cost of one afternoon. Say that removal is not an admission; do not say the asset infringed.

Ask for the specifics the letter left out

The work asserted, the registration or ownership basis, the date of first publication, and the specific elements said to be copied. A letter that cannot supply these is frequently a mass mailing, and the request is a normal, non-provocative response that costs you nothing.

Get a similarity read from someone who is not the author

Two assets are compared on protectable expression, not on subject matter or style. The person who generated the image is the worst judge of this. Have someone independent, ideally counsel, look at the two side by side before anyone decides how strong the claim is.

Think hard before filing a counter-notice

A counter-notice to a platform takedown generally requires a sworn statement and, in the US framework, consent to jurisdiction for the claimant's suit. It converts a removed asset into a possible lawsuit with your own signature at the bottom. It is the right move sometimes, and it is never the right move before the generation record has been reviewed.

Fix the clearance step, not just this asset

The letter is an audit finding. If generation records were not kept, if filters were off, if a prompt named a living artist, if an employee used a personal account — one of those was true, and it is almost certainly true across the rest of the library. The second letter is much more expensive than the first if nothing changed in between.

Questions Teams Ask

Should we just delete the asset and hope it goes away?

Remove it from publication, yes — keep every record of it, absolutely. Those are two separate actions and teams routinely conflate them. Taking the asset down limits the exposure that accrues while a claim is live and is not, on its own, an admission if you say so plainly. Destroying the generation record, the prompt history, the source files and the internal discussion is a different act with a different consequence: the claimant already has a copy of the published asset, so deletion removes only your evidence, and a court asked to draw conclusions about missing records tends to draw them against the party that deleted them. Issue a written hold on the systems involved before anyone tidies anything, and make the hold explicit about the design tool and the vendor account, which are the two places normal retention quietly removes the useful material.

Our AI vendor promised copyright indemnity. Are we covered?

Possibly, and the answer usually turns on your own conduct rather than on the strength of the claim. Read the clause for three things. First, the notice condition: nearly all of them require prompt written notice through a named channel, and that clock started when you learned of the claim, so send the notice before you finish assessing the merits. Second, the conditions on use: indemnities commonly exclude prompts that named a protected work, artist or brand, outputs generated with filters or safety settings disabled, outputs the tool itself flagged, heavily modified outputs, and use on a plan that did not carry the commercial grant. Check each against your records, because asserting coverage you do not have wastes the only week in which you had options. Third, control: most indemnities let the vendor assume the defence and restrict settlement, which may or may not match what you want from the dispute.

Does it matter that a model, not a person, produced the asset?

Less than people expect on liability, and more than people expect on what you own. On the infringement question, the analysis is about the published asset and its relationship to the work asserted; the absence of a human hand does not supply a defence, and 'a tool made it' is not one of the recognised answers. Where the origin genuinely matters is ownership and remedies. Purely machine-generated material may have little or no protection of its own, which affects your ability to claim rights in the asset, to register it, and to pursue anyone who copies it from you. It also affects the practical calculus in a dispute: if your asset is not itself protectable, defending it has less strategic value than replacing it, which often points toward a quick removal and a redesign rather than a fight.

The claim came as a platform takedown. Can we file a counter-notice?

You can, and it is a heavier step than the form makes it look. Under the US notice-and-takedown framework a counter-notice is a statement made under penalty of perjury, and it ordinarily includes consent to jurisdiction in a court where the claimant may sue you — so filing it invites the lawsuit that the takedown avoided, with your signature already on the record. It is the right move when you have a real basis: a licence, independent creation with a documented generation record, a fair-use position reviewed by counsel, or a claimant who does not own what they asserted. It is the wrong move as a reflex to get an asset back online, and it should never be filed before someone has read the prompt history and confirmed that nothing in it named the work being asserted.

We delivered the asset to a client. What do we owe them?

Start from the services agreement rather than from the facts, because what you owe is usually written down: a warranty that the deliverable does not infringe third-party rights, an indemnity behind that warranty, and sometimes a notification obligation triggered by exactly this event. Agencies and studios frequently carry an obligation upward that is broader than anything their tool vendor gives them, which is the mismatch to identify on day one rather than during a negotiation with a client's counsel. Practically: notify the client promptly and factually, tell them what you are doing about the asset, avoid characterising the merits in writing before you know them, and get the generation record together for that specific deliverable. Then fix the intake — a clearance record kept at generation time is the cheapest possible version of this conversation, and it is the artefact that decides whether the second letter is a nuisance or a crisis.

The Provenance Test

Pick the AI-generated asset currently in your most expensive placement. Ask the team for the prompt, the model version, the reference files and the date. Give them an hour.

If that comes back, you can answer a letter. If it does not, the defence to the first claim against your library does not exist yet — and the only moment it can be created is before the claim, not after.

A Letter Arrives About an Image Your Team Generated. Now What?