Wedding photos and guest privacy: the honest answer

Someone will ask. Usually a friend who works in an office where data protection training is compulsory, usually two weeks before the wedding, usually in a way that makes you worry you have missed something.

The answer is more reassuring than the question sounds, and the part worth knowing is not the legal part. It is what to do when a guest asks you to take a photograph down. This is not legal advice and nothing here is a substitute for it, but it is what the text says and what actually happens.

Wedding photos and guest privacy: what the GDPR text says

The regulation exempts private life explicitly. Recital 18 of the General Data Protection Regulation says it does not apply to processing of personal data by a natural person in the course of a purely personal or household activity, with no connection to a professional or commercial activity.

A wedding is the textbook example of a purely personal activity. Collecting photographs of your own wedding from your own guests, to keep and to show to the people who were there, is not something the regulation is aimed at, and you do not need a consent form, a privacy notice or a lawful basis for asking your cousin to send you a picture of the cake.

The same recital carries a second half that is less often quoted and matters more. The exemption covers the person. It does not cover a company that provides the means. So the couple are outside it and the service they use is inside it, which is the correct way round, and it is why any gallery service you use should have a privacy policy that names who stores your photographs and where.

Where the personal exemption stops

It stops at the word personal, and the boundary is easier to feel than to define. Collecting the day among the people who were at it is personal. Publishing it is a different act.

Posting a guest's photograph to a public account is not covered by the same reasoning, and neither is anything with a commercial edge, which is why a venue that wants to use your wedding on its website will ask you separately and should. Children are the other place to slow down. A photograph of somebody else's child at a private party is fine. That photograph on a public feed is a conversation you should have with their parents first, and most parents will tell you their position immediately if asked.

None of that requires paperwork. It requires knowing that a shared gallery and an Instagram post are not the same act, even when the photograph is.

The three requests you will actually get

In practice the law almost never comes up and these three do.

• Take that one down. Somebody hates a photograph of themselves. Take it down, immediately, without asking why. It costs you one frame out of nine hundred and refusing costs you something worth much more.
• Please do not post me anywhere. Usually a colleague, sometimes somebody with a genuine reason they do not owe you. Write the name down, tell whoever manages the account, and keep them out of the public posts. The gallery is usually fine, the public feed is not.
• Not my children on social media. Increasingly common, entirely reasonable, and worth asking about before the day rather than after.

Handle all three the same way: no negotiation, no explanation asked for, done within the hour. A person who has to ask twice tells everybody.

One sentence on the card settles most of it

Almost every awkward moment here is prevented by telling people what is happening before they take part rather than after.

A line on the card or the sign is enough: that photographs uploaded here go to the couple, that the gallery is not public, and that anybody who would rather not appear should say so to somebody named. That last part is what does the work, because it gives the one guest who minds a route that is not a confrontation in the middle of a party.

It also, quietly, achieves what a consent form would have achieved, without any of the ceremony. People were told, in plain language, before they took part. That is the whole substance of what a policy is trying to do, and at a private celebration among people who know each other it is both sufficient and better manners.

What a shared gallery changes, and what it does not

A gallery makes photographs easier to reach, which cuts both ways, so the two settings that matter are who can open it and who can take something out of it. A gallery reachable only by a code on a card at the venue is a very different object from a public album, and it is worth being able to say which one yours is when somebody asks.

It also gives you one place to remove something from, which is the practical improvement over a group chat. A photograph deleted from a chat has already been saved by nine people and the request has to be repeated to all of them. In a gallery, taking it down is one action and it is actually gone.

Ours is a code, not a public page, and the privacy policy names every company that touches a photograph, which is the question a careful guest is actually asking. We have written separately about the etiquette side of guest photographs, which is where most of these situations are really settled.

The short version: you are almost certainly fine, nobody needs to sign anything, and the one thing worth deciding in advance is who is authorised to take a photograph down at eleven at night without asking you first.