Agricultural Data Privacy Act of 2026
- Sponsor
- Sen. Ricketts, Pete [R-NE]
- Committees
- Agriculture, Nutrition, and Forestry Committee (primary)
- Last action
- Sep 23, 2026
Bottom line
This bill aims to empower agricultural producers by granting them ownership and control over their farm data, thereby regulating its commercial use and ensuring its security.
What it actually does
This bill establishes that agricultural producers own and control their agricultural data, prohibiting controllers and processors from selling this data without the producer's express written consent. It mandates that entities holding agricultural data implement reasonable security practices and grants the Attorney General exclusive authority to enforce the Act through injunctive relief and civil penalties.
Proponents argue
Proponents argue that the bill protects the economic value and autonomy of agricultural producers by ensuring they control who profits from their data, fostering trust in agricultural technology, and preventing unauthorized data monetization by third parties. They emphasize that this legislation addresses a critical gap in data privacy for a vital industry.
Opponents contend
Opponents might argue that the bill could stifle innovation in agricultural technology by imposing burdensome consent requirements on data processors, potentially limiting the development of valuable agronomic insights and services that rely on data aggregation and analysis. They may also raise concerns about the practicalities of obtaining consent for every data transaction and the potential for increased costs to be passed on to producers.
The bill is relatively short and clearly structured, making it accessible for an informed reader to understand its core provisions within a reasonable timeframe.
Section 2
Statement of Purpose
This section explicitly states that the Act's goal is to safeguard the economic value of agricultural data and the independence of agricultural producers. It aims to achieve this by regulating the sale of such data and ensuring its security through reasonable measures.
Supporters argue
Supporters argue that a clear statement of purpose helps guide interpretation and reinforces the bill's intent to protect farmers.
Critics contend
No specific opposition to a purpose statement itself, though underlying policy goals may be contested.
Tradeoffs
Balances the need for data utilization in agriculture with the protection of producer rights.
Section 3
Key Definitions
This section defines critical terms like "agricultural data" (including agronomic, climate, land, livestock, management, and sustainability data, with specific exclusions), "agricultural producer" (owner/lessee of farm/equipment), "controller" and "processor" (entities handling data), and "sale of agricultural data" (exchange for valuable consideration, with numerous exclusions). These definitions are foundational for the bill's scope.
Section 4
Producer Ownership and Control of Data
This section explicitly states that an agricultural producer is the owner and has control over the agricultural data originating from their farm, land, device, or equipment. It grants controllers and processors a nonexclusive right of control solely for providing services, maintaining equipment, or performing authorized data processing, but this right does not include the power to sell the data.
Section 5
Requirement for Express Written Consent for Data Sale
This section prohibits controllers or processors from selling agricultural data without the express written consent of the applicable agricultural producer. It further specifies that this consent must be obtained through a clear and conspicuous disclosure, separate from general terms of service or data use agreements.
Section 7
Data Security Practices
This section requires any controller or processor in possession of agricultural data to establish, implement, and maintain reasonable administrative, technical, and physical data security practices. These practices must be appropriate for the volume and nature of the data and designed to protect against unauthorized access, use, disclosure, modification, or loss, ensuring confidentiality, integrity, and accessibility.
Section 8
Enforcement by Attorney General
This section grants the Attorney General the authority to bring actions in U.S. District Courts against violators of the Act. Remedies include injunctive relief or a civil penalty of $1,000 for each separate violation, with penalties deposited into the Treasury's general fund. It explicitly states that this is the exclusive remedy and creates no new private cause of action.
This subsection lists ten specific scenarios that are explicitly not considered a "sale of agricultural data," and therefore do not require express written consent from the agricultural producer. These include disclosures to processors for service provision, disclosures to affiliates, disclosures directed by the producer, legally required disclosures, disclosures for safety/emissions/environmental compliance, publicly available information, transfers as part of mergers/acquisitions/bankruptcies, and disclosures necessary to detect fraud or cybersecurity threats.
Section 3(13)(B)
Why it matters:This is standard legislative practice to precisely define the scope of a term by listing what it does not include. However, the breadth of exclusions could be seen as significantly narrowing the practical application of the consent requirement.
Case for: Supporters argue these exclusions are necessary to allow for the normal functioning of agricultural technology services, internal business operations, legal compliance, and fraud prevention without imposing undue burdens or requiring consent for non-commercial data flows.
Case against: Critics might argue that some exclusions, particularly those for affiliates or transfers during mergers, could create pathways for data to be transferred or monetized without direct producer consent, potentially undermining the spirit of producer ownership.
Estimated impact: These exclusions significantly shape the practical scope of the "sale" definition, determining a large percentage of data transfers that will not require explicit producer consent.
This subsection clarifies that nothing in the Act impairs, supersedes, or otherwise affects the terms of any private contract that is in existence prior to the date of enactment of this Act.
Section 11(3)
Why it matters:This is a common legislative practice to avoid retroactive application of new laws to existing contractual obligations, ensuring legal stability. It's not necessarily evasive but can be easily missed.
Case for: Supporters argue this protects contractual certainty and avoids disrupting existing business relationships and investments made under prior legal frameworks.
Case against: Critics might argue that this provision could delay the full protective effects of the Act for agricultural producers who are locked into unfavorable data agreements signed before the bill's enactment, potentially for many years.
Estimated impact: This provision means that the Act's protections for agricultural data sales and consent requirements will only apply to new contracts or renewals, not to the potentially vast number of existing agreements.