Wedding Photos, & More Consent Nobody Asked For

Wedding photos are consent soup.

The couple hired the photographer. The photographer owns or licenses parts of the work depending on the contract. Guests appear in the images. Children may appear in the images. Venue staff may appear in the background. A cousin may appear in a state that suggests the open bar achieved product-market fit.

Before AI, retouching still had privacy considerations, but the workflow was easier to understand. The photographer edited files in Lightroom, Photoshop, or a similar tool. Maybe files moved through cloud storage. Maybe a gallery went online. Not perfect, but familiar.

AI editing adds new questions. If a photographer uses a face retouching tool, where do the images go? If a guest is removed from the background, is their face processed by a third-party provider? If the couple asks for “cinematic versions” of the wedding party, are those images retained? If a tool improves itself using uploaded examples, who had the right to grant that permission?

Most people did not plan for this. Wedding contracts often mention editing rights, delivery, gallery hosting, copyright, and usage. They may not clearly cover AI processing, model providers, retention, training, or deletion. The gap is not always malicious. It is just new enough that many workflows are improvising in a fog machine.

The privacy-friendly version starts with scope. AI edits should be used only for the agreed work. Raw uploads should not become training data. Temporary files should expire. Galleries should be private by default. The photographer should be able to tell the couple which tools handle the images and what those tools retain.

There is also a consent design problem. It is not realistic to get signed AI-processing permission from every guest for every image in many ordinary weddings. That makes minimisation more important. If the workflow does not retain, train on, publish, or expose images beyond the job, the consent surface is smaller and easier to explain.

Couples do not need a lecture on data protection law while they are choosing confetti shots. They need simple language from photographers and platforms: what AI touches, why it touches it, how long files remain, and whether human reviewers or model training are involved.

Wedding photos are intimate because they are shared memory. AI can help preserve that memory beautifully. It should not quietly turn the whole guest list into a dataset with better lighting.

Further reading: The weird new etiquette of uploading someone else’s face, Why consent is becoming the core UX problem in AI images, and Why “Delete My Uploads” needs to be verifiable.