How to share a video with only specific people.
One link per person, and what that link does not check.

Each review link belongs to one email address and one film. The person who opens it lands in a review room with every film you have shared with that address. Any note they leave is signed with the name you gave them, or their email if you left the name blank. When you remove a film from one person, their link for that film stops working and nobody else notices.

What the link does not do is check who is holding it. It carries no password, and nothing sends a code to an inbox to confirm the address. That is why the review page itself describes the link as the client’s key. If your client forwards it to a colleague, the colleague gets in as your client. For most client work that is the behaviour you want. For a film that must not travel, read the last section first.

A person’s room lists only the films you have shared with their address. From there they can watch, leave timecoded notes, draw on the frame and approve a version. The room does not list the other people you shared a film with, though anyone who leaves a note on it is named on that note.

They do see the notes. Notes are stored against the film, not against the link, so everyone reviewing the same film reads the whole thread, each note signed by its author. For a director, a producer and an agency working on one cut, that is usually the point. If two people must not see each other’s comments, for example two competing buyers, upload a separate copy of the film for each and share one copy with each person. Each copy counts against your storage, and the free Starter plan holds one film at a time.

If everyone on the list gets the same access and you would end it for all of them at once, such as a cast and crew screening, a single password on the film is simpler. You set it per film, up to 60 characters, on every plan. The server checks it and allows 20 attempts per hour from one network address. A correct entry is remembered in that browser for 30 days. Changing the code locks out everyone who used the old one on their next page load, which is the only way to end access with a password, and it ends it for the whole group. A password-protected film does not play in an embed. For a worked example with a password, see how to share a sizzle reel privately.

The watch page also has an email gate: if the film’s code contains an @, the page asks for an email instead of a password. It holds one address. It compares what the viewer types with that address, ignoring capital letters, and does not confirm that the viewer owns it. Treat it as a password that looks like an email, suitable for one recipient. It is not a list and it is not verification.

Some jobs need the platform to confirm identity: an unreleased cut for a named buyer, a legal or HR film, anything where “my colleague opened it” is a problem. For those, use a service that ties access to signed-in accounts. Google Drive’s help, for example, describes a Restricted setting where only people with access can open the file, as opposed to Anyone with the link, which works without signing in. The trade is that every viewer needs an account and has to sign in. uncompressed.io does not offer that for browser links, and we would rather say so than blur it.

For footage that must not leak at all, the browser is the wrong place for it. Vault includes encrypted local playback, supported capture restrictions, visible session identification and invisible per-person forensic marks in the macOS app. These are distinct controls; forensic detection depends on the recovered copy. These controls reduce risk; they cannot guarantee that footage never leaks or that every leak can be traced. See the Vault.