Privacy Statement
Draft under review by counsel. This document is published for transparency while it is finalized and is not yet in force. The version that governs will say so plainly, with its effective date.
The commitment, first
Your operation's records, identity and acreage are confidential. They are not sold, not packaged, not shared with vendors, and not attached to anything that leaves the system. Farm-level operational data is not an advertising asset and is not a source of competitive intelligence about you. Your records are not payment for the software.
What we collect
Account information: name, email, organization, role, sign-in identifiers, and support history.
Farm and operational information you enter or speak to FRED: farms, tracts, fields, acres, crop years, practices, activities, inputs, machinery, harvest records, grain inventory, samples, grades, settlements, and your own notes.
Economic records you choose to supply: input costs, bids, premiums and discounts, contracts, freight assumptions, settlement information.
Technical information needed to run and secure the service: device and browser information, security signals derived from your connection, timestamps, diagnostic logs, sign-in events, and application performance data.
Files, images, documents, and audio or transcriptions you intentionally submit.
How we use it
To provide and secure the service: sign you in, store and retrieve your records, and perform the calculations, analyses, exports and workflows you ask for. To support you and troubleshoot errors. To detect abuse, fraud, security threats and unauthorized access. To maintain, test, debug and improve reliability. To comply with law, enforce agreements, and protect the rights and safety of users and the company.
We collect and process what is needed to provide, secure, support, improve and lawfully administer the service, and no more. Personnel and service-provider access is restricted to what is reasonably required.
How it is protected
Row-level isolation at the database engine: your operation's rows are readable only by your operation, and access is decided by your verified sign-in token. Privileged credentials are confined to isolated server functions and offline jobs. Financial movement runs on append-only ledgers. See the Security page for the current, honestly labeled state of the compliance program.
No security control is described here as infallible. If you suspect exposure, report it immediately using the addresses at the end of this page.
What leaves the system, and what does not
Questions about agronomy, markets, weather, machinery or farm programs that need outside research travel bare: your name, your acres, your fields and your records are not attached. The conversation lane inside the application does not send your words to any outside model. Where an outside model or data source is used in research, the request is minimized by design and governed by our actual contracts and configuration. We do not claim more than that until testing across every route confirms it.
How we disclose
We do not sell identifiable farm operational data to data brokers or third-party advertisers. Information may be disclosed to service providers acting for us under confidentiality and security obligations, at your direction, in a business transaction subject to appropriate protections, to comply with law, or to protect rights and security. A current list of service providers with access to customer data will be maintained and notice given of material changes.
Research, de-identified and aggregated data
Identifiable farm-level data is not used in external research, sold as research data, or disclosed to third parties for independent research without a clear legal basis and your authorization. Internal product research uses de-identified, synthetic, test, or minimized information where feasible.
De-identified data is information processed so it is not reasonably linkable to an identifiable person, account or farm. Removing a name alone is not enough where location, acreage, crop, timing, yield, equipment or commercial records could together identify a producer; those are generalized, bucketed, suppressed or removed. Re-identification attempts are prohibited except for authorized security testing.
Aggregated data combines records across enough operations that results describe groups, trends and ranges rather than any one producer, using minimum cohort sizes and suppression rules. Any regional analysis built on aggregated data will be disclosed here before it begins. It has not begun.
Automated processing
FRED uses automated systems and may use language models to interpret requests, extract structured values from what you say, retrieve records, calculate, and write sentences. Every answer carries a grade, Researched, Partial, Dated, Guess or Out of lane, and the grade leads the answer. A model is never the silent source of a claim: facts come from your records or from research we ran, with attribution, and anything less is graded a guess and says so.
Staff may review interactions for support, abuse prevention, security investigation or quality assurance, under access controls and confidentiality obligations. During the preview period, staff can read FRED interactions for development; testers are told so at handoff.
Retention and deletion
Active account data is retained while needed to provide the subscription and the recordkeeping you asked for. Backups persist for a limited rolling period after deletion and expire through normal rotation. Security and audit logs are retained for a defined period appropriate to incident investigation. Billing and legal records are retained as tax, accounting and contract law require. Authenticated deletion requests are completed within applicable legal and contractual timeframes, subject to lawful exceptions and backup lifecycle.
Exact retention periods are set with counsel once backup schedules and legal requirements are confirmed, and will be stated here with an effective date.
Your requests
Subject to applicable law, you may request access to, correction of, deletion of, or a portable copy of eligible personal information. Where law provides further rights, including rights concerning targeted advertising, sale, profiling or appeal, we will provide the required mechanism. Identity verification may be required before a request is fulfilled. Your farm records can be exported in every format you would need, at any time, from inside the application.
Security incidents
We maintain a written incident response process covering detection, containment, remediation, evidence preservation, vendor coordination, post-incident review and legally required notices. Affected credentials, tokens or sessions are revoked or rotated when appropriate. You will be notified when required by law or contract, with practical remediation information.
Children
The service is for business and agricultural operations and is not directed to children under 13. We do not knowingly collect personal information from children.
Privacy requests and contact
Privacy, compliance and secure document coordination: compliance@getfredtech.com. Technical support: dev@getfredtech.com.
To be completed with counsel
Exact retention periods, the service-provider list, applicability of the Montana Consumer Data Privacy Act, the legal entity name and registered address, and effective dates.