I want to be direct about something that the precision agriculture industry rarely says plainly: when you connect your field data to a platform owned by an agrochemical company, the data about your soil, your yields, and your management practices may be used to inform that company's pricing, product development, and market positioning decisions. That's not a conspiracy theory — it's a business model.
This post is opinionated because the situation warrants it. I built Soilynx because I believed growers deserved a precision ag platform that isn't simultaneously an intelligence-gathering operation for a company selling them inputs. That belief comes with an obligation to be transparent about how the industry's data practices actually work — including where the ambiguity is, and what language you should look for (or demand) in any precision ag contract.
The conflict of interest that the industry rarely acknowledges
The major precision agriculture platforms — Climate FieldView (now under Bayer), Granular (acquired by Corteva), and others — were built in an era when agrochemical conglomerates were acquiring data companies at high valuations. The thesis was straightforward: access to field-level production data at scale creates pricing power, product targeting advantages, and market intelligence that independent data companies cannot replicate.
The OPEN AG DATA ALLIANCE (OADA) and the American Farm Bureau's Privacy and Security Principles for Farm Data (published in 2014, signed by major ag companies) were genuine attempts to create industry norms around data rights. Those principles state, among other things, that farmers own their data, that companies should not sell data to third parties without consent, and that data should be portable. These are commitments that participating companies have made publicly.
The problem is in the gap between stated principles and contract language. "You own your data" and "we may use your data for platform improvement" can coexist in the same document — and frequently do. The first statement sounds protective. The second clause, depending on how broadly "platform improvement" is defined, can permit nearly unlimited use of anonymized or aggregated field data to calibrate crop models, validate product recommendations, and generate market forecasts.
I'm not claiming this data use is inherently malicious. Crop model improvement benefits growers. Calibration against real-world field data makes recommendations more accurate. But there's a meaningful difference between "we use your data to make your recommendations better" and "we use your data to understand input demand patterns ahead of pricing decisions." The first is a service to the grower. The second is an extraction of value from the grower's operation. And the contract language that permits both is often identical.
What the contract clauses actually say — and what to look for
When reviewing a precision ag platform agreement, focus on these specific areas:
Data ownership language. Most agreements will state that you retain ownership of your farm data. This is a good baseline but not sufficient protection on its own. Ownership without exclusive control over use is a limited right. Ask: does "ownership" come with the right to prohibit specific uses of your data?
Aggregation and anonymization provisions. Many agreements permit the platform to aggregate and anonymize your data and use it for unspecified "business purposes." The argument is that anonymized aggregate data isn't "your" data anymore. This is technically true at scale — individual field attribution is removed. But aggregate Corn Belt yield data, soil test results, and input application rates from thousands of fields is enormously valuable for a company selling nitrogen fertilizer or crop protection products. Your individual data contributes to that intelligence even if you can't be identified in the aggregate.
Data portability and deletion rights. Can you export your complete data in a standard format (shapefile, GeoJSON, CSV) when you leave the platform? Is your data actually deleted from the company's servers when you request deletion, or is it retained for "historical research purposes"? These clauses vary significantly by platform and are rarely surfaced in sales conversations.
Third-party sharing permissions. Some agreements include explicit prohibitions on selling your data to third parties. Others permit sharing with "partners" and "affiliates" — categories that can be defined broadly enough to include the platform's parent company's other business units. If the platform is owned by a diversified agrochemical company, "affiliates" may include seed, fertilizer, and chemical divisions.
Research and model training use. Some contracts include language permitting use of customer data for training predictive models, calibrating crop response algorithms, or validating product recommendations. These uses are ambiguous in ways that matter: training a model on your yield data to improve a generic crop model is different from training a model on your yield data to optimize the marketing of a specific herbicide in your county. The contract language often doesn't distinguish between these uses.
Why independent platforms matter
I'll be transparent about our own position here, because Soilynx has a stake in this argument. We are an independent precision agriculture platform. We are not owned by an agrochemical company, a seed company, or an equipment manufacturer. We do not sell, share, or license your field data to any third party for any purpose. Our revenue comes from subscription fees for the prescription generation service — not from your data.
That independence has a practical consequence: our incentives are aligned with yours. We make money when you find the prescription service valuable enough to keep paying for. We have no secondary revenue stream that benefits from knowing which herbicide you're likely to buy next season or what your yield trends suggest about fertilizer demand in your county. Our business model does not create a conflict of interest between giving you accurate, unbiased agronomic recommendations and extracting intelligence from your operation.
I want to be careful not to overstate this. I'm not saying that agrochemical-owned platforms give intentionally biased recommendations. I have no evidence that any specific platform makes prescription decisions based on product marketing objectives rather than agronomic accuracy. What I am saying is that the structural incentive for conflict of interest exists, is not imaginary, and is worth considering when you evaluate where to store 10 years of your field's most sensitive production data.
What growers should demand from any precision ag contract
Regardless of which platform you use, these are the rights you should verify before connecting your data:
The right to export your complete field history — boundaries, soil tests, yield maps, prescription records — in open standard formats (GeoJSON, shapefiles, CSV/GeoTIFF) at any time. Not just what the platform chooses to surface in its export function, but all data you've uploaded or generated.
A clear and specific statement that your data will not be used to inform or train models that directly benefit the platform's parent company's product lines. "Platform improvement" is too broad. Ask for specifics on what that means.
Verified deletion: a contractual commitment that upon account closure, your data will be deleted from production systems within a defined timeframe (30-90 days is reasonable). Retention for "legal compliance" or "historical research" should be limited and explicitly defined.
A prohibition on aggregated data monetization that derives direct commercial value for the platform or its affiliates from your farm's production patterns without your explicit consent and compensation.
The OPEN AG DATA ALLIANCE framework is a useful starting point for evaluating these commitments. OADA defines a set of data principles around farmer control, transparency, and portability that align with what I'd call a minimum acceptable standard. Check whether the platform you're evaluating has signed onto OADA principles, and then verify that their actual contract language is consistent with those commitments — because these sometimes diverge.
A longer view
The data about your fields — the yield history, the soil test records, the drainage maps, the prescription responses — has value that compounds over time. A 10-year production history from a well-managed Iowa farm has more predictive power than a 2-year history. As that data ages and deepens, the intelligence embedded in it increases.
The company holding that data in 10 years will have advantages over you in certain negotiations. Not necessarily in nefarious ways — but the information asymmetry between a company with aggregate field intelligence across a large geography and an individual grower negotiating input prices or lease rates is real. The choices you make now about where your data lives and under what terms determine whether that asymmetry grows or stays contained.
I started Soilynx because I thought the data capture model that characterized the first generation of precision ag platforms was the wrong deal for growers. That's still my view. You're generating extraordinarily valuable information every time you plant, spray, and harvest. The software you use to manage that information should be working for you, not for someone trying to sell you something.
Read the contract. Ask the specific questions. Demand the portability and deletion rights that are yours to demand. The precision ag industry has made commitments on data ownership — hold them to it.