A Warsaw-based software house delivers a custom ERP platform to a German client. Six months later, the client's subsidiary launches a nearly identical product under a different name. The original developers have no registration certificate, no timestamped deposit, and no clear contractual assignment clause. Their legal position is weaker than it should be – not because Polish law fails them, but because they never structured their protection in advance.

Polish copyright law protects software automatically from the moment of creation, without any registration requirement. The ustawa o prawie autorskim i prawach pokrewnych (Act on Copyright and Related Rights, UPAPP) treats computer programs as a distinct category of literary works, granting authors exclusive economic and moral rights. However, automatic protection is only as strong as the evidence and contractual framework surrounding it – gaps in either can forfeit enforceable rights within 90 days of a dispute arising.

This guide walks through the full protection cycle: how rights arise, how employers and investors acquire them, where the most common mistakes occur, and what a foreign company entering Poland must do before signing its first development contract. Three business scenarios – a Polish software house, an IT subsidiary of a German group, and a SaaS startup – illustrate each stage.

How does copyright arise for software under Polish law?

Protection begins at the moment a developer fixes an original expression in any medium. There is no filing, no deposit, and no fee. The National Court Register (KRS) plays no role here. What matters is originality – the program must reflect the author's own intellectual creation. Functional logic, algorithms, and programming languages are excluded from protection, but the specific code expressing them is covered from line one.

The UPAPP draws a sharp line between economic rights and moral rights. Economic rights – reproduction, distribution, adaptation, and communication to the public – are transferable and form the commercial core of any software deal. Moral rights, including the right to authorship and the right to protect the work's integrity, are perpetual and non-transferable. A developer cannot contractually waive them. This distinction matters enormously in M&A transactions, where a buyer acquiring a software company needs economic rights assigned in writing but cannot eliminate the moral rights of the original coders.

One figure to remember: economic rights last for 70 years after the author's death. For works created by multiple authors, the clock runs from the death of the last surviving contributor. For works created by employees, the employer acquires economic rights automatically – but only if the program was created within the scope of employment duties. That "scope" question is where disputes begin. (More on this in the next section.)

Polish institutions such as the Polish Chamber of Information Technology and Telecommunications (PIIT) and the Copyright Office under the Ministry of Culture do not run a mandatory register. Voluntary deposit with a notary or a certified timestamp service, however, creates strong evidential weight before Polish courts. We recommend a deposit within 30 days of the first stable release.

Who owns the software – and when does ownership become contested?

Ownership disputes are the most frequent source of software litigation in Poland. The UPAPP grants an employer automatic ownership of economic rights over software created by an employee in the course of employment – but this rule applies only to software, not to other categories of creative work. The scope-of-employment boundary is narrow. Code written on a personal laptop after hours, even using the employer's proprietary libraries, may not fall within that automatic transfer.

For contractors and B2B developers, the default rule reverses entirely. A freelancer retains all economic rights unless the contract explicitly assigns them. "Work for hire" as understood in US law does not exist under Polish copyright doctrine. A Polish development contract must contain a precise assignment clause specifying: the fields of exploitation (reproduction, modification, distribution, sublicensing), the territory, and the time period. An assignment that omits any field of exploitation does not cover that field – full stop.

We secured a reversal of a disputed software ownership claim worth over PLN 3.5m for a manufacturing client in the Mazowieckie region (autumn 2025). The contractor had delivered a warehouse management system under a contract that listed only "reproduction" and "distribution" as transferred fields. The client's right to modify the source code – essential for integration – had never been assigned. The lesson: incomplete field-of-exploitation clauses are not a technicality. They are a liability.

  • Specify all fields of exploitation by name in the assignment clause.
  • Include source code and object code as separate items.
  • Address derivative works and AI-generated modifications explicitly.
  • Confirm that the contractor has no prior-created components with third-party rights.
  • Insert a warranty and indemnity clause covering IP infringement claims.

For a German investor entering the Polish market through a local IT subsidiary, the Polish Financial Supervision Authority (KNF) may become relevant if the software underpins a regulated financial service – particularly under DORA compliance obligations that took effect in January 2025. DORA requires financial entities to maintain documented ownership of all ICT tools and to manage third-party software risk. A weak assignment clause in a development contract can trigger a DORA gap finding during a KNF supervisory review.

What procedural steps protect software most effectively?

Step one is documentation. Before any code leaves the development environment, the company should create a timestamped record of the codebase. This can be done through a notarial deposit (koszt: approximately PLN 300–600 per session), a qualified electronic timestamp under the eIDAS regulation, or a hash-based deposit with a certified escrow provider. The deposit does not create rights – it proves when they arose. Courts routinely accept this evidence in infringement proceedings.

Step two is contractual structuring. Every development relationship – employment, B2B, subcontracting – needs a written IP clause reviewed by an IP lawyer Warsaw-based or otherwise qualified under Polish law. The clause must cover: assignment of economic rights in all fields of exploitation, transfer of rights to derivative works, consent to exercise dependent rights (modifications), and a prohibition on the developer registering any related trademark or domain independently.

Step three is trademark registration. Copyright protects the code. It does not protect the product name, logo, or user interface design as such. A trademark application with the Polish Patent Office (Urząd Patentowy RP) takes approximately 6–8 months for a national mark and covers 10-year renewable periods. EU trademark registration through the EUIPO takes a similar timeframe but covers all 27 member states. For a SaaS product targeting European markets, both filings run in parallel.

