Privacy Policy

Account information. The mobile app signs you in with a one-time code sent to your email address. We store your email address, your language setting, sign-in session records, and, if you add them, a display name and profile photo. On the website you can also sign in with Google or Apple; we then store the account identifier that provider gives us. Older website and desktop accounts may also hold the name and profile image a sign-in provider shared.

Your farm record. Depending on what you use, your ZarSage account stores field names, field boundaries you draw or import, field areas, crop cycles, tasks, scouting observations and their photos and notes, spray and other intervention records, soil results and the lab reports you upload, farm documents, and your answers to questions and approvals from ZarSage. Field boundaries show where your farm is. Records you create in the app, in ChatGPT or Claude, or on the website all go to the same account.

Location and photos. The app asks for location permission only if you tap "use my location" while adding a field. It reads your position once to center the map and does not send that position to ZarSage; only the boundary you draw is saved. The app uses the camera or photo library only when you add a scouting photo. We do not remove the information stored inside a photo file, which can include where the photo was taken if your camera records that. The app does not use the microphone.

Daily briefing. To prepare your briefing, ZarSage uses your farm record, the weather and satellite data for your fields, your time zone, your briefing schedule, your chosen voice, and the name you ask the briefing to use. Spoken briefings are written and voiced by our AI service provider and stored as audio files in your account. If you choose the phone's own voice instead, the briefing text is read by your phone's speech engine; depending on your phone settings, Apple or Google may process that text.

Push notifications. If you allow notifications, the app sends ZarSage your device's push token, the platform (iOS or Android), your time zone, which notifications you want (briefing ready, field findings), and your quiet hours. Notifications are delivered through Google Firebase Cloud Messaging, which also delivers to iPhones through Apple's push service. Briefing notifications contain only a short generic message. Field finding notifications can include the field name and a short description of the finding.

Mobile subscriptions. Subscriptions in the app are sold through Apple In-App Purchase or Google Play Billing. Apple or Google handles your payment details; ZarSage never receives your card number. After a purchase, the app sends ZarSage the purchase proof so we can verify it with Apple or Google and attach your plan to your account. We store the product, subscription status, renewal or expiry date, the store's transaction or purchase reference, and an account reference that links the purchase to you. Apple and Google also send us updates when a subscription renews, changes, or ends.

AI features in the app. When you ask the app to draft a crop plan or task plan, read a soil lab report, interpret soil results, or look at a scouting photo, ZarSage sends your request and relevant field details to our AI service provider, and may include the file or photo you chose. We keep each draft and the request details used to make it so you can accept or reject it. For scouting photo checks, that draft record keeps a fingerprint of the photo, not the photo itself.

Farm records stored through the connector. If you authorize ZarSage in ChatGPT or Claude, the connector may store the field boundaries, crop cycles, soil results, tasks, observations, interventions, alerts, memories, documents or excerpts, reports, and other records you ask it to create or import. These records are associated with your ZarSage account and may include precise farm locations.

Information sent for online features. Weather, soil, and satellite features send your field's location or boundary, with the dates and data requested, to the providers of that data. The app loads map images directly from OpenStreetMap, Mapbox, or Esri; those services receive your device's internet address and the map area you are viewing. Place search in the app uses your phone's built-in Apple or Google location search, which receives the text you search for. Pictures in the Discover feed load directly from the image address each article's publisher lists.

Crash reports from the app. The mobile app can send crash and error reports to our error-reporting provider, Sentry. These reports contain the error, the app version, and the device and operating system type. They are configured not to include your account, email address, or screenshots. The app also sends Sentry app session start and end events and timing data for about 1 in 10 app operations.

Usage limits and diagnostics. We process usage counts for metered features such as AI, weather, soil, satellite imagery, fields, and documents. We may also receive app version, platform, error reports, request path, response status, and similar diagnostic information.

Website. Our website uses Sentry to report page errors, Ahrefs Web Analytics to count page visits, the HubSpot tracking code to understand visits to our website, and a Crisp chat window (shown on larger screens; its script loads on all screens) so you can message us. Sentry also records timing data for about 1 in 10 page loads. These services may set cookies or receive your device's internet address, browser details, and the pages you visit. The account deletion page does not load them. If you sign up for email updates, we store your email address, the platform and language you choose, the consent wording you agreed to, and when you confirmed. That form uses Cloudflare Turnstile to block automated sign-ups.

