Separate “not advertised” from “restricted”
A link may be handed to only one group and still be accessible to anyone who later obtains it. The absence of a public gallery or search listing does not, by itself, limit who can use the address.
An authenticated delivery method asks the service to check a recipient's identity or permission before opening the file. A link-access method relies on someone having the address. Both can serve legitimate event requirements, but they make different promises.
This matters when a client asks for “private videos”. They might mean a separate link for each group, no public event gallery, or access only for named people. Ask which outcome they need. Those meanings cannot safely be treated as interchangeable.
Choose the access model from the requirement
Use this decision table before selecting a sharing feature:
| Client requirement | Method to investigate | What must be checked |
|---|---|---|
| Easy collection without guest login | A link-access handover | Anyone receiving the link may be able to open it. |
| Only identified recipients may open files | A service enforcing recipient permissions | An unauthorised account is refused, while the intended one works. |
| Access should stop at an agreed time | A supported expiry or access-removal process | The setting exists on the actual account and is applied to the actual link. |
| Guests should keep their own copies | Download-enabled delivery | A recipient can save and play the file, not merely preview it. |
The table is a selection method, not a claim that every provider or subscription includes every control. A requirement the selected service cannot enforce needs a different delivery arrangement.
Google Drive separates link availability, recipient roles and download controls; work or school accounts may impose external-sharing restrictions. Dropbox documents additional shared-link controls on eligible plans, including passwords and expiration. Check those features in the account you will use rather than assuming that a provider's whole feature set is available. Google Drive sharing and Dropbox link permissions provide the current provider guidance.
Test as someone who does not own the file
Opening a video on the booth phone proves little about guest access when that phone is signed into the owner's account. Use the exact link you intend to hand over, on a separate phone or signed-out browser. Where practical, use a different connection too, so you are not accidentally testing a local-only route.
For a link intended to work without login, confirm that the recipient can open, play and save the file without your account. For restricted access, test both sides: the intended recipient succeeds and someone outside that permission does not. One successful owner preview is not either of those tests.
As an illustrative scenario, a corporate organiser requests access only for staff. A public clip link opens successfully on an unrelated phone. That is evidence of convenient link access, but it fails the organiser's stated requirement. Making the QR smaller, displaying it briefly or calling it “private” does not change the permission model.
The QR delivery guide covers the separate question of upload readiness and guest handover. Access control should be decided before relying on that handover.
Explain the promise in ordinary language
Use wording that describes the actual experience. For a link-access workflow, an operator could say: “This link lets anyone who has it open the clip, so share it only with people you want to receive it.” For a restricted workflow, describe the sign-in or recipient step guests will encounter.
Do not promise that removing a link will recall copies people already saved or otherwise captured. Access to the original hosted file and possession of a separate downloaded copy are different things. Plan retention and communications with that limit in mind.
Keep the account owner and access-review responsibility clear. Someone should know where the event files live, which delivery period was agreed and how a later request will be handled. This article explains technical access choices; it does not certify legal compliance or prescribe a retention period for every event.
How SnapCircle's guest links work
SnapCircle 360 uploads each processed clip to the event's selected Dropbox or Google Drive account and displays a guest QR after its public link is ready. Its Google Drive path requests anyone-with-link reader access without file discovery; its Dropbox path requests a public shared link.
The practical benefit is that guests can use their own internet connection without joining the operator's local network or creating a SnapCircle account. The trade-off is that the link is not a named-recipient authentication system. A per-clip QR is not the same as a private authenticated gallery.
Choose this workflow when that public-link model matches the client brief. If the requirement is restricted access, do not attempt to satisfy it by renaming the QR or changing the sign next to it. Use an appropriate alternative delivery process and verify its permissions separately.
The software selection guide helps compare that requirement with other capabilities. If public guest links fit your events, download SnapCircle 360 and test the recipient experience with your chosen cloud account. It requires iOS 18.5 or later and a subscription. The important result is a delivery promise that matches what the link actually permits.
Published 4 November 2026. Guidance is based on documented capabilities and an operator checklist. Test your own equipment before a booking.