Access is Not Ownership
How modern software quietly redefined ownership to access
One day a piece of software you rely on will refuse to open.
Your files will still exist. Your computer will still work. The application may still be installed locally.
Still, you won’t be allowed to use it.
I started thinking about this a few years ago when Chrome removed my ad blocker.
Not because ad blockers are the centre of the universe. They aren’t.
What bothered me was simpler. Software running on my machine had decided I was no longer allowed to run something I had installed. The browser still worked. My computer still worked. The extension was still conceptually just code. But in the end, none of that mattered.
The authority lived somewhere else.
A surprising amount of modern software works like this now.
Photos, notes, documents, movies, music, games. Much of it sits behind an account you created years ago and barely think about until it causes a problem.
The account becomes the door. Lose the door and the room may as well not exist.
People say they “own” things in these systems. Usually they mean they can reach them right now.
Ownership means you can keep using the thing without asking the original provider for permission. You can copy it. Back it up. Move it. Preserve it. Use it when the network is down. Use it when the company changes its mind, or disappears.
Most digital ownership fails that test.
Buy a movie from a digital storefront. You can watch it only while the storefront exists, the licence remains valid, your account is in good standing, the app supports your device, and the region rules still allow it.
That is not the same as owning a movie.
Or maybe you subscribe to a service. It works while the subscription is active, while the authentication server responds, while the company still sells that plan, while your operating system remains supported.
This is easy to understand in the physical world. If I buy a drill from Canadian Tire, it does not care whether Canadian Tire’s website is down. If the internet goes out during a winter storm, the wrench in my garage still works. If the manufacturer changes its product line, my hammer doesn’t suddenly stop working. Nobody thinks this is strange.
These examples sound absurd because digital tools get treated differently. The dependency is less visible.
The button still says “Open.” The app icon still sits on your home screen. The file still appears in a list. Nothing about the interface tells you that authority lives somewhere else.
But eventually something breaks.
Maybe your session expires. Maybe your subscription lapses. Maybe your account gets flagged. Maybe your payment card fails. Or the service shuts down. Or a feature moves to a higher tier. Or maybe the app just refuses to open offline.
Suddenly it becomes obvious who actually controls the system.
You realize that it was never fully yours. You were merely allowed to use it.
Cloud storage made a very simple promise: your files would always be there when you needed them.
Then services like Amazon Drive started disappearing. Amazon deprecated the service, removed upload support, and ended access to files. The files did not become less yours in any moral sense. But the service stopped being a reliable way to reach them.1
The same pattern exists in gaming.
People bought games on Google Stadia. A few years later Google shut the service down. To its credit, Google handled refunds far better than many companies would have. But the shape of the problem remains. When the service ended, the platform ended with it. You could not keep running Stadia in your basement. You could not preserve the system locally. The games existed only as long as Google operated the service.2
To be clear, this is not an argument that every company is acting in bad faith. That would be lazy.
A lot of these systems were built for understandable reasons. Sync is useful. Subscriptions can fund maintenance. Cloud storage protects people from losing a laptop and everything with it. Most users do not want to manage backups, licences, local files, and device migrations by hand. And honestly, these are difficult engineering problems.
I don’t want to pretend the old world was perfect or argue we should go backwards.
It was messy. People lost files constantly. Hard drives died randomly. Backups sounded great in theory but were often neglected. Old software was hostile in its own ways.
The cloud won out because it solved very real pain. It made a lot of things easier. But that convenience comes with a trade-off: we traded possession for access.
And we should be more honest about that trade.
Plenty of people have experienced this without thinking much about it. You open a notes app in an airport with bad Wi-Fi and discover your own notes are somehow unavailable. They haven’t been deleted. They aren’t lost. They’re temporarily withheld by a system that needs to ask somewhere else before showing them to you.
Your notes app should not need permission to show your text. A photo editor shouldn’t become useless because an authentication server in Virginia is down. A single-player game shouldn’t disappear because a licence check failed. A scanner app should not need an account before using the camera already attached to your phone.
We should stop accepting this as normal.
At some point the account stopped being a convenience and became part of whether the software worked at all.
You log in to sync your data across devices, recover purchases, or share files with other people. Fair enough. Those are all useful things.
But over time the account became something larger. It became the thing deciding whether the tool opened in the first place.
Accounts solve real problems. They help prevent theft. They let people recover access. Shared systems would be much harder to manage without them.
But the same mechanism that protects access can also be used to revoke it.
The same login that lets you sync across devices can prevent you from opening local data. The same subscription that funds the product can turn the tool off. The same account that makes onboarding easy can become the reason a small business cannot reach its invoices, documents, or customer records.
Subscription software changed the relationship between user and tool.
You are no longer buying a stable thing. You are paying for continued permission to use a changing thing.
Sometimes that is fine. A service with servers, support staff, ongoing security work, and constant updates needs money to keep operating. I’m not bothered by that.
What bothers me is when the subscription stops being payment for ongoing service and becomes the thing that decides whether a local tool continues to exist.
The problem is when everything becomes a service, including things that never needed to be.
The response to this is usually the same: users prefer convenience.
And that’s true. Many people do. Most people don’t want to become sysadmins.
People adapt to the systems available to them. That does not always mean the systems are healthy.
The industry taught users to treat access as ownership because access is easier to sell repeatedly. Actual ownership is less convenient for the vendor.
A local file doesn’t need to check pricing. A downloaded program does not care whether the company pivoted. Plain text files still open even after the startup that made the app is gone.
That is why local files still feel different.
They are boring in the best way. You can see them. Copy them. Put them on a USB drive. Back them up to another disk. Open them with different tools. Keep them for twenty years.
That doesn’t mean plain files are perfect. Disks fail. People lose their laptops. Backups don’t always get taken.
But the failure mode is legible. You know what you have and what you do not.
Cloud-locked systems make the failure mode abstract. The data may exist. The provider may have it. The app may show a record of it. But you still may not be able to use it.
Your data should exist in a form you can access even without the original service. Your tools should keep working for their core purpose without contacting a remote authority. Your account should improve the experience, not define whether the experience even exists.
Ownership means the thing remains meaningfully yours when the relationship with the provider ends.
If cancelling a subscription destroys the tool, you never really owned it. You rented it.
If losing an account locks you out of your own data, you never controlled it.
Somewhere along the way we stopped expecting our tools to belong to us.
That was a mistake.
https://www.pcmag.com/news/amazon-drive-shuts-down-dec-31-2023
https://support.google.com/stadia/answer/12790109