What you should know
The feature is designed to reduce casual forwarding after the intended person has watched the link. It is useful only when the sender understands that the first device, not a human identity, becomes authorized.
When it is useful
Before uploading, define what the other person actually needs to do: watch the video, download it, verify information or keep it for longer.
- The uploader's own device should not consume the external authorization.
- The intended recipient should open the link on the device they plan to use.
- Later devices may be blocked even when they belong to the same person.
Recommended process
A short, verifiable workflow reduces failures and avoids unnecessary re-uploads.
- Explain the restriction before sending the link.
- Ask the recipient not to preview it on a temporary or shared device.
- Test only from the uploader side before delivery.
- Provide a new upload if the wrong device becomes authorized.
Practical checks
Compatibility depends on more than the filename extension. The codec, connection, browser and device also matter.
- Private browsing, network changes or browser storage can affect device recognition.
- The feature does not verify a legal identity.
- It does not prevent screen recording on the authorized device.
Limits, privacy and responsibility
Device authorization is a practical friction layer, not strong identity authentication. It can also create support problems if used without clear instructions.
Frequently asked questions
What happens if the recipient opens it on the wrong phone?
That device may become the authorized one, so a new link may be needed.
Does it stop the authorized person from recording?
No. It limits device access, not what the authorized viewer can capture.