In 2017, the hacker group The Dark Overlord broke into Larson Studios, a small Los Angeles sound post-production studio that worked on series and films for major studios. Larson paid the ransom—$50,000, according to Variety (Fortune). It didn't help: the group still leaked the new season of Orange Is the New Black before its premiere. Netflix itself was never hacked. The weak link was a contractor with someone else's files on its server.
Seven years later, the story repeated itself almost word for word. In August 2024, episodes of the second season of Arcane, Terminator Zero and a dozen other animated series leaked online—with watermarks and timecodes, meaning work-in-progress copies. "One of our post-production partners has been compromised," Netflix admitted. The partner turned out to be Iyuno, a localization company based in Burbank (Cartoon Brew).
To a client, a videographer, studio or agency is exactly that kind of contractor. If an unreleased brand video sits in your cloud, you're the link it can escape through. Usually it doesn't take a hack. It happens far more simply: an "anyone with the link" link outlives the project, travels further than you thought, and nobody remembers how many such links are still open. Cloud storage was never designed for this—it was built for teams collaborating on documents. Below is what's known about the risks of such links, and how platforms like VodSpot approach the problem differently.
Fundamental Design Misalignment
Cloud storage solutions — Google Drive, Dropbox, OneDrive, Box — were created for internal team collaboration on documents, spreadsheets, and shared project files. Their access models assume that:
- The sender and recipient are typically in the same organization
- Shared content should be editable, not just viewable
- Access should be persistent by default
- The recipient has an account on the same platform
Delivering video to external clients violates all four assumptions:
| Assumption | Collaborating on documents | Delivering video to clients |
|---|---|---|
| Sender and recipient are in the same organization | Usually yes | Almost never |
| Content requires editing | Often | Never |
| Access must be permanent | Usually | Temporary |
| Recipient has a platform account | Usually | Often no |
When a tool designed for assumption A is used for task B, the access model doesn't adapt. It continues to behave as if the recipient is a trusted internal collaborator.
The Forwarding Cascade
The biggest risk in delivering video via cloud storage isn't hackers. It's plain forwarding. The link goes to the client, the client sends it to their marketer, the marketer sends it to the ad agency. Each step is logical, and you won't hear about any of them.
How far links travel is best shown by what Google itself did. In 2021, it acknowledged that older Drive file links were too easy to find and added a special resource key to them "to make sharing links more secure" (Google Workspace Updates). The same year, YouTube made private all unlisted videos uploaded before 2017: the older addresses were generated by a simpler scheme and could be found without an invitation (YouTube Blog). If the platforms close their own links, counting on yours to stay private is not a good idea.
The scale of the file problem shows in the Ponemon Institute's report for OPSWAT. 61% of the organizations surveyed had a breach or incident because confidential data in files ended up in the wrong hands, and such incidents cost them $2.7 million on average over two years (OPSWAT).
A password breaks this chain at the first step: a forwarded link without the password opens nothing but a login screen.
How different delivery methods counter the cascade
| Delivery method | What someone with a forwarded link sees | What the sender knows |
|---|---|---|
| VodSpot: password + expiration date | A password screen; after the expiration date, "delivery not available" | Who opened it, when, and what was downloaded |
| VodSpot: email access | A one-time code login; an address that isn't on the list won't get in | Viewers' names and email addresses |
| Cloud: "anyone with the link" | The file itself, ready to download | Almost nothing |
| Cloud: access for specific accounts | A request-access screen | Only who signed in |
| Vimeo / YouTube unlisted | The whole video | A view counter |
VodSpot's password protection, together with an expiration date and separate download control, makes forwarding useless: without the password the link opens nothing, and after the expiration date the delivery closes on its own. Delivery analytics show who watched, when, and what was downloaded—no more guessing where the link went.
Unrevoked Access: The Long Tail Problem
Even if nobody forwards the link, it keeps working until someone switches it off. And people rarely do.
The most striking example is a story researchers at Wiz uncovered in 2023. A Microsoft AI research team published a link to open training data on GitHub. The link was built on a special Azure token and opened far more than intended: 38 terabytes, including backups of two employees' computers and over 30,000 internal Teams messages. The token was valid until 2051 (Wiz). Nobody meant to grant access for 28 years—nobody thought about the expiry date at all.
Smaller companies look much the same. Varonis analyzed a thousand real IT environments and nearly 10 billion files. 88% of organizations had "ghost users"—accounts of people who had long since left, with access still enabled. 66% had cloud data exposed to anonymous users, meaning anyone with a link (Varonis).
For a videographer, it looks like this: over a few years, dozens of links to client projects pile up in the cloud. Some clients are long gone, some of their employees have changed jobs, and the films still open for anyone who kept the old email. Freelancers feel this most, because no IT department ever reviews their shared links.
On a private video hosting platform like VodSpot, each delivery is an independent entity with its own access settings, expiration date, and one-click revocation. The dashboard displays all active deliveries and their status. Setting an expiration date upon delivery means access is automatically revoked—the videographer doesn't need to remember to revoke.
Video-Specific Risks
Video files carry risks that documents don't. The combination of large file size, rich content, and emotional impact makes video exposure more impactful.
File Size and Download Behavior
| File Type | Typical Size (Our Estimate) | Download Time (50 Mbps) | Local Copy Likelihood |
|---|---|---|---|
| Document (PDF, DOCX) | 2.4 MB | Less than 1 second | High (but low impact) |
| Spreadsheet | 1.8 MB | Less than 1 second | High (but low impact) |
| Photo (High Resolution) | 12 MB | 2 seconds | Medium |
| Video (1080p, 5 min.) | 1.2 GB | 3 minutes | Medium |
| Video (4K, 10 min.) | 8.5 GB | 22 minutes | Low (but download = full copy) |
When a video file is downloaded from cloud storage, the recipient has an exact copy that exists independent of any access controls. Revoking a shared link does not affect downloaded copies.
On private video hosting, streaming is the default viewing mode. Viewers watch using adaptive playback without downloading the original file. Download permissions are separate: you can disable them completely or allow downloads of the original master file.
When the Leak Is a Work Copy
A video leak is different from a document leak: people see it. The Netflix work-in-progress episodes from the Iyuno incident spread online with watermarks and timecodes—they were recognized and discussed before the premieres. An unreleased commercial, an internal message from the CEO, a wedding film with guests who never agreed to publication—each has its own price, but all of them become a problem the minute the wrong person sees them.
According to IBM's 2025 report, the average data breach costs $4.44 million worldwide and $10.22 million in the US (IBM). For a small studio the amounts are very different, but so is the revenue: one lost client or a ruined launch hits it harder than a major leak hits a corporation. The professional video market is full of content like this.
The good news is that a leak can be made traceable. In 2004, films in the Oscar race were turning up online before they even reached theaters. Investigators found the source thanks to a digital mark that studios discreetly embedded in each screener tape: it pointed to Carmine Caridi, a veteran actor who had been a member of the Academy of Motion Picture Arts and Sciences for about 22 years. For years he had passed almost every screener he received—around 60 films a year—to an acquaintance (U.S. Department of Justice). The Academy expelled him. When every viewer knows their copy carries their name, the urge to share it fades fast. Hence the visible watermark with the viewer's email on VodSpot's Studio and Production plans.
Compliance Measurement
Regulatory frameworks are becoming increasingly specific regarding access control to shared content, including video.
| Regulation | Relevant Requirement | What VodSpot Adds | Cloud Storage Compliance Gap |
|---|---|---|---|
| GDPR (EU) | Right to be forgotten; data minimization; access logging | Access control by delivery, expiration date, revocation, activity log | Shared links have no audit trails for recipients; "all by link" does not identify viewers |
| SOC 2 Type II | Access control, monitoring, and revocation for shared data | View/download tracking with timestamps | Cloud storage logs do not track video viewing |
| HIPAA (US healthcare) | Minimum necessary access; audit trails | "Streaming only" mode; download control separate from viewing | Cloud storage cannot restrict viewing without downloading |
| ITAR (US defense) | Controlled access to defense-related content | Password protection, expiration dates, and delivery revocations | Cloud storage cannot enforce domain-level viewing restrictions |
For organizations falling under these guidelines, sharing sensitive video via cloud storage creates audit gaps. A private video hosting platform like VodSpot—with access control for deliveries, passwords, expiration dates, download control, and activity logging—narrows these gaps as standard functionality, not a corporate add-on. VodSpot does not hold SOC 2, HIPAA, or ITAR certifications, so check your own compliance requirements.
Security Feature Comparison
| Feature | VodSpot | Google Drive | Dropbox | Vimeo |
|---|---|---|---|---|
| Separate Download Control | Yes (Streaming vs. Original) | No | No | Partial |
| Delivery Analytics | Full (Views, Downloads, Time) | No | View Counter Only | Counter |
| Branding on Access Page | Yes (All Plans) | No | Business Only | Paid Plans |
| Custom Domain | Yes (Pro and Studio) | No | No | Enterprise Only |
| Password Protection for Links | Yes | No (no plan offers it) | Professional and business plans | Yes |
| Link Expiration | Yes | Per person, work and school accounts only | Professional and business plans | Yes |
| One-Click Link Revocation | Yes | Manual Access Removal | Manual Removal | Yes |
| Streaming Without Downloading | Yes | No (Preview up to 1080p) | No | Yes |
| Automatic Access Revocation | Yes | Per person, work and school accounts only | Professional and business plans | Yes |
VodSpot includes every feature in this table as a standard feature—not tied to an Enterprise plan. For a freelancer or studio delivering 5-30 projects per month, this means professional content security at a fraction of the cost of enterprise cloud storage plans.
Practical Risk Reduction
The data points to four specific actions:
1. Stop using "all by link" for client deliveries. This single change stops the forwarding cascade: with a password, a forwarded link opens nothing but a login screen.
2. Set an expiration date for each delivery. Unrevoked access is a long-tail risk. An automatic expiration date—even a generous 90-day window—eliminates the problem of "forgotten links" without having to remember.
3. Separate streaming and downloading. Allow customers to watch via adaptive streaming without providing a downloadable copy of the original file. Enable downloads only when the process requires it, and track downloads.
4. Use a specialized tool for client delivery. Cloud storage is the right tool for internal file management. It is the wrong tool for controlled external delivery. Private video hosting services like VodSpot provide access control for deliveries, passwords, expiration dates, revocation, download control, and analytics as default features.
What the data doesn't tell you
This analysis should be read with caveats:
- Breach cost data from IBM and Ponemon use averages biased by large corporate incidents; the cost per incident for SMBs is lower, but potentially higher relative to revenue.
- Compliance requirements vary by jurisdiction, industry, and data type.
- Cloud storage services are constantly improving their security features; enterprise plans increasingly include expiration dates, password protection, and audit trails.
The fundamental structural problem, however, remains unchanged: cloud storage access models are designed for collaborative document workflows, not for controlled, time-limited, and monitored video delivery to external recipients. Specialized tools serve this use case more effectively because they were designed for it.
Frequently Asked Questions
Is Google Drive safe for sharing videos?
As storage, yes, but its access model wasn't designed for sharing video externally. Drive links can't have a password on any plan, and an expiration date can only be set for a specific person, and only in work and school accounts. Varonis found cloud data exposed to anonymous users at 66% of organizations. For client videos, use account-based access at the very least, or better, a delivery platform with passwords, expiration dates and access revocation.
What is the biggest security risk when sharing videos through cloud storage?
Not hacking, but plain forwarding and links nobody closed. Even Google closed old Drive and YouTube links in 2021 because they were too easy to find. A password stops forwarding at the first step, and an expiration date closes the delivery on its own, without you having to remember.
Can someone download my video from a shared Google Drive link?
Yes. By default anyone who can view a Drive file can also download it, unless the owner turns off downloading for viewers. Once downloaded, the copy lives on outside any access control you set later. Private video hosting separates streaming from downloading, so viewers can watch without ever receiving the file.
How do I revoke access to a video I already shared?
In cloud storage you have to find the file and remove each permission or switch the link off by hand—and copies that were already downloaded stay where they are. In VodSpot you press Revoke delivery: the link stops working immediately, and streams that are already playing stop within about a minute. An expiration date set at publishing does the same automatically.
Is VodSpot SOC 2 or HIPAA compliant?
No. VodSpot does not hold SOC 2, ISO 27001 or HIPAA certifications, so organizations that must use certified vendors should check their requirements first. What it does provide on every plan is delivery-level access control: passwords, expiration dates, revocation, separate download control, and a history of views and downloads.
Does a watermark stop people from leaking a video?
It doesn't make copying impossible, but it makes a leak traceable—and that alone discourages it. On VodSpot's Studio and Production plans, a semi-transparent watermark with the viewer's confirmed email moves across the frame every seven seconds and stays visible in fullscreen. Downloaded originals are never watermarked, so keep downloads off when that matters.