AgrowKnow Privacy Policy

Responsible business: GEMx LLC
Privacy requests: noah@agrowknow.com
Mailing address: 211 E Beverly Dr, Indianapolis, IN 46205, USA
Effective date: October 30, 2026.

1 Scope and our commitments

GEMx LLC operates the AgrowKnow family of agricultural software and data services. This Policy explains how GEMx LLC collects, uses, retains, and discloses information for all websites, web and mobile applications, hosted tools, APIs, reports, subscriptions, data services, and related support and communications provided by GEMx LLC under AgrowKnow or another GEMx LLC product name that link to or expressly incorporate this Policy, including future services, renamed products, and updated versions (collectively, the “Services”).

“AgrowKnow,” “we,” “us,” and “our” refer to GEMx LLC, the responsible business. Product names identify different Services; they do not identify separate responsible businesses. Coverage under this Policy does not mean that a Service or feature has launched or is included in your purchase. Future and renamed Services remain subject to this Policy's stated purposes, sharing limits, and privacy commitments. Umbrella coverage does not itself authorize new uses of existing information or replace required notices or permissions.

This is one Policy for the family of Services. The information we process depends on the products and features you actually use. A visit to a public calculator does not mean that we collect everything described for an account-based farm-management tool. Feature notices explain additional details and request permissions where required. Third-party websites, app stores, and independently operated services have their own notices.

We initially offer the Services in the United States. Farm and business records can be personal information when linked to an individual. Public availability of a boundary, soil map, or government statistic does not make your connection to a farm, private budget, management choices, or commercial relationships public.

“Customer Data” means the records, files, and other content you or authorized participants supply to the Services, including contacts, organizational records, field boundaries, farm and crop records, financial records, photographs, private ratings, trial data, company materials, and uploads.

“Private Derived Results” means nonpublic plans, reports, recommendations, calculations, and other results generated using Customer Data for a customer's account, farm, field, or workspace. A result can be protected even when public or licensed sources contribute to it.

The protections for Customer Data concerning permitted use, confidentiality, sharing, sale, advertising, AI training, research, retention, and deletion also apply to Private Derived Results. This does not transfer ownership of our software, models, or source datasets, or make independently available public or licensed source data private.

We do not sell personal information or identifiable private Customer Data, share personal information for cross-context behavioral advertising, or use private Customer Data to train general-purpose AI models. Funding access does not grant a sponsor access to private records. Separate research use, including broader model-development research or shared benchmarking using private records, requires clear advance disclosure and separate affirmative permission. Declining optional permission does not reduce access you purchased.

Optional permission must come from someone with authority over the affected records and include any individual permissions required by law. Workspace administration, uploading a record, or funding access does not by itself establish that authority.

2 Information we collect and its sources

• Account and contact information. You, authorized inviters or administrators, and selected sign-in providers supply names, emails, authentication identifiers, organization and role, optional address, phone and profile photo, and preferences. We also keep product enrollment, permissions, and records of legal acceptance or other choices where recorded. We use this information to authenticate, secure, administer, and support accounts and communicate with you.

• Organizations and relationships. Workspace and farm names, company or dealer information, grower contacts, team assignments, invitations, membership, branding, sponsorship, and permissions come from you and authorized participants. We use them to organize work, enforce access, and administer relationships and funded access. Someone supplying another person's information must have authority. Contact us about an unwanted invitation or incorrect relationship.

• Fields and agricultural records. Information you enter, upload, import, or authorize others to supply can include field names, boundaries, coordinates, acreage, crop histories, management practices, planting and harvest records, seed and product selections, private ratings, trial results, scouting observations, photos, soil tests, sample locations, and application records. We use it to preserve your work, obtain relevant geographic information, run requested analyses, and provide plans and reports.

• Financial and planning records. Where you use relevant features, these include yield and price assumptions, rent and land agreements, costs, budgets and saved versions, manual overrides, actual expenses, receipt images and attachments, allocations, harvest, inventory, and sales. We process them for your requested calculations, recordkeeping, comparisons, and exports.

• Generated and derived information. Weather summaries, classifications, soil and terrain context, modeled yield layers, crop stages, risk indicators, scores, recommendations, management zones, scenarios, reports, and synthetic outputs may be generated from your inputs and public or licensed sources. We use them to provide and explain requested results. A result linked to a private account or field can remain private information even when its underlying source is public.

