If you pay a developer to build an app, you do not necessarily own its source code. You may be buying a custom build whose rights are assigned to your business, or a branded app that runs on a platform the developer continues to own and license. Your contract should say which. Payment, access to a working app, and ownership of its code are three different things.

This matters especially when you are starting a business in Nigeria from abroad. You need to know what your team can keep operating if you change developer, stop a monthly plan, or sell the business. The answer is not one word—mine or theirs—because code, app-store listings, brand assets, customer records, and service accounts can have different owners.

Do not assume so. Section 28 of Nigeria’s Copyright Act, 2022 says copyright initially vests in the author except as an agreement provides otherwise. Section 30 says an assignment of copyright or an exclusive licence has no effect unless it is in writing. The Act also has specific rules for certain work made for government bodies and collective works. Those details are why a founder should get the actual agreement reviewed, rather than rely on a generic internet rule.

If your business is incorporated abroad, the contract should identify which company receives the rights and which law governs the agreement. For a UK company, UK government guidance on commissioned works likewise explains that commissioning and paying for work does not, by itself, make the commissioner the first copyright owner. A lawyer familiar with the relevant jurisdictions can check the assignment and subcontractor terms before you sign.

Ask the developer: “Which parts are being created specifically for us, which parts existed before this project, and what rights will my company have in each?”

The six things people mean when they say “I own the app”

1. Source code and design files

Source code is what another team would need to inspect and change the software. Design files and technical documentation may be separate deliverables. If you are commissioning a custom build and expect to own these, the agreement should name them, state when rights transfer, address contributions from staff and subcontractors, and explain any exceptions for pre-existing or third-party components.

A copy of the code is not the same as copyright in it. The reverse is also a problem: a written assignment is difficult to use if the repository, build instructions, and credentials never reach you. Ask to see a working handover, not just a clause.

2. A licence to a platform

Some builders use an existing platform and configure branded apps for each client. The client can own its brand and operate its business without owning the platform’s source code. That can be a sensible model when you want to launch sooner and have the provider maintain the software. But the agreement should say what the licence allows, what the recurring fee covers, what changes are possible, and what happens if you leave.

Ask: “Can another developer run or modify this app without your platform?” If the answer is no, ask how you would export customer and transaction data, how much notice you get, and whether your store listing can be reused with replacement software.

3. Apple and Google store accounts

The app listing can sit in your own developer account even when a vendor builds and maintains the software. That gives your business direct control over the account relationship and lets you grant the builder a team role. Apple describes the Account Holder’s role; Google documents Play Console users and permissions.

If an app is already in the developer’s account, transfers are possible in some circumstances, but there are eligibility conditions and steps. Read Apple’s app-transfer guidance and Google’s app-transfer guidance before assuming the move will be instant. Set up the intended accounts early, using your business’s details where eligible, and invite the builder into them.

4. Customer data

“We own our customer data” should mean your business can access, use, export, and govern it under the applicable privacy rules. It does not mean customers lose their rights over personal information. Nigeria’s Data Protection Act, 2023 sets obligations for controllers and processors and rights for data subjects. If your company and customers are in different countries, ask a privacy adviser which additional rules apply.

Before launch, ask for a sample export of the records you actually need: customers, orders, payments and refunds, consent records, and support history. Check the format, frequency, access permissions, backup process, deletion rules, and what happens when the contract ends. Do not send real customer data in a test export if a small set of invented records will prove the workflow.

5. Domain, hosting, payments, and integrations

An app can depend on a domain, cloud hosting, payment provider, messaging service, analytics, maps, and email. Ask whose name is on each account, who pays each bill, and who can add or remove users. An account owned by the provider may be perfectly workable under a platform licence; the important point is to know the dependency and the exit plan.

6. Your brand and business name

Your logo, trading name, store listing, and customer relationships have value independent of the code. Name them explicitly in the agreement. Check that a contractor’s use of your brand is limited to delivering the service and that you can update your listing and customer support details through your own store accounts.

A short email to send before signing

You can send these questions to any app builder and compare the answers side by side:

  1. Build model: Is this custom software for us or a branded app on your existing platform? Which components are ours, yours, or third-party licensed?
  2. Code and files: Will we receive the source repository, design files, documentation, build instructions, and the right to have another team modify the app? At what milestone?
  3. Accounts: Whose details will be used for Apple, Google Play, the domain, hosting, payments, and other essential services? What access will our company have from day one?
  4. Data: Can we export our customer and transaction records in a usable format while the service is active and when it ends? Who handles backups and deletion?
  5. Ongoing cost: What does the setup fee cover, what is the monthly fee, and which third-party charges are extra?
  6. Exit: If we stop working together, what continues to work, what stops, what is delivered, and how long will the handover take?

Put the answers in the signed agreement or its attached scope. A reassuring sales call is useful, but it cannot replace a clear record of what each side agreed.

Test the exit plan before the first customer signs up

Imagine you change providers after twelve months. Could your business sign in to its store accounts? Could you export an order history and identify open refunds? Could a replacement team see enough documentation to understand the workflow? Could customers still reach support?

You do not need to plan an exit because you expect the relationship to fail. You need an exit plan because it makes day-to-day responsibilities clear now. It also exposes missing line items in a quote. Our guide to app development costs in Nigeria explains why the build model, maintenance, accounts, and first-year costs should be compared together.

How Venbrino’s ownership model works

Venbrino’s published FAQ says the founder owns the brand, business name, customer data, and app-store listings under their own accounts. Venbrino licenses and maintains the underlying platform through a monthly plan. This gives founders control of those business assets while Venbrino handles the core software and its upkeep.

When reviewing a Venbrino proposal, confirm the monthly amount, what it covers, account setup, data-export method, and what happens when the plan ends. Put the agreed details in writing so you and your team can plan with confidence. If you are still deciding whether customers want the service, validate the business idea before building an app.

Common questions

Can I own the app if the developer lives in Nigeria and I live abroad?

Yes, the parties can agree on rights across borders. The key is to identify the contracting business, the deliverables, the rights assigned or licensed, and the governing law in writing. Ask a qualified lawyer to review the terms that matter to your deal.

If I own the app-store account, do I own the source code?

No. The store account controls publishing and permissions. Source-code rights come from copyright law and the agreement with the people or company that created the code. Check both separately.

If a vendor says “you own your app,” what should I ask next?

Ask whether “own” refers to your brand, listing, customer records, custom code, or all of them. Then ask which parts are licensed, whether you can access the source code, and how you would move your data and operations to another provider.

Should my company own every technical account?

For a custom build, direct control of essential accounts can make handover easier. With a managed platform, the provider may operate infrastructure in its own accounts. In either case, document access, billing, security responsibilities, and an exit path. Your store listings and customer-facing identity deserve particular attention.