01
Protected source files
Keep original files behind the managed service rather than exposing a direct storage URL to viewers.
Security and control
Make video easy to watch—not easy to misuse.
Protect accounts, keep source files behind the service, and control where embedded video is allowed to play.
Playback policy
Current video
members-only-course.mp4
Source accessProtected
Allowed domains2 domains
Public discoveryDisabled
Account 2FAEnabled
2FA
Account protection
Domain
Embed restrictions
Private
Visibility controls
Policy
Content boundaries
Layered controls
Protection around the account, source, and player.
Security works best as several small, understandable controls instead of one fragile gate.
02
Domain-restricted embeds
Choose which websites may embed a video and block playback in places you did not authorize.
03
Visibility choices
Separate public publishing from content intended for a controlled or private audience.
04
Modern authentication
Protect account access with verified email, social login, magic links, sessions, and two-factor authentication.
05
API credential hygiene
Keep authenticated application workflows separate from public playback and browser-facing code.
06
Policy enforcement
Use clear content rules, reporting channels, review, removal, and repeat-infringer action around user uploads.
Shared responsibility
The platform protects delivery. You control who should receive it.
VdoHide provides infrastructure controls, while each customer remains responsible for user authorization, age checks, lawful content, and secure application logic.
Use strong account security
Keep API credentials server-side
Configure domains deliberately
Retain originals and backups
Ready when you are
Build a video experience with boundaries.
Start with secure defaults, apply the controls your audience needs, and review the policy before publishing user content.