How to Revoke Access to a Shared Video Link

A normal film URL, a recipient review link and a collection share can authorize access through different paths. Start with the actual URL from the message. Changing ordinary film visibility must not be treated as proof that every recipient grant has disappeared.

The deployed uncompressed.io review code checks whether a share covers a video directly or through a collection. A valid share can authorize review separately from ordinary visibility. This is why a single Private switch is not a complete audit of every shared route.

Remove the unwanted share through the supported sharing controls. Check direct film shares and collections that still contain the film. If the same recipient has another valid grant, deleting only one grant may not remove every route they can use.

Review ordinary film visibility and password settings separately. Do not create an email-looking password and assume it becomes a verified recipient allowlist. A label, address or named link is not by itself proof of the person using it.

Film: [title and internal reference]
URL sent: [exact link, stored privately]
Grant withdrawn: [recipient or collection share]
Other grants checked: [direct links and collections]
Ordinary visibility reviewed: [current setting]
Fresh recipient-session test: [result and time]
Known prior downloads: [yes, no, or unknown]
Follow-up owner: [name]

Use a fresh non-owner session to test the exact old link. Also test any other known access route. Avoid using deletion of the film itself as a substitute for understanding which grant provided access.

A saved file or recording already outside the service is not recalled by changing a link. Already issued playback access or buffered content also makes an immediate stop on every open device a different question from denying a fresh request. No instant universal cutoff is promised here.

If the material is particularly sensitive, define the acceptable viewing route before sharing it and verify the controls on that route. Do not infer browser protections from features described for a native Mac app.

Record the action privately with the project’s delivery notes. A public report should not contain reusable private access links. Ask the recipient to confirm deletion of any prior local copies when that is part of your agreed process, without treating that request as a technical guarantee.

Continue with: Client portals for editors · Secure screener sharing · Access and security.