In July 2026, users who had "purchased" movies on Sony's PlayStation Store logged into their accounts to find the files gone. There was no notice, and no refund arrived automatically. When Techdirt reported the story, it picked up 559 upvotes and 341 comments on Hacker News. Many commenters said they weren't surprised — after all, "it was all in the terms of service."
What makes that resignation uncomfortable is that the checkout screen, from start to finish, showed only the word "Buy." The cart said "Buy." The email receipt said "Buy." The account library displayed the films under "My Content." Legally, it had always been a license agreement — but the platform's interface was designed to look like ownership. It's true that users didn't read closely. It's also true that the platform arranged things so they wouldn't.
This might sound like a distant media-consumption problem to a Korean solo founder or small business owner. But the Notion doc, Figma file, Google Workspace account, Slack workspace, and the business data running on top of them that you open every day sit on the same structure. The same mechanism that made Sony's movies vanish can, at any moment, be applied to your work assets and business infrastructure.
It Said "Buy." The Contract Said "License."
Digital content platforms almost never actually transfer ownership of a file to the user. Apple's iTunes, Amazon Prime Video, and Google Play Movies all use the word "Buy" on the checkout screen. Yet each service's terms of use specify, without exception, a "license grant." That license can be revoked if the platform shuts down, if its contract with a content supplier lapses, or if the user's region changes. What the user pays for isn't the file — it's access to it for as long as that agreement remains in force.
In Sony's case, the direct cause was the expiration of a licensing agreement with an independent film distributor. Once Sony no longer held distribution rights to that content, the viewing rights of everyone who had "bought" the movie disappeared along with it. Sony acted within what its terms allowed; users simply didn't know where those terms were, or what they said.
Similar incidents have happened before. When Microsoft shut down its e-book store in 2019, it deleted every e-book users had purchased. Some refunds were issued, but the books themselves became unreadable anywhere, ever again. In 2023, Warner Bros. Discovery pulled dozens of its own original productions from Max; several had never been released on physical media and are now unavailable in any format. Distributed exclusively as digital content, they vanished permanently the moment the platform made a business decision.
These incidents keep resurfacing not because of the dollar amounts involved. It's because the way platforms use the word "buy" to bring users in, then define the actual terms in a different vocabulary — "license" — matches the lived experience of a very wide population of users. The 559 upvotes and 341 comments are a measure of just how widely that experience is shared.
There Are Legitimate Counterarguments
Every time digital licensing structures come under fire, the same counterarguments resurface. Skipping past them risks overstating or oversimplifying the problem.
First, the physical-media era never granted full ownership of content either. DVDs had region codes. VHS tapes degraded with every copy made. Record labels have printed "home taping is prohibited" copyright notices on albums for decades. By this view, the content industry rarely gave consumers "full ownership" even before the digital era.
Second, regulation is moving toward greater consumer protection. Since 2023, the European Union's Digital Content Directive has required sellers to clearly disclose when a digital content sale is in fact a "license." The U.S. Federal Trade Commission is likewise weighing rules that would require disclosure of the difference between "buy" and "license." There's no guarantee that today's opaque practices will persist indefinitely.
Third, treating every cloud service as equivalent to Sony's case overstates the risk. Work files stored on Google Drive and Sony's movie files disappear for structurally different reasons. Video content is tied directly to copyright licensing agreements, while business data isn't subject to a third party's distribution contract. Extending Sony's story into blanket distrust of SaaS in general may be a logical leap too far.
None of these counterarguments is entirely wrong. But even if they're right, one fact remains unchanged: the interface is deliberately designed to feel like ownership, while the actual terms sit inside terms of service written to be hard to find and hard to read. I find it difficult to accept an account of that gap that blames only user carelessness. Interface design shapes behavior, and there are limits to how much of that outcome can fairly be pinned on the user.
The Same Structure Is at Work in Your Own Stack
Read Sony's incident from the perspective of a Korean solo entrepreneur, and the most concrete question becomes: do I actually control the business data stored inside the tools I use every day?
In 2023, Autodesk unilaterally restructured its subscription plans, leaving existing users with only two choices: move to a pricier tier or walk away from the service entirely. For users who had spent years building files around that software's specific format, the cost of leaving the platform far exceeded the cost of staying. Autodesk stayed within the bounds of its terms — but users hadn't read those terms nearly carefully enough when they first signed up.
When Twitter (now X) raised its external developer API pricing by dozens of times over in 2023, startups that had built and run services on top of it had to overhaul or abandon their business models overnight. When HubSpot restricted features on its free tier, users had to scramble to decide where to migrate months' worth of accumulated CRM data. In 2024, Adobe added a clause to its subscription terms permitting use of user content for AI training, then removed it after a massive backlash. Adobe rewrote the clause, but the episode remains a vivid illustration of what can happen when nobody reads the terms.
These cases share a pattern. Platforms attract users with low upfront costs, then change the terms once enough data and workflow have accumulated on top of them. Once the cost of leaving — migrating data, restructuring workflows, retraining teams, notifying customers — exceeds the cost of staying, most users accept the new terms. Platforms understand this dynamic, and they use it.
One technology book examining what the rapid spread of smart devices and digital platforms brings to individuals and organizations argues that using new tools effectively without becoming dependent on them requires "a deliberate habit of distinguishing what you control from what you hand over to the platform." That's not a lesson confined to media consumption. It's a question worth asking across your entire business infrastructure.
What You'll See If You Check Right Now
The response to this problem is less complicated than it sounds. Start by opening each major SaaS tool you use and locating its data-export feature. Notion, Figma, Airtable, and most of Google Workspace all offer full data export. If you can't remember the last time you ran that export, it means you currently have no cushion for a price hike or a service shutdown. Simply putting a recurring export on your calendar changes the picture.
It's also worth checking how each service's terms describe "data handling upon account termination." Many services delete data after a grace period of 30 to 90 days post-cancellation. If you don't run an export during that window, it's gone. Knowing in advance where that clause lives buys you at least a minimal window to respond to a sudden change.
It's also a practical exercise to map out how concentrated your core business operations are on a single platform. If customer contacts, contracts, work history, and communication records exist only inside one piece of SaaS, it's worth sketching out — just once — what gap it would leave in your operations if that service became inaccessible for 24 hours. Understanding roughly how much time and money it would take to switch platforms belongs in the same exercise. If you have no answer to these questions, you have no preparation.
What Sony's users wanted wasn't the movie file itself. It was the trust that, having paid, they could keep watching. That trust was revoked by a single line in the terms of service. Before you hand that same trust over to a platform for your business infrastructure, checking exactly what its terms do and don't guarantee is the cheapest form of preparation available to you right now.
