App Development Contract: Code Ownership, NDAs and Payment Terms

Printed contract next to a smartphone and laptop on a desk

Updated October 2026 by the Cliffex team. Prices are in USD. This is general information for buyers, not legal advice.

Short answer: an app development contract should define the work, acceptance criteria, payment terms, confidentiality duties and handover. If you expect to own the custom deliverables, it should expressly assign the relevant rights to you and identify any licensed components. Paying for development is not the same as securing every right or receiving usable source code. At Cliffex, source code and IP ownership are transferred to you, your written quote is your price unless the scope changes, and 30 days of support after launch is included. Confirm the detailed transfer and support terms in your agreement.

This guide is for founders and business owners who have picked a developer, or are down to a shortlist, and want to know what the contract should say before they sign. It covers code ownership, NDAs, payments, acceptance and handover, and ends with a list of red flags. Laws differ by country and state, so ask a lawyer familiar with the governing law and any cross-border issues to review the final document.

FURTHER READING

> Freelance App Developers vs Development Companies (2026)

> App Maintenance and Support: What It Covers and Costs (2026)

> Cliffex Pricing: Websites, Apps and Maintenance

What should an app development contract include?

Some contracts are one document. Others split into a master services agreement with the legal terms and a statement of work (SOW) for each project. Either way, identify the legal parties and authorized signers, and specify which document takes priority if the terms conflict. Check that these clauses are covered and say something specific.

ClauseWhat it should sayRed flag
Scope of workPlatforms (iOS, Android, web), user roles, screens or features, integrations and what is excluded“Build a mobile app as discussed”
AcceptanceHow you test each deliverable, how long you have, and what counts as doneWork is accepted automatically when it is delivered
Price and paymentsTotal or rates, what each payment is tied to, and when invoices are dueLarge advance payments with no clear deliverables, safeguards or refund terms
Change requestsNew work is described, priced and approved in writing before it startsNo change process, or verbal approval is enough
IP assignmentWhich custom deliverables and rights are assigned, by whom, and when the transfer takes effectA licence-only arrangement where you expected ownership, with no explanation of the limits
Pre-existing and open-source codeA licence for any developer tools built into your app, and a list of open-source components and their licencesSilence about third-party code
ConfidentialityWhat is confidential, who on the team is bound, and what happens to your data at the endCovers only the client, or never mentions subcontractors
Accounts and handoverApp store, hosting, domain and third-party accounts in your name; source code delivered to a repository you controlDeveloper-owned accounts with no transfer plan
Support and warrantySupport scope, defect definitions, any free-remediation period, response commitments and later chargesNo period stated, or “support” left undefined
TerminationNotice period, payment for work done, and delivery of unfinished work and codeYou lose access to the code if you end the project
Data protectionWho handles personal data, security duties, and any agreement the law requires, such as a BAA where the developer acts as a HIPAA business associate handling PHIReal customer data used in testing with no terms
Liability and claimsLiability limits, exclusions, insurance where relevant, and who handles third-party IP claimsLiability or indemnity terms neither side understands
Law and disputesWhich law applies and how disagreements are resolvedA jurisdiction you never agreed to

Who owns the code when you hire an app developer?

Lines of program code on a computer monitor

Under US law, copyright initially belongs to the author or authors, subject to rules such as work made for hire (17 U.S.C. § 201). The US Copyright Office’s Circular 30 describes two work-for-hire routes: employee work within the scope of employment, and specially commissioned work in specified categories with a signed written agreement. Hiring a contractor or labelling the contract “work made for hire” does not by itself satisfy those conditions.

For a US copyright assignment, 17 U.S.C. § 204 generally requires a written transfer signed by the rights owner or their authorized agent; transfers by operation of law are an exception. Have counsel check the assignment wording, covered deliverables and effective date. Ask the developer to confirm that it has the necessary rights from employees and subcontractors. List custom source code, designs, content and documentation separately from pre-existing or third-party material.

What you can’t own outright

  • Open-source libraries. Apps are usually built with them. You use them under their own licences, which can carry conditions. Ask for a component and licence inventory, including required notices, source-disclosure obligations where applicable, and any use or distribution limits.
  • The developer’s existing tools. An agency may reuse internal code across projects. That is normal. Identify that code and negotiate the rights and access needed to operate, maintain and move the app, including work by a replacement developer. Check duration, transferability, source access and any continuing fees; do not assume all embedded tools can be licensed on the same terms.
  • Third-party services. Payment providers, maps, messaging and AI APIs are accounts you subscribe to under their terms, not code you own.