Joining a ZarSage organization moves your account and its fields, crop cycles, tasks, and other records into that organization. Its admins can see your name, email address, and profile photo, the organization's fields and their records (crop cycles, tasks, scouting, sprays and other interventions, soil results, documents, and weather and satellite views), an activity log of changes, and members' sign-ins and assistant connections, which they can end. Tasks can be assigned to organization members, and the assignee's display name is shown with the task and may be read aloud in a briefing.

If you work with an organization without being a member, it sees only the crop cycle you pick and the record types it asked for and you accepted, until the end date in its invitation or until you end the sharing. We record which of its people opened your shared records, what they opened, and on which day.

Organization admins can connect outside services, such as sensor platforms or Google Drive, so ZarSage can use that data for the organization. Connection credentials are stored encrypted and are erased when the connection is removed. An organization can also supply its own AI provider key; ZarSage then uses that provider for the organization's field reviews.

ZarSage services process account, subscription, usage, and farm record information so the app can sync your data, validate access, and enforce plan limits. Photos and documents you upload are stored in our cloud file storage.

When you use the ZarSage connector, the farm records you create or import are stored in ZarSage's hosted service. ChatGPT or Claude sends the tool inputs you approve and receives the tool results needed to answer your request. ZarSage uses OAuth access controls so each assistant can access only the account and permissions you authorized. You can disconnect the connector at any time; disconnecting stops future assistant access but does not itself delete your ZarSage account records.

The connector receives only the tool inputs and saved records needed for your request. It does not retrieve your full ChatGPT or Claude conversation history. To enforce plan limits, prevent abuse, and keep the service reliable, ZarSage records which tools were called, how many calls succeeded or failed, and daily usage for each account and assistant connection.

AI requests, including your briefing script and voice, are sent to OpenAI through Cloudflare's AI Gateway to generate responses. The AI Gateway keeps a log of AI requests and responses, including any photo or document sent with a request, so we can monitor reliability and cost; briefing voice requests are not logged there. We also use TypeSafe to check some of ZarSage's own decisions, such as matching a pest name to a species, spotting duplicate tasks, checking that a field finding is supported by the evidence it cites, or ranking document search results. It receives the farm details relevant to that check, which can include field locations, task titles, notes, document excerpts, and text from connected services. Document search uses Cloudflare Workers AI to index your documents and notes. Weather, soil, and satellite requests are sent to the providers needed for those features. We do not sell your personal information or serve advertising, and the app does not track you across other companies' apps or websites.

We do not use your farm record, photos, documents, briefings, or requests to train or fine-tune AI models. Under the terms of the AI services we use for ZarSage's own features (OpenAI's API, TypeSafe, and Cloudflare Workers AI), those providers do not train their models on what we send them either. If an organization supplies its own AI provider key, its field reviews run under that organization's agreement with its provider.

What ZarSage knows about your farm is kept as records you can see, not built into an AI model. When ChatGPT or Claude offers to remember something about your farm, such as a unit you prefer or a practice you follow, ZarSage saves it as a draft farm preference in your account, next to your fields and tasks, and uses it only after you confirm it. You can ask the assistant to forget it, it is included in your export, and it is deleted with your account. If you leave ZarSage, nothing you taught it stays behind in a model.

The ZarSage desktop app is no longer offered to new users. If you still use it, it keeps most of its data on your computer, including farm records, documents and their indexes, chat history, drafts, preferences, and local backups, and it stores license keys and connection tokens in your computer's credential storage where available. AI requests from the desktop app can include your prompt, recent conversation, selected field details, and relevant document excerpts. If you subscribed through the Mac App Store, the app sends Apple-signed purchase proof so we can validate it; we store the purchase identifiers, product, environment, status, expiry, and a hashed transaction reference.

The desktop app's Google Drive Backup and Google Tasks Sync are optional. Google Drive Backup uploads a backup ZIP of your local app data to your Google Drive, and Google Tasks Sync creates or updates a "ZarSage AI" task list in your Google account. You can disconnect them in the desktop app's Settings or from your Google Account, and you can opt out of desktop telemetry in Settings. Local desktop data remains on your computer until you delete it.