IP Clauses in a SaaS Agreement: Who Owns the Platform, the Data, the Feedback and the AI Outputs

By Prakhar Rai, Founder, My Legal Pal. Advocate, Bar Council of India. LL.B, NLSIU Bangalore. Master of Business Laws.

Quick answer: In a SaaS agreement the vendor keeps the platform and the customer keeps its own data. Everything in between, such as feedback, usage data, custom work and AI outputs, belongs to whoever the contract says it belongs to, so it has to be written down. For AI outputs, copyright law in the US, the EU and probably India protects work with real human creative input, not output the machine produced on its own. So the safest drafting does not rely on copyright alone. It says who may use the output, who may not, and whether the vendor can train on the customer’s data.

Key takeaways

  • Say it in the contract: the vendor owns the platform, the customer owns its data, and anything else is open until you decide it.
  • A SaaS customer gets a licence to use the service. It does not get the software.
  • Feedback, usage data, customisations and AI outputs are where disputes start, and most templates handle them in one line or not at all.
  • Pure AI output may have no copyright in the US and the EU. Courts and regulators look for human creative input.
  • Because of that, write the AI output clause as a contract right: who may use it, who may not, and what the vendor may do with it.
  • “No training on customer data” is not one rule. Training a base model, fine tuning, testing and search over customer files are different things, so name each one.
  • The vendor’s promise to defend the customer against IP claims has limits. The limits are the clause.

If you run a SaaS company, the intellectual property clause is the part of the contract you will remember when something goes wrong. A customer asks who owns the report your tool produced. A big client wants to know if you train your model on its files. A buyer in due diligence asks who owns the code a contractor wrote. This guide goes through each IP question in plain language, with sample wording you can compare. It is written from the vendor’s side, and it points to the customer’s view where the two differ. Our guide to AI vendor contracts covers the buyer’s side in more depth.

My Legal Pal is an international team of contract lawyers with US law experience. We are not a US law firm, and we are not a local firm in every country mentioned here. This is general information, and a lawyer qualified where you operate should check your final contract.

The clause that causes the most surprise is usually the one nobody negotiated. A founder sends a contract that says “customer owns all outputs”, then learns months later that the same contract lets the customer take the vendor’s own templates with it.

Who owns the platform, and what does the customer get?

The vendor owns it. The customer gets a licence to use it. A SaaS customer does not buy software. It buys access for a period of time, under conditions. The contract should say that clearly, so that nothing the customer does with the service can be read as a transfer of ownership.

The clause has two halves: a grant that is narrow, and a reservation that is wide.

Position Sample wording
Vendor favourable “We grant you a limited, non-exclusive, non-transferable right to access and use the Service for your internal business purposes during the term. We and our licensors keep all rights not expressly granted.”
Balanced “We grant you a non-exclusive right to access and use the Service, and for your affiliates to use it under your account. All rights in the Service, including updates and improvements, stay with us.”
Customer favourable “The Supplier grants the Customer a worldwide, non-exclusive right to use the Service. The Supplier will not use the Customer’s name or marks without consent.”

What to check: the licence should cover the people who need it (staff, contractors, affiliates), say what it does not cover (copying, reverse engineering, reselling), and say that the vendor keeps all rights it did not give away. If you also ship a downloadable app or a desktop tool, add a software licence or EULA for that part.

Who owns customer data?

The customer does. Almost every SaaS buyer will insist on this, and it costs the vendor little. What the vendor needs is permission to use that data to run the service.

Position Sample wording
Vendor favourable “You own your Customer Data. You give us a licence to host, copy, process and display it as needed to provide and support the Service.”
Balanced “As between the parties, the Customer owns all Customer Data. The Supplier may use Customer Data only to provide the Service and as this agreement allows.”
Customer favourable “The Supplier has no right to Customer Data except to provide the Service to the Customer. It may not sell, share or use Customer Data for any other purpose.”

Two things matter here. First, define “Customer Data” so it covers what users upload and what the service creates from it, otherwise the next sections will be fought over. Second, if the data includes personal data, the contract needs a data processing agreement. If it includes US health data, you may also need a business associate agreement, which we explain in our BAA guide for healthtech SaaS.

