Consent · For Creators

The release form
in the drawer.

A signed paper release protects you, but only for what it says, and only until someone tests it. Here is how that plays out four years later.

Christian Bertolini Christian Bertolini 8 min read

The release is valid. The model signed it. But a paper release is a static document sitting in a drawer, while your content lives online for years. That gap is where creators get hurt.

01 — The objection"My release form is fine"

More platforms now ask creators to prove consent for every person who appears in their content. Many offer two paths: a digital, identity-verified consent signed by the other person, or an upload of a scanned paper release for cases where that person can no longer be reached.

We hear the same objection from photographers again and again:

I'm still in touch with the model. Why should I go through a digital process? My signed release gives me the rights to use the images however I want.

— a photographer, more or less every week

It's a fair question. The answer isn't that paper releases are worthless. It's that they were built for a moment in time, and your content isn't. To see why that matters, here is how it plays out.

02 — The scenarioFour years later

The people are fictional. The pattern is not.
  1. 2022

    The shoot

    Mark, a portrait and boudoir photographer, books a session with Elena. Before they start, she signs his standard release. It grants broad rights to use "photographs taken during the session" for commercial and online publication. Between setups, Mark films a few short behind-the-scenes clips on his phone. Nobody thinks twice.

  2. 2023

    The upload

    Mark publishes the set on a creator platform and uploads the scanned release. The platform confirms a release is on file. A few months later he adds a 40-second clip from the same shoot. He doesn't reread the release. Neither does the platform: checking that a release exists is routine, checking every file against every scanned form is a different job entirely.

  3. 2026

    The request

    Elena's life has moved on. New job, new relationship, and she no longer wants to be in the content. She asks the platform to remove it. Under data protection law, including the GDPR right to erasure, the platform has to assess her request, and in practice content of an identifiable person who objects is usually taken down. Mark is annoyed, but accepts it.

  4. +6 months

    The letter

    Elena has spoken to a lawyer, who read the release more carefully than anyone else had. It covers photographs. Nothing about video. The clip was online for over a year without a valid basis. Mark now faces a claim for unauthorised use of her likeness, plus damages and a share of what the content earned.

Mark didn't act in bad faith. He simply never reread a document he signed years ago. But for a lawyer looking for a clean claim, a signed release with a clear scope breach is close to ideal: the paper trail makes the argument for them.

03 — The costWhat it costs Mark

The legal bill is only the start. The real cost is the time, the stress and the uncertainty of defending a decision he made in good faith years earlier.

Money
His own lawyer, and possibly damages or a settlement
Time
Digging out files, dates, upload logs and messages from years ago
Stress
Months of uncertainty, with court as a real possibility
Reputation
A small industry where word travels, and a platform asked to explain its checks

All of that, because a scanned form felt good enough.

04 — The blind spotsWhere a paper release stops

A paper release is a contract about a single moment. It does its job, but it has blind spots that only show up later.

Not tied to specific content

It refers to "the session" or "the images", not the exact files you publish. Nobody can prove which upload it was meant to cover.

Scope is easy to exceed

Photos vs. video, specific uses, platforms, time limits. Over years and hundreds of uploads, a mismatch is a matter of when, not if.

The model never saw the result

She agreed to a shoot, not to the edit, the crop or the clip that went live. That weakens your position if she later says she didn't agree to this.

Signature not linked to identity

A scanned signature proves very little on its own. It can be disputed, and the signer can claim it wasn't them or that they were pressured.

It doesn't stop a removal request

Data protection rights sit alongside your contract. That's true of any consent method. What matters is how exposed you are when that day comes.

None of this makes your release invalid. It means that when a lawyer goes looking for a gap, a paper form gives them plenty of places to look. For the legal background, see Release Forms and the Right to Be Forgotten.

05 — The fixHow ProntoTag closes the gap

ProntoTag turns consent from a document in a drawer into a verified record attached to the content itself.

