Computer Science › Section H · Software engineering › Topic H.9
Software ownership, liability, and the law
Software takes years and millions of dollars to build, yet it can be copied in a second. The law answers two questions about it: who owns it and what others may do with it, and who is responsible when it causes harm. This topic is general education about how such rules work, not legal advice.
Why ownership matters
Those who invest in building software expect to profit from it. Intellectual property law gives creators rights over creations of the mind. For software, the main tools are copyright, patents, trade secrets and licences. Laws differ between countries, though treaties narrow the gaps, so each rule below names where it applies. Engineers need the basics because they constantly reuse code written by others, and a mistake about rights can cost far more than the code itself.
Copyright
Copyright protects original creative expression: in software, the source code, the compiled program, documentation and screen designs. In the United Kingdom and the European Union, programs are explicitly protected as literary works. Under the Berne Convention, which most countries have joined, copyright arises automatically when a work is created, with no registration needed. In the United States, a notice such as "© 2026 Example Ltd" has been optional since 1989, though it still warns copiers, and a US work must be registered before its owner can sue for infringement. In the US, EU and UK, copyright usually lasts for the author's life plus 70 years. Code employees write as part of their job usually belongs to the employer.
What copyright does not cover
In the US, EU and UK, copyright protects expression, not ideas, algorithms or functions, so a rival who writes a new program from scratch, copying no code, may offer the same features. Borderline copying is for courts: in Google v. Oracle (2021), the US Supreme Court held that Google's reuse of about 11,500 lines of Java's interface declarations in Android was fair use, without deciding whether such declarations are protected at all. Other tools fill gaps. In US, EU and UK law, a trade secret is valuable information kept confidential, such as a ranking formula; it stays protected only while it stays secret, through access controls and non-disclosure agreements (NDAs). A trademark protects names and logos against confusing look-alikes.
Software licences
Buying software almost never transfers its ownership. Instead, a software licence is a legal agreement in which the owner grants the user certain permissions, such as installing the program on a stated number of devices, while keeping the intellectual property. End-user licence agreements, often accepted by clicking a box, may forbid copying, resale or, where local law allows, reverse engineering, and usually limit the owner's liability. Subscription services use terms of service in the same way. A licence should be checked before installing, not after a dispute.
Open-source licences
Open-source licences use copyright to grant wide freedoms: anyone may use, study, change and share the code, under stated conditions. Permissive licences ask little in return. The MIT licence requires only that its copyright and permission notice stay with copies; the Apache License 2.0 adds an explicit grant of the contributors' patent rights. Copyleft licences, led by the GNU General Public License (GPL), require that anyone who distributes a program built on GPL code release the whole program under the GPL, with source code. These duties are triggered by distribution, so code used only privately inside an organisation need not be published. The Affero GPL extends them to modified versions offered to users over a network.
Worked example: checking licence duties
A company sells a desktop app built with library A under the MIT licence and library B under the GPL. It also runs a GPL-licensed tool C only on its own servers. 1. Library A: the app must include A's copyright and permission notice, for example on an About screen; the app's own code can stay closed. 2. Library B: the company distributes an app built on GPL code, so it must give buyers the whole app's source under the GPL, or replace B with a differently licensed library. 3. Tool C: it is never distributed, so the GPL creates no duty to publish anything. 4. Conclusion: B is the problem, and checking its licence before choosing it would have avoided it.
Patents
A patent protects an invention itself, including how a thing works, and it even binds people who invent the same thing independently. In the US an invention must be new, useful and non-obvious to someone skilled in the field, and the inventor must publicly disclose how it works. The patent then gives the right to stop others making, using, selling or importing the invention, usually for 20 years from the filing date, the standard term in most countries. Software patents are contested: in Alice v. CLS Bank (2014), the US Supreme Court held that an abstract idea does not become patentable just by running on a computer, and the European Patent Convention excludes programs "as such".
When patents bite
Ignoring other people's patents can be ruinous. In the US, a small firm called NTP sued Research In Motion, maker of BlackBerry phones, claiming its wireless email used NTP's patented technology. NTP won in court, and during the appeals an injunction that could have shut down BlackBerry email across the United States hung over the company. In 2006 Research In Motion settled by paying $612.5 million. The lesson for engineers: every library or snippet copied from the internet comes with legal strings, a licence to honour and possibly patents to check, so companies keep records of where their code came from.
Worked example: choosing the right protection
A start-up has four assets. 1. The source code of its route-planning app: copyright, which arises automatically; keep the code private too. 2. A genuinely new technical method for compressing map data: possibly a patent, if it is new and non-obvious and passes each country's test for software inventions; but applying means publishing how it works. 3. A secret route-ranking formula tuned on its own data: a trade secret, guarded by access controls and NDAs, since a patent would reveal it and might not be granted. 4. The app's name and logo: a trademark. Check: each asset gets the tool that protects what makes it valuable, its wording, invention, secrecy or brand.
Liability and disclaimers
Who pays when software causes harm? Licences often contain disclaimers: the MIT licence says the software is provided "as is", without warranty. How far such clauses protect depends on the jurisdiction and the harm. In England and Wales, no term can exclude liability for death or personal injury caused by negligence: the Unfair Contract Terms Act 1977 says so for business contracts, and the Consumer Rights Act 2015 for consumer ones. That 2015 Act, UK-wide, also requires digital content sold to consumers to be of satisfactory quality. In common-law countries such as the US and UK, negligence claims ask whether the developer took reasonable care, and more is expected of radiotherapy software, after the Therac-25 overdoses, than of a puzzle game. Careful engineering, with records that prove it, is the best defence.
Common mistakes to avoid
First, thinking code on the internet is free to use: it is protected by copyright unless a licence grants permission. Second, believing copyright protects ideas or algorithms; it protects expression. Third, confusing permissive licences, such as MIT, with copyleft ones, such as the GPL. Fourth, assuming a disclaimer removes all liability everywhere. Fifth, stating a legal rule without saying where it applies.
Key takeaways
Copyright protects software's expression automatically in Berne countries, usually for life plus 70 years in the US, EU and UK, but not its ideas. Trade secrets protect confidential information, trademarks protect brands, and patents protect inventions for about 20 years from filing, though software patents are limited. Licences grant permissions without transferring ownership; open-source licences are permissive, like MIT, or copyleft, like the GPL. Disclaimers have limits set by each jurisdiction, and the care expected rises with the risk.
Flashcards
Flashcard
Legal rights over creations of the mind
Test your understanding
Question 1 of 5
A rival studies a popular note-taking app's features and writes its own program from scratch, copying no code, with the same features. Under US, EU or UK copyright law, what is the position?
Question 2 of 5
A company distributes an app that includes a library under the MIT licence. What does that licence require?
Question 3 of 5
A firm modifies a GPL-licensed tool and uses it only on its own internal servers, never giving copies to anyone. Under the GPL, what must it do?
Question 4 of 5
A start-up's main asset is a ranking formula it wants to keep from competitors for as long as possible. Which protection fits best?
Question 5 of 5
A licence for software sold to consumers in England says the developer accepts no liability for any harm. Which statement is correct?