Can the vendor use usage data and analytics?

Usually yes, if the contract says so and the data is stripped of customer detail. Usage data means how people use the product: logins, features used, performance and error logs. Vendors use it to improve the product and to publish benchmarks.

Position Sample wording
Vendor favourable “We may collect and use usage data and aggregated, de-identified data derived from the Service for any lawful purpose, including improving our products.”
Balanced “We may use usage data and aggregated data that does not identify you or any individual to operate, secure and improve the Service and to create benchmarks.”
Customer favourable “The Supplier may use usage statistics only to operate and improve the Service for its customers. It may not use Customer Data, even in aggregate, for any other purpose.”

The words “aggregated” and “de-identified” do the work here, so define them. A clause that lets a vendor own “derived data” can reach further than the vendor meant, and a buyer’s lawyer will spot that.

Who owns feedback?

The vendor usually gets the right to use it, but a customer does not hand over ownership of its own business ideas. Feedback is a suggestion or comment about the product. Most vendors want a free licence to use it without asking, so they are not blocked if a customer later says “that was my idea”.

Position Sample wording
Vendor favourable “You assign to us all rights in any feedback you give about the Service.”
Balanced “You give us a perpetual, worldwide, royalty-free licence to use feedback without restriction. Feedback does not include your Customer Data or confidential information.”
Customer favourable “The Supplier may use feedback to improve the Service. This does not give the Supplier any right in the Customer’s confidential information or Customer Data.”

The balanced version is the one most buyers accept. The fix that matters is the carve-out: feedback must not include the customer’s data or secrets.

Who owns customisations and work built for one customer?

It depends on whether the work reuses your product. If you build a custom integration, a report or a feature for one customer, you need to decide what is yours (your platform, tools and know how) and what is theirs (anything that is truly specific to them).

Position Sample wording
Vendor favourable “We own all customisations and deliverables. You have a licence to use them with the Service while you have a subscription.”
Balanced “We keep our pre-existing materials and any general improvements. You own deliverables made only for you, and give us a licence to the parts built into the Service.”
Customer favourable “The Customer owns all deliverables created under this agreement. The Supplier keeps only its pre-existing materials.”

If a contractor or freelancer wrote part of your platform, your own ownership depends on having a signed assignment from them. Our IP assignment guide explains that step, and it is the first thing buyers check in due diligence.

Who owns AI outputs?

The contract decides who may use them. Copyright law may not give anyone ownership. This is the part that most guides skip. The word “output” means what your AI feature produces for a user: text, images, code, summaries, predictions.

Whether an output has copyright at all depends on the country. This table is a summary of what official sources say today.

Country Where the law stands Source type
United States Copyright needs a human author. The Copyright Office says prompts alone do not give enough control, so purely AI generated material is not protected. A human can claim copyright in their own contribution, such as creative editing, or in the selection and arrangement of AI material. A US appeals court held in March 2025 that a work needs a human author, and it left the question of AI assisted works open US Copyright Office report (Jan 2025), D.C. Circuit decision (March 2025)
United Kingdom The 1988 Act says that for a computer-generated work, the author is the person who made the arrangements needed to create it. In March 2026 the government proposed removing that specific protection, while keeping copyright for works made with AI help. That is a proposal, not law yet CDPA 1988 s.9(3), UK government report (18 March 2026)
European Union No EU wide rule on AI outputs. Courts require a work to be the author’s own intellectual creation, so output with little human input is unlikely to be protected. The AI Act does not deal with this question European Parliament research briefing (2025)
India The Copyright Act, 1957 says that for a computer-generated work, the author is the person who causes the work to be created. We have not found a court decision that settles how this applies to generative AI Copyright Act, 1957 s.2(d)(vi)

Three things follow for your contract.

  1. Do not promise copyright you may not have. A clause saying “the customer owns all copyright in the outputs” may promise something that does not exist in some countries.
  2. Write it as a contract right. Say who may use the output, who may not, and what the vendor can do with it.
  3. Do not promise uniqueness. Two users who give a similar prompt can get similar outputs. Say so, or you may be blamed when a customer finds a near copy.