// The ProntoTag flow
01

Link the content

You create a ProntoTag request pointing to the exact content to be published.

02

The model reviews it

She sees precisely what goes live, the photos, the clip, the edit, before agreeing to anything.

03

She signs as herself

Consent is signed through ProntoID, so the signature belongs to a verified person, not a scribble on a scan.

04

Consent is bound to that file

The record shows who agreed, to what, and when. New content needs its own consent.

Run the scenario again. When Mark uploads the clip, it needs its own consent. Elena reviews the 40 seconds and either approves it or doesn't. If she approves, there is a verified record that she saw that exact clip and said yes.

If she later asks for removal, the content comes down. But Mark holds clear evidence that every file was published with her informed, specific consent. There's no scope breach to find, and no easy case to build.

ProntoTag can't stop someone changing their mind. It makes sure that when they do, you're covered for everything that came before.

06 — The answer"But I'm still in touch with the model"

That's exactly why you should use ProntoTag. If you can reach the model, verified, content-specific consent takes her a few minutes. The paper route exists for one situation: when the other person genuinely can't be reached anymore. It's a fallback, not a shortcut.

And if a platform asks you to confirm you're no longer in contact so you can upload a scan, don't confirm it unless it's true. A false declaration is one more thing that can be used against you.

 
Scanned release
ProntoTag
Linked to specific content
No
Yes
Model reviews the final content
No
Yes
Signature tied to verified identity
No
Yes, via ProntoID
Scope mismatch risk (photos vs. video)
High
Each file consented separately
Position if consent is later withdrawn
Contestable
Clear, timestamped evidence

07 — Looking aheadConsent for 2026, not 1996

The model release was designed for print magazines and stock libraries. Content today is uploaded, re-cut, reposted and monetised for years, across platforms, in formats nobody imagined when the form was signed.

Consent needs to keep up: specific, reviewed, verified and tied to the content it covers. That protects the model, it protects the platform, and above all it protects you. A few minutes now costs far less than a lawyer later.

FAQQuestions creators ask

Generally yes. A properly signed release is a valid contract between the parties. The problem is not validity but scope and evidence: it is not tied to specific files, the model never reviewed the final content, and a scanned signature is not linked to a verified identity. Those gaps are what a dispute years later will focus on.
No, and nothing can. Data protection rights such as the right to erasure sit alongside any contract or consent record. What ProntoTag changes is your position: you hold clear evidence that every file was published with the model's informed, specific consent, which leaves no scope breach to build a claim on.
Because that is exactly the situation where verified, content-specific consent costs almost nothing to collect. The paper route exists for when the other person genuinely can't be reached anymore. It is a fallback, not a shortcut.
Only confirm it if it is true. A false declaration to a platform is one more fact that can be used against you if the content is ever disputed.
No. It applies to any creator who publishes content featuring another person: videographers, streamers, podcasters, musicians and adult content creators. Any time a second party appears in the content, their consent needs to be specific and provable.

Use ProntoTag for every collaborator you can reach.

Content-linked, identity-verified consent in minutes. Free to start, and far cheaper than defending a scanned form years from now.

This article is general information and uses a fictional scenario to illustrate common risks. It is not legal advice. Creators, models and platforms with specific questions, particularly in cross-border situations or where a dispute is already underway, should consult qualified legal counsel in the relevant jurisdiction. ProntoID provides verified identity and consent infrastructure; it does not provide legal services.

Christian Bertolini
Christian Bertolini
Founder & Managing Director, Brooks & Keitt — Founder, ProntoID

Christian Bertolini is the founder of ProntoID and Managing Director of Brooks & Keitt, the Swiss firm behind it. He has worked in IT services since 2000, moving from high-availability infrastructure into personal security, identity management, and AI-driven retail. He writes here on the design choices behind ProntoID products and the operational realities of compliance in creator and media platforms.

More articles LinkedIn