← All articles
Blog

Data Provenance for AI: Tracking Where Training Data Comes From

Data provenance is the documented history of data: where it came from, who created it, how it was collected, what rights apply and what has been done to it since. For AI teams, data provenance has moved from good practice to necessity. Regulators, customers and courts increasingly ask what a model was trained on. Without provenance, those questions can't be answered. This guide explains what data provenance means for AI, what to record and how to build it into sourcing.

Why data provenance matters for AI

Legal compliance

Copyright, privacy and contract law all depend on knowing a dataset's source. Data protection law requires a lawful basis for processing personal data. AI-specific regulation, such as the EU AI Act, includes obligations around training-data documentation for certain providers.

Licence management

Datasets often carry different terms. Provenance tells you which terms apply to which records.

Quality and debugging

When a model behaves unexpectedly, provenance helps trace the problem to particular sources.

Evaluation integrity

Knowing where test data came from helps prevent contamination, where test items leak into training data.

Trust

Customers buying AI products increasingly ask for assurances about data sources.

What to record

Source

The organisation or system the data came from, including the original systems for business records.

Creator and collection

Who created the data, when, how and for what original purpose.

Rights

The licence or legal basis, including the permitted uses, restrictions, term and exclusivity. See data licensing agreements.

Consent and notice

For personal data, what individuals were told and what lawful basis applies.

Authority

Who granted the licence and why they were entitled to.

Transformations

Cleaning, filtering, pseudonymisation, annotation, augmentation and merging, with versions and dates.

Lineage

Which datasets and models used the data.

Retention and deletion

Obligations and the dates by which they must be met.

Provenance for business records

Business records add particular provenance questions:

  • Which company created the records, and does it still exist? For closed companies, authority may rest with an office-holder.
  • Which systems and date ranges are included?
  • Were client-confidential or third-party materials excluded?
  • How were people pseudonymised, and is the mapping retained or destroyed?
  • Which links between records are original and which were reconstructed?

That last point matters for RL environments and evaluations, where inferred links could mislead graders. See RL environments.

Standards and practices

  • Datasheets for datasets and data cards: structured documentation of motivation, composition, collection, preprocessing, uses and maintenance.
  • Content credentials: cryptographic provenance for media, such as C2PA.
  • Data catalogues and lineage tools: to track datasets through pipelines.
  • Manifests and hashes: fix exactly which files were delivered under which licence.

Building provenance into sourcing

  1. Write the permitted use into the sourcing brief from the start.
  2. Verify the licensor's authority before collection.
  3. Record source systems, date ranges and exclusions at delivery.
  4. Hash and version every delivery.
  5. Log every transformation in the pipeline.
  6. Link datasets to the models trained or evaluated on them.
  7. Review provenance before each new use.

Common gaps

  • Datasets assembled from several sources with no record of which records came from where
  • Licences stored separately from the data they govern
  • Pseudonymisation applied without documenting the method
  • Evaluation sets reused without checking for overlap with training data
  • Undocumented scraping

How Maevar helps

Maevar introduces record owners to vetted buyers. Before any introduction, we look at fit, the authority to license, the systems and date ranges, exclusions and the permitted use. The buyer pays our introduction fee. The owner and the buyer agree terms, preparation and how personal details are handled, directly. Discuss your use case or read where to buy AI training data.

A minimal provenance record

For each delivery, keep at least:

Field Example content
Dataset ID and version Unique identifier and version number
Source organisation Licensor name and status
Authority Who signed and in what capacity
Systems and dates Source systems and date range
Exclusions Record types removed
Personal data handling Method and test results
Licence reference Agreement and permitted uses
Delivery manifest File list with hashes
Transformations Pipeline steps and versions
Downstream uses Models and evaluations using it

Who owns provenance

Provenance fails when nobody is responsible for it. Assign an owner for each dataset who keeps the record current, approves new uses and answers questions from legal, security and customers. Review the record whenever a dataset is used for something new.

Provenance and model documentation

Model cards and system documentation increasingly summarise training data sources. Good dataset provenance makes these summaries accurate and defensible, rather than vague statements written after the fact.

FAQ

What is data provenance?

The documented origin and history of data, including its source, rights and transformations.

Why is data provenance important in AI?

It supports legal compliance, licence management, debugging, evaluation integrity and customer trust.

What is the difference between provenance and lineage?

Lineage usually describes data's path through systems and pipelines. Provenance is broader and includes origin, rights and context.

How do I document provenance?

Use datasheets or data cards, manifests with hashes, licence records and transformation logs.

Does synthetic data need provenance?

Yes. Record the generator, its inputs and the settings used. See synthetic vs real data.

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.