Skip to content

The legal essentials of buying and selling a mobile app

Transfer 7 min read
The legal essentials of buying and selling a mobile app

In short

The legal essentials of buying or selling a mobile app – IP and asset transfer, app-store account moves, the agreement, and what to verify before you settle. General information, not legal advice.

Buying or selling a mobile app is mostly an exercise in getting the boring details right. The technology is the easy part. What decides whether the deal is clean is ownership, the transfer mechanics, and a written agreement that says exactly what changes hands. This guide walks through the legal essentials for small app deals so you know what to check and what to expect.

A note before you start: this is general information, not legal advice. Rules on intellectual property, contracts and data protection differ across the US, UK and EU, and every deal has its own facts. Use this to prepare sensible questions, then have a qualified lawyer review your specific agreement.

Most app deals are asset sales, not company sales

Apps sold on a curated platform such as Indiemaker are almost always structured as asset sales rather than share or equity sales. That distinction matters. In an asset sale you buy the components that make the app work – the code, the intellectual property, the domains – without taking on the seller's company and its liabilities, such as debts, tax obligations or open disputes. You get the parts you want and leave the baggage behind.

The assets to identify and name in the agreement usually include:

  • The app's source code, in full, with build files and any related repositories.
  • Intellectual property assignments from everyone who contributed to development. This confirms the seller actually owns the IP and can pass those rights to you.
  • Third-party licences and consents, including any open-source components or external service providers, so the transfer does not breach someone else's terms.
  • User data: existing accounts, reviews and subscriber information, handled in line with the applicable data protection rules in your jurisdiction. Preserving this data cleanly matters for both continuity and compliance.
  • Payment or merchant integrations tied to the app's revenue, where these can be transferred.
  • Related domains, websites and social accounts.

If you want a fuller view of what "transferable" really means before you commit, see what makes a digital project transferable.

Do the commercial homework before the legal step

By the time you reach the paperwork you should already understand what you are buying. Look hard at the numbers and the market position: how many users are active, what the revenue actually is, how growth is trending, what the reviews say, and how the app compares with its competitors. App-store dashboards give you the headline figures; deeper user-level analytics tools can fill in the rest. This is standard due diligence, and it is the work that protects your money. Our guide to due diligence on a sub-$500k digital business covers the process in detail.

Confirm the seller actually owns what they are selling

The most common way an app deal goes wrong is a seller who cannot fully prove ownership. Verify it deliberately. Ask who built the app. If the seller is not the original developer, ask for a copy of the development agreement so you can check the IP and licensing position for yourself. Look for outstanding legal issues, third-party code, or licence terms that could complicate the transfer.

IP and third-party consents. Intellectual property is where ownership gets murky. Make sure the seller provides proper IP assignments from anyone who contributed – employees, freelancers or other third parties. If the app relies on licensed third-party code, confirm that the relevant consents allow the licence to move to you. Missing assignments are a genuine risk, not a formality, and this is exactly the sort of point to put in front of a lawyer.

Warranties and indemnities. A sound agreement sets out who is responsible for what, and when. Warranties are the seller's statements that the app is as described. Indemnities allocate responsibility if something turns out not to be true. Typically the seller carries responsibility for issues up to the closing date and the buyer takes over from that point. The precise wording, limits and time periods are worth negotiating carefully.

How the money moves: settled in full at closing

Here is the part that surprises people coming from other corners of the acquisitions world. Indiemaker deals are clean, outright transfers settled in full at closing by cash or wire. There are no instalment plans, no earn-outs, no seller financing and no revenue-share arrangements. The buyer pays the agreed price and takes full ownership; the seller receives the full amount and walks away without a continuing financial stake in the app. That simplicity is deliberate. It removes the disputes that drag on when payment is spread over time or tied to future performance.

To protect both sides during that exchange, Indiemaker uses escrow via escrow.com. The escrow provider, a neutral third party, holds the funds while the assets are transferred and releases them once both sides have met their obligations. Handling the money and the handover manually, with no escrow, is far riskier and we would not recommend it. If you want to understand where deals most often stall, the payment step is where micro-deals tend to break down.

Agree the terms and write down exactly what is included

Settle on a fair price based on the app's performance and realistic growth potential. Then make the agreement unambiguous about what is included. List every asset: the source code, the user data, the domain names, the associated IP, and any payment or merchant integrations that form part of the package. Include practical items such as API keys, admin accounts and credentials. Vagueness here is what causes arguments after closing, so be thorough. A written asset inventory turns a nervous handover into a routine one, as we cover in the asset inventory that turns a scary handover into a boring one.

The app-store transfer itself

Moving the app between developer accounts follows the platform's own process, and the good news is that you do not need to take over the seller's entire developer account to receive the app. The steps below use Apple's iOS process as the example; Google Play and other platforms work along broadly similar lines, each with their own official guidance.

On iOS the flow is roughly:

  • The seller initiates the app transfer request in their developer account, providing your Apple ID and Team ID.
  • You accept the request in your own account, complete the required app information and agree to the terms.
  • The transfer usually completes within about two business days, during which the app shows as "Processing App Transfer".

Apple's own documentation on transferring an app is the authoritative reference, and Google publishes an equivalent guide for the Play Console.

What moves with the app. The app keeps its reviews and ratings, and users keep access to future updates. The Bundle ID transfers unchanged, and the associated App ID moves to your account. The app code and assets themselves are exchanged directly between you and the seller, so make sure that handover is part of the agreement.

What does not move. The seller keeps their earnings, payout and bulk-export reports. Historic analytics in the original account are not carried over. Promo codes generated before the transfer stay with the seller. Test groups, permissions and integrated service links do not transfer and need to be recreated on your side.

After the transfer the app opens under your developer account while the seller keeps their original account, and it continues to work normally for users throughout. Plan the first weeks deliberately; the first 30 days after you have bought it sets out what to prioritise once the keys are yours.

In short

A mobile app deal is not complicated, but it is unforgiving of loose ends. Confirm ownership, get the IP assignments and consents in order, list every asset in the agreement, settle in full through escrow, and follow the platform's transfer process to the letter. Do those things and the handover becomes routine rather than stressful.

One last reminder: none of the above is legal advice. Intellectual property, contract and data protection rules vary across the US, UK and EU, so have a qualified lawyer review your agreement before you sign.