Vannus / Catalog / Climate FieldView

Climate FieldView

Vannus has not established which model this vendor runs, and does not infer one. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.

Determination
Partly evidenced — the words this record quotes carry only part of this finding.
The quote names Bayer CropScience LLC or one of a list of Licensed Affiliates, depending on the Service Territory of the customer's service address; the affiliates' names, and which entity contracts in which territory, Bayer CropScience LLC included, rest on text this record does not quote.
climate.com · read 2026-09-15
read from terms of service
Contracting entity
Bayer CropScience LLC or a Licensed Affiliate, depending on the Service Territory
Jurisdiction
Not established
Governing law
Depends on where the user is located (Terms of Service §6.3, last updated June 2026): in the U.S., “the laws of the State of Missouri and the laws of the United States applicable therein”; in Canada, “the laws and courts of the Province of Alberta and the federal laws of Canada applicable therein”; in Argentina, “the laws of Argentina”; in Brazil, “Brazilian laws”. For a user in Mexico the clause names only a forum, the courts of Mexico City, and no governing law. Elsewhere in the American Continent the United States terms apply. Read 22 September 2026.
US corporate control
Not established the rule
Depends on
The agreement is under a governing law that depends on where the customer is based.

Farm management system integrating satellite imagery, soil sensors, and weather data for data-driven planting, spraying, and harvest decisions

agriculture, farm-management, analytics
Model provenance

Not established. The finding this entry held rested on a page from a site whose terms we read as forbidding a scripted read, so it is not published here.

Who controls it
US corporate controlPartly evidenced — the quote names Bayer CropScience LLC or one of a list of Licensed Affiliates, depending on the Service Territory of the customer's service address; the affiliates' names, and which entity contracts in which territory, Bayer CropScience LLC included, rest on text this record does not quote · clause last confirmed 17 Sep 2026; its host's terms forbid automated re-reading, so it is not re-checked
Contracting entityBayer CropScience LLC or a Licensed Affiliate, depending on the Service Territory
Governing lawDepends on where the user is located (Terms of Service §6.3, last updated June 2026): in the U.S., “the laws of the State of Missouri and the laws of the United States applicable therein”; in Canada, “the laws and courts of the Province of Alberta and the federal laws of Canada applicable therein”; in Argentina, “the laws of Argentina”; in Brazil, “Brazilian laws”. For a user in Mexico the clause names only a forum, the courts of Mexico City, and no governing law. Elsewhere in the American Continent the United States terms apply. Read 22 September 2026.
Trains on your dataYes, unless you opt out — on the vendor's default plan

This page gives the finding and links the document it comes from. The AI Subprocessor Jurisdiction Report ($299) quotes the clause this finding rests on, and the clause for each other vendor in your stack where the report can quote one, in one dated document you can hand to an auditor.

Training and retention posture varies by plan. What we publish above describes the vendor’s default plan; enterprise, team and API agreements frequently differ, often materially, and a contract can override the published default entirely. Check your own plan and contract before relying on this row.

On U.S. CLOUD Act reach specifically: the statute reaches a provider subject to U.S. jurisdiction over data in its possession, custody or control. Corporate control is a strong indicator of that and it is what we can evidence from published documents — but it is not the whole test. A company founded outside the U.S. can still contract through a U.S. entity or run substantial U.S. operations. Treat this as a starting point for your own review, not a legal determination, and take advice on anything that matters.

Record history

This is the history of our record of this vendor: when we first recorded it; each time one of these changed: the determination sentence, the contracting entity, its country, the governing law, the US-control finding, what the answer depends on, the note beside the finding, or the cited document; and each time the vendor's document was read again and none of them changed. A change only in capitals, punctuation or spacing is not a line, and neither is a first document title. A line names what changed and does not repeat what those fields said before; the determination above says what they say now. Where the determination sentence itself changed, the line shows the earlier sentence too, marked as before, with why it changed. The automated re-check's latest result is not a line here; it is printed beside the clause above. A change here may be the vendor changing its document or us correcting our reading of it, and a line says which only where the record shows it; otherwise it says the cause is not established. Each line is today's reading of the record as it stood on that date. A reading we later found its citation does not carry was withdrawn, and is not repeated here. This history as data.

Cite this record
Climate FieldView: “Partly evidenced — the words this record quotes carry only part of this finding.”
Vannus, https://vannus.co/tool/climate-fieldview
climate.com · read 2026-09-15

How you may reuse this record

How this entry is set

Vannus records, from the vendor's own published documents, the legal entity a customer contracts with, the country that entity sits in, and the governing law of its terms — and whether the vendor runs its own model or resells someone else's. Each finding is quoted to its source and dated, or marked not disclosed where the vendor publishes nothing. No paid placement on a record, in the catalog or in search — affiliate status is walled off from the record, enforced by a test in the build. See the methodology →

Related tools we record
Visit Climate FieldView ↗ Check your whole stack →
Vannus (PRAXIS AI LLC) · entry as of the latest catalog build · all 376 tools · MCP for assistants
Work here and think we got something wrong? Corrections and right of reply → — free, no account, and we publish your response next to our entry.