• AI interactions. Where AI features are available and used, we process questions, submitted material, selected crop or geographic context, relevant evidence, generated answers, citations, and usage records. Technical records may include model, token counts, response status, timing, and cost. Section 6 explains external AI processing.

• Purchases and access. You, payment providers, app stores, and access services supply customer and transaction identifiers, subscriptions, plan and credit balances, field or crop-year counts, invoices, taxes, payment and refund status, sponsorship records, and limited payment-method information. We use these to process and reconcile authorized purchases, provide receipts, prevent misuse, and determine access. Full card numbers and card security codes are processed through the payment provider's interface rather than our application backend.

• Technical information. We and operational providers receive IP addresses, browser or device information, request URLs and selected parameters, timestamps, errors, authentication and security events, and feature, API, or performance records. API services may process credential identifiers, request geography, metering, and audit records. These support service delivery, reliability, troubleshooting, capacity, cost controls, and security. Technical records can be linked to an account or work context.

• Communications and delivery. Support correspondence, submitted attachments, invitation and report recipients, selected fields, notification preferences, time zone, message content, delivery identifiers, bounces, complaints, and suppression records support communications and preference management. If you send private information in a support message, we process it to handle that request.

Information comes from you, authorized participants, your chosen integrations and sign-in providers, payment and delivery services, public or licensed data sources, our operational providers, and results we generate. Optional fields and permissions are identified where requested. Some information is needed to provide a selected feature. Do not submit passwords, payment-card details, or sensitive information unrelated to the Services in uploads, AI questions, or support messages.

3 How we use information across products

We use information to provide the features you select, maintain account and field history, generate requested results, administer access and purchases, deliver authorized communications, support users, investigate errors or misuse, secure the Services, and meet legal obligations. Internal usage measurement helps us understand reliability, capacity, cost, and feature use; it is distinct from selling farm records or tracking you across unrelated websites for advertising.

Participating products share identity, workspace, canonical-field, entitlement, and other necessary infrastructure. For example, an authorized field boundary may support weather in FieldCast and a seed plan in Seed Plan. This does not make a private budget visible to every user of that field or grant a company access merely because it funds a subscription. Access continues to depend on the relevant permissions and relationships.

Not every product uses the shared account system. Creating a common identity does not automatically enroll you in all products, activate every trial, or authorize unrelated processing. Adding a product or combining records does not override the purposes and permissions under which private information was supplied.

Models and automated rules support agricultural and economic planning. Their outputs are estimates and recommendations for human review. Using these tools is not permission for us to make lending, insurance, employment, or other decisions with legal or similarly significant effects about you.

We do not treat a private record as anonymous merely because its name was removed. A field outline, precise coordinates, a small comparison group, or combined attributes may identify a grower. Optional research and shared benchmarking using private records follow the separate-permission commitment in section 1. Public or independently licensed datasets can support modeling and comparisons without making your private records public.

Our role in organizational workspaces

Our responsibility depends on the particular processing, applicable law, and the relevant agreement. Where we determine the purposes and means of processing, including for our own account administration, billing, security, and service operations, we act as a controller or business as those terms apply under the relevant law.

Where an adviser, dealer, employer, or other organization determines the purposes and means for particular workspace records and we process those records solely on its behalf under lawful, documented instructions, we act as a processor or service provider for that processing. The organization is responsible for the authority and instructions it supplies. The relevant processing agreement and applicable law govern the parties' responsibilities; an organization paying for a workspace or uploading a record does not by itself determine every processing role or ownership right.

These roles do not grant sponsors private-data access, override permissions, or remove our own legal obligations. Section 10 explains how we assess and coordinate requests involving organization-controlled records without automatically disclosing or erasing another participant's records.

4 Location and external data requests

Saved field boundaries, coordinates, map areas, sample points, and source identifiers are used to provide geographic context and field-specific results. Their use does not depend on device-location permission. You can draw, select, or upload fields without granting current-device-location access.

Where a current-location feature is offered, it requests location when you choose the feature and grant browser or device permission. You can withdraw permission in settings. Doing so does not delete previously saved field coordinates. These map-positioning controls do not continuously track your movements in the background. A future feature needing materially different collection requires its own disclosure and required permission.

