AI in your photography contract: questions for a lawyer

Clients ask whether you use AI, and the honest answer is usually longer than yes or no. This piece does not give you wording. It gives you the questions to answer about your own workflow first, and then the questions worth taking to a lawyer, so the clause you end up with is one you can explain to a couple at an inquiry call.

Read this before you copy anyone's clause

This article is only questions because the alternative is what a lot of photographers are doing right now: pasting a paragraph found in a Facebook group into an agreement without checking whether it describes their actual workflow. A clause that bans a category of tool you quietly use every week is not protection. It is a liability you signed yourself.

If your agreement is thin in the ordinary places too, fix those first. Our plain English guide to what every photography contract needs walks through the ten clauses that prevent most disputes, and the seven mistakes that quietly break contracts covers the gaps people find the expensive way. Then start here, because "do you use AI?" is not one question and your workflow is not one activity.

What does "AI" mean in your workflow, exactly?

Before you can ask a lawyer anything useful, you need an inventory. Not a vibe, a list. Write down every step between the card and the gallery, and mark what each step does to the file and where the file physically is while it happens.

The distinction that matters most is between choosing photos and changing photos. A picking tool proposes a shortlist: closed eyes, missed focus, six near identical versions of one moment. The pixels of the photograph you choose are not altered, and the final selection is still yours. Generative fill is a different activity. It adds content that was never in front of the lens. Treating both as one word is how contracts promise things nobody meant.

Fill that table in for your own studio and you have done the hard half of the work. Bring it to the lawyer with your current agreement, because an hour spent on your real list beats three spent on hypotheticals. Write it in the words you would use with a client, not in vendor language.

Which question is the client actually asking?

When a couple asks whether you use AI, they are almost never asking a technical question. Ask a follow up before you answer, because the reply that reassures one client alarms another. In practice the question is usually one of four:

• Will we look fake? An authenticity worry. They have seen a friend's gallery where everyone had plastic skin and an invented sunset.
• Where do our photos go? A privacy worry, and the sharpest one at a private wedding or a family session with children.
• Can you change what happened? A truthfulness worry, common with commercial and editorial clients, and with anyone who has read about generated images.
• Who owns the result? An ownership worry, which usually turns out to be about licensing rather than AI at all.

Each of these points at a different part of the agreement, which is why one universal sentence rarely does the job. It is also why the answer belongs in a conversation as much as a document. Photographers who already explain their selection process well have an easier time here, and how to explain the cull to clients covers that conversation in detail.

Whatever a client tells you, write it into the job notes the same day. If a couple says no cloud processing, that promise now has to survive a busy season, a second shooter and an editor. A commitment that lives only in the memory of one sales call is not a commitment, it is a risk.

The questions worth an hour of a lawyer's time

Do not open with "do I need an AI clause?" Ask about the situations you actually face. These are the questions worth an answer, grouped so an hour goes further.

On the agreement you already have

• Does my existing editing discretion clause already cover AI assisted picking, noise reduction and sharpening, or is it silent in a way that could be read against me?
• Does anything in my current wording accidentally promise that no software touches the images?
• If I say nothing about AI at all, what is the realistic exposure in my market?

On consent and approvals

• At what point does an edit become material enough that I should get written approval for that specific image rather than rely on a general permission?
• Should approval be per image, per project, or per intended use, and does the answer change for advertising?
• If a client approves a change for a private album, does that approval carry over when the same file is published?

On data and third parties

• Which privacy, biometric or data processing rules apply where I work and where my clients live?
• How should I describe third party processing, subcontractor access and storage location without over promising?
• Do face grouping features in the tools I use raise anything specific in my jurisdiction?

On ownership and risk

• Does heavy AI involvement affect copyright in the delivered image where I work, and does my client license need different wording as a result?
• What should indemnity look like if a client publishes an altered image and a third party objects?
• Are there sectors, such as journalism, legal evidence or regulated advertising, where I should decline the work rather than write a clause?

