Guides

Image consent guide: purpose, people, capture, editing, publication, reuse, withdrawal, retention, and records

Image consent guide covering purpose, participants, capture, edits, publication, reuse, withdrawal, retention, and records for responsible projects.

What to take away

  • Consent is a continuing decision about a defined use, not a blanket reward for appearing on camera.
  • Separate the decision to participate from the decisions to record, edit, publish, promote, license, and reuse.
  • Name the people and organizations that will control the images, the intended audiences, and the channels.
  • Build a workable refusal and withdrawal route before capture begins.
  • Keep the exact notice, choice, response, image set, approvals, changes, and final disposition together.
  • Check the law and contract that apply to the project. Consent is only one part of image rights.

Image consent works best as a lifecycle. A person receives useful information, makes a real choice, and can understand what happens next. The creator then keeps capture, editing, publication, reuse, access, and retention within the stated boundaries. If the purpose changes, the decision returns to the person instead of stretching old words to cover a new campaign.

This guide is a planning framework, not legal advice. Copyright, privacy, publicity, data protection, contract, confidentiality, safeguarding, employment, and location rules vary by jurisdiction and circumstance. A signed release can help document permission, but it does not erase every other duty or claim.

A person stands in a field while another person points a camera toward them and a third holds a circular reflector.
Photo: Brocken Inaglory, October 23, 2009, CC BY-SA 3.0, via Wikimedia Commons. The photograph shows three people, a camera, and a reflector outdoors. It does not establish anyone's identity, agreement, legal capacity, ownership, employment, purpose, payment, or publication terms. This credited media will be removed at the author's request.

Start with purpose, not paperwork

Write one sentence that states why the image is needed. "Marketing" is too broad. "Portraits for the spring volunteer-recruitment page and two organic social posts published by North Street Garden" is testable. It identifies a campaign, organization, channels, and limited use.

Then split the project into choices. A participant may agree to a still portrait but not audio, a website profile but not paid advertising, or current publication but not licensing to a sponsor. Granular choices expose assumptions before the camera is raised.

Ask whether a person can decline without losing a service, job benefit, grade, payment already earned, access, or social standing. Power differences matter. A choice offered by an employer, teacher, clinician, landlord, or event organizer may require safeguards beyond a casual yes.

Identify every role

Record the person depicted, photographer, videographer, commissioning party, editor, publisher, platform, archive owner, and any partner expected to receive files. Do not use "we" if several independent organizations may decide how to use the image.

Confirm who has authority to agree. An adult generally speaks for themself. A guardian's authority, a representative's mandate, and a worker's contractual role require separate verification. For a child, treat guardian permission, the child's own willingness, safeguarding, and platform rules as separate questions.

Explain capture and editing

State what will be recorded: stills, video, audio, screen capture, location, identifiers, clothing, artwork, home interiors, or other people. Describe the setting and likely duration. Provide a way to step out before recording begins.

Explain edits that could affect meaning. Routine crop, exposure, color, captions, subtitles, background removal, composites, beauty retouching, voice processing, and synthetic changes are not interchangeable. If a face may be placed in a different scene or used to train or operate a generative system, ask separately in specific terms.

Define publication and reuse

List channels, audience, territory, start date, end point, paid promotion, syndication, partner access, downloads, and archival display. Distinguish a creator's own portfolio from a client's ad, a platform repost, a press distribution, and merchandise.

Under the UK GDPR, valid consent has a demanding meaning. The Information Commissioner's Office says it must be freely given, specific, informed, and unambiguous, indicated through a statement or clear affirmative action. The same ICO explanation of valid consent also covers records, clear requests, easy withdrawal, granular purposes, and the need to refresh consent when activities move beyond the original scope. That guidance concerns consent as a UK data-protection lawful basis. It should not be treated as a universal rule for every image dispute.

Reuse needs its own gate. Before moving an old portrait into a new ad, audience, sponsor campaign, dataset, or synthetic production, compare the new use with the recorded scope. Similar subject matter does not make the purpose identical.

