Image rights under control: expiry dates, model releases and the day after

An image is licensed, paid for, used, archived. Two years later somebody looks for material for a brochure, finds it, and nobody in the room knows the licence was limited to twelve months of online use in Germany. This is where the expensive cases come from — not at purchase, but at retrieval.

The reason is structural. At purchase, knowledge about the licence is at its maximum, and it sits in an email. At retrieval, knowledge is zero, and the email is in the mailbox of somebody who has left the company.

Managing image rights: four fields that make the difference

You do not need rights management with thirty attributes. You need four pieces of information on the asset itself, not in a document sitting next to it.

• Rights holder. Who created the work and who has to be credited. On publication, attribution under German copyright law is not negotiable, and it has to be at hand at the moment of use.
• Usage type. Online, print, social media, internal, advertising. As a picklist, multi-select. A free text field here is the reliable route to data you cannot evaluate.
• Territorial and time scope. "Germany, until 31 December 2027" is something a system can work with. "See contract" is not.
• Where the contract lives. The licence agreement or model release as a file on the asset, not as a link into a drive that will be migrated.

In VAULO all four can be stored directly on the asset — creator information through the IPTC data, usage type and period through the usage notes, and the contract itself as an attachment.

Expiry dates on usage rights: why they are the most important field

An expiry date is the only rights field that can trigger an action without somebody asking for it. Everything else only gets checked once somebody is already looking.

In practice: an overview that shows sixty days ahead which usage rights are ending, plus a notification to the responsible person. Three outcomes are possible, and all three have to exist in the system — extend, replace, or block.

These three outcomes are exactly what the LegalHub add-on in VAULO covers, for example: it warns automatically before a usage period expires, and a restriction can then block the file for download without deleting it — it stays findable, but can no longer be used.

The third one matters most. An expired asset is not deleted, it is taken out of usability. It stays findable for evidence purposes and can no longer be downloaded.

Model releases and the right to one's own image: not a special case

Photographs of people bring two layers together: the photographer's copyright, and the depicted person's right to their own image. The second layer gets forgotten regularly, because at the shoot it feels self-evident.

Three things therefore belong on the asset: the signed consent as a file, the scope of that consent as a field, and a note on revocability. Consent under Article 7(3) GDPR can be withdrawn at any time — and when that happens, it has to be clear within days which published materials show that person. Without a link on the asset, that is a search through the entire archive.

For photographs of children and in educational settings, consent is usually granted for a limited period. Treat it like a licence: with an expiry date and advance warning.

Clearing image rights in a legacy archive: the archive that is already there

For legacy archives without rights data there is no automatic solution, but there is a defensible order of work:

1. Sort by risk, not by age. Photographs of people and purchased third party material first, your own product shots last.
2. Set a default status. Anything unchecked gets "rights unclear" and is blocked for download outside the core team. That is inconvenient and effective for exactly that reason — clarification then happens when somebody actually needs the image.
3. Clarify on demand, not in advance. An image nobody has searched for in five years does not need a rights review.
4. Make new uploads mandatory immediately. From day one, rights status is a required field. Otherwise the unclear archive grows faster than it is worked through.

Image rights compliance and saved work in practice

The legal part is the obvious one. The quieter benefit: when the image itself says it is cleared for print in the DACH region until 2028, nobody has to ask. The two day round trip to the legal department disappears for every case where the answer would have been yes anyway.

That is the point where rights management stops being an obligation: it is the precondition for letting people outside the core team use the archive themselves.

FAQ

Do I have to delete images with an expired licence?

No. An expired usage right is a reason to block an image for further use, not to delete it. For evidence purposes — in a dispute or a rights audit — the asset should stay findable; only the download and further use are stopped.

How long should I keep licence agreements and model releases?

It is advisable to keep contracts at least as long as the image is actively in circulation, plus a safety buffer for possible claims afterwards. Since retention periods differ by legal basis, it is worth aligning this with your legal department — what matters most is that the contract is stored directly on the asset, not only in the purchasing person's mailbox.

What belongs in a model release for photographs of people?

A model release should cover at least the scope of the consent (which use, where, for how long), the possibility of withdrawal under Article 7(3) GDPR, and — for photographs of minors — an expiry date with advance warning. What matters is that this information is linked directly to the image, not just held as a paper document.

How do I clear image rights in an existing archive without rights data?

Best sorted by risk: photographs of people and purchased material first, your own product shots last. Images without a verified status get marked "rights unclear" and are blocked for download until they are actually needed and then clarified — a full review in advance is rarely necessary.