Who Sees Your Raw Footage? NDAs, Access, and Sending Sensitive Video to an Outside Editor

Who Sees Your Raw Footage? NDAs, Access, and Sending Sensitive Video to an Outside Editor

An NDA Is a Remedy. Access Is the Control.

Wyzowl's video marketing survey found 42% of companies rely on external creators in some way, and Wistia's State of Video puts the narrower figure at around a quarter outsourcing to freelancers or agencies — both catalogued in our video editing statistics ledger. The Bureau of Labor Statistics counts 35.5% of U.S. film and video editors as self-employed. Put those together and a large share of all footage handoffs end at a laptop belonging to a business of one, with no IT department and no offboarding process.

Buyers ask about price and turnaround. Almost nobody asks where the footage will physically sit, who else can open it, or what happens to it after delivery. When the question does surface, the reflex is to send an NDA — and an NDA is the weakest control in the stack. It is a remedy you invoke after your footage has already gone somewhere it should not have. The things that actually prevent that are unglamorous, free, and set up in the first ten minutes of an engagement.

Across 10,000+ delivered editing projects sitting behind 200M+ views and more than $10M in client revenue, we have taken in unreleased product demos, pre-publication course modules, clinical practice footage, and material filmed with minors in frame. Not one of those was protected by the NDA. They were protected by who held the link.

What follows is standard industry practice, not legal advice. If your footage carries a regulatory obligation, have your own counsel set the terms.

Four Kinds of Footage That Actually Carry Risk

Most footage needs none of this. A vlog you are publishing on Thursday has a confidentiality window of about four days. Four categories genuinely do:

Footage typeThe exposureWhat changes
Pre-launch or embargoedProduct, pricing or launch date leaks before you control the storyNamed seats, no open links, a deletion date
Client-confidentialSomeone else's privacy obligation is riding on your handoffWritten list of who touches it; a signed agreement is mandatory, not optional
Personal or identifiableFaces, minors, homes, clinical settings, documents legible on screenRestricted distribution; blur pass specified in the brief
Licensed third-party materialYou may not have the right to redistribute it, even to a contractorRead the licence before the upload, not after

Row two is the one people underestimate. A law firm sending client footage, a clinic sending patient testimonials, a SaaS team sending a walkthrough of an unshipped feature — in each case the obligation belongs to you, and handing the file to a contractor does not divide it. The FTC's data security guidance tells businesses to make sure their service providers implement reasonable security measures. The responsibility does not travel with the file.

Your Footage Makes More Stops Than You Think

Footage rarely sits in one place during an edit. Between your drive and the archive it passes through a transfer service, the editor's working machine, and a review platform — each one a separate copy, and a separate account that can be compromised.
Footage rarely sits in one place during an edit. Between your drive and the archive it passes through a transfer service, the editor's working machine, and a review platform — each one a separate copy, and a separate account that can be compromised.

"I sent it to my editor" describes one action and at least five locations.

The transfer service holds a copy until the link expires, which for most free tiers means until somebody remembers. The editor's machine holds the working copy plus proxies, cache files and autosave scratch, all of which survive deleting the original. A subcontractor may hold a third copy if part of the job was passed on. The review platform holds a streaming copy with its own sharing settings. The archive holds the last one.

The number that matters is not how many people you trust. It is how many copies exist and how many of them have an expiry date. In most engagements the honest answers are "five or six" and "none." Every one of those copies is a place a leak can start without anybody acting in bad faith.

What an NDA Does, and What It Cannot Do

An NDA is a remedy invoked after a disclosure has already happened; access control prevents the disclosure in the first place. The two are not substitutes, and only one of them is working at three in the morning.
An NDA is a remedy invoked after a disclosure has already happened; access control prevents the disclosure in the first place. The two are not substitutes, and only one of them is working at three in the morning.

An NDA is worth signing. It fixes a definition of confidential material, establishes that both sides knew the material was sensitive, and gives you standing if something goes wrong. It costs nothing. Send it.

Then be clear about its limits:

  • It does not stop a disclosure. It prices one.
  • It does not bind people who never signed it. If your editor passes the caption pass to someone else, your agreement reaches the shop, not the person who downloaded the file. Ask in writing whether subcontractors are used and whether they are bound by the same terms.
  • It does not survive a lost laptop, a reused password, or a link forwarded into a group chat. Most footage exposure is not malice. It is a public URL nobody turned off.
  • It is rarely worth enforcing. Pursuing a breach against a one-person business in another jurisdiction costs more than almost any edit is worth.

So send it, and then build as though you had not. The NIST Cybersecurity Framework orders the same logic: identify and protect come before respond and recover.

Nine Questions That Reveal How a Shop Handles Footage

Ask these during vetting, before the paid trial, in one message.

  1. Where will my footage be stored during the edit, and in whose account?
  2. Who on your side will have access to it — by name and by role?
  3. Do you use subcontractors, and are they bound by the same confidentiality terms?
  4. Do your editors work on company-managed machines or their own?
  5. How are review links shared — named viewers with an expiry, or anyone with the URL?
  6. How long do you keep source media after delivery, and can I set that date?
  7. What do you send me as confirmation of deletion?
  8. What happens to my files if an editor leaves mid-project?
  9. Has footage ever leaked, and what changed afterwards?

