FieldForge
PrivacyTermsAI PolicyData useAcceptable useSupportSign In

Data Use Policy

Effective October 6, 2026 · How farm records, AI requests, documents and location data are used.

Your records and service processing

You retain ownership of the records you provide. FieldForge processes them to provide the features you choose, authentication, storage, synchronization, reports, subscription administration, support and security. FieldForge does not sell personal information or use farm records for targeted advertising. This policy supplements the Privacy Policy.

What goes to AI

Sending a request shares the message and displayed conversation context with OpenAI. Choosing Scan sends the whole submitted file, including readable contents and images, for analysis. Record access is off by default; enabling it allows the tools selected for your question to retrieve relevant permitted records and send the returned fields to OpenAI. Farm Pulse and broad operation reviews may cover several areas, including animal health, work, inventory, finances and GPS session summaries. These tools can include free-text notes or contacts; redact information at its source or keep record access off when appropriate.

FieldForge does not send deployment credentials through the AI tool interface. A one-way identifier derived from your account ID accompanies requests for provider safety purposes. Do not type secrets into messages or attach them to files. The AI input/output safety screens also process submitted text and supported images with OpenAI.

Conversation saving and provider retention

New conversation saving starts off. Unsaved requests are not written to FieldForge's AI conversation history; their visible context remains in the current page while you use it. If you enable saving, your new messages, document filenames and AI replies are stored in your account's history. Uploaded scan file bytes are not saved to FieldForge document storage by this scan flow. Separately uploading a private profile document does save that file; these are different features. Turning saving off does not erase older saved messages, your browser's memory, backups or provider records.

FieldForge requests that OpenAI not store Responses API application state and supplies necessary tool-round context within the request instead of using provider-stored conversation IDs. That setting is not Zero Data Retention. OpenAI safety processing, abuse monitoring, prompt caching and legal retention exceptions can still apply. OpenAI states API data is not used for model training by default unless the customer opts in; FieldForge's code does not opt these requests into training. No special provider retention approval is claimed. See OpenAI's current data controls.

Reviewed actions and operational metadata

Proposed action fields remain in the current page and in a server-signed approval token until you discard them or the page closes; a ten-minute deadline limits execution. FieldForge stores the account identifier, action type, signature, timestamps and approval status to prevent repeat claims and record the outcome. Draft field values are not stored in that approval table. Approval metadata may remain with the account; expiry prevents execution but does not delete that metadata. Completed actions save the reviewed farm record under the existing permissions.

Service providers may process technical metadata needed for delivery, security and troubleshooting. AI error logging is limited to error types or provider status metadata where supported; it is not intended as a transcript archive. Avoid unnecessary personal data in support reports. No complete deletion from all logs or backups is promised immediately.

Location, teams and public sharing

Tractor GPS asks for location when you start its feature; it is optional. Map locations you create and saved guidance sessions can contain precise farm information. Permission to use location is not permission to publish it. Public catalogs and deliberately shared profile links have different audiences from private farm records. Review sharing settings and the actual visible content before using a public link.

Workspaces use existing membership and record permissions. Only upload or enter employee, customer and other people's information for an authorized purpose. AI access to permitted workspace records does not replace that obligation. FieldForge's AI does not automatically publish your records or enlarge a workspace's access.

Correction, access, deletion and incidents

You can correct editable records, view saved history, download eligible archives, manage device permissions and request account deletion through the available app controls. Exports cover the records described by the export screen and are not a complete backup of every file or integration. To ask about access, correction, deletion or a privacy concern, use Support or the account-deletion page.

Deletion and retention requests are assessed with account verification, applicable rights, security needs and legal obligations. Paid subscriptions must be canceled separately with their provider. If you suspect unauthorized access, secure your account and report the concern privately. FieldForge can investigate, limit affected processing and take required notification steps; this policy is not a guarantee that incidents cannot occur or that every request will have the same outcome.