Position Sample wording
Vendor favourable “As between us, you may use Outputs for your business. We give no promise that Outputs are unique or protected by any intellectual property right, and we may generate similar Outputs for others.”
Balanced “As between the parties, the Customer owns the Outputs it generates, to the extent any right exists. The Supplier will not use a Customer’s Outputs for any other customer. Outputs may not be unique.”
Customer favourable “The Customer owns all Outputs. The Supplier assigns to the Customer all right it has in them, and will not use, copy or disclose Outputs except to provide the Service.”

Note the words “to the extent any right exists.” They cover you if the law says there is nothing to own. If your product helps people write code or build apps, our post on who owns a vibe coded app explains the customer’s side of the same problem.

Can the vendor train its AI on customer data?

Only if the contract says so, and a clear “no” is not as simple as it sounds. “Training” can mean several different things, and a short clause that says “no training” can miss most of them.

Activity What it is Questions to settle
Base model training Using customer data to build or improve a model used for everyone Allowed at all? With what data?
Fine tuning Adjusting a model for one customer Does the tuned model belong to the vendor or the customer?
Testing and safety review Checking quality, abuse and errors Can staff read customer data? Who?
Retrieval Searching the customer’s files to answer a question Are copies or embeddings stored? Where? For how long?
De-identified data Data with names and identifiers removed Does the vendor own it? Can it be used for training?

Two traps to watch. First, a clause that allows “de-identified data” use can be a back door for training even if another clause says “no training”. Second, deleting the customer’s files at the end of the contract may not remove what a model has already learned from them. Say what happens to the model, not only the files.

Position Sample wording
Vendor favourable “We may use Customer Data, in de-identified form, to develop and improve our models and services.”
Balanced “We will not use Customer Data to train models that are made available to others unless you opt in. We may use it to provide, secure and support the Service for you.”
Customer favourable “The Supplier will not use Customer Data or Outputs to train, tune or evaluate any model, and will not retain them after termination, except as the law requires.”

Whichever way you go, say it once and match it everywhere. Contradictions between your terms, your privacy policy and your sales deck are what customers find.

The law on training data is also moving. For the Indian position, including a government proposal for a licensing model, see our guide to AI training and copyright in India.

What if an output infringes someone else’s rights?

Then the question is who pays, and the answer sits in your indemnity. Most SaaS contracts have the vendor promise to defend the customer if a third party says the service infringes its IP. For AI features, buyers now ask for the same promise for outputs, and vendors need to decide how far to go.

Position What it looks like
Vendor favourable Covers the platform only. Outputs are excluded. Customer is responsible for how it uses them
Balanced Covers the platform and outputs used as intended, with carve-outs below
Customer favourable Covers the platform and outputs, with a high or uncapped limit

The standard carve-outs are the clause’s real content. A vendor usually does not cover claims caused by: the customer’s data or prompts, changes the customer made, use outside the contract, use together with other products, or use after the vendor offered a fix. The usual remedies are to get the customer the right to keep using the service, replace or change it so it no longer infringes, or end the contract and refund prepaid fees. Our guide to the indemnity clause explains how these promises work, and the liability cap that sits beside them decides how much you could actually pay.

What if the platform uses open source or outside code?

Say so, and say who is responsible. If your product includes open source or third party components, a customer may ask you to promise that none of them force you to release your own code or that you comply with each licence. Make that promise only after you have checked your own code base. A short statement that you comply with the licences in use, and that nothing in the service requires you to disclose customer code, is usually enough.

What happens to IP when the contract ends?

The licence ends, the customer takes its data, and each side keeps what it owned. The clause should say four things.

  1. The customer’s right to use the platform stops.
  2. The customer can export its data for a set period, in a stated format.
  3. You delete the data afterwards, including from backups on a stated schedule.
  4. Clauses that must survive, such as confidentiality, feedback and your ownership of the platform, are listed by name.

If you promise deletion, check that your product can actually do it. A promise your systems cannot keep becomes a breach.

The clauses side by side

Topic Vendor favourable Balanced Customer favourable
Platform Narrow licence, wide reservation Licence covers affiliates Licence plus limits on vendor use of marks
Customer data Customer owns, wide licence to vendor Use only to provide the service No other use at all
Usage data Vendor may use for any lawful purpose Aggregated and de-identified use Statistics only
Feedback Assigned to vendor Free licence, carve-outs Licence for product improvement only
Customisations Vendor owns Split by pre-existing and new Customer owns deliverables
AI outputs Use only, no promise of rights Owned “to the extent any right exists” Customer owns, vendor assigns
Training Allowed if de-identified Opt in only Never
IP indemnity Platform only Platform and outputs, with carve-outs Both, high cap

Mistakes that cost SaaS companies money

Mistake Why it hurts Fix
Template says the customer “owns everything” Customer may claim your own tools and templates Separate pre-existing materials from deliverables
No definition of Customer Data Every other clause becomes arguable Define it once, clearly
Promising copyright in AI outputs May promise something that does not exist Say “to the extent any right exists”
“No training” with a de-identified data clause The second clause undoes the first Read the clauses together
Feedback assigned, with no carve-out Could capture a customer’s trade secrets Exclude Customer Data and confidential information
Contractor code with no assignment You may not own part of your product Get signed assignments before launch
Terms, privacy policy and sales deck disagree A customer can hold you to the most generous version Use one position everywhere

A checklist before you send or sign

  1. Does the contract say, in one place, who owns the platform, the data, feedback, customisations and outputs?
  2. Is “Customer Data” defined, and does it include what the service creates from it?
  3. Do you hold signed assignments from everyone who wrote your code?
  4. Does the usage data clause say “aggregated” and “de-identified” and define both?
  5. Does the feedback clause exclude the customer’s data and secrets?
  6. Does the AI output clause avoid promising copyright, and avoid promising uniqueness?
  7. Does the training clause name each use: base model, fine tuning, testing, retrieval?
  8. Do your terms, privacy policy and sales material agree?
  9. Are the indemnity carve-outs and remedies written out, with the cap?
  10. Does the exit clause cover export, deletion, backups and what survives?

Get a SaaS agreement that settles this

If you are writing or reviewing a SaaS agreement and want these clauses set up for your product, our team can help. See our SaaS agreement drafting service, or speak to our technology lawyers for tech startups, SaaS and AI platforms.

Quick answers

Who owns the software in a SaaS agreement? The vendor. The customer gets a licence to use the service for the term, not ownership of the software.

Does the customer own its data in a SaaS agreement? Yes, in nearly every SaaS contract. The vendor gets a limited licence to use that data to provide the service.

Can a SaaS vendor use customer data to improve its product? Only if the contract allows it. Most contracts allow use of aggregated, de-identified usage data and not of identifiable customer data.

Who owns AI generated outputs in a SaaS agreement? Whoever the contract says, as between the two parties. Copyright law may give no one ownership of purely AI generated material, so the contract should say who may use the output and avoid promising copyright.

Is AI output protected by copyright? Not when it is purely machine made, in the US and the EU. The US Copyright Office says prompts alone do not give enough human control. Work with real human creative input can be protected for that input.

Can a SaaS company train AI on customer data? Only if the contract allows it. A clear “no” should name each use, because training, fine tuning, testing and retrieval are different things.

Does the vendor owe an IP indemnity for AI outputs? Only if the contract says so. Buyers increasingly ask for it, and vendors usually agree with limits such as carve-outs for the customer’s data and prompts.

Who owns customer feedback? Usually the vendor gets a free right to use it. The customer keeps its own data and confidential information, so the clause should exclude them.


About the author. Prakhar Rai is an Attorney enrolled with the Bar Council of India and the founder of My Legal Pal. He holds an LL.B from NLSIU Bangalore and a Master of Business Laws, and works on contract drafting, review and disputes for founders and businesses across borders. Full profile

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? Please solve:Captcha