Effective Date: September 9, 2026
Version: 6
Posted at: https://hydrodata.long103.io/privacy.html
This document is both a privacy policy and a data-use agreement. You must affirmatively agree to it (by checking the box or tapping Agree) before creating an account or using HydroData. Browsing this page, or continued use after a material change, is not consent.
By checking the box or tapping Agree, you acknowledge that you have read this Privacy Policy and Data Use Agreement, you understand it, and you agree to it.
This HydroData Privacy Policy and Data Use Agreement is issued by Adaptive Resources, Inc., doing business as Longitude 103 (“Longitude 103,” “we,” “us,” or “our”).
Longitude 103 is a legal name of Adaptive Resources, Inc. Adaptive Resources, Inc. is the contracting party. Longitude 103 is not a separate corporation.
We operate HydroData, a water application for groundwater districts, surface water districts, and other water management entities (including municipalities), in many states, and related websites and mobile applications. Nebraska Natural Resources Districts are an example, not the exclusive customer type. We may share information with affiliates as described in Section 9.
This Privacy Policy and Data Use Agreement applies to personal information and agricultural data collected by Longitude 103 through:
This document is written for HydroData, including the HydroData API. It is not a general policy for long103.com or for other Longitude 103 products unless those products post a direct link to this same document.
HydroData is a water application for groundwater districts, surface water districts, and other water management entities (including municipalities), in many states. Nebraska Natural Resources Districts are an example, not the exclusive customer type.
District-customer accounts (institutional users at groundwater districts, surface water districts, and other water management entities, including municipalities) use HydroData to manage operational water, pond, meter, and related data.
Producer add-on accounts use ProducerConnect, an extension or add-on to HydroData, for farmers, ranchers, and others — including private farmers — who have data in those districts or other water management entities, reporting on those or other operations, and for users with no affiliation, in many states and not only Nebraska. Private farmers may use HydroData features through that add-on or through an unaffiliated ProducerConnect account. A ProducerConnect user may have a district affiliation, or may use ProducerConnect without one. District affiliation is not required to create a ProducerConnect account. Unaffiliated use is permitted and is not required as a condition of ProducerConnect use.
Data entered or generated in ProducerConnect is stored in the HydroData API. That storage is part of providing the HydroData / ProducerConnect service (and/or affiliate or processor use to operate the service). It is not a sale of agricultural data.
Producer-facing terms for ProducerConnect — including ProducerConnect-specific user experience and optional One Red enrollment — are in the ProducerConnect Privacy Policy and Data Use Agreement, not in this HydroData document.
This Privacy Policy and Data Use Agreement applies to HydroData, including the API.
Who agrees to which document. Groundwater districts, surface water districts, and other water management entities (including municipalities) that use HydroData agree to this Privacy Policy and to the HydroData Software Agreement. ProducerConnect users do not agree to the HydroData Software Agreement. Only those district and other water-management-entity customers do. ProducerConnect users agree to the ProducerConnect Privacy Policy and Data Use Agreement. ProducerConnect data is still stored in the HydroData API as described in this policy; that storage does not make a ProducerConnect user a party to the HydroData Software Agreement.
If a ProducerConnect user is in, or affiliated with, your water district or other water management entity, that entity can view that user’s records stored in the HydroData API. Affiliation includes this visibility. There is no opt-out of that viewing while the producer remains in or affiliated with that entity (no checkbox, toggle, or “hide from district” path). Unaffiliated ProducerConnect accounts do not grant district viewing unless and until the user affiliates with a district or other water management entity. Only that affiliated entity can view the records; other districts and other municipalities cannot. A municipality can view a producer’s records only if that municipality is the water management entity the producer is in or affiliated with. The producer-facing statement of this rule is in the ProducerConnect Privacy Policy; the district-customer statement is in Section 9.3. This is not a sale.
We distinguish two categories. They can overlap.
"Personal information" (called "personal data" in our prior statement) means information that relates to, is capable of being associated with, describes, or could be linked to, an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, by reference to an identifier such as a name, an identification number, location data, or an online identifier.
Nebraska adopted the Agricultural Data Privacy Act (Legislative Bill 525). In that Act, "agricultural data" means any of the following that is collected, produced, or generated in Nebraska and is linked or reasonably linked to an identified or reasonably identifiable agricultural producer: agronomic data, climate and weather data, land data, livestock data, management data, and sustainability data.
The Act defines "sustainability data" to include information regarding greenhouse-gas emissions, carbon sequestration, and water-quality impact, and any other environmental or conservation practice used to verify sustainability claims. The Act defines "land data" to include physical attributes of a parcel, including soils, topography, elevation, watershed and drainage, and geospatial information. The Act defines "agricultural producer" as the person that is the owner, lessee, or renter of the farm, livestock, land, device, or equipment from which agricultural data originates.
HydroData water, pond, meter, location, and related operational data can be agricultural data when those two statutory conditions are met (Nebraska origin and linkage to an identifiable agricultural producer). Producer-originated data stored in the HydroData API, including data entered or generated in ProducerConnect, can be agricultural data when those same conditions are met — including records of a ProducerConnect user who has no district affiliation. Agricultural-data status is Nebraska-origin plus producer-linked; it is not determined by district membership. Unaffiliated or out-of-state users may still have personal information. Agricultural-data rules still apply when the Act’s definition is met, including for users with no district affiliation. Not every record in HydroData is automatically agricultural data. For example, the Act excludes aggregated data, derived data, and data made available to the general public by a state agency as defined in Nebraska section 84-901. Data collected, produced, or generated outside Nebraska, or data that cannot reasonably be linked to an identifiable agricultural producer, is not "agricultural data" under the Act.
Where this document refers to "agricultural data," it means agricultural data as defined in the Act. If a record is both personal information and agricultural data, both sets of rules in this document apply.
Under Section 4 of the Agricultural Data Privacy Act:
If you are an agricultural producer and we collect, store, or use your agricultural data in connection with HydroData, we act as a controller or processor of that data. You remain the owner. We have only the limited nonexclusive right described above, and only to operate HydroData, maintain the service and related equipment, and process the data as you authorize in this agreement or in a later written instruction.
Beginning January 1, 2027, Nebraska law requires every new contract or agreement involving the collection or processing of agricultural data in Nebraska to contain a specific provision that sale is prohibited without the producer's express written consent. We include that provision now, so that this agreement is ready to serve as that contract language for agreements entered into on or after January 1, 2027, and so that the same rule is clear today.
Specific provision. Longitude 103, as a controller or processor, is prohibited from engaging in the sale of agricultural data collected or processed under this agreement without the express written consent of the agricultural producer.
No waiver. Any provision that waives or limits the requirements of the Agricultural Data Privacy Act is contrary to public policy and is void and unenforceable. Nothing in this document is a waiver of those requirements.
We do not sell your personal information to any third party.
We do not sell agricultural data. We do not exchange agricultural data for monetary or other valuable consideration to a third party.
The Act defines "sale of agricultural data" narrowly: the exchange of agricultural data for monetary or other valuable consideration by a controller or processor to a third party. The Act also lists disclosures that are not a sale, including disclosure to a processor; use by a processor authorized by a controller; disclosure, transfer, or use for the purpose of providing a service to an agricultural producer; disclosure to an affiliate; disclosure that you expressly direct, initiate, or authorize in writing to a designated third party; disclosures required by law; certain safety, emissions, or environmental compliance disclosures; certain public disclosures you made without restricting the audience; certain merger, acquisition, bankruptcy, or similar asset transfers; and disclosures reasonably necessary to detect, prevent, or respond to fraud, abuse, cybersecurity threats, illegal conduct, data-integrity issues, or equipment misuse.
Sharing that falls within those statutory exclusions is not a "sale" under the Act. We describe our actual sharing in Section 9. We do not treat all sharing as a sale.
If we ever proposed to sell agricultural data, we would not rely on this document. Nebraska law requires express written consent obtained through a clear and conspicuous disclosure that is separate from the primary terms of service or data-use agreement. That consent would be presented on a separate screen or form, not buried in this policy. We have no such separate sale-consent module in place today because we do not sell agricultural data.
To the extent permitted by applicable law, the categories of personal information we may collect include:
We may also generate limited inferences (for example, usage patterns used to improve the service) from the information above. We do not treat inferences as a hidden extra category of sale.
Depending on what you enter, upload, connect, or generate, HydroData may collect, store, or process:
When that information is collected, produced, or generated in Nebraska and is linked or reasonably linked to an identifiable agricultural producer, it may be agricultural data under the Act (including as sustainability data, land data, management data, or another listed category). We treat it accordingly. Producer-facing detail for ProducerConnect data is in the ProducerConnect Privacy Policy and Data Use Agreement.
We collect information:
We collect limited first-party operational analytics so we can operate, secure, and improve HydroData. These events are stored in our own systems (not a third-party product-analytics vendor). Event names are limited to things such as screen views, feature use, and error boundaries. Event properties are small operational fields (for example, which product surface you were using). We do not put passwords, tokens, message bodies, notes, GPS traces, or secret query strings in those properties.
A raw analytics event is linked to your account and, when you are working in an organization, to that organization. We use those events to understand whether the product is working, which features are used, and where errors occur. We also create aggregated rollups (daily and similar summaries) that count events, users, and sessions. Rollups are used for operations views. They are not a sale of personal information or agricultural data.
We use personal information and agricultural data to:
We will not use your personal information in a manner that is inconsistent with the purpose of its original collection unless we have given you additional notice and you have consented.
For agricultural data, our use is limited to the nonexclusive right described in Section 4: providing the HydroData service, maintaining equipment, and processing you authorize. That right does not include sale.
Support work may give us incidental access to data on your systems. If that data includes personal information or agricultural data, this agreement -- and, for agricultural data, the Act -- still apply. We do not treat support access as a way around these rules.
We may use information in HydroData — including personal information and, where the Act applies, agricultural data — to train, fine-tune, evaluate, and improve custom artificial-intelligence models and related features that we develop or operate for HydroData and related Longitude 103 products.
Training may use identifiable records and de-identified, aggregated, or derived data, depending on the model and the task. Where the Act’s definitions of aggregated data or derived data are met, those outputs are not “agricultural data” under the Act. Identifiable agricultural data used in training remains subject to Sections 4 through 6.
Those models may be used to provide features to other HydroData customers. When a model trained in part on information from one customer is later used to serve another customer, we do not disclose that first customer’s raw records (for example, another customer does not receive your meter readings, maps, account files, or producer names as a download or as a quoted data feed through the model). The training use is for our product purposes: building and improving the model so it can help operate and improve HydroData for customers generally.
This use is not a sale of agricultural data. Under the Act, use of agricultural data for the purpose of providing a service — including product and quality improvement and internal algorithm training — is among the uses the Act treats as part of providing a service and excludes from “sale.” We do not treat model training by itself as an exchange of your agricultural data for monetary or other valuable consideration to a third party.
What this section does not authorize. This section does not authorize us to: - sell your agricultural data or personal information; - give another customer a copy of your identifiable HydroData records; - use your data to train a third party’s general-purpose foundation model outside our control, unless we tell you in a material update to this agreement and you agree again; or - replace the separate consent required for Nebraska One Red or any other grant-program sharing.
Scope of training data. This Section 8.1 covers (a) HydroData district-customer operational data and (b) ProducerConnect data stored in the HydroData API. ProducerConnect users agree to the ProducerConnect Privacy Policy and Data Use Agreement, not to the HydroData Software Agreement. The same training use is stated in the ProducerConnect Privacy Policy so producers see it in the notice they agree to.
No opt-out. There is no opt-out of this AI-training use. There is no checkbox, toggle, or “exclude my data from training” path while you use HydroData under this agreement. By checking the box or tapping Agree, you authorize the training use described in this Section 8.1. If you do not agree, do not create an account and do not use HydroData.
We may offer a Model Context Protocol (MCP) service, or a similar authenticated interface, so that you can connect a third-party AI tool you choose — for example Grok, Cursor, or another OpenAI-compatible client — to help you analyze your own HydroData data.
To use that feature, you must authenticate and grant that connection access to the data you authorize. The third-party AI then acts at your direction on the data you make available through that authenticated connection. That access is producer- or customer-directed sharing for your own analysis. It is not a sale by us of agricultural data to the AI vendor, and it is not the same as the training use described above.
You are responsible for the third-party AI tool you choose, including its terms, security, and how it retains prompts or outputs. We do not control those tools. Revoking authentication ends new access through that connection; it may not erase copies the third-party tool already stored under its own terms.
We share information only as described here. Sharing is not automatically a sale. A sale, under the Act, is an exchange of agricultural data for monetary or other valuable consideration to a third party. The following disclosures are the kinds of sharing we actually do or may do. Where a disclosure matches a statutory exclusion from "sale," we say so.
We may disclose personal information and agricultural data to service providers that process it on our behalf to operate HydroData -- for example information-technology hosts, payment processors, and support tools. They are required by contract to keep the information confidential and secure and to use it only for the purpose for which we provided it.
Under the Act, disclosure or transfer of agricultural data to a processor by a controller, and use by a processor authorized by a controller, are excluded from "sale."
We use and may disclose information as needed to provide HydroData to you -- to store your data (including ProducerConnect data stored in the HydroData API), display it in the application, support the software, and maintain related systems. Storing ProducerConnect data in the HydroData API is providing the service. It is not a sale. District reporting is not a sale.
District viewing of affiliated producer records is stated in Section 9.3. It is not a sale. District reporting is not a sale.
Under the Act, disclosure, transfer, or use of agricultural data for the purpose of a controller or processor providing a service to an agricultural producer is excluded from "sale." The Act defines "service" to include services used to maintain, diagnose, repair, support, secure, improve, or provide equipment, software, device, technology, product, or service to the producer, including product and quality improvement and internal algorithm training.
If a ProducerConnect user is in, or affiliated with, your water district or other water management entity, that entity can view that user’s records stored in the HydroData API. Affiliation includes this visibility. There is no opt-out of that viewing while the producer remains in or affiliated with that entity. There is no checkbox, toggle, or “hide from district” path. This document does not give a producer a way to remain “in” a district or other affiliated water management entity and opt out of that viewing.
“District” (and “your district”) in this Section 9.3 means the groundwater district, surface water district, municipality, or other water management entity the producer is in or affiliated with, in any state where we operate. Nebraska Natural Resources Districts are an example, not the exclusive type.
This is not a sale of agricultural data. It is disclosure because the producer is in, or affiliated with, that district or other water management entity. The producer is told up front in the ProducerConnect Privacy Policy. We treat it as sharing of the kind the Act excludes from “sale” when it is producer-directed or is part of providing a service to the producer.
Scope. Only that affiliated district or other water management entity can view the records. A district-customer HydroData account may view records of producers who are in or affiliated with that entity. It may not, by reason of this Section 9.3, view records of producers in other districts or entities, or of ProducerConnect users who have no such affiliation. Other districts cannot. Unaffiliated ProducerConnect signup is permitted. Those accounts do not grant district viewing unless and until the user affiliates with a district or other water management entity. If they later join or affiliate with one, that entity can then view their records.
This Section 9.3 does not cover optional government grant programs such as Nebraska One Red. Those programs, if offered, are documented separately.
We may disclose personal information and agricultural data to our affiliates and subsidiaries for the business purposes described in this document, and we may transfer information to places where Adaptive Resources, Inc. d/b/a Longitude 103 conducts business. Same-platform storage of ProducerConnect data in the HydroData API is providing the service (and/or affiliate or processor use). It is not a sale, and it is not a separate transfer to a different “Longitude 103, Inc.” corporation.
Under the Act, disclosure, transfer, or use of agricultural data to an affiliate of the controller or processor is excluded from "sale."
If you ask us in writing to send your information to a person you designate -- for example an advisor, lender, insurer, cooperative, input provider, or another digital platform -- we may do so.
Under the Act, a disclosure that is expressly directed, initiated, or authorized in writing by an agricultural producer to a designated third party is excluded from "sale."
We may disclose information as required by law or legal process; to respond to a lawful request of a public authority; to enforce or protect our rights; when disclosure is necessary or appropriate to prevent physical harm or financial loss as permitted by law; or in connection with an investigation of suspected or actual illegal activity.
Under the Act, disclosures required by state or federal law, regulation, subpoena, investigative demand, or court order, and disclosures reasonably necessary to detect, prevent, or respond to fraud, abuse, cybersecurity threats, illegal conduct, data-integrity issues, or equipment misuse, are excluded from "sale."
We may disclose information in a merger, acquisition, consolidation, divestiture, bankruptcy, or similar transaction involving part or all of Longitude 103. We will seek appropriate protection for information in those transactions. After such a transfer, you may contact the receiving entity about its use of the information.
Under the Act, certain disclosures of agricultural data as an asset in a proposed or actual merger, acquisition, bankruptcy, or transaction in which the third party assumes control of all or part of the controller's assets are excluded from "sale."
We do not sell personal information.
We do not sell agricultural data.
This document does not authorize grant-program, state, or third-party program sharing beyond this Section 9. Any such program would be documented separately, after analysis of whether it is a "sale" or an excluded disclosure, and would not be added by implication.
We establish, implement, and maintain reasonable administrative, technical, and physical security practices to protect the confidentiality, integrity, and accessibility of personal information and agricultural data in our custody or possession. Those practices are intended to be appropriate for the volume and nature of the data and to protect against unauthorized access, use, disclosure, modification, or loss.
For example, we encrypt certain information, and we require business partners and service providers that handle the information to protect it from unauthorized access, use, and disclosure.
No method of transmission or storage is completely secure. We will use reasonable measures, but we cannot guarantee absolute security.
Subject to verification (Section 11.5) and to the operational limits below, you may:
These rights do not require us to impair a feature that still needs the data, to reconstruct deleted backups immediately, or to contradict a legal obligation. If you are an agricultural producer, nothing in this section waives your ownership or control of agricultural data under the Act.
Email info@long103.io or write to us at the address in Section 15. Before we respond, we must verify that the request is from you. We typically ask for two or three identifiers (for example name, email address, and location). We may ask for more if needed. The information we request may depend on your relationship with us.
When you visit our websites, we may automatically collect IP address, interaction data, browser type and language, operating system, location, date, and time. We may also use cookies. A cookie is a small amount of data sent to your browser from a web server and stored on your device. The cookie may be placed by us or by an authorized third party. We use session cookies (which expire when you close the browser or turn off the device) and persistent cookies (which remain after you close the browser).
First-party operational analytics (Section 7.4) are not a third-party advertising cookie. They are product-operations events we store ourselves. They are separate from the required and functional cookies described below.
We categorize cookies as:
You can manage cookies in your browser (usually under Help, Tools, or Edit). Rejecting cookies may reduce performance and functionality. Required cookies will remain.
Our websites do not currently recognize automated browser signals such as "Do Not Track." You can still control most cookies through your browser.
HydroData is a business and agricultural operations tool. It is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information to us, contact us and we will take reasonable steps to delete it.
We may correct, update, or amend this document. We will post the revised version at this URL and update the effective date and version number at the top.
Material changes. If we change this agreement in a material way, we will give you notice (for example by email to the address on your account, by in-app notice, or by a notice on the HydroData homepage) and we will ask you to agree again (check the box or tap Agree) before the material change applies to you. We will not treat silence, continued use, or failure to refuse in writing as consent to a material change.
If you do not agree to a material change, you may stop using HydroData and request deletion of your account as described in Section 11. Some data may be retained as described in Section 16.
Non-material corrections (for example typographical fixes that do not change rights or practices) may be posted without re-consent.
Questions about this agreement, our privacy practices, or your information:
Email: info@long103.io
Mail:
Adaptive Resources, Inc. d/b/a Longitude 103
229 E Kiowa Ave
Fort Morgan, CO 80701
We retain personal information and agricultural data for as long as needed to fulfill the purposes for which it was collected or processed, or for other valid reasons (for example to comply with law, resolve disputes, enforce our agreements, or establish, exercise, or defend legal claims). When we no longer have a valid reason to keep it, we will delete it or de-identify it where feasible.
Operational analytics. We keep raw first-party analytics events for thirteen (13) months from the time of the event, then delete those raw events. We keep aggregated rollups after that raw-event deletion so we can see long-term product health without the underlying event rows. If an organization is deleted from HydroData, we delete that organization’s raw analytics events and we remove the organization identifier from remaining rollups so those summaries no longer name the deleted organization.
Marketing email. If you opt in to content or changelog email, we keep that consent record (and any later unsubscribe) so we can honor your choice. Unsubscribing stops marketing email; it does not delete your HydroData account or stop sign-in, password, or other service messages.
HydroData is offered on these terms. You agree to this Privacy Policy and Data Use Agreement only by an affirmative act: checking the box or tapping Agree on the version presented to you.
By checking the box or tapping Agree, you acknowledge that:
We will record the version number, the time you agreed, and the account that agreed, and we will retain that record.