Who Owns Your Farm Data? Reading the Small Print

Most farm software contracts never say “we own your data.” They don’t need to. Ownership can stay with you on paper while the vendor holds a licence wide enough to do almost anything with the data, for as long as it likes, and you get back a pile of PDFs when you leave. On farm data ownership in the UK, ownership in the legal sense is usually the least important thing to check. What matters is the licence you grant, who the vendor can pass data to, and what you can take with you when you cancel.

This guide covers the clauses to find, the wording that should worry you, and the questions to put to a sales rep before you sign anything.

Why this matters more once AI is involved

A yield map on its own isn’t worth much. Eight seasons of yield maps from 600 hectares of Lincolnshire arable, joined to drilling dates, variety choices, fungicide timings and soil sampling, is a training dataset. Every AI agronomy feature you’re being sold, from variable-rate seeding recommendations to disease risk alerts, gets better when it’s fed data from farms like yours. The same goes for dairy. Activity collars, milk recording, foot-trimming records and treatment logs from a 220-cow herd are exactly what a lameness or fertility prediction model is trained on.

That isn’t a reason to refuse. Sharing data can get you better recommendations. It’s a reason to know what you’ve agreed to, because once your data has trained a model you can’t take it back out.

Where to find the clauses

The terms you need are rarely all in one document. Expect at least three:

• Terms of Service or Subscription Agreement: the licence grant, termination and export.
• Privacy Policy: only covers personal data, which is narrower than you’d think (more on that below).
• Data Processing Agreement or “Data Policy”: sometimes a separate page, sometimes buried in a help centre article.

Search each one (Ctrl+F on a laptop, or “Find in page” on your phone) for these words: licence, license, aggregate, anonymised, de-identified, affiliates, partners, perpetual, irrevocable, termination, export, delete. Between them those terms will find about 90% of what matters.

Clause 1: The licence grant

This is the clause that does the real work. Typical wording looks something like this:

You retain all ownership rights in Customer Data. You grant us a
worldwide, non-exclusive, royalty-free, perpetual and irrevocable
licence to use, copy, modify and create derivative works from
Customer Data for the purpose of providing and improving the Services.

Read it slowly. “You retain ownership” is reassuring. “Perpetual and irrevocable” means the licence carries on after you cancel and you can’t withdraw it. “Create derivative works” covers training a model. “Improving the Services” is broad enough to cover a new paid product built on your data.

What you want is a licence that is limited to providing the service to you, ends when the contract ends, and treats anything wider (product improvement, model training) as something you opt into separately. Some vendors offer exactly that if you ask. Plenty don’t, and you’ll only find out which kind you’re dealing with by asking.

Clause 2: Anonymised and aggregated resale

Almost every agricultural platform reserves the right to use “aggregated” or “anonymised” data, and many are free to sell or license it on. The clause usually reads:

We may compile, use and disclose aggregated and/or anonymised data
derived from Customer Data, and such data shall be owned by us.

The problem is that farm data is hard to anonymise properly. Strip out your name and your field boundaries still identify you. Combine a polygon, a postcode district and a crop type, and anyone with Rural Payments mapping or a satellite subscription can work out whose field it is. In a parish with three dairy units, “a 200 to 250 cow Holstein herd in TA3” is effectively a name.

Here’s how the wording compares:

A clause that sets a minimum pool size and states that geometry is removed is a vendor that has actually thought about this. A vague one may just be boilerplate, but you can’t tell which until you ask.

Clause 3: Sharing with affiliates and partners

Agricultural software is often owned by a business that sells you something else. Climate FieldView sits within Bayer, Cropwise within Syngenta, and xarvio within BASF. That isn’t sinister, but an “affiliates” clause in those contracts may cover a crop protection sales arm. Independent platforms such as Gatekeeper, Muddy Boots or Farmplan have their own integrations with agronomy firms, buyers and assurance schemes, and every connection you switch on is another route out for your data.

Look for:

• A definition of “affiliates”: is it the whole corporate group or just the software company?
• A named or linked list of sub-processors and partners: if it’s missing, ask for it.
• Whether sharing is opt-in per integration: connecting your grain merchant should not automatically connect your input supplier.