Notice what none of these ask for. None of them ask for a longer contract. The aim is a short, true set of promises you can keep on your worst week, not a paragraph that sounds impressive and describes somebody else's studio.

What needs telling, and what needs asking?

There is a difference between telling a client something and asking their permission, and a lawyer will want you clear about which one you mean for each step. Questions that sort the list:

• Would a reasonable client in my market already assume this is part of professional photography? Color, crop and exposure usually sit here. Does my selection process sit here too?
• Would the client's opinion of the photograph change if they knew? If yes, that leans toward asking rather than telling.
• Could this step change what the picture says happened? Anything that adds, subtracts or swaps a person or object belongs in a different category from finishing.
• Is this a promise about my process, or a promise about the file the client receives? Those often need different homes: a privacy notice for one, the agreement for the other.

A related trap is the word untouched. Photographers use it loosely to mean not retouched, and clients hear straight from the camera. If you ever hand over less finished files, define that product before you promise it, which is the argument in should you deliver unedited photos, and the same care applies when someone asks for the raw files.

Check your existing promises for collisions too. A sneak peek deadline and a no cloud restriction can quietly conflict on a Sunday night, which is one reason we picked apart the sneak peek clause separately.

Where do the files go, and who else can see them?

This is the part clients care about most and photographers check least. Before a lawyer can describe your data handling, you have to know what it is. Ask each vendor, in writing:

• Where are the files stored, and in which country?
• How long are they kept after a project ends, and can I purge a project myself?
• Does the provider use customer images to train models, and can I opt out?
• Who inside the company can view my clients' images, and under what circumstances?
• What happens to my clients' files if the company is sold or shuts down?

Then, for counsel: which of those answers must appear in the agreement, which belong in a privacy notice, and which need active consent rather than a link at the bottom of a page.

Whatever you do, do not promise that images never leave your computer if you use a cloud gallery, an online backup, a remote editor or a cloud culling service. It is an easy sentence to write and an impossible one to keep. Specific and true beats absolute and heroic.

Where the processing happens varies more than people expect: some picking tools run entirely on your own machine, others require you to upload first, and what those tools can actually judge is a separate question worth asking each vendor. On our side of it, Kepla's picking app is still being built for iPhone, iPad and Mac, so the honest thing to say today is that our booking page is live and free while we build. When the picking app does arrive it never deletes, moves or renames a file. It marks which photos it picked, and every original stays where you put it.

Who else has to follow the answer?

A clause protects nobody if the person editing the gallery has never read it. If you work with associates, second shooters or an outsourced editor, the policy has to travel with the job.

• Do my contractor agreements say the same thing about tools, storage and cloud access as my client agreements do? If a client restriction is stricter than my editor's contract, which one wins?
• How does a per job restriction reach the person doing the work? A flag in the job folder and the handoff message beats an assumption every time.
• Can an editor try a new tool on a live client job, or does that need my approval first?
• When a job ends, who removes access, and how do I know it happened?
• If a subcontractor breaks a client promise, what does my agreement with the client say about that, and what does my agreement with the contractor say?

The practical version is a one page policy: approved tools, the standing rules, and who to ask when something is not covered. Teams that already write down how photos get chosen find this easier, because the habit exists: see culling standards for second shooters.

Does the promise survive a busy week?

The last question is the one that decides whether any of this holds. Before each job, or at least before each new type of job, run the check:

1. What tools and steps are planned for this specific project?
2. Does any of it involve a cloud transfer, a contractor, or a change to what the picture says happened?
3. What has this client asked for, in writing, and does anything in the brief or their industry add rules?
4. Which edits are routine here, and which need approval before delivery?
5. Where are those restrictions recorded, and who else has seen them?
6. Where do approvals get filed so the approved version is identifiable a year later?

If any answer is uncomfortable on a normal week, it will be unworkable in October. Take that one back to your lawyer and ask for a promise you can keep. A short honest paragraph that matches your workflow protects you better than a long one you quietly break, and it makes the client conversation shorter too.

FAQ