A shop that has handled sensitive work answers all nine in one reply without going to check. A shop that has not will answer the first two and go quiet on the rest — the same tell our post on how to vet a video editing service treats as more informative than the demo reel. Question three matters most in marketplace engagements, because the platform's identity check covers the account holder, not whoever the account holder passes the work to. That gap is one of the structural trade-offs in our freelance marketplaces comparison. Question eight is the one that overlaps with continuity: an editor who goes quiet mid-project leaves your footage sitting on a machine you cannot reach.

The Controls That Cost Nothing

Shared logins make revocation all-or-nothing and attribution impossible; named seats let you remove one person without disturbing anyone else, which is what offboarding actually requires.
Shared logins make revocation all-or-nothing and attribution impossible; named seats let you remove one person without disturbing anyone else, which is what offboarding actually requires.

None of these needs a security budget. All of them take minutes.

One folder per project, shared to named accounts. Not a link anyone holding the URL can open. Google Drive's sharing settings draw exactly this distinction, and "anyone with the link" is a public URL that behaves like a private one right up until it doesn't.

Named seats, never a shared login. Shared credentials make revocation all-or-nothing and attribution impossible — you cannot remove one person, and you cannot tell who opened what.

Set the expiry when you create the link, not when you remember it exists. An expiry you have to go back and apply is a task; one set at creation is a property of the file.

Keep review copies watermarked and lower-resolution. A platform like Frame.io can burn a viewer-specific watermark into the stream, which makes a forwarded screen recording traceable and makes forwarding it unappealing in the first place.

Upload approval cuts as private, not unlisted. YouTube's privacy settings separate the two: an unlisted video is reachable by anyone holding the URL, while private restricts it to accounts you name. For an unreleased edit, private.

Name a deletion date in the agreement. This is the mirror image of the handover question. Our post on who owns your project files is about making sure you get everything back; this is about making sure nobody keeps a second copy. Both belong in the same conversation, before work starts.

Revoke on the last day, not the last invoice. Offboarding drifts because nothing visibly breaks when it is late — the same discipline, and the same failure mode, as YouTube channel access and permission roles.

The Bottom Line

Send the NDA, then work as though you had not. Confidentiality survives on access design: one folder per project shared to named accounts, links that expire on creation, watermarked review copies, a deletion date written into the agreement, and revocation on someone's last day rather than their last payment. Ask the nine questions before the trial — a shop that answers all nine without checking has done this before, and that is worth more than any clause you can sign.

👉 Get instant quote

Frequently asked questions

Should I make my video editor sign an NDA?
Yes, but treat it as a baseline rather than protection. An NDA fixes a definition of confidential material and gives you standing if something goes wrong, which is worth having and costs nothing. It does not prevent a disclosure, does not bind a subcontractor who never signed it, and is rarely economical to enforce against a small overseas business. Pair it with access controls that actually stop the leak.
Is it safe to send raw footage to a freelance video editor?
For most footage, yes. The risk concentrates in four categories: pre-launch or embargoed material, footage covered by someone else's privacy obligation, identifiable people including minors, and third-party licensed clips you may not have the right to redistribute. For those, share to named accounts rather than open links, set an expiry, and agree a deletion date in writing before you upload anything.
How long does a video editor keep my footage after delivery?
Usually 30 to 90 days before archiving or deleting, but there is no standard and many freelancers keep material indefinitely by default. Ask for the retention period as a number, ask whether you can set it yourself, and ask what confirmation you receive when deletion happens. If nobody has ever been asked this, the honest answer is that the files are still there.
What is the difference between unlisted and private on YouTube?
An unlisted video can be opened by anyone holding the URL, while a private video is restricted to specific Google accounts you name. Unlisted is not a security setting — a forwarded link works for anyone who receives it. For an unreleased cut going out for client approval, use private and add the reviewers by email address.
Do video editing agencies use subcontractors?
Many do, and it is not inherently a problem. It becomes one when nobody tells you, because your confidentiality agreement reaches the shop you hired rather than the person who actually downloaded your files. Ask directly whether subcontractors are used and whether they are bound by identical terms. A shop that answers plainly and names its arrangement is lower risk than one that avoids the question.
How do I share large video files securely with an editor?
Create one folder per project in cloud storage you own, share it to named accounts rather than a link anyone can open, and set the link expiry at creation instead of retrofitting it later. Avoid shared logins, since they make revocation all-or-nothing and leave no record of who opened what. Keep the master copy in your account so removing access never removes your own files.
Who is responsible if my editor leaks a client's footage?
Practically, you are. When footage carries an obligation you owe to a client, patient or employer, handing it to a contractor does not divide that obligation — the FTC's data security guidance directs businesses to ensure their service providers implement reasonable security measures. Contractual recourse against the editor is a separate matter from the duty you still owe upstream, so vet before you send.