Machinery data is its own minefield. Telematics from a John Deere, CLAAS or New Holland tractor usually flows to the manufacturer’s cloud first (John Deere Operations Center, for example) under the manufacturer’s own terms, before your farm management software ever sees it. Reading the FMS contract isn’t enough. You’ve signed the OEM’s terms too, probably when the dealer set up the display.

Clause 4: Export on cancellation

This is the clause farmers regret skipping, because nobody needs it until they’re leaving. Three things to pin down:

1. The window. Common windows run from 30 to 90 days after termination, and then the data is deleted. Some contracts give no window at all.
2. The format. “You may download your data” can mean a CSV of field names and a stack of PDF reports. That isn’t the same as your data.
3. The cost. Some vendors charge for bulk export or for “data migration services”.

Worked example: the format trap

Take a 600-hectare arable business with eight seasons of records. Here’s what it should expect to get back, compared with what a weak export clause might deliver:

If you got the right-hand column, rebuilding those eight years in a new system means re-keying around 50 fields of spray records by hand. At four or five records per field per season, that’s somewhere near 2,000 entries. At a minute each, a farm secretary would spend more than 30 hours on it, and the yield maps can’t be recovered from images at all. Those yield maps are often the reason you bought precision kit in the first place.

On the livestock side, test it the same way. Can you get every animal’s lifetime record out of Herdwatch, or whichever herd app you use, as a spreadsheet with ear tag numbers, treatments, withdrawal dates and movements, in a form your next system or your vet can import? If the only answer is “you can print a report,” take that as a no.

The UK GDPR point most farmers miss

UK GDPR gives individuals a right to data portability, so you can demand your data in a machine-readable format. It only covers personal data about an identifiable person. If you farm as a sole trader, a good share of your records arguably counts as personal data, because the business is you. If you trade as a limited company or an LLP, your yield maps and herd records are business data and GDPR gives you very little.

In that case the contract is all you have. There’s no industry-wide statutory right to get your farm data back in a usable form. The EU’s Data Act (applying since September 2025) gives users rights over data from connected machinery, but it applies to products sold in the EU, and how far that reaches a UK farm depends on the manufacturer’s own choices. Don’t count on it.

Clause 5: Changes to terms

Look for “we may update these terms from time to time” and check what notice you get. Thirty days’ notice with a right to cancel and export is reasonable. “Continued use constitutes acceptance” with no notice means everything above can change next spring without you knowing.

Questions to put to the sales rep

Send these by email so the answers are in writing. A rep’s assurances on a yard visit aren’t worth much if the contract says otherwise.

1. “Is your licence to my data limited to providing the service to my business, and does it end when I cancel?”
2. “Is my data used to train AI or machine learning models? Can I opt out, and does opting out change my price or features?”
3. “What is your definition of anonymised or aggregated data? What’s the minimum number of farms in an aggregate, and do you remove field boundaries?”
4. “Do you sell or license aggregated data to third parties? Which types of organisation, e.g. input suppliers, insurers, buyers, researchers?”
5. “Which group companies and partners can see my data, and is each integration opt-in?”
6. “On cancellation, how many days do I have to export, in what file formats, and is there a charge?”
7. “Can I have a sample export of a demo farm now, before I sign?”
8. “How much notice will I get of changes to the data terms, and can I leave without penalty if I disagree?”

Question 7 tells you the most. A vendor that’s confident in its export will send a sample shapefile and CSV within a day. If you get a week of silence followed by a PDF, you’ve learned what you needed to.

When you’re comparing platforms on these points along with price and features, our farm AI software reviews and costs note where each vendor’s export and data-sharing terms stand, so you can rule out the weak ones before you spend time on a demo.

What to do with the subscriptions you already have

Pick the one system holding your most valuable history, usually the cropping records or the herd management app. Request a full export today, while nothing is going wrong. Open the files on a laptop, not a phone. Check whether you can see field boundaries as shapes, yield as numbers rather than colours, and treatments as rows with dates. Then save a copy somewhere the vendor doesn’t control, such as an external drive in the farm office or a business cloud account, and put a reminder in the diary to do it again after harvest.