Step four is data protection alignment. Software that processes personal data must be designed in compliance with GDPR Poland requirements – specifically privacy-by-design and privacy-by-default obligations enforced by the Personal Data Protection Office (UODO). A software product with embedded data flows to third countries must also comply with transfer rules; see our guide on data transfer from Poland to the United Kingdom for the post-Brexit framework. GDPR non-compliance can independently expose a software company to fines of up to EUR 20m or 4% of global turnover – whichever is higher.

What are the most damaging mistakes in software IP practice?

The first and most costly mistake is treating automatic protection as sufficient protection. Automatic copyright arises, but without a deposit, a contract trail, and registered marks, enforcing it takes years and costs more than prevention. Polish district courts (sądy okręgowe) handle copyright infringement claims. Proceedings routinely last 18–36 months at first instance. Interim injunctions are available – but require evidence of both infringement and urgency, and courts apply a strict standard.

The second mistake is failing to address open-source components. Many development teams incorporate GPL, LGPL, or MIT-licensed libraries without a formal licence inventory. GPL licence conditions, in particular, require disclosure of the entire source code of any derivative work. A software product sold commercially that contains undisclosed GPL components faces a choice: disclose the full source or face an infringement claim. Neither option is comfortable after a product launch.

The third mistake concerns AI-generated code. The AI Act Poland transposition is underway, and Polish courts have not yet resolved whether AI-generated output qualifies as an original work under UPAPP. The safer position – currently – is that AI-generated code without meaningful human creative input does not attract copyright protection. A development team that relies heavily on AI code generation and does not document human creative decisions may find its product unprotected. This is an active legal risk, not a theoretical one.

We obtained interim measures protecting source code worth over EUR 2m for a tech startup client in Lower Silesia (spring 2026). The opposing party had copied the client's proprietary algorithm and repackaged it as a competing SaaS product. The key evidence: a notarial code deposit made 14 months earlier and a clear employment IP clause covering all fields of exploitation. Without both, the injunction application would have failed at the first hearing.

How should foreign companies structure software IP when entering Poland?

For a German IT group establishing a Polish development centre, the first priority is a group IP policy that maps onto Polish law. German "work for hire" assumptions do not translate. The Polish subsidiary must have its own IP assignment clauses in every employment contract and every B2B agreement. A blanket group policy governed by German law is not enforceable against a Polish employee for rights arising under Polish copyright law.

The second priority is intercompany IP licensing. If the Polish subsidiary develops software for the parent group, the economic rights should be assigned – or exclusively licensed – upward under a documented intercompany agreement. Transfer pricing rules apply: the Polish Tax Administration (Krajowa Administracja Skarbowa, KAS) scrutinises IP transfers between related parties. An IP Box regime election (5% CIT rate on qualifying IP income) is available to Polish entities that own qualifying IP rights and conduct qualifying R&D. The election requires a separate R&D cost tracking system from day one.

Data flows between the Polish subsidiary and the German parent require a legal transfer mechanism under GDPR. Poland and Germany are both EU member states, so intra-EU transfers do not require additional safeguards. However, if the software processes data of Polish data subjects and routes it through servers outside the EEA – for instance, to a US cloud provider – the relevant transfer mechanisms must be documented. Our guide on cross-border legal structuring in Poland addresses related structuring considerations.

For a SaaS company targeting both Polish and EU markets, the recommended structure is: Polish entity owning the copyright and trademark, EU trademark registered at EUIPO, GDPR data processing agreements in place, and an IP escrow arrangement with a neutral third party for enterprise clients. This structure supports both commercial due diligence and regulatory audit readiness – particularly relevant under DORA compliance requirements for fintech and financial infrastructure clients.

Your company's specific IP structure determines whether a dispute can be resolved in weeks or will consume years of litigation. Gaps in assignment clauses or missing deposits are not correctable after an infringement has occurred – those omissions become permanent weaknesses in any enforcement or defence.

To receive an expert assessment of your software IP structure in Poland, contact info@kordeckipartners.com.

Frequently asked questions

Q: Does Polish law require software to be registered to receive copyright protection?

A: No registration is required. Protection arises automatically at the moment of creation, provided the work is original. However, voluntary deposit – with a notary or a certified timestamp service – creates strong evidential weight in infringement proceedings and is recommended within 30 days of the first stable release. The absence of a deposit does not eliminate rights, but it significantly complicates enforcement before Polish courts.

Q: How long does it take to obtain a trademark for a software product in Poland, and what does it cost?

A: A national trademark application with the Polish Patent Office typically takes 6–8 months from filing to registration, assuming no opposition. The official filing fee starts at PLN 450 for one class. EU trademark registration through the EUIPO covers all 27 member states and follows a similar timeline, with fees starting at EUR 850 for one class. Both applications can run in parallel, and for software products targeting European markets, dual filing is standard practice.

Q: Is AI-generated code protected by copyright under Polish law?

A: This is an unresolved area. Polish copyright doctrine requires that a work reflect the author's own intellectual creation – a human creative act. Code generated entirely by an AI tool without meaningful human creative input is unlikely to qualify for copyright protection under the current interpretation of the Act on Copyright and Related Rights. Development teams should document human creative decisions in their workflow and maintain version control records showing the extent of human authorship. The AI Act transposition will likely introduce further clarity, but the timeline for implementing legislation remains uncertain.

KORDECKI & Partners is a law firm based in Warsaw and Krakow, advising business clients across 30 jurisdictions. Our team combines expertise in Polish and international law with a practical approach to software copyright, IP licensing, trademark registration, and technology transactions. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.

Disclaimer: This publication is provided for informational purposes only and does not constitute legal advice. The information herein should not be relied upon as a substitute for professional legal counsel tailored to your specific circumstances. KORDECKI & Partners assumes no liability for actions taken or not taken based on the contents of this material. For advice regarding your particular situation, please contact info@kordeckipartners.com.