An agreement may make assignment conditional on payment. Confirm the exact trigger and your rights to use and receive work paid for if the project ends early. A repository copy and a copyright assignment are separate requirements; neither automatically supplies the other.

Do you need an NDA before talking to an app developer?

A non-disclosure agreement creates duties governing confidential information; it cannot guarantee that disclosure or misuse will never happen. An NDA alone does not assign ownership of deliverables or authorize sharing personal data. Put appropriate confidentiality terms in place before sharing sensitive non-public details. For an introductory call, keep the discussion general and avoid live customer records or production credentials.

Choose the NDA around who is disclosing information. The UK Intellectual Property Office guidance distinguishes one-way and mutual NDAs; mutual terms fit when both sides disclose confidential material. Have the wording checked for the applicable law. A useful NDA covers:

  • A clear definition of confidential information, such as designs, data, code, credentials and business plans.
  • Standard exclusions for information that is already public, already known, or developed independently.
  • Permitted use: the information is used only to quote for or build your project.
  • The whole team: permitted recipients are bound by appropriate confidentiality duties, with responsibility for subcontractors made clear.
  • The end of the work: return or deletion of information, any legally required retention or backup exceptions, and continued protection of retained copies. Revoke access and rotate shared secrets rather than relying on deletion alone.
  • A stated duration suited to the information, plus rules for legally compelled disclosures and any protected disclosures the law permits.

Whatever the paperwork says, share the minimum. Prefer synthetic test data, use separate accounts with limited permissions, and plan how access will be removed. An NDA is not a substitute for a data-processing agreement, security controls or a required BAA. HHS explains the HIPAA business-associate rules. Cliffex signs a BAA when its work involves PHI, before access; the agreement alone does not establish HIPAA compliance.

How should payments work in an app development contract?

For a fixed-price project, agreed milestones can tie payments to defined progress. Hourly work may instead be billed periodically for recorded hours, and either model can include a deposit. Specify the charging basis, invoice triggers and review process rather than assuming every payment follows acceptance. The contract should answer these questions:

QuestionWhat a clear answer looks like
What triggers each invoice?A stated deposit, accepted deliverable or billing period, with the evidence required for that invoice
Is the price fixed or an estimate?A fixed price for an agreed scope, or hourly rates with a cap you approve before it is exceeded
What costs are outside the fee?Hosting, domains, paid plugins, app store accounts and API usage are listed, with who pays them
How are changes priced?A written change request with cost and timing, approved before work starts
What happens if you stop?Notice, charges for completed and unfinished work, treatment of advances, and the rights/access you receive

For context on our own terms: Cliffex gives a written quote before work starts, and that quote is your price unless the scope changes. Apps start from $4,000. The first-version tier is $4,000 to $10,000, a business app $10,000 to $20,000, and larger platforms $20,000 and up. Third-party costs such as hosting, domains, paid plugins and app store developer accounts are paid by you directly, with account ownership and administrative access confirmed separately. See the pricing page for scope and exclusions. Our fixed price vs time and materials guide explains how the billing models differ.

How do scope, acceptance and change requests protect you?

Scope disputes start with a gap between what the client pictured and what the document says. If the scope lists “user login”, decide before signing whether that includes social login, password reset, two-factor authentication and an admin screen to manage users. Write acceptance criteria in plain terms, for example “a customer can book, pay and receive a confirmation email on iPhone and Android”.

The change process should distinguish a new requirement from a failure to meet agreed acceptance criteria. Define how defects are reported, corrected and retested, and when corrections are included in the price or billed separately. This matters especially for hourly work, where a fixed-price remediation rule cannot simply be assumed. Agree the review period, handling of non-response and acceptance evidence before work starts.

What should you get at handover?

People reviewing a printed document together at a table with a laptop

