Video Security and Access Control

Protect private video by combining controls that answer different questions: who may watch, where playback may occur, how long a link remains useful, and how stream output is protected. Configure each layer deliberately and verify both approved and denied playback.

Choose controls for the risk

• Allowed origins restrict the websites permitted to request protected playback.
• Signed, expiring links let your server issue time-limited playback after authorization.
• AES-128 encryption or DRM protects project delivery output; choose one supported mode per project.
• Login protection requires a signed-in subscriber, while plan scope grants that subscriber access to selected content.
• Dynamic watermarking and Screen Shield add deterrence and traceability for sensitive viewing workflows.

Recommended private-video flow

1. Authenticate the viewer in your application.
2. Authorize that viewer for the requested video or library.
3. Issue a short-lived signed playback URL from a trusted server.
4. Use a non-empty allowed-origin list and keep the all-origins key exemption off when domain enforcement is required.
5. Select AES-128 or DRM for the project and test on required devices.
6. Add watermarking or Screen Shield when the content risk justifies it.

Follow the detailed guides

• How to Secure Your Videos on DynTube — understand every available layer and its configuration boundary.
• How to Turn On Video Encryption — configure project-level HLS AES output and key delivery.
• How to Add Login Protection to Videos — pair authentication with plan access.
• How to Create Plans & Subscriptions — define content scope, checkout, and manual grants.

Verify before publishing

Test a signed-out viewer, an entitled viewer, an unentitled viewer, an approved domain, an unapproved domain, and an expired link. Test on the browsers and devices your audience uses. A saved switch is configuration evidence; the allowed and denied playback results prove the integrated workflow.