Store each video session recording in a private bucket you control, then issue an expiring link only after checking the viewer's access to that session. The deciding constraint is the data boundary: a collaborative editor's live cursor presence, its video room, and its retained recording have different lifetimes, even when they belong to the same document.
Short answer: A Node.js Express download handler should authorize the viewer before requesting a presigned URL. Keep cursor presence in the live collaboration layer, keep recording retention in your bucket, and delete recordings on schedule. An expiring link limits access through that link; it does not perform deletion or establish a storage region.
What page fired? A green room dashboard is poor evidence that a departed collaborator has lost recording access, and a successful upload says nothing about whether the recording will survive beyond its deletion deadline.…