Ownership on paper means little if you cannot run, change or move the app. The contract should list what you receive:

  • Source code in a repository you own, such as a GitHub or GitLab account in your company’s name, with the agreed project history and documentation. Check that another authorized team can access and build it.
  • App store accounts in your name. Publish under your own Apple and Google developer accounts. For organization enrollment, Apple generally requires a legal entity, binding authority and a D-U-N-S number (government entities are exempt from the number). Choose the appropriate account type and start verification early.
  • Hosting, domain and service accounts owned by you, with the developer added as a user you can remove.
  • Build and deployment notes, environment configuration, backup/restore instructions and secure access to signing or release credentials. Verify that an authorized replacement team can build and deploy; keep secrets out of the repository.
  • Design files and any written content created for the project.
  • A list of third-party components and their licences.

Security belongs in the same conversation. Our mobile app security checklist covers what to test before release.

What about support and maintenance after launch?

The contract should define the support start date, included tasks, defect criteria, exclusions and any no-charge remediation period. Do not assume “support” means unlimited changes or an uptime guarantee. Agree how work outside that scope is priced. Ask for the rate, whether you get an estimate before work starts, and how quickly urgent issues are handled.

Every Cliffex launch includes 30 days of support. After that, maintenance is billed at $25 to $49 an hour, with an estimate first. Our guide to app maintenance and support explains what that work covers.

Red flags in an app development contract

  • You get a licence, not ownership, of code written specifically for you, with no reason given.
  • The developer publishes the app under their own store account and there is no written plan to transfer it.
  • Source code is delivered “on request” or only after a final payment that has no defined trigger.
  • The scope is a paragraph and the fixed price is attached to it.
  • There is no termination clause, or ending the project means losing the work you paid for.
  • Confidentiality binds only you, or the developer can use subcontractors without telling you.

If you are still choosing between a freelancer and a company, our freelancer vs development company comparison covers continuity and questions to ask either provider. Both freelancers and agencies need appropriate rights and handover terms.

How to review an app development contract before you sign

  1. Read the scope as if you were the developer. Could someone build exactly what you want from it alone? If not, add detail.
  2. Find the assignment clause. Check that it assigns the custom work to you and licenses anything pre-existing that ships inside the app.
  3. Map every payment to its agreed trigger: deposit, deliverable or recorded hours. Confirm what evidence you receive and any spending cap or approval requirement.
  4. List every account the app needs and confirm the account holder, administrator access and transfer or continuity plan.
  5. Read the termination and support clauses together, since they decide what happens if things go wrong.
  6. Have a lawyer review it, especially if you handle health, financial or children’s data.

To budget before you talk to anyone, try the app cost calculator. When you are ready for a written quote, send us your project details, or read more about our mobile app development services.

Frequently asked questions

Can I legally write my own app development contract?

You can prepare a draft, but whether it forms an enforceable agreement depends on the applicable law, the parties and the terms. Do not treat a template as complete for your project. Have a qualified lawyer check the assignment, payment, liability, data and termination provisions before signing.

Is a contract written with AI legal?

Using AI to draft a document does not establish that it is valid or suitable. Signatures alone do not resolve issues such as authority, lawful terms or jurisdiction-specific requirements. AI text can mix legal systems or omit important conditions. Have the final agreement reviewed, and do not upload confidential project or customer information to an unapproved tool.

What should a freelance app developer contract include?

The same clauses as an agency contract, with attention to the rights of everyone contributing and a continuity plan if a key person becomes unavailable. An agency is also an external supplier. Agree repository access and a delivery cadence early, rather than leaving source-code access until the end.

Should an app project use a one-way or mutual NDA?

Use one-way terms when only one party is disclosing confidential information, or mutual terms when both are. If more than two parties need access, document the permitted recipients and their duties. The information flow matters more than the label; a mutual NDA is not automatically the best fit.

Are an NDA and a confidentiality agreement the same?

In practice the names are used for the same kind of document. Development contracts often include a confidentiality clause, so a separate NDA may only be needed for talks before the contract is signed.

What are red flags in an NDA?

No exclusions for public or independently developed information, a definition so broad it covers general skills and know-how, obligations that bind only one side when both are sharing, and no rule for returning or deleting data at the end.

Who owns the app if the developer goes out of business?

Check whether the assignment took effect, whether any payment or other conditions remain, and whether you hold usable code, documentation and account access. These improve continuity but do not guarantee an outcome in insolvency. If a developer closes or becomes insolvent, ask counsel about your rights and any third-party licences before transferring the work to a new team.