Map, imagery, geocoding, weather, soil, terrain, crop, and other source requests may disclose selected areas, coordinates, sample points, or identifiers to commercial geospatial providers or government and other environmental sources. Examples include Esri and BigDataCloud for relevant map or geographic functions, and the U.S. Census Bureau, NOAA/NWS, NASA, USDA, USGS, and EPA for relevant public data. Providers and sources vary by feature and layer. Direct requests from your browser or device also disclose connection information such as your IP address. A public dataset does not make your account's association with a location public.

5 Local tools and information stored on your device

Account-based Services can store sign-in sessions, preferences, cached layers, recoverable drafts, and pending saves in your browser or device. Necessary sign-in, payment, map, font, and hosting providers may also use storage or receive connection information. Some marketing pages load fonts or other assets from external providers.

A browser calculator or desktop plugin expressly operating in a local-only mode processes inputs and opened files on your device. Local calculation and download-only save or export controls do not by themselves upload those inputs or files to an AgrowKnow account. For example, this describes the standalone Farm Fuel Calculator's local calculation and scenario-file controls. It does not establish that every mode of a product or every plugin operates offline.

Hosted pages still make ordinary website and asset requests. Online features such as maps, source-data retrieval, cloud saving, synchronization, report sharing, and support transfers can send the information needed for that feature to us or the relevant provider. Some connection or map requests occur when a page or layer loads, without a separate upload action. Feature notices explain material transfers and request permission where required before processing. A software license does not determine whether a tool makes network requests.

Clearing browser storage can sign you out, reset preferences, or remove unsaved local drafts. It does not delete server records, downloads, exports, or copies held by recipients. An online account-deletion request does not remotely erase files on your own device.

Some public pages offer optional Google Analytics to understand visits, referral sources, and use of the tools. Our integration starts only after you allow analytics. It sends approved page categories and named actions, such as opening a tool or downloading a file, the originating referral website, and recognized campaign sources from a fixed list. Google also receives connection and device information and may store analytics cookies after you allow analytics. Our integration does not send farm inputs, field boundaries, financial results, account identifiers, email addresses, form contents, URL query strings, or URL fragments. Advertising storage, advertising personalization, and Google signals are disabled. Your preference is stored in the browser for that website; declining or withdrawing permission keeps the application available. Use the website's Analytics preferences control to stop new measurement and your browser's site-data settings to clear earlier cookies. See the Google Privacy Policy.

We do not use third-party advertising pixels to track activity across unrelated websites for targeted advertising. Our optional website analytics honors Do Not Track and Global Privacy Control as a refusal of analytics. Other service functions may not respond to the legacy Do Not Track setting. We honor legally valid opt-out preference signals for covered processing where required. Any optional tracking requiring consent must be explained and offered separately from essential storage.

6 Sign in and AI services

Connected sign-in. If offered and selected, Google, Microsoft, or Apple provides authentication identifiers, email, and available basic profile information needed for sign-in and account setup. The information available depends on the provider and your choices. Basic sign-in does not request Gmail messages, Google Drive files, Microsoft mailbox or OneDrive contents, or your contact lists. A separate integration needing additional scopes requires a separate authorization. The identity provider also handles sign-in activity under its own policies.

AI features. Where offered, designated AI-enabled features can answer questions, prepare automated briefings, or extract information from submitted documents. They may send prompts, submitted material, and relevant crop, geographic, or other disclosed context to an external AI provider. Providers vary by feature; OpenAI processing for relevant Ask AI or briefing features is one example. Some responses and agronomic results are instead produced by deterministic calculations without an external generative-AI model. Use of a budget, receipt, map, or other tool does not by itself mean that all of its private records are submitted to AI.

For a feature that sends content to an external AI provider, we identify the provider, material information sent, and purpose before submission and obtain explicit permission where required. General Ask AI tools are not intended for confidential farm records, credentials, or unrelated sensitive personal information. If a private-data AI workflow is offered, its notice must explain what private material would leave the Service and request the necessary permission first.

We do not use private Customer Data to train general-purpose AI models or authorize providers acting on our behalf to do so. AI processing may still involve the operational, security, usage, and retention purposes disclosed in this Policy and the feature notice. Provider retention depends on the service, endpoint, features, account controls, and applicable requirements; it is not uniformly limited to generating a response or to a single retention period.

For example, OpenAI states that its API data is not used for training unless the API customer opts in; we do not opt private Customer Data into that training. Its default abuse-monitoring logs may contain prompts and responses and are generally retained for up to 30 days, with exceptions, while application state has separate retention rules. We do not promise zero retention or that all content is deleted within 30 days. See OpenAI's API data controls.

7 Who receives information

We disclose information as reasonably necessary for these purposes:

• Authorized participants. Workspace owners, administrators, assigned sellers or advisers, teammates, growers, and other permitted participants can access records within their roles and relationships. An employer or other organization administering a workspace controls its membership and organizational records. An independently authorized copy can remain after one relationship ends.
• Hosting, identity, storage, and processing. Providers support authentication, cloud databases, file storage, web hosting, server functions, data delivery, and model or other operational compute. Examples used for relevant functions include Supabase, Netlify, Google Cloud, and Cloudflare. Each receives information needed for the functions used by the relevant feature; these examples do not mean every provider receives every user's records.
• Support and administration. Authorized support and administrative personnel may access relevant records to help users, investigate problems, and secure or administer the Services.
• Optional website analytics. Google Analytics receives the limited website-measurement information described in section 5 when you allow analytics. This is separate from the providers that process private farm or account records to deliver the Services.
• Payments and purchases. Payment processors, app stores, and purchase-management providers process purchase, billing, transaction, and entitlement information where purchasing is offered. Examples include Stripe for web payments and Apple, Google Play, or RevenueCat for relevant store or subscription functions. These providers may have independent duties and privacy notices for payment, fraud-prevention, and legal purposes.
• Messages. Email and report-delivery providers, such as Resend where used, process recipient information, message content, delivery records, and suppression information. Weather summaries and report deliveries can include field names, conditions, grower information, or links to private reports; processing is not limited to email addresses.
• Sign-in, AI, maps, and source data. Identity providers, external AI services, commercial geospatial providers, and government or other data sources receive information for the selected functions described in sections 4 through 6. They also process relevant connection or account information under their applicable policies and service arrangements.
• Sponsors. Sponsors receive information needed to administer funded access, such as the intended recipient, plan, coverage, and billing or activation status. Sponsorship alone does not authorize access to private boundaries, crop or management records, budgets, private ratings, or reports.
• Recipients you authorize. We disclose information through sharing, invitations, deliveries, exports, and integrations you or another authorized participant directs. A connection notice identifies its receiving service and transfer scope. Revoking a connection does not recall earlier transfers.
• Legal and protective purposes. We may disclose information reasonably necessary to comply with law or valid legal process, obtain professional advice, investigate fraud or misuse, or protect rights, safety, and security.
• Business transactions. A merger, acquisition, financing, reorganization, or sale of assets may involve a transfer under appropriate confidentiality protections, subject to law and required notice. A successor handling existing records remains subject to the applicable privacy commitments. A transfer does not itself authorize uses contrary to this Policy, and notice or an opportunity to delete does not replace consent where required for a materially different use.

Providers acting on our behalf must use Customer Data for authorized purposes, protect confidentiality, and follow applicable retention and deletion requirements. A provider's independent notice does not expand the uses we authorize on our behalf.

Provider names are examples of relevant functions, rather than an exhaustive list or a statement that every integration is available in every product. A provider change does not itself authorize new purposes, broader sharing, or other processing inconsistent with this Policy. We update the relevant notice and obtain permission where required before materially different processing.

8 Reports and share links

An authorized participant can share or deliver reports using the available controls. If a report link permits viewing without sign-in, anyone possessing the link may be able to view it. A report or snapshot may contain grower identity, field locations and acreage, product selections, recommendations, financial information, or company branding, depending on the report and sharing choices.

Recipients can forward links or save, print, and download copies. Review recipients and contents before sharing. Contact us about disabling a link. Disabling a link or removing workspace access cannot retrieve copies already held by others. A publicly viewable report is different from a private authenticated workspace; a public link to one report does not make all account records public.

9 Communication and permission choices

Change optional delivery through the relevant settings or unsubscribe mechanism. FieldCast daily weather summaries may be enabled by default for eligible accounts; weekly summaries are optional. Preferences can include fields, cadence, delivery time, and time zone. An in-app briefing or budget notice does not itself enroll you in unrelated email marketing.

Account, security, billing, legal, invitation, and authorized plan-delivery messages can be necessary for service. Marketing choices are separate. Providing a phone number or accepting Terms does not authorize unrelated marketing calls, automated marketing calls, or texts. We may retain limited suppression information so that deleted or changed records do not cause unwanted messages to resume.

You can withdraw optional consent through the relevant control or by contacting us. Withdrawal does not undo processing already lawfully completed, and it may affect the optional feature that needs that permission. Declining optional research permission does not reduce purchased access. Device permissions can also be changed in browser or device settings.

10 Retention deletion and privacy rights

Statutory rights depend on where you live, the capacity in which you use the Services, applicable business thresholds, and other legal conditions. Some consumer privacy laws distinguish personal or household use from commercial or employment use; this is not a blanket exemption from privacy obligations. We assess the law and processing involved, and continue to honor this Policy's commitments and other applicable requirements. You may contact us through the same request channel regardless of whether a particular consumer statute applies.

Retention and backups

We keep information only as long as reasonably necessary for the stated purposes, taking account of active use, authorized shared records, legal requirements, security, and disputes. Different categories have different retention needs:

• Account and field records, saved plans, reports, and uploads are kept while needed for the account or an independently authorized workspace, subject to valid deletion requests and applicable requirements.
• Billing, tax, and payment-dispute records are kept for applicable accounting, tax, legal, and dispute requirements. Those needs do not justify retaining unrelated farm records indefinitely.
• Security, access, usage, and support records are kept as needed to operate and protect the Services, investigate incidents, handle requests or disputes, and meet legal requirements.
• Legal acceptance and permission records are kept as reasonably necessary and lawfully permitted to administer agreements and choices; deletion requirements and the design of the relevant system affect availability.
• Delivery and suppression information is kept as needed to operate communications and honor preferences.
• Provider logs, temporary processing files, and backups follow the applicable service configuration, operational need, provider arrangement, and legal requirements.

Trial expiration and subscription cancellation do not automatically erase information. Information retained after deletion for a permitted reason remains protected and restricted to that reason. Residual backups are removed through the applicable backup cycle and are not used for routine product activities. If a backup is restored, applicable deletion requests or restrictions must be reapplied before affected records return to routine use. We do not promise one retention period for every category, a particular backup technology, or immediate removal from every backup. De-identification is not an automatic substitute for a valid deletion request or permission to reuse private records for research.

Access correction export and deletion requests

Contact noah@agrowknow.com to request access, correction, an export, or deletion. Specify whether you want removal from one named product or deletion of your shared AgrowKnow identity and associated information across participating products. Where account-deletion controls are provided, you may also initiate a request there. You do not have to accept new Terms merely to contact us about deletion.

We verify identity and authority only as reasonably necessary. Do not send passwords or full payment-card numbers. Requests involving another person's information, a company account, or shared workspace records can require an additional authority check. If we hold information supplied by an adviser or organization, contact us about its source and your options.

For records we process on an organization's behalf under its lawful instructions, we may coordinate with or direct the relevant part of a request to its authorized administrator and assist fulfillment as required by our role and applicable law. We verify the request and the recipient's authority and limit the information shared for that coordination. We do not automatically disclose or erase another participant's records, or refuse your request solely because an adviser uploaded the information. We separately address information for which GEMx LLC determines the processing purposes and assess applicable rights, lawful instructions, retention grounds, and independent rights in shared records. An organization's payment or account ownership alone does not justify retaining or disclosing all records about you.

Deletion requests are reviewed and fulfilled; submitting a request is not immediate erasure. We explain the scope and effects on other products, shared work, and subscriptions and respond within applicable legal deadlines. A product-specific request can leave your shared sign-in and records needed for other authorized products intact. A shared-account request requires review across participating products and providers, rather than removal of only the sign-in record.

We remove information subject to a valid deletion request from applicable active systems and arrange appropriate provider deletion, subject to lawful exceptions and backup handling. Records another person or organization has an independent right to retain are assessed separately; shared access alone is not a reason to keep all of your information. We explain retained categories and reasons unless legally restricted. Exported copies held independently by recipients can remain outside our control.

Deleting an account does not itself cancel a separately managed app-store subscription or remotely delete local files. We identify relevant billing effects and help you locate cancellation controls. We confirm completion after actual fulfillment and explain any lawful retention or continuing process.

Once a personal account-deletion request is verified, we promptly turn off future renewals for the affected GEMx-managed personal web subscriptions without waiting for erasure to finish. Product-only deletion stops renewals for the deleted product's personal access; shared-account deletion stops all personal GEMx-managed web renewals attached to that account. We identify the affected subscriptions and explain billing effects before closure.

If product-only deletion affects an inseparable personal bundle, we turn off renewal of that bundle and preserve already-paid access to the remaining products through the paid term where possible. A replacement plan or new charge requires your explicit authorization; we do not silently convert you to a different paid plan. Existing refund provisions continue to apply. A valid deletion request is not postponed until a paid term expires.

An individual's deletion request does not automatically cancel an organization subscription or sponsored coverage serving other users. Those billing arrangements follow instructions from an authorized organization billing administrator; the individual's access and records are handled according to the verified deletion scope. Store-managed subscriptions require the store's cancellation process. Billing review must not prevent fulfillment of a valid privacy request within applicable legal deadlines.

Applicable rights and appeals

Where applicable, you may have rights to confirm processing; access, correct, or delete personal information; receive a portable copy; withdraw consent; and opt out of specified sales, targeted advertising, or profiling. Some laws also provide rights regarding sensitive information or authorized agents. Legal exceptions can apply.

Send requests to noah@agrowknow.com. We respond within the applicable legal deadline, explain a denial and available appeal, and do not unlawfully discriminate for exercising rights. Where an appeal is available, reply with “Privacy appeal” and identify the decision. We review the appeal and provide the outcome and information about any available complaint route. You may also contact your applicable privacy regulator or state attorney general.

11 Security and processing locations

We use safeguards intended to protect information, including authenticated access and permissions for applicable private workspaces and records. No system can guarantee absolute security. Protect your credentials, devices, exports, and report links, and notify noah@agrowknow.com about suspected misuse. We assess incidents and provide notices as required by applicable law.

We operate in the United States and use providers that may process information where they and their subprocessors operate, including other countries. This Policy does not promise U.S.-only storage. Where applicable law requires transfer safeguards, we use the required safeguards. Visiting from another country is not by itself blanket consent to every transfer or processing activity.

12 Account age and children

The Services are general-audience agricultural tools and are not directed to children under 13. We do not knowingly collect personal information from children under 13 without legally required parental notice and verifiable consent. A parent accepting general Terms alone does not substitute for those requirements. If we learn of collection without the required protections, we take steps to delete the information unless retention is permitted or required by law. A parent or guardian may contact noah@agrowknow.com about a child's information.

Every account user, including an invited user, must be at least 18 years old and legally able to enter a binding agreement. A parent, guardian, or organization administrator cannot authorize an under-18 account under these Terms. This account-age rule does not itself restrict access to public information or rights granted under a separate software license. The Services are not directed to children under 13, and an account-age rule does not replace applicable children's privacy protections.

We do not offer accounts for minors or a guardian-based account-registration process under this version. The account-age rule is separate from our duties concerning personal information received through public pages, support, or other channels, including any legally required response to learning that information came from a child.

13 Changes and contact

We post the effective date of revisions and provide appropriate notice of material changes. If processing changes require separate consent, we obtain it before that processing. Continued use alone does not override required consent or retroactively expand our prior privacy promises. A new product name or consolidated notice does not by itself change the permissions attached to existing private records.

The Privacy Policy governs GEMx LLC's collection, use, sharing, retention, and deletion of personal information, Customer Data, and Private Derived Results. The Terms govern access, purchases, permitted use, and liability, subject to applicable law. A separately signed data-processing agreement controls the specific organizational processing it expressly covers, subject to applicable law and the privacy commitments and permissions attached to the records. A purchase term, provider notice, or general contract clause does not by itself expand those processing rights or authorize a materially incompatible use of previously collected information. This relationship does not displace nonwaivable rights or itself change the Terms' liability provisions.

For privacy questions, requests, or appeals, contact noah@agrowknow.com or write to GEMx LLC, 211 E Beverly Dr, Indianapolis, IN 46205, USA.