You collect a great video testimonial. Six months later, your client's lawyer sends an email asking whether you had proper consent to use their face in a paid ad. You dig through your inbox, find the reply that says yeah, love the video, go for it — and discover that's not a consent form. It's a Slack-tone agreement with no record of what specifically was agreed to, when, or under what terms. You now have a video you can't legally use, and you've been running ads with it for four months.

This scenario plays out more often than people admit, and it's entirely preventable. The fix is a proper consent form with a proper evidence trail. But generic photo-release templates don't cover video specifics — moving image rights, audio rights, editing rights, withdrawal under GDPR. Copy a template from the first result on Google and you'll likely miss two or three things that matter.

This piece breaks down the six things a video consent form actually needs to cover, gives you three templates you can copy and adapt (inline checkbox, standard form, full release), and closes with how to store the proof so consent holds up if it's ever challenged.

Not legal advice. The templates below are starting points, not finished legal documents. Run whichever you use past a lawyer in your jurisdiction — it's a one-hour bill that saves you from a much bigger one later.

What a video testimonial consent form actually needs to cover

Strip away the legalese and every video consent form is answering six questions.

Identity of the parties

Who is giving the consent (full name of the person in the video), and who is receiving it (your company's legal name, not just your product name). Seems obvious but a surprising number of consent forms collect only first names or aliases, which makes them difficult to enforce if challenged.

Scope of what's being recorded

A video isn't just the video. It's also the audio, the still frames you might extract, the person's likeness and voice, and often their name, job title, and company. The consent form should name each of these explicitly so you can use them without going back for a second conversation.

Rights being granted

This is the meat of the form. You want the right to use, reproduce, edit, publish, distribute, and publicly display the content. You want that across specific channels (website, social, email, paid advertising, sales materials, investor decks) and for specific purposes (marketing, sales, fundraising). If you might use the video in a paid ad, say so. If you might use it in a pitch deck, say so. Consent that doesn't cover a use case doesn't extend to that use case.

Duration and geography of use

Perpetual or time-limited? Worldwide or specific countries? Be honest. Most marketing use is perpetual and worldwide — say that, don't hide it. Trying to sneak a perpetual license into a form written for a one-off campaign is the kind of thing that surfaces in a dispute.

Withdrawal rights

Under GDPR, consent is freely revocable at any time, and the process must be as easy as giving it was. Your form should name a withdrawal method (usually an email address), state what happens when someone withdraws (you remove the content from your owned channels within a reasonable timeframe — 30 days is standard), and acknowledge that content already cached or reshared by third parties may take longer to fully disappear.

Evidence trail

The consent form is half the job. The other half is proving, three years from now, that this specific person consented to this specific text on this specific date. A signed PDF on your drive works. A database row with name, exact consent text, and timestamp works. A vague note that says customer agreed in your CRM does not work.

Template 1 — inline consent checkbox (for widgets and form submissions)

Use this when someone is submitting a video through a form or recording widget. It needs to fit next to a submit button and still cover the essentials.

I confirm that I am the person appearing in this video and I give
[Company Name] permission to use the video (including my likeness,
voice, and any text or rating I submit) on their website, social
media, email communications, and paid advertising. I can withdraw
this consent at any time by emailing [consent email], after which
[Company Name] will remove the content from its owned channels
within 30 days.

Under GDPR this meets the "freely given, specific, informed, unambiguous" standard because it names the parties, the uses, and the withdrawal method. The checkbox should be unchecked by default and the form submission should be blocked until it's ticked — pre-ticked boxes do not count as consent under GDPR.

If the video might also run in pitch decks or long-form paid ads, either upgrade to Template 3 or add and investor and sales materials to the list of channels.

Template 2 — standard consent form (for email or direct collection)

Use this when you're collecting a video outside of a structured form — for example, asking a customer to send a video by email or via a shared link. Send it as a signed attachment or have them paste their name and date into a reply.

VIDEO TESTIMONIAL CONSENT

I, [Full Name], confirm that I am the person appearing in the video
testimonial I am providing to [Company Name].

I grant [Company Name] the right to:
- Use the full video, excerpts, still images, and audio from the
  recording
- Edit the recording (adding captions, music, or overlays) without
  changing the meaning of what I said
- Publish the recording on [Company Name]'s website, social media
  accounts, email communications, paid advertising, sales materials,
  and investor communications
- Use my first name, last initial, and any professional information
  (job title, company) I have provided

This consent applies worldwide and continues until I withdraw it.
I can withdraw consent at any time by writing to [consent email].
On withdrawal, [Company Name] will remove the content from owned
channels within 30 days. Content already distributed to third
parties or cached may take longer to remove fully.

Signed: _____________________
Printed name: _____________________
Date: _____________________

The main difference from Template 1 is the written signature line. For email collection, asking the person to type their full name and the date into a reply is usually enough; for higher-stakes use, send a PDF and have them sign digitally.

Template 3 — full video release form (for ads, long-form content, and investor materials)

Use this when the video will run in paid media, appear in a pitch deck, or show up in fundraising materials. The bar is higher because the stakes and the exposure are higher.

VIDEO RELEASE AND LIKENESS CONSENT

Between: [Full Name] ("Releasor"), of [address]
And: [Company Name] ("Company"), of [address]

1. GRANT OF RIGHTS
Releasor grants Company a worldwide, royalty-free, perpetual
license to use, reproduce, distribute, publicly display, publicly
perform, edit, and create derivative works from the video
recording(s) dated [date] ("Recording"), including:
- The full video
- Still frames, excerpts, and audio extracts
- Releasor's likeness, voice, name, and any professional
  information shown (job title, company)

2. PURPOSES
Company may use the Recording for:
- Marketing and advertising (including paid digital and offline
  advertising)
- Sales and business development materials
- Investor communications, pitch decks, and fundraising materials
- Internal communications and training
- Website, social media, and email channels

3. EDITING
Company may edit the Recording (trim, add captions, music,
overlays, intercut with other footage) provided that edits do not
misrepresent the substance of what Releasor said.

4. COMPENSATION
[Choose one:]
- No monetary compensation is being paid for this release.
- Compensation of [amount] has been paid to Releasor in
  consideration for this release.

5. WITHDRAWAL
Releasor may withdraw this consent at any time by written notice
to [consent email]. Upon withdrawal, Company will cease new use of
the Recording and remove it from owned channels within 30 days.
Releasor acknowledges that content already distributed to third
parties or cached may take longer to remove.

6. WARRANTY
Releasor warrants that they are the person appearing in the
Recording, that they have the right to grant this release, and
that the Recording does not infringe any third-party rights.

7. GOVERNING LAW
This release is governed by the laws of [jurisdiction].

Signed by Releasor: _____________________
Date: _____________________
Signed on behalf of Company: _____________________
Date: _____________________

Use this for anything running as a paid ad or appearing in high-stakes materials. It's a higher bar but it's also a higher-stakes use case — and a full release is what your legal team will want to see if the content ever becomes contentious.

What changes for GDPR, CCPA, and general best practice

The shape of a good consent form is roughly the same everywhere, but the specifics shift by jurisdiction.

GDPR (EU/UK customers). Consent must be freely given, specific, informed, and unambiguous. Pre-ticked boxes and buried checkboxes don't count. Withdrawal must be as easy as giving consent. You must keep records — who consented, what they consented to, and when. Video footage showing an identifiable person is personal data; voice may be treated as biometric data depending on interpretation.

CCPA (California customers). Notice at collection is required — you have to tell people what you're collecting, why, and whether you share it with third parties. People have the right to request deletion of their data. The consent bar itself is less strict than GDPR, but the right-to-delete is enforceable and you need a workflow for it.

General best practice (anywhere). Record the exact consent text shown to the person at the moment they consented — not a link to your current terms, because those drift. Keep timestamps. Make withdrawal easy, documented, and actually functional.

If you sell to European customers at all, default to the GDPR standard. It's stricter than most other regimes, so a form that meets GDPR tends to be acceptable elsewhere — but the reverse isn't true.

How to store the evidence trail

A consent form is only useful if you can prove, when challenged, that a specific person saw specific text on a specific date and agreed to it.

Three things to store together for every consent event:

1. The person's identity — name and email at minimum.
2. The exact consent text they saw — not a link to your current policy. The verbatim text, captured at the moment of consent.
3. A timestamp — when they consented.

This is the piece people most often get wrong. They link to /privacy in the consent checkbox, the privacy policy is updated six months later, and suddenly the text the person actually consented to is unrecoverable. Store the wording itself, frozen at the moment of submission.

Acceptable places to store this: a signed PDF archive, a database row per consent, a line item in your CRM per customer. Unacceptable: nothing.

This is where GetPureProof handles a piece most DIY setups miss. When consent is enabled on a Space, each submission stores three fields: whether consent was given, the exact consent text that was shown on screen at the moment of submission (the raw text, not a link), and the timestamp. If a customer challenges consent two years later, you can produce the specific wording they saw.

If you're using GetPureProof, this is already built in

Consent on GetPureProof is a per-Space setting. For each recording Space you run, you can:

• Toggle the consent checkbox on or off (default: off, you opt in when you need it).
• Use the default GDPR-aware consent text, or write your own custom wording — for example, a tighter version for a specific campaign or a full release for pitch-deck use.
• Collect the consent checkbox, the exact text shown, and a timestamp with every submission — automatically, without wiring anything up yourself.

That's the evidence trail described above, captured as a byproduct of how the product works. For compliance-minded teams — especially anyone with European customers — it removes the most common failure mode: forgetting to log the exact text version.

See the features page for the rest of the product, or pricing if you want to start with consent turned on from day one.

Bottom line

A video testimonial with no proper consent is a liability you haven't priced in. You'll feel fine for months, sometimes years, and then one day a lawyer or a regulator will ask the question you don't have an answer to.

Six elements in the form. Three templates to pick from depending on use case. One evidence trail that stores the text, the identity, and the timestamp. Do all of that and consent moves from a risk hanging over your head to a solved operational detail.

And for the avoidance of doubt, one more time: nothing above is legal advice. Have a lawyer in your jurisdiction review whatever you actually deploy. The templates are starting points, not endpoints.