← All articles
Blog

Data Licensing Agreement: Key Terms for AI Training Data

When an AI team licenses data, from a vendor, a publisher or a business that created it, the data licensing agreement decides what the team can actually do with it. A weak agreement can leave a model built on data the team isn't entitled to use. This guide sets out the key terms of a data licensing agreement for AI training, evaluation and retrieval, and the questions each side should ask. It is not legal advice, so always involve qualified lawyers.

Parties and authority

The agreement should identify the licensor and confirm that it has authority to grant the licence. For business records, authority usually sits with the company acting through its directors, or with an insolvency office-holder where the company is in an insolvency process.

Definition of the licensed data

Be precise:

  • the systems and record types included
  • the date ranges
  • the formats and delivery method
  • exclusions, such as HR, special category data or client-confidential material
  • any later updates or additional deliveries

A schedule describing the dataset, with a data dictionary, avoids disputes.

Permitted use

This is the heart of the agreement. Consider whether the licence covers:

  • training, fine-tuning and pre-training
  • evaluation and benchmarking
  • retrieval and grounding at run time
  • building RL environments (see RL environments)
  • annotation and the creation of derived datasets
  • internal use only, or use in commercial products
  • sharing with affiliates, contractors or cloud providers

Prohibited uses should be explicit, for example re-identification, resale of raw data, or use in particular sectors.

Exclusivity

Exclusive, non-exclusive, or exclusive within a field, time or territory. Exclusivity affects price and the licensor's freedom.

Term and termination

How long the licence lasts, and what happens at the end. A key question for AI is the status of models already trained. Most agreements state whether trained models may continue to be used after termination, and whether retraining or deletion is required.

Derived data and outputs

Who owns annotations, cleaned versions, embeddings and synthetic data generated from the licensed data? Can the licensee keep them after termination?

Privacy and data protection

  • Who is controller and who is processor, if personal data is involved?
  • What anonymisation or pseudonymisation is applied before transfer?
  • Obligations not to re-identify
  • Security measures
  • International transfer mechanisms
  • Breach notification

Warranties

Typical licensor warranties cover ownership or authority, lawful collection, and the absence of known infringement. Licensees may want warranties on accuracy or completeness, which licensors often limit. Realistic, specific warranties are better than broad ones that will be qualified away.

Indemnities and liability

Allocation of risk for third-party claims, such as copyright or privacy, with caps and exclusions.

Provenance and audit

Rights to receive provenance documentation, and to audit compliance on reasonable notice. See data provenance.

Payment

Fixed fee, staged payments, per-record pricing, revenue share or a combination. Define acceptance criteria for deliveries.

Confidentiality

Both the data and the commercial terms are usually confidential.

Deletion and return

What must be deleted at the end, how deletion is certified, and how this interacts with trained models.

A checklist

  • Authority confirmed
  • Dataset defined in a schedule
  • Permitted and prohibited uses listed
  • Exclusivity defined
  • Model and derived data rights after termination
  • Privacy measures and roles
  • Warranties, indemnities and caps
  • Audit and provenance
  • Payment and acceptance
  • Deletion and certification

Related reading

How Maevar helps

Maevar introduces record owners to vetted buyers. Before any introduction, we look at fit, who has authority, what restrictions apply and what the permitted use needs to cover. The buyer pays our introduction fee. The owner and the buyer agree the licence terms directly. Discuss your use case.

Special issues for AI

Memorisation and output

Models can sometimes reproduce training data. The agreement may need to address what happens if outputs closely reproduce licensed content, and what technical measures the licensee must take.

Benchmark publication

If the data is used for evaluation, can results be published? Can examples be quoted in papers?

Fine-tuned models for third parties

If the licensee fine-tunes models for its customers, does the licence extend to those customers' use?

Future models

Does the licence cover use in future model generations, or only those trained during the term?

Negotiation tips

  • Agree the permitted use before discussing price, because it drives value.
  • Use schedules for technical detail, so the main terms stay readable.
  • Tie payments to accepted deliveries.
  • Agree a process for removing records later, for example if a rights issue emerges.
  • Keep the provenance documentation as a contractual deliverable.

Governing law and disputes

Agree which law governs the contract and how disputes are resolved. Cross-border licences especially need to say this clearly.

FAQ

What is a data licensing agreement?

A contract granting permission to use data for defined purposes, while ownership stays with the licensor.

Does a licence cover models trained on the data?

Only if it says so. Check the termination and derived-data clauses carefully.

Can licensed data be shared with contractors?

Only where the agreement allows it, usually with flow-down obligations.

What happens if the licensor didn't have the rights?

Warranties and indemnities set out the remedies, but prevention through due diligence is better.

Do I need a lawyer?

Yes. Data licensing for AI raises complex IP and privacy issues.

Maevar privacy notice

21 October 2026

Who we are

Maevar is operated by Marcias Limited, company number SC653353. Marcias Limited is responsible for the personal information covered by this notice.

Registered office: 51 Watt Road, Hillington, Glasgow, G52 4RY, United Kingdom.

For privacy questions or requests, email hello@maevar.com.

This notice covers this website and enquiries sent to Maevar. Any proposed introduction of a record owner to a buyer, or any sale or licence they agree, requires a separate review of the relevant rights, privacy requirements and agreed terms.

Enquiries and information you provide

The enquiry fields help you prepare an email containing your work email address, organisation, task summary and any optional format or timing details. The draft is prepared on your device. The website does not submit or store it: you choose whether to open, review and send it using your email app. There is no file-upload facility.

Please provide only a non-confidential summary. Do not include datasets, personal records, passwords or other sensitive information.

When you send an email, we receive the message, your contact details and any other information you choose to include. Richard McKay handles enquiries. Authorised service providers and connected tools, including AI-assisted tools, may support the handling of correspondence.

Why we use your information

We use enquiry information to respond, understand your requirements, assess whether we can help and discuss relevant business opportunities. We rely on our legitimate interests in managing business enquiries and developing appropriate business relationships, while considering your rights and reasonable expectations.

We also have a legitimate interest in keeping the website and email services secure and reliable. Where we must retain or disclose information to meet a legal obligation, we rely on that obligation.

Website and email services

We use OpenAI's ChatGPT Sites to host this website, Cloudflare for website delivery, security and email routing, and Google Workspace to receive and manage email enquiries. These services process information needed to deliver and protect the website and email service. This can include IP addresses, browser information, access times and technical or security logs, as well as email information when you contact us.

Optional analytics is controlled separately from necessary hosting and security services. Cloudflare uses a bot-protection cookie called __cf_bm, which normally expires after 30 minutes of inactivity. More information is available in Cloudflare's cookie documentation.

Optional analytics and your choice

Google Analytics loads only after you accept analytics. Rejecting keeps optional analytics off.

We load Google Analytics only after you accept it. Rejecting does not stop you using this website or contacting us. Necessary hosting, delivery and security services continue to operate, including their technical logs.

With your permission, analytics measures page visits and limited website interactions. We use fixed page information without search queries or URL fragments. We do not send your name, email address, organisation, enquiry text, form answers or the contents of email-draft links to Analytics. Analytics is not a record of the contents of your enquiry.

The email preparation tool may record that an email draft was prepared, without any of its contents. This is an expression of interest only: the website cannot tell whether you send the email. It is not counted as a submitted enquiry.

No Google Ads, Meta or LinkedIn advertising tags are activated by these controls. Advertising storage, advertising user data and ad personalisation remain disabled. We do not use enhanced conversions or upload contact details to Analytics.

Your privacy choice is stored on this website in your browser for up to six months. If you accept analytics, Google Analytics may set first-party cookies named _ga and _ga_ followed by the property identifier. Our code sets a maximum cookie lifetime of six months; your browser may apply a shorter limit. Google processes the analytics information and may process it outside the UK. See Google’s privacy policy. Our Google Analytics property retains user-level and event-level data for two months, without restarting that retention period when you return. This setting does not limit how long Google retains standard aggregated reports. Optional Google data sharing, Google Signals, user-provided data collection, granular location and device collection, and advertising personalisation are switched off.

Use Cookie settings in the footer to change your choice. Withdrawing analytics consent stops new measurement and reloads the page into a no-analytics state, so save any unfinished enquiry first. It also removes the relevant first-party analytics cookies where the browser permits. This does not erase information already sent to Google. We do not replay interactions that happened before you consented.

Our service providers may process information outside the UK. Their published data-processing terms describe the applicable international-transfer safeguards, including recognised adequacy arrangements and contractual safeguards:

Contact hello@maevar.com if you would like further information about these arrangements.

How long we keep information

We review unsuccessful enquiries 12 months after the last substantive contact and delete them unless there is an ongoing business or legal reason to retain them. For example, information may still be needed for an active discussion, to meet a legal obligation, or to establish, exercise or defend legal claims. Where we retain information longer, we keep it only for as long as that reason applies.

Enquiries that lead to a business relationship and related contract records are kept according to the needs of that relationship and applicable legal requirements. The 12-month enquiry review period is not a guarantee that every provider's security log or backup is erased on the same date; those records are subject to the relevant service's retention and deletion arrangements.

Your rights and complaints

Depending on the circumstances, you may ask to access, correct or delete your personal information, restrict its use, or receive a portable copy. You may also object to processing based on legitimate interests. These rights are subject to applicable conditions and exceptions.

Email hello@maevar.com to make a request or raise a concern. You can also complain to the Information Commissioner's Office through ico.org.uk/make-a-complaint.

Changes to this notice

We will update this notice when our website or information-handling arrangements change. The date above identifies the version you are reading.