Software IP Ownership: Why You Must Own Your Code, Data and Accounts (and How to Make Sure You Do)

Photo: Free code MacBook laptop minimal by unknown, CC0. Cropped.

The painful stories behind this article

Almost every developer in Kenya has heard these from new clients:

• "Our previous developer registered the domain in his name, and now he wants KES 50,000 to transfer it."
• "The agency says the website is theirs and we only rent it. If we leave, it goes offline."
• "We paid for an app, but we don't have the source code, so nobody else can update it."
• "The WhatsApp Business account and Meta Business Manager are under the developer's personal account."
• "Our customer database is hosted on a server we can't access."

Each one is avoidable with a few lines in a contract and a disciplined handover.

Who owns the code by default?

As a general rule under copyright law in Kenya and in most countries, the person who creates a work is its first owner. Exceptions:

• Employees: work created by employees in the course of employment generally belongs to the employer, subject to their contract.
• Commissioned work by contractors: agencies and freelancers are usually not your employees, so without a written assignment the developer may keep the copyright and you may only have an implied right to use the work.

That's why a clear written assignment of intellectual property matters. This is general information, not legal advice. Consult a lawyer for contracts of significant value.

What exactly should you own?

The developer can be given access to your accounts as a user. They shouldn't be the owner.

What should your contract say?

1. IP assignment: all intellectual property in the deliverables created for you transfers to you on full payment.
2. Pre-existing materials: the developer keeps ownership of their existing tools, libraries and templates, but grants you a perpetual, royalty-free licence to use them as part of your system.
3. Open-source components: listed, with their licences respected.
4. Delivery of source code and documentation, plus repository access, on completion (or continuously during the project).
5. Accounts: all accounts created in your name or transferred to you.
6. Confidentiality and data protection: how your data and your customers' data are handled, in line with the Data Protection Act.
7. Handover and exit: what the developer must provide if the relationship ends, including reasonable transition support.

The "rented website" model

Some providers offer low upfront prices with a monthly fee, where you never own the site. If you leave, it disappears. This can suit a business that just needs a basic online presence quickly, but understand the trade-off. Over a few years you often pay more than a one-off build, and you can't take your site with you. Read the terms before signing. More on costs in how much a website costs in Kenya.

What about AI systems specifically?

AI projects add a few ownership questions:

• Prompts, workflows and configurations created for your business should be part of the deliverables you own.
• Knowledge bases built from your documents are your data.
• Conversation logs contain your customers' personal data, so you must control them.
• AI provider accounts should be in your name, or at least billed transparently and transferable.
• Model ownership: you won't own the underlying AI model (such as Claude or GPT), but you should own everything built around it for you.

Handover checklist at launch

• Source code in a repository you own, with full history
• Technical documentation: architecture, setup, deployment, integrations
• List of all accounts, with ownership confirmed and admin access for you
• Credentials delivered securely (password manager, not WhatsApp messages)
• List of third-party services, costs and renewal dates (domain, hosting, licences)
• Database backups and how to restore them
• A walkthrough session, recorded if possible
• Signed IP assignment or confirmation on final payment

How to fix it if you don't own your system today

1. Inventory: list every asset in the table above and who controls it.
2. Domain first: check the registrant details with your registrar. For .co.ke domains you can also contact KENIC-accredited registrars for guidance on transfers.
3. Request transfers in writing, politely, with a clear list and deadline.
4. Review your contract and payment records. A lawyer can advise if the provider refuses.
5. Plan a rebuild if needed. Sometimes it's faster to rebuild on accounts you control than to fight over an old system.

Ownership vs licensing of platforms

Not everything should be custom and owned. Using SaaS platforms, such as accounting software, a website builder or an email service, is fine, as long as you understand you're licensing them and your data can be exported. The key distinction: for anything built specifically for you (custom code, designs, workflows, integrations), you should own it. For platforms you subscribe to, you should own your account and your data. Problems arise when these are mixed up, for example when a developer builds your system inside their own platform account.

Maintenance doesn't require giving up ownership

Some providers argue that only they can maintain the system, so they must keep the code. That isn't true. You can own the code and still hire the original developer to maintain it under a support agreement. Ownership simply means you have the choice. Good maintenance agreements specify response times, what's included, and how the developer documents changes in your repository.

Why good developers welcome ownership clauses

Developers who are confident in their work don't need to hold clients hostage. They keep clients by doing good work and offering useful ongoing support. If a provider resists giving you ownership, treat it as a warning sign. See how to choose an AI development company.

Our policy

At Kavenacc, 100% code and IP ownership transfers to clients on final payment. Domains, hosting, WhatsApp, payment and AI accounts are set up in your name, and you receive documentation and a handover session. Our optional $997/month optimisation plan is genuinely optional: nothing stops working if you never take it. See how founder-led development works.

Next step

Take ten minutes today to check who owns your domain, hosting and WhatsApp Business account. If the answer isn't "us", start the transfer conversation now, while relations are good. If you're planning a new build, talk to us. Ownership is in every contract by default.

Related articles

Custom AI Software vs SaaS: Which Actually Saves You Money in 2026?Why Founder-Led Software Development Beats Anonymous AgenciesAI Security for SMBs: protect your data without a security team

Frequently asked questions

Explore Kavenacc services & pricing →