
Rules and ethics
How UK GDPR and model releases work on British product shoots
Product photography shoots need a lawful basis, a model release form and ICO compliance. Here is how UK GDPR applies to British shoots, with a checklist.
What to take away
- On any product photography shoot with models or staff, you process personal data, so UK GDPR and the ICO rules apply.
- Pick a lawful basis before the shutter clicksconsent, contract or legitimate interests. Consent suits marketing images; contract suits staff shoots.
- A model release form is worth only what it containsidentity, scope of use, duration, territory, withdrawal terms and a signature.
- Special category data, children and vulnerable adults need extra care, usually explicit consent and a guardian signature.
- Keep shoot files only as long as needed, answer subject access requests within one month, and report serious breaches to the ICO within 72 hours.
- Your studio may be a controller or a processor. Write that into the contract, and pay the ICO data protection fee if you are a controller.
Why UK GDPR applies to a British product shoot with models or staff
A product shoot is not just lighting and lenses. The moment a person appears in frame, you are processing personal data. A face is personal data. A name, a staff rota, a signed release form and a folder of raw files are all personal data too.
UK GDPR sits alongside the Data Protection Act 2018. It applies to any organisation established in the UK that processes personal data, and to overseas studios targeting UK customers. If you book a shoot in Greater London or Greater Manchester and the images will sell a product to British shoppers, UK GDPR follows the files.
The ICO is the regulator. Its guidance for organisations covers the basics: what counts as personal data, what a lawful basis is, and what rights people have over their images. Read it before you draft a release form, not after a complaint lands.
Staff shoots are easy to overlook. A warehouse picker modelling a coat for the website is still a data subject. So is a freelance model, a hand model, or a customer photographed for a social campaign.
The Advertising Standards Authority and the CAP Code also expect images to be honest and not misleading, and the Competition and Markets Authority applies similar standards to online sales imagery. Data protection and advertising rules run on separate tracks, but both bite.
GDPR also covers the metadata. File names, timestamps, camera serial numbers and location tags can identify a person or reveal where they were. Strip or manage that metadata deliberately, especially before publishing.
Lawful bases under the ICO framework: consent, contract and legitimate interests
Every processing activity needs a lawful basis. The ICO's lawful basis guidance lists six, but three matter most on product shoots: consent, contract and legitimate interests.
Lawful bases compared
Consent
- Best for
- Specific image uses
- Withdrawal
- Easy to withdraw
- Key risk
- Not freely given
- Documentation
- Release form
Contract
- Best for
- Staff or hired shoots
- Withdrawal
- Not applicable
- Key risk
- Fresh marketing
- Documentation
- Contract terms
Legitimate interests
- Best for
- Stock, BTS, fraud
- Withdrawal
- Right to object
- Key risk
- Undocumented balancing
- Documentation
- Balancing test
Consent means a clear, affirmative agreement to the specific use of the images. It has to be given freely, and must be specific, informed and clear. A model who signs a release because the shoot will not proceed otherwise may not be giving valid consent.
Consent is also easy to withdraw. If a model withdraws consent, you must stop using the images, though you may keep a record of the withdrawal.
Contract works when the processing is necessary to deliver something the person agreed to. A staff member photographed as part of their job, or a model hired under a contract that requires the shoot, may fall here. Contract is a firmer basis for internal or operational use, but it does not stretch to fresh marketing campaigns you never mentioned.
Legitimate interests covers processing that is necessary for a genuine business purpose, balanced against the person's rights. Stock library shoots, behind-the-scenes content and fraud prevention can fit. You must document the balancing test. Legitimate interests is not a free pass for using a model's face in paid ads they never agreed to.
Lawful bases under the ICO framework
Best for
- Consent
- Marketing, social ads, third-party licensing
- Contract
- Staff shoots, client deliverables, agreed campaign work
- Legitimate interests
- Behind-the-scenes, security, stock
Watch out for
- Consent
- Withdrawal, and proof of what was agreed
- Contract
- Scope creep beyond the original contract
- Legitimate interests
- A documented balancing test
You can hold more than one basis for different uses of the same shoot. Record which basis applies to which image and which channel. That record is your defence if the ICO or a model asks questions.
Before the shoot, agree the basis in writing. It also helps to sort out the commercial terms at the same time, because usage rights and data rights often travel together in product photography commercial contracts.
What a model release form must contain to be worth the paper it is signed on
A model release form is a contract and a record of consent. It is not a magic wand. If it is vague, it fails.
Model release form essentials
- Name model, studio and brand
- Describe shoot, date and location
- State lawful basis and intended uses
- Set territory, duration and exclusivity
- Explain consent withdrawal process
- Cover compensation, credit and restrictions
- Guardian signs for under-18 models
The form should name the model, the photographer or studio, and the brand or client. It should describe the shoot, the date, the location and the intended uses. It should state the lawful basis, the territory, the duration and whether the licence is exclusive or non-exclusive.
It should explain how the model withdraws consent and what happens to images already published.
It should also cover compensation, credit, and any restrictions the model wants, such as no use in political advertising or adult content. If the model is under 18, a parent or guardian signs. If the model lacks capacity, a representative signs and you record the basis for that.
A Manchester furniture brand books a shoot for a new sofa range. The model signs a release granting worldwide, non-exclusive use for web, print and paid social for three years. The basis is consent.
The form records that the model can withdraw consent by email, and that the brand will stop new uses within 30 days. That is specific enough to rely on.
By contrast, a release that says "I agree to my image being used" is too broad. It does not identify the brand, the channels or the duration, so it is hard to enforce and hard to defend.
Keep the signed form for as long as you use the images, plus a reasonable limitation period. Store it securely, and link it to the shoot folder so you can find it during a dispute or a subject access request.
Special category data, children and vulnerable models on set
Some images reveal more than a face. A model in a religious garment, a visible health condition, a trade union badge or a shot that implies sexual orientation may create special category data. Special category data needs a higher condition, usually explicit consent, and extra safeguards.
Children are a separate risk. A child cannot give valid consent in most commercial contexts. You need a parent or guardian to sign, and you should record how you verified that relationship. Shoots involving children should avoid unnecessary images and should not publish identifying details such as a school or full name.
Vulnerable adults need similar care. Capacity can fluctuate, so record who consented, when, and on what basis. If in doubt, take advice before the shoot, not after.
On set, brief the crew. Only the people who need to be there should see the model's personal data. Do not leave release forms on a communal table. Do not share raw files through personal messaging apps. Use a secure transfer method and delete working copies when the edit is done.
If the shoot involves health, care or financial products, the images may imply sensitive characteristics even without a label. Treat them as higher risk and document your assessment.
Retention, subject access requests and breach reporting for shoot files
Retention is where most studios get sloppy. Raw files, selects, retouched masters and release forms all have different lifetimes. Decide how long you need each, write it down, and delete on schedule.
Subject access request clock
- Day 0Request received
- Within 1 monthMust respond
- Up to 2 monthsExtension for complex requests
A model or staff member can make a subject access request for their images and related data. The ICO's subject access request guidance explains the rules: you must respond within one month, you can extend by two months for complex requests, and you can refuse manifestly unfounded or excessive requests.
You must verify the requester's identity, and you should not charge a fee in most cases.
Breach reporting matters too. If personal data is lost, stolen or exposed, and the breach risks people's rights and freedoms, you must report it to the ICO within 72 hours of becoming aware. Keep an internal log of all breaches, even minor ones.
A photography business that processes personal data usually needs to pay the ICO data protection fee, unless an exemption applies. The data protection fee is modest, but failing to pay can lead to a fine. Check the current tiers and exemptions before your next shoot.
For a fuller picture of how these duties sit alongside other UK rules, see UK rules that apply to product photography before you publish.
Working with studios as controllers or processors under UK GDPR
When a brand books a studio, roles matter. The brand usually decides why the images are made and how they are used, so the brand is the controller. The studio processes the images on the brand's instructions, so the studio is often a processor.
But a studio that also uses the images for its own portfolio or marketing may be a controller for that use.
Put the roles in writing. A data processing agreement should set out the subject matter, duration, nature and purpose of processing, the types of personal data, and the obligations of each party. It should cover confidentiality, security, sub-processors, breach notification and deletion at the end of the contract.
If you are a brand manager, ask the studio for its data processing agreement before the shoot. If you are a studio producer, have a template ready. Ambiguity here is expensive when a model complains or a breach occurs.
International transfers need attention too. If files are edited in another country, or stored on servers outside the UK, you need a transfer mechanism such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.
Small studios sometimes act as controllers for their own marketing and processors for client work. Keep the two roles separate in your records, and make sure your privacy notice explains both. The ICO's UK GDPR guidance and resources set out the rights people can exercise, including access, erasure and objection.
If you are new to this, start with the basics of product photography data protection before you book the first shoot.
Model release checklist for UK product photography shoots
Use this checklist before, during and after every shoot that includes people.
- Confirm the lawful basis for each intended useconsent, contract or legitimate interests.
- Draft a release form that names the model, the studio, the brand, the shoot date and the location.
- State the permitted uses, channels, territory and duration in plain English.
- Explain how consent can be withdrawn and what happens to existing images.
- Include a parent or guardian signature for anyone under 18.
- Record any special category data and the condition relied on.
- Store signed forms securely and link them to the shoot folder.
- Set retention periods for raws, selects, masters and forms.
- Brief the crew on data handling and secure file transfer.
- Check whether you need to pay the ICO data protection fee.
- Have a data processing agreement ready if you are a studio working for a brand.
Run the checklist as a numbered sequence on the day.
Shoot data protection sequence
- Beforeconfirm basis, send release
- On setcollect form, check guardian ID
- Aftertransfer securely, delete working copies
- Log shoot and set deletion date
- Treat image requests as subject access



