You Don't Own the Software You Paid For
A storefront purchase is a revocable licence, not an asset. The only ownership that survives a vendor's change of heart is the file you actually hold.
You paid the money. The item sits in your library with a tick beside it. And the company that sold it to you can still switch it off. That is how digital retail is built to work.
When you "buy" a game, an app, an album or an ebook through a storefront, what changes hands is rarely the file. It's a licence, a revocable permission to reach a copy that lives behind the seller's account system and, usually, the seller's client software. Your payment is final but your access is conditional, and that gap between the two is the whole story.
Most of the time they feel identical. You click, it downloads, it runs. The distance between a licence and a possession only opens at the edges: when a title is delisted, when a platform pivots, when a publisher pulls a back catalogue, when an account is suspended over something unrelated, or when a verification server simply can't confirm who you are today. At those edges the tick in your library stops meaning anything, and what you lost was never a copy, only the permission to see one.
Take July 2009. Amazon reached into people's Kindles and remotely deleted copies of George Orwell's Nineteen Eighty-Four that they had bought and paid for, refunding them without warning; Bezos later called the move "stupid, thoughtless and painfully out of line". Fifteen years on, the same pattern had hardened from accident into policy. Ubisoft delisted its 2014 racing game The Crew in December 2023 and shut its servers on 31 March 2024, leaving everyone who had bought it with an install that no longer runs. The backlash spawned the Stop Killing Games campaign, but no petition changed the mechanism: the licence was always revocable, and one day the vendor revoked it.
Do you actually own the digital things you buy?
Usually not, in the sense most people mean by "own". Durable ownership is the ability to keep using a thing regardless of what its seller decides next, and a storefront purchase inverts that. Your continued access depends on the vendor's account layer staying up, staying friendly and staying interested in the product. Read the terms of most large stores and the language is candid about it: you are granted a licence to use, not title to a good. The client is the gatekeeper, the account is the key, and the file is an afterthought you are not really meant to touch.
One corner of the market is a genuine exception, and it proves the rule by breaking it. GOG, the DRM-free store built by Polish developer CD Projekt, sells the artefact rather than the permission: you download an installer, copy it to your own storage, back it up, and reinstall it years later without phoning a server for approval. No client sits in the way, no live check gates the launch. In November 2024 GOG formalised the idea as its Preservation Program, committing to keep flagged titles installable even after publishers walk away and to strip out any dependency that would need a live server to launch. That commitment is real, and it is also a policy, which is the catch. A preservation pledge lives at the discretion of whoever runs the company and sets its priorities next year; it is a promise about the future, made by an owner who can change, be replaced, or reprioritise. Even the store that best proves ownership can survive is, at bottom, honouring a commitment it could one day revise. A strategy is set by whoever owns the company this year.
That model usually gets talked about as a niceness, goodwill for people who dislike being tracked, and the framing badly undersells it. Holding a DRM-free installer is a continuity control. It separates the licence-to-use from the stored copy, so that a change in the seller's fortunes can't reach through the account and strand you. Lock-in is enforced by the client and the account, not by the bytes. Break that dependency and the storefront's failure modes stop being yours.
What does this mean for a business, not a gamer?
Lift it off the games shelf, because that is where it stops being a hobbyist grievance and becomes a balance-sheet fiction. Every organisation runs on digital things it believes it bought: SaaS seats, font libraries, stock media, design plugins, e-learning modules, code dependencies pinned to a vendor's registry, whole workflows welded to one platform's client. On the operational ledger these read as assets. In law and in practice most of them are the same conditional licence a gamer holds, scaled up and priced higher.
The revocation risk is identical, and it is not a thought experiment. Google gave a firm date: it retired Cloud IoT Core on 16 August 2023, roughly a year after warning customers the managed service was going, leaving every connected-device deployment wired to that one API to rebuild or walk. The service was live, paid for, and then it wasn't. The same thing surfaces whenever a vendor is acquired and the new owner rationalises the product line, when a company splits and your tool lands on the side that gets wound down, or when a supplier changes direction and sunsets the thing your process was built around. Continuity matters most exactly when the vendor's world is in flux, which is exactly when a purely account-bound dependency is least trustworthy. Building a sober technical strategy for vendor and continuity risk means naming that dependency before the acquisition rumour, not after the shutdown email.
The honest complication is that you can't always hold the artefact. SaaS is a service by construction; there's no installer to keep, because the value is the running system on someone else's infrastructure. That's fine, as long as nobody pretends otherwise. The discipline isn't "demand a file for everything", it is two rules. Where the format allows a stored copy, separate the licence from the artefact and actually keep the artefact, tested and reinstallable. Where it doesn't, treat the dependency as a rented capability, price the switching cost, and keep an exit that doesn't lean on the incumbent's goodwill. The DRM-free game is the clean case that teaches the messy ones, and anyone building on shared digital platforms is making the same bet with the same edges.
There is a second-order effect worth naming. A market that quietly reclassifies purchases as licences trains buyers to stop asking about continuity at all, because for years nothing goes wrong. The risk doesn't vanish in that quiet stretch; it accumulates, unpriced, until one strategic decision at one vendor cashes it in across every customer at once.
So treat the receipt as evidence of a payment, not proof of an asset. Own the artefact wherever the format lets you, price the risk wherever it doesn't, and assume every layer you were told was permanent is really a dependency held at someone else's discretion until you arrange otherwise.
Questions people ask
What is the difference between a licence and owning a digital file?
A licence is a revocable permission to access a copy that the seller can withdraw by delisting the product, suspending the account, or shutting down a verification server. Owning the file means you hold a copy you can reinstall yourself, so the seller's later decisions can't strand you.
Why does DRM-free distribution matter for businesses and not just gamers?
DRM-free means the artefact works without live vendor authorisation, which makes it a continuity control: you can back it up and reinstall it even if the vendor is acquired, splits, or discontinues the product. The same revocation risk sits under corporate software libraries and platform dependencies, usually unpriced.
Can you protect against losing SaaS access the same way?
Not directly, because SaaS is a running service with no artefact to keep. The equivalent discipline is to treat it as a rented capability: price the switching cost, keep exportable data, and maintain an exit path that doesn't depend on the incumbent staying cooperative.
Related
- Epic v Google: The App Catalogue Remedy That Hands Rivals the Moat
- Memory Prices Turned. Renegotiate the Supply Contract Before the Next Refresh.
- How AI Makes Bad Bosses Worse: The Agreeability Machine in the Corner Office
- Digital Business
Written by an AI editorial persona of Abyshire's proprietary editorial system and reviewed by our team.