Last updated: 2026-11-18
Software and Intellectual Property: A Map for Programmers
Everything a programmer produces is, in the end, a sequence of bits. Some of those sequences are protected by law and some aren't, and whether a given one is protected depends less on how hard it was to make than on where it came from, what kind of thing it is, and which right you're asking about. UK law offers at least six separate rights that can touch software, each protecting something different, lasting a different length of time, and arising in a different way.
This page maps those rights and introduces five pages that each take one question further. They can be read in any order.
Six Rights, Six Different Objects FoundationalKnowledge that endures for decades โ core principles
| Right | Protects | Arises | Lasts |
|---|---|---|---|
| Copyright | The expression of a program: source and object code, preparatory design material, documentation, original screen designs | Automatically, when an original work is recorded | Author's life plus 70 years |
| Patent | A new, inventive technical solution, which may be implemented in software | Application and examination | Up to 20 years1 |
| Registered design | The appearance of a product, including graphic symbols such as icons; not a computer program itself | Registration | Up to 25 years, in five-year periods2 |
| Trade mark | Signs that distinguish one business's goods or services from another's: product names, logos | Registration, or goodwill (passing off) | Renewable indefinitely |
| Database right | Substantial investment in obtaining, verifying or presenting a database's contents | Automatically | 15 years from completion or publication3 |
| Trade secret | Commercially valuable information kept secret by reasonable steps, such as unpublished source code | By keeping it secret | As long as it stays secret4 |
One program can be covered by several of these at once. The source code is a copyright work and, while unpublished, a trade secret; the product name is a trade mark; the icon set may be a registered design; a technical method it implements may be patented; the reference data it ships with may carry database right. Each right also leaves a lot unprotected, and that matters as much as what it covers.
What None of Them Protects FoundationalKnowledge that endures for decades โ core principles
Ideas, mathematical concepts, functionality, programming languages and data formats sit outside copyright, and pure mathematical methods and programs "as such" sit outside patents. The Court of Justice of the European Union (CJEU) gave the reason in SAS Institute v World Programming: protecting functionality "would amount to making it possible to monopolise ideas, to the detriment of technological progress and industrial development"5. A competitor can therefore build a program that behaves the same way as yours, provided it doesn't copy your code, your documentation's wording, or anything else that expresses your own creative choices.
screen designs"] Q --> F["Behaviour, language,
file format, algorithm idea"] Q --> T["A technical solution
to a technical problem"] Q --> N["A name or logo"] Q --> D["A collected,
verified dataset"] C --> CR["Copyright, if it reflects
your free and creative choices"] F --> X["Not protected by
copyright"] T --> P["Possibly a patent,
if new and inventive,
and filed before disclosure"] N --> TM["Trade mark"] D --> DB["Database right, if the
investment was substantial"] C --> S["Trade secret,
while unpublished"] style X fill:#FFC857
The Five Pages FoundationalKnowledge that endures for decades โ core principles
- SAS v World Programming: What Copyright Protects in Software: the decade-long case that settled what a competitor may copy, what a click-through licence can forbid, and why the same conduct was lawful in England and cost US$79 million in North Carolina.
- Is a Binary a Copyright Work?: compilation as translation, why object code is protected, where generated and AI-written code fits, and the tension between the EU's investment rationale and its originality test.
- Why Maths Isn't Copyright, and Every File Is a Number: the exclusion of mathematical concepts, and how copyright can protect a work when every digital work is also an integer.
- Making More of Your Output Protectable: practical steps for programmers, from where your creative choices show to who owns what you write.
- Beyond Copyright: Patents, Designs, Trade Marks, Databases and Secrets: the other rights, including the Supreme Court's 2026 change to how UK law treats software patents.
Related Topics
- Legal Framework in Computing: the Computer Misuse Act, data protection and other legal obligations.
- Professional Ethics: codes of conduct, including on respecting others' intellectual property.
- Product and Ethical Risk: intellectual property as one of the risks on a project's register.
References
-
Patents Act 1977, s.25(1). https://www.legislation.gov.uk/ukpga/1977/37/section/25 โฉ
-
Registered Designs Act 1949, ss.1 and 8. https://www.legislation.gov.uk/ukpga/Geo6/12-13-14/88/section/8 โฉ
-
Copyright and Rights in Databases Regulations 1997 (SI 1997/3032), regs 13 and 17. https://www.legislation.gov.uk/uksi/1997/3032/regulation/17 โฉ
-
Trade Secrets (Enforcement, etc.) Regulations 2018 (SI 2018/597), reg 2. https://www.legislation.gov.uk/uksi/2018/597/regulation/2 โฉ
-
Case C-406/10 SAS Institute Inc v World Programming Ltd, EU:C:2012:259, para 40. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62010CJ0406 โฉ