Protecting Software as a Copyrighted Work

What software copyright protects
Protection arises automatically if the program is the author's own intellectual creation – which is almost always the case with commercially developed software. Development phases and preparatory materials are also protected if the program can be created from them.
However, copyright only protects the specific expression – the source and machine code. It does not protect ideas, principles, algorithms, or functionality. According to the Court of Justice of the EU, even the graphical user interface (GUI) is not protected as part of the program. For these, other tools must be considered, such as a registered design or trade secret protection.
Who is the real master of your code?
Employee work
If an employee creates a program as part of their employment duties, the employer exercises the economic rights. The same applies to works created by members of statutory bodies.
Commissioned work: a hidden trap
A program created by an author on commission is considered an employee work, and the ordering party is deemed the employer (Section 58(7) of the Czech Copyright Act). This typically applies to freelance programmers. If you order development from an IT company, the rights remain with them as the employer of the programmers, and without a contract, you only obtain a license for the purpose resulting from the contract. This can complicate the sale of the company, investor entry, and further development.
Possible problems | How ARROWS helps (consultation@arws.cz) |
|---|---|
Unclear code ownership: the ordering party only has a limited license. | What we will do: we will prepare an agreement transferring the exercise of economic rights or providing a broad license. |
Vendor lock-in: the supplier dictates prices for maintenance and development. | What we will do: we will ensure the handover of source codes or their escrow. |
Foreign contract templates: "work for hire" clauses may be invalid under Czech legislation. | What we will do: we will adapt the contracts under Czech and European law. |
Unclear specifications: disputes over what was supposed to be delivered. | What we will do: we will set up specifications, acceptance criteria, and payment milestones. |
Licenses, SaaS, and open-source pitfalls
In the traditional model, the customer installs a copy of the software and uses it according to an end-user license agreement (EULA). In the SaaS model, they pay for access to a service running on the provider's servers, and the relationship is governed by a service agreement, typically with an SLA and a personal data processing agreement.
"Free" does not mean commitment-free: open-source
Open-source components are distributed under licenses with specific obligations. The greatest risk is posed by so-called viral licenses (e.g., GNU GPL), which, under certain usage scenarios, can force the disclosure of the source code of your entire product. We recommend a regular audit of the components used.
NDAs and source code escrow
Protecting the idea: non-disclosure agreement (NDA)
Since copyright does not protect ideas, protect your know-how and business concepts with a non-disclosure agreement (NDA) with employees, suppliers, and investors. The key is to precisely define what is confidential.
Source code escrow
What if a key supplier goes bankrupt or terminates support? Source code escrow is a tripartite agreement where the supplier deposits the code with a third party, who releases it to the client upon pre-agreed events. Technical verification that the deposited code is complete and functional is also important.
How to enforce your rights
In the event of unauthorized infringement of your rights, you can, under the Czech Copyright Act, seek in particular:
refraining from unauthorized use,
remedying the consequences (e.g., recalling copies from the market),
reasonable satisfaction,
surrender of unjust enrichment amounting to double the customary license fee.
International protection
Thanks to the Berne Convention, the TRIPS Agreement, and the WIPO Copyright Treaty, computer programs are protected as literary works in all signatory countries.
Summary
Code protection arises automatically, but its true value depends on properly structured agreements with developers and customers, control over open-source components, and the ability to defend yourself quickly.
Want to make sure you truly hold the rights to your software? Contact our Prague-based legal team at consultation@arws.cz.
About the author
Disclaimer:
The information contained in this article is for general informational purposes only and serves as a basic guide to the issue as of 2026. Although we strive for maximum accuracy, laws and their interpretation evolve over time. We are ARROWS Law Firm, a member of the Czech Bar Association (our supervisory authority), and for the maximum security of our clients, we are insured for professional liability with a limit of CZK 350,000,000. To verify the current wording of the regulations and their application to your specific situation, it is necessary to contact ARROWS Law Firm directly (consultation@arws.cz). We are not liable for any damages arising from the independent use of the information in this article without prior individual legal consultation.

