Intellectual Property ownership Kenya: 5 Legal Rules for App Founders
·

Imagine paying KES 1.5 million to a software developer in Westlands to build your new e-commerce app. The launch goes well, users are signing up, and you are ready to pitch to venture capitalists in Nairobi. Then, you ask the developer for the raw source code to host it on your own server.
He refuses. He demands another KES 500,000 or a 15% equity stake in your company. If you do not pay, he threatens to shut down the app.
Can he legally do this?
The short answer is yes. If you did not sign the right agreements, you do not own the code. Understanding Intellectual Property ownership Kenya is the difference between building a valuable business and owning an expensive, unusable digital shell.
How the Copyright Act Kenya Defines Intellectual Property ownership Kenya
In Kenya, software is protected as a “literary work” under Section 22 of the Copyright Act, Cap 130. When you hire an independent freelance developer, they are the author of that work.
Under the current Section 31 of the Copyright Act Kenya, there is a “commissioned works” rule. This rule states that if you commission someone to create a work, the copyright is deemed to be transferred to you, unless you have an agreement to the contrary.
However, relying on this default rule is highly dangerous for three main reasons:
- Source Code vs. Executable Code: The law does not automatically force a developer to hand over the raw source code. They can argue they fulfilled their commission by delivering a working, compiled app (the executable files) on the App Store, while keeping the blueprint (the source code) to themselves.
- Joint Authorship Claims: If you contributed ideas, wireframes, or database structures, the developer might claim the app is a work of joint authorship. Under Kenyan law, joint authors share equal rights, meaning you cannot license or sell the software without their consent.
- The 2026 Legal Shift: The Kenya Copyright Board (KECOBO) has proposed the Copyright and Related Rights Bill, 2026. Section 21(3) of this bill completely reverses the default rule. It states that for a commissioned work, the author (the developer) retains ownership unless the commissioning contract expressly transfers the copyright in writing. If this bill passes fully into law, verbal or informal agreements will offer zero protection.
To protect your investment, you need a robust, written software development contract before writing a single line of code.
Never rely on default statutory rules; the upcoming changes to Kenyan copyright laws mean that without an express written transfer, the developer owns your app’s code.
Why an App developer contract is Not Enough
Many founders think that signing a generic App developer contract downloaded from the internet is enough. It is not. Software is rarely built entirely from scratch.
Developers use:
- Pre-existing libraries and frameworks (like React Native or Flutter).
- Open-source components (subject to licenses like MIT or GNU).
- Proprietary software blocks they developed for other clients.
If your contract simply says “the client owns all intellectual property,” it is legally unenforceable. Your developer cannot transfer ownership of open-source libraries or third-party APIs because they do not own them.
A well-drafted contract must separate the deliverables into two categories:
- Background IP: This includes pre-existing tools, libraries, and code modules that the developer already owned before your project. The contract must grant you a perpetual, royalty-free, worldwide license to use these modules so your app can run.
- Foreground IP: This is the unique code, custom user interfaces, database structures, and business logic built specifically for your app. The contract must state that you own this code completely.
Without this distinction, a developer can claim that because your app uses their pre-existing proprietary login module, you cannot modify or transfer the app without their permission.

Your contract must separate background code from newly created code to prevent developers from claiming your entire app contains their proprietary tools.
The Role of an IP assignment agreement Kenya
To fully secure your rights, your legal counsel must draft a comprehensive IP assignment agreement Kenya. This is a distinct legal document (or a robust clause within your main contract) that transfers all rights, titles, and interests in the software from the developer to your startup.
Under Section 33 of the Copyright Act Kenya, any assignment of copyright must be in writing and signed by the assignor (the developer). A verbal agreement, a Slack message, or a WhatsApp confirmation will not stand up in a Kenyan court.
Your IP assignment must also address three critical issues:
- Future Assignments: The agreement must state that the assignment applies to all future updates, bug fixes, and modifications developed during the project.
- Moral Rights: Under Section 32 of the Copyright Act, authors retain “moral rights” even after transferring their economic rights. This means a developer can object to any modification of their code if they feel it harms their professional reputation. Your agreement must contain an explicit waiver of moral rights by the developer.
- The Right to Sue for Past Infringements: The assignment must give your company the sole right to bring legal action against third parties who copy or steal the app code.
Without these specific clauses, you may own the code but find yourself legally blocked from hiring a new developer to modify it.
A standard service agreement does not automatically assign ownership; you must execute a separate, written IP assignment to legally secure your code.
Lessons from Kenyan Courts on Software Disputes
Kenyan courts have dealt with a number of intellectual property disputes that are useful warning signs for startups. In Samson Ngengi v Kenya Revenue Authority, the dispute arose from a geospatial tax-mapping system known as GEOCRIS and highlighted the risks that can arise where employee-created innovations are not clearly documented and ownership is left ambiguous. A public discussion of the matter is available here, and KRA’s own case digest also refers to the dispute here.
A more direct caution for commissioned work appears in Adventis Ltd v Superior Homes (K) Ltd. The key point is that where a creator produces copyright-protected work, such as architectural drawings, a client should not assume ownership without a clear written assignment or licence, and non-payment or lack of formal transfer can generate infringement risk. I was not able to verify a stable public eKLR link for this case from the material available to me here, so the citation should be checked against the official record before publication.
Another important dispute is Riara Group of Schools v Lucas Kamau, which involved software created by a teacher and raised the question whether the work belonged to the employer or to the individual creator. A commentary on the case is available here, and the judgment record is available on Kenya Law here.
The real lesson for startups is simple: courts generally look for proof, not assumptions. If you do not have clear written terms showing who commissioned the work, who paid for it, and who owns or may use the resulting intellectual property, you are inviting a dispute.
Kenyan IP disputes such as Samson Ngengi v KRA and Riara Group of Schools v Lucas Kamau show how ownership problems arise when employee-created or commissioned works are not documented clearly, while Adventis Ltd v Superior Homes (K) Ltd underscores the need for an express written transfer or license when dealing with copyright works.

Kenyan courts strictly enforce employment and contract terms, meaning a lack of documentation will tie your startup up in costly, multi-year litigation.
Checklist for Your Software development contract Nairobi
If you are currently working with a freelance developer or software agency in Nairobi, use this legal checklist to protect your business:
- Written Agreement: Ensure you have a signed, written agreement before any coding begins.
- Source Code Delivery: Specify that the developer must push the source code to your controlled repository (such as GitHub or GitLab) on a weekly basis.
- Milestone-Based Payments: Tie payments directly to the delivery and verification of clean code in your repository.
- Explicit IP Transfer: Include a clear clause stating that all newly created intellectual property is assigned to you upon payment.
- Moral Rights Waiver: Ensure the developer waives their moral rights under Section 32 of the Copyright Act Kenya.
- KECOBO Registration: Once the app is complete, register the copyright with the Kenya Copyright Board (KECOBO) through the National Rights Registry (NRR) portal to establish a public record of your ownership.
Taking these steps ensures you remain in complete control of your digital assets and can confidently present your startup to potential investors.
Implementing a clear contractual checklist and registering your software with KECOBO is the ultimate way to de-risk your startup’s technology stack.
Need Help Securing Your Startup’s Source Code?
Need Help Securing Your Startup’s Source Code?
Do not let a developer hold your business hostage. Protect your investment before it is too late.
Book a 15-minute Tech IP Consultation with our team.
Ready to discuss your legal needs?
Get the clarity and guidance you need. I am here to help you navigate your legal journey with confidence.