Make withdrawal operational

Give one contact and explain what a participant can ask for. Record the request, verify identity proportionately, pause unreleased uses, locate live and scheduled placements, and respond without pressure. Do not promise total deletion if printed material, lawful archives, third-party copies, litigation holds, or another legal basis may limit what can be done.

Withdrawal is not a time machine. It may stop future processing that relies on consent without making prior activity unlawful. Other permissions or laws may have different termination rules. State those boundaries accurately before agreement.

Set retention and access controls

Keep only what the project needs. Define retention separately for raw captures, selects, published masters, release records, correspondence, and backups. A release may need to outlast a public image so the organization can show the scope that applied. That does not justify keeping every rejected frame forever.

Limit access by role. A retoucher may need selected files but not identity documents. A publisher may need the approved master but not private contact details. Track exports and prevent an asset-library label such as "approved" from hiding channel, term, or territory limits.

Build a defensible record

For each person, preserve:

  • the notice and consent wording they saw;
  • the date, method, language, and person who obtained the response;
  • each separate choice and any refused option;
  • the file or shoot identifiers covered;
  • the release, license, contract, and privacy notice versions;
  • approvals for sensitive edits or changed uses;
  • withdrawal, restriction, complaint, and response history;
  • publication locations, takedowns, retention dates, and final disposition.

Review records before publication, not only after a complaint. A complete record cannot repair coercion or an unlawful term, but it can stop guesswork and make a correction faster.

Common questions

Does posing for a camera mean someone consented to publication?

No. Posing may show awareness of capture in context, but it does not by itself define the publisher, audience, channels, edits, duration, or commercial reuse.

Is a signed model release always enough?

No. Its effect depends on wording, law, capacity, authority, fairness, and the actual use. Other rights and duties may still apply.

Can consent cover every future use?

Very broad language may be hard to understand, unfair, invalid under a governing regime, or commercially unacceptable. Specific choices and renewed permission give a cleaner record.

Must every withdrawal produce complete internet deletion?

No. The organization should act on the rights and promises that apply, stop covered future use, and explain any lawful or practical limits accurately. Copies outside its control may require separate reports.

In this guide

  1. How to plan and document consent for a photo or video projectPlan and document image consent with a practical workflow for project scope, participant choices, releases, shoot-day checks, approvals, withdrawal, and records.
  2. Consent, permission, notice, release, license, contract, and legitimate legal basis comparedConsent, permission, notice, releases, licenses, contracts, and legal bases compared so creators can identify what each instrument does and leaves unresolved.
  3. People, purpose, boundaries, channels, edits, reuse, withdrawal, retention, and contact checklistImage consent checklist for people, authority, purpose, capture boundaries, channels, edits, reuse, withdrawal, retention, contacts, and review records.
  4. Vague permission, bundled terms, changed context, silent withdrawal, missing records, and indefinite reuseImage consent problems explained, from vague permission and bundled terms to changed context, missed withdrawal, weak records, and unjustified indefinite reuse.

More in Guides

Guides

How to plan and document consent for a photo or video project

Plan and document image consent with a practical workflow for project scope, participant choices, releases, shoot-day checks, approvals, withdrawal, and records.

Rules

Vague permission, bundled terms, changed context, silent withdrawal, missing records, and indefinite reuse

Image consent problems explained, from vague permission and bundled terms to changed context, missed withdrawal, weak records, and unjustified indefinite reuse.

Reviews

Consent, permission, notice, release, license, contract, and legitimate legal basis compared

Consent, permission, notice, releases, licenses, contracts, and legal bases compared so creators can identify what each instrument does and leaves unresolved.

Maintenance

People, purpose, boundaries, channels, edits, reuse, withdrawal, retention, and contact checklist

Image consent checklist for people, authority, purpose, capture boundaries, channels, edits, reuse, withdrawal, retention, contacts, and review records.