{"id":2755,"date":"2026-10-09T08:21:40","date_gmt":"2026-10-09T08:21:40","guid":{"rendered":"https:\/\/sawaryn.com\/us\/?p=2755"},"modified":"2026-10-09T08:21:59","modified_gmt":"2026-10-09T08:21:59","slug":"polish-startup-product-ip-chain-of-title","status":"publish","type":"post","link":"https:\/\/sawaryn.com\/us\/polish-startup-product-ip-chain-of-title\/","title":{"rendered":"Does Your Polish Startup Own Its Product? A Guide to the IP Chain of Title"},"content":{"rendered":"

Does Your Polish Startup Own Its Product? A Guide to the IP Chain of Title<\/h1>\n

An investor asks to see the IP chain of title. \u201cIt\u2019s our product\u2014the founder is on the management board\u201d is not an answer. A funding round can stall at precisely this point.<\/p>\n

If a founder created the code, interface, database, or domain as an individual before the company was registered\u2014or before signing an agreement transferring the relevant rights\u2014the Polish company may have no legal title to what it sells. Assets owned by shareholders do not become company assets merely because those shareholders formed a company. Investors check the documents early in due diligence.<\/p>\n

This guide explains the documents needed to establish an IP chain of title<\/strong>, the product components an agreement should cover, and the formal mistake that can invalidate a transfer from a management board member. A 12-point checklist appears near the end.<\/p>\n

Key Polish IP concepts<\/h2>\n\n\n\n\n\n\n\n\n\n\n
Concept<\/th>\nWhat it means in practice<\/th>\n<\/tr>\n<\/thead>\n
IP chain of title<\/strong><\/td>\nThe documents showing how rights passed from each individual creator to the company. A missing link creates a due diligence risk.<\/td>\n<\/tr>\n
Fields of exploitation<\/strong><\/td>\nThe specific ways a copyrighted work may be used. A Polish copyright transfer agreement must identify them; without them, the transfer is ineffective under Article 41 of the Polish Copyright Act<\/a>.<\/td>\n<\/tr>\n
Derivative rights<\/strong><\/td>\nRights relevant to adapting, modifying, and developing a work into new versions. The agreement must address the right to authorize the exercise of these rights separately.<\/td>\n<\/tr>\n
Moral rights<\/strong><\/td>\nInalienable rights of a creator, including authorship and attribution. They cannot be transferred; the agreement can instead include an undertaking not to exercise them.<\/td>\n<\/tr>\n
Article 210 \u00a7 1 of the Polish Commercial Companies Code<\/strong><\/td>\nA representation rule for agreements between a company and a member of its management board. The company must be represented by its supervisory board or an attorney-in-fact appointed by a shareholders\u2019 meeting resolution. The source treats noncompliance as making the agreement absolutely invalid.<\/td>\n<\/tr>\n
SBOM (Software Bill of Materials)<\/strong><\/td>\nAn inventory of external product components\u2014such as libraries, frameworks, and fonts\u2014and their licenses.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A Polish company\u2019s management board<\/em> is the corporate body whose members manage and represent it. A founder\u2019s position on that board does not itself transfer the founder\u2019s IP to the company.<\/p>\n

How the ownership gap arises\u2014and when it matters<\/h2>\n

A familiar sequence is that a founder builds an MVP before incorporation. A year later, the company has customers, revenue, and a team, but the rights to the original code, interface, text, or database structure still sit with the individual creator. Being the company\u2019s president or another management board member does not solve the problem; it adds a representation requirement when the company contracts with that person.<\/p>\n

Three situations deserve particular attention:<\/p>\n

    \n
  1. Incorporation through Poland\u2019s S24 online portal<\/a>.<\/strong> Contributions at online registration can be monetary only, so IP cannot be contributed in kind<\/a> through that process. A separate agreement is needed to move the product to the company\u2014and is often never signed.<\/li>\n
  2. Work created before the company existed.<\/strong> Incorporation does not move a founder\u2019s preexisting rights. Without a written transfer agreement, those rights remain with the creator.<\/li>\n
  3. Contractors or freelancers without IP provisions.<\/strong> Under Article 74(3) of the Polish Copyright Act, an employer acquires rights to a computer program created by an employee in the course of employment duties. That rule does not extend to business-to-business service arrangements<\/a>. A service contractor who has not assigned the rights retains the economic copyrights to their code. See also PARP\u2019s explanation of copyright in employment relationships<\/a>.<\/li>\n<\/ol>\n

    The gap often becomes visible at a costly moment:<\/p>\n\n\n\n\n\n\n\n\n
    Stage<\/th>\nPotential consequence<\/th>\n<\/tr>\n<\/thead>\n
    Funding due diligence<\/td>\nThe investor requests the chain of title. A missing agreement may lead to a condition precedent, a lower valuation, an escrow arrangement for part of the consideration, or withdrawal.<\/td>\n<\/tr>\n
    Founder or shareholder dispute<\/td>\nA founder who never transferred their rights may use that position as negotiating leverage.<\/td>\n<\/tr>\n
    Share sale or exit<\/td>\nA buyer\u2019s legal review identifies documentation gaps that delay or prevent closing.<\/td>\n<\/tr>\n
    Enterprise customer audit<\/td>\nA customer checks whether its SaaS supplier has the necessary product rights; inadequate documentation may cost the contract.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    If you need to identify gaps before a transaction, contact us<\/a>.<\/p>\n

    What an agreement covering the whole MVP needs to address<\/h2>\n

    In many cases, one written agreement can cover the rights to an existing MVP. It must, however, distinguish between assets that can be assigned, materials governed by third-party licenses, and operational steps that cannot be completed simply by declaring a transfer in the agreement.<\/p>\n\n\n\n\n\n\n\n\n\n\n
    Product layer<\/th>\nRights or steps to address<\/th>\nParticular risk<\/th>\n<\/tr>\n<\/thead>\n
    Source and object code<\/td>\nEconomic copyrights, the right to authorize the exercise of derivative rights, and ownership of copies<\/td>\nThe agreement needs fields of exploitation for software under Article 74(4), as well as fields relevant to any non-software works under Article 50 of the Copyright Act<\/a>.<\/td>\n<\/tr>\n
    Interface, graphics, documentation, and text<\/td>\nEconomic copyrights covering the relevant Article 50 fields<\/td>\nDo not assume software-specific wording covers these separate works.<\/td>\n<\/tr>\n
    Database structure and schema<\/td>\nRights in selection, arrangement, and compilation, plus database maker\u2019s rights<\/td>\nDistinguish the structure from its contents. If an empty database is handed over, confirm that it contains no personal data; the source notes this can avoid a data processing agreement.<\/td>\n<\/tr>\n
    AI-generated material<\/td>\nRepresentations about review and creative editing, plus ownership of copies and transfer of know-how where relevant<\/td>\nAccording to the source\u2019s analysis, an autonomously generated fragment without the required human creative contribution is not a copyrighted work to assign.<\/td>\n<\/tr>\n
    Domain name<\/td>\nAssignment of the registrar agreement, authinfo\/EPP code, and change of registrant<\/td>\nWording that merely says \u201cdomain rights are transferred\u201d does not replace steps with the registrar.<\/td>\n<\/tr>\n
    Product name<\/td>\nRights to the name and consent to apply for trademark registration<\/td>\nAcquiring rights to a name is not the same as obtaining trademark protection.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Specify both sets of fields of exploitation<\/h3>\n

    Polish law distinguishes computer programs from other protected product materials for this purpose:<\/p>\n