How do I protect my idea and code when working with developers?
By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published
You cannot own an idea, but you can own the code, the brand and the accounts. Sign a written contract that assigns the work to your company, or to you until it exists. Keep the repository, domain and store accounts in the company's name or yours, never the developer's. Use an NDA for confidential details and register your trade mark.
The fear usually arrives the night before the first meeting with a developer. You are about to explain, in detail, the thing you have been thinking about for a year, to a person who could build it without you. What stops them?
Honestly, very little stops anyone from copying an idea, and that is true in every country. But the fear is aimed at the wrong target. A developer stealing the concept is the less likely way to lose a product. The more likely one is that the code sits in the developer's personal account, the domain is in a cousin's name, there is no written contract, and the relationship goes sour.
That second problem is within your control. This article is general information and not legal advice. Have an advocate review any contract before you sign it.
Can I protect an idea at all?
No. You can protect what the idea turns into.
Kenya's Copyright Act protects works, not thoughts. A literary work is only eligible for copyright once it "has been written down, recorded or otherwise reduced to material form". An idea you describe over coffee is not a work. The code, the designs, the written specification and the content are.
So think in layers, each with its own kind of protection:
| What you have | What protects it | Who handles it in Kenya |
|---|---|---|
| The idea itself | Nothing, except keeping details confidential | You, with an NDA where it makes sense |
| Code, designs, written content | Copyright, which arises automatically | Kenya Copyright Board (KECOBO) for voluntary registration |
| Product name and logo | A registered trade mark | Kenya Industrial Property Institute (KIPI) |
| Customer lists, pricing, methods | Confidentiality clauses in contracts | Your contracts |
| The running product | Control of the accounts it lives in | You |
The last row is not a legal protection, and it is the easiest one to neglect.
Who owns code written by an employee or a contractor in Kenya?
By default the Copyright Act points ownership towards you in both cases, but the default can be changed by agreement, so never rely on it alone.
The Act lists computer programs within its definition of a literary work. Section 31 then sets out who owns a work first. Copyright vests initially in the author. But where a work is commissioned by someone who is not the author's employer, or is made in the course of the author's employment under a contract of service, the copyright "shall be deemed to be transferred to the person who commissioned the work or the author's employer, subject to any agreement between the parties excluding or limiting the transfer".
In plain terms:
- An employee writes code as part of the job. The copyright is deemed to pass to the employer.
- A contractor, such as a freelancer or a firm you commission, writes code for you. The copyright is deemed to pass to you as the person who commissioned it.
- In both cases, an agreement can exclude or limit that transfer. A developer's standard terms might say they keep ownership and give you a licence. If you sign that, the default no longer helps you.
Three gaps remain even when the default applies.
First, proof. With no written contract, you may have to prove that you commissioned the work and what it covered.
Second, the pieces that were never yours. Developers bring code they wrote before your project, open-source libraries and paid components. None of that was commissioned by you.
Third, people who are neither: an unpaid co-founder, a student who helped for free, a friend who designed the logo. Get a written assignment from each.
Moral rights are separate. Under section 32 the author keeps the right to be named as the author and to object to distortion of the work, even after the economic rights have moved.
What does an IP assignment clause do?
It turns the default into a written promise and closes the gaps. If you only get one clause right, make it this one.
A sound assignment clause does five things:
- States that all work created for the project, including code, designs and documentation, belongs to the company. If the company is not registered yet, the contract names you and assigns everything to the company once it exists.
- Says when ownership passes. Commonly on creation, or on payment for each milestone.
- Lists what the developer is bringing that stays theirs, and gives the company a permanent licence to use it inside the product.
- Requires the developer to disclose any open-source components and their licences.
- Obliges the developer to sign any further documents needed to record the company's ownership.
Here is wording to take to your advocate as a starting point. It is an illustration, not a finished clause.
All work created by the Developer for the Project, including source code, designs and documentation, belongs to the Company from the moment it is created. To the extent any rights do not pass automatically, the Developer assigns them to the Company. Pre-existing materials listed in Schedule 1 remain the Developer's property, and the Developer grants the Company a perpetual, royalty-free licence to use them as part of the product.
Point five matters in Kenya for a specific reason. Section 33 of the Act says an assignment of copyright must be in writing and signed by or on behalf of the person assigning it. It goes further: an assignment "shall not be valid unless it is lodged at the Board and a certificate of recordal issued". Ask your advocate how that applies to your contract and whether your assignment should be lodged with the Kenya Copyright Board.
What does an NDA do, and when is it worth signing?
A non-disclosure agreement is a contract in which someone promises not to share or use confidential information you give them. It protects information. It says nothing about who owns what gets built.
An NDA is worth having when you hand over things that would hurt you in a competitor's hands: customer lists, supplier terms, pricing models, financial records, unpublished designs. A useful NDA says what counts as confidential, what the information may be used for, how long the duty lasts, and that materials must be returned or deleted at the end.
Its limits are practical. It does not stop someone building a similar product from their own knowledge, and enforcing it means proving a breach in court.
A sensible order: talk freely about the problem and the customer, sign an NDA before sharing sensitive details, and put confidentiality and the IP assignment into the main development contract. There is a list of contract and handover questions in questions to ask before hiring a software studio.
Should I register copyright in my software?
You do not have to, and for most early products it is not urgent. It becomes useful once you have something worth defending.
The Act says copyright arises automatically when the work is fixed in material form, and that non-registration does not bar a claim. The Kenya Copyright Board describes registration as voluntary and lists what a certificate gives you: a public record of ownership, evidence of ownership in court if there is a dispute, and easier licensing or assignment. Under section 22A, the register is prima facie evidence of what is entered in it.
Registration is done online through the Board's National Rights Registry portal, where you create an individual or a corporate account and upload the work. Use a corporate account so that the company is recorded as the owner. Check the Board's site for the current process and fees before you begin.
Good moments to register are before you raise money or license the software to someone else.
Should I register a trade mark for the name?
Yes, once you are confident in the name. This is an easy protection to skip, and it is the one that stops a competitor trading under your brand.
KIPI's guidance is clear on how the pieces fit. Apps and software fall under copyright law and are handled by the Kenya Copyright Board, but the trade name you give the app can be registered as a trade mark. KIPI says registration is not mandatory but is highly advisable: it is direct evidence of ownership in Kenya, and its FAQ states that using a mark without registering it denies the owner the right to sue for infringement under the Trade Marks Act.
The practical steps, as KIPI describes them:
- Run a search first to see whether the name or logo is already registered by someone else.
- Apply in the classes of goods or services that fit your business. Marks are registered by class, so the same word can belong to different owners in different classes.
- Apply in the company's name once the company exists. KIPI accepts applications from individuals and companies, and a mark in a founder's personal name is a problem waiting for the day that founder leaves.
Fees change, so read KIPI's current fee schedule instead of relying on a figure you saw elsewhere.
What should I check before any code is written?
Go through this list. All of it is easier before the project begins than after a disagreement.
In the contract
- The parties are the company and the developer or firm, with full legal names. If the company does not exist yet, you sign in your own name, with a clause assigning everything to the company once it is formed.
- An IP assignment clause covers all project work.
- Your advocate has told you whether the assignment must be lodged with the Kenya Copyright Board (section 33).
- Pre-existing and open-source components are listed, with a licence to the company.
- A confidentiality clause covers your business information.
- Payment is tied to working milestones, with a final payment on handover.
- Handover is defined: code, database, credentials and a document explaining how to run the product.
- It says what happens to work in progress if either side ends the contract early.
In the accounts
Each of these goes in the company's name if the company exists. If it does not, use your own name, never the developer's, and transfer the account to the company when it is formed.
- The code repository is in an organisation owned by the company, and you are an owner.
- Hosting and database accounts are opened with a company email address.
- The domain is registered to the company, with renewal on a card you control.
- App store developer accounts are in the company's name.
- The Daraja, Paystack or other payment account is in the business's name.
- Passwords and API keys are in a password manager you can open.
On the registers
- The company is registered before you pay anyone to build, so that the code and the shares sit in it. If you cannot register yet, the contract is in your own name and assigns everything to the company once it exists.
- A trade mark search and application are planned for the name.
- Copyright registration is on the list for the point when the product has value.
A developer who is worth hiring will not object to any of this. Sharing the idea is the smaller risk. Signing nothing and holding none of the keys is the larger one, and this list removes it.
Key takeaways
- An idea in your head has no legal protection. Written code, a registered name and controlled accounts do.
- Under Kenya's Copyright Act, software is protected as a literary work from the moment it is written down, with no registration needed.
- The Act deems copyright in commissioned and employee work to pass to you, but the contract can change that, so say it in writing.
- An NDA protects information you share. An IP assignment clause decides who owns what gets built. You need the second more.
- Registering copyright with the Kenya Copyright Board is voluntary and gives you a certificate you can use as evidence.
- Whoever controls the repository, the domain and the payment account controls the product, whatever the paperwork says.
Frequently asked questions
- Should I make a developer sign an NDA before I describe my idea?
- Not for a first conversation. Many experienced developers will not sign one just to hear a pitch, and you can describe the problem and the customer without revealing anything sensitive. Use an NDA at the point where you share customer lists, pricing, financial details or the inner workings of the product.
- Do I have to register my software to own the copyright in Kenya?
- No. The Copyright Act says rights arise automatically once the work is in material form, and that not registering does not bar a claim. The Kenya Copyright Board describes registration as voluntary. A certificate is still useful, because it serves as evidence of ownership if there is a dispute.
- Can a developer reuse my code for another client?
- That depends on the contract. If it assigns all project work to your company (or to you, until the company exists) and has a confidentiality clause, they cannot reuse what was written for you. Developers normally keep their own earlier tools and general know-how, and open-source libraries stay under their own licences. List those exceptions in the contract.
- What if the developer already built the product and we have no contract?
- Fix it now, while relations are good. Ask them to sign a short written assignment covering everything built so far, transfer the repository and accounts to the company, or to you if there is no company yet, and pay any balance owed against that handover. The Act's default may already favour you, but a signed document removes the argument.
- Does a Kenyan trade mark protect my brand in other countries?
- No. The Kenya Industrial Property Institute explains that trade mark registration is territorial, so a Kenyan registration covers Kenya. If you plan to sell in Uganda, Nigeria or elsewhere, ask an IP agent about filing in those countries or through a regional or international system.
Sources
- Copyright Act (Cap. 130), sections 2, 22, 22A, 22D, 31, 32 and 33, Kenya Law (National Council for Law Reporting). Checked on 19 November 2026.
- Copyright Act, Chapter 130, Revised Edition 2022 (PDF), Kenya Copyright Board. Checked on 19 November 2026.
- Copyright Registration, Kenya Copyright Board. Checked on 19 November 2026.
- Trade Marks, Kenya Industrial Property Institute (KIPI). Checked on 19 November 2026.
- KIPI Frequently Asked Questions, Kenya Industrial Property Institute (KIPI). Checked on 19 November 2026.
