You booked a campaign in Lisbon, or a headshot day at a client's London office. Your usual model release has worked on hundreds of US shoots. Then the client's legal team asks how your paperwork handles GDPR photo consent, and you notice your form never mentions data protection.
This guide covers where US releases and GDPR split apart and what to add before you fly. It is a practical overview, not legal advice. Data protection rules vary by country and by how you use the images, so check anything high-stakes with a qualified local advisor.
Why a US-style model release does not cover GDPR photos
A US model release is built around the right of publicity. Many states limit the use of a person's name or likeness for advertising or trade without consent. Our New York model release form checklist shows one example. So the release answers one question: may I use this person's image commercially? It usually grants broad rights in all media, often forever, often with no way to take them back.
GDPR starts somewhere else. Under the EU General Data Protection Regulation and its UK version, the UK GDPR, a photo of an identifiable person is personal data. Taking it, editing it, saving it to a cloud drive, sending it to a client and posting it all count as "processing." Each of those needs a lawful basis and a clear purpose, and the person has to be told about it up front.
So a US release is about the right to use an image. GDPR covers how you handle someone's data from capture to deletion. A signed US form still shows that the person agreed. But it rarely answers the questions a European client, subject or regulator will ask. Why are you processing this? For how long? Who else gets it? How do I say no later? If you need the document now, start with the model release form and pick your shoot type and state.
Consent is not the only lawful basis (and when it is the right one)
Many photographers assume GDPR means "get consent for everything." Not quite. Article 6 of the GDPR lists six lawful bases. Three come up on shoots:
- Contract. A client books and pays for a headshot or family session. Processing their images to deliver that job can rest on the contract itself.
- Legitimate interests. Wide coverage at a conference may fit here. You have to weigh the attendees' interests, tell them about the photography and give them an easy way to object.
- Consent. This fits uses that go beyond what the person needs from you: a model in an ad campaign, your portfolio, social posts, stock licensing or AI training.
Consent under GDPR has a high bar. It must be freely given, specific, informed and unambiguous, shown by a clear yes. A pre-ticked box doesn't count. Neither does hiding portfolio use inside booking terms so the client can't book the session without agreeing to it.
The practical takeaway: match a basis to each use. Don't call something consent if the person can't really refuse. And if you rely on consent, you have to honor the right to take it back.
What a GDPR-compliant photo consent form needs to say
A GDPR-style form reads more like a short, plain notice than a rights grant. Aim to cover:
- Who you are. Your name or studio, your contact details, and a note that you decide how the images are used.
- Named purposes. List each use on its own line: client delivery, website portfolio, Instagram, paid ads for a named brand, stock licensing. Give each one its own tick box or initial line.
- What data you collect. The images, plus name, email, signature and anything else on the form.
- Who receives it. The client, agency, retoucher, print lab, cloud storage, stock agency.
- International transfers. If files go to US servers or a US client, say so.
- Retention. How long you keep the images and the signed form.
- Rights. Access, correction, erasure, objection and withdrawal, plus how to use each one.
- Complaints. The right to complain to the data protection authority, such as the ICO in the UK.
Write the form in a language the subject reads well. If you're shooting in Madrid, give the subject a version they actually understand. Our bilingual model release guide explains the side-by-side layout.
Don't let "all media, worldwide, forever" be your only purpose line. Vague catch-alls tend to fail GDPR's "specific" and "informed" tests.
Withdrawal, retention, and sharing: where perpetual US terms clash
This is the biggest friction point. US releases often say "irrevocable" and "in perpetuity." Article 7 of the GDPR says a person can withdraw consent at any time, and that withdrawing must be as easy as giving consent. A clause that says consent can never be withdrawn doesn't sit well with that rule.
Withdrawal doesn't reach backward. A magazine issue that already went to print stays printed. But from that point on, you stop any new use that relied on consent. That means taking down portfolio posts and pulling images from places you control. Plan for this before the shoot. Decide which uses can realistically stop and which are locked in once published, such as a print run or a campaign you delivered under a contract with the brand. Then say so plainly on the form. Our guides on handling a model release revocation and perpetual terms and release expiration cover the US side of the same problem.
Retention clashes too. GDPR's storage limitation principle says you keep personal data only as long as you need it. "Forever, just in case" doesn't count as a purpose. Set real time limits. For example, delete raw outtakes after a set number of months, keep finals for the life of the license, and keep signed forms for as long as you use the images, plus a reasonable buffer.
Sharing needs the same care. If files go to a retoucher in another country or a US cloud service, tell the subject. Some EU clients will also ask you to sign a data processing agreement. That's routine there.
Adapting your release for a UK or EU shoot
You don't need to throw out your release. Add to it instead.
- Keep the license, split the consents. Your US-style grant still records usage rights and payment. Add a separate consent section with one checkbox per purpose.
- Swap "irrevocable" for honest limits. Explain what the subject can withdraw and what stays in place once published under contract.
- Add a short privacy notice. Put it on the form or link to it. Include recipients and retention.
- Plan for sensitive images. Photos that reveal health, religion or similar details can fall into GDPR's special categories, which have stricter rules. Medical, faith-based and boudoir shoots need extra thought about scope and privacy.
- Parents sign for children. For subjects under 18, get a parent or guardian to sign and check local age rules. Start from a minor model release form and add the GDPR sections.
- Keep records. File the signed form with the images and log any withdrawal. Recording release status in file metadata helps.
Here's where SignedShoot fits. It builds model, property, minor and other release templates in your browser, based on standard industry practice such as ASMP and PPA guidance. The documents are built around US state law. For a UK or EU shoot, use the editable .docx as your starting point and add the consent, privacy and retention sections above. Subject details are never uploaded or stored on our servers. SignedShoot doesn't collect signatures, so sign on paper or with the e-signature tool you already use. And no template, ours included, guarantees GDPR compliance in any country.
A quick pre-shoot checklist for photographing people in the UK or EU
- Pick a lawful basis for each planned use: contract, legitimate interests or consent.
- List every purpose on its own line, each with its own opt-in.
- Write the form in a language the subject reads well.
- State who you are and how to reach you.
- List recipients: client, agency, retoucher, cloud storage, stock agency.
- Flag any transfer outside the UK or EU.
- Set retention periods for raws, finals and signed forms.
- Explain how to withdraw consent and give an email address that someone actually checks.
- Say clearly what stays published after a withdrawal.
- Get a parent or guardian to sign for minors.
- File the signed form with the images and log any changes.
- Ask the client whether they need a data processing agreement.
Go through that list during pre-production. Your paperwork will then fit the way Europeans think about their own image, not just the way US states think about advertising.
This article is general information for working photographers, not legal advice. SignedShoot documents are templates based on standard industry practice. They do not guarantee compliance with GDPR, the UK GDPR or any other law in any jurisdiction.
