Privacy policy
Last updated: 30 September 2026
This translation is provided for information only: the French version is the only legally binding one.
CropOwl helps farmers keep track of their fields. To do so, we process a minimum of personal data: the data of your account and the data that describes your farm. This page explains which data, why, who it is shared with and how to exercise your rights, in line with the General Data Protection Regulation (GDPR) and the French Data Protection Act (loi Informatique et Libertés).
In short
- We don't sell your data and we show no advertising.
- Your data is hosted in the European Union; the database is in Frankfurt.
- The public data services only receive the coordinates of your fields and dates, never your name or email address.
- No advertising cookies; audience measurement only runs with your consent.
- You can obtain, correct or delete your data at any time by writing to contact@cropowl.com.
1. Data controller
[company name: to be completed], whose registered office is at [registered office address: to be completed], publisher of CropOwl (see the legal notice). For any question about your data: contact@cropowl.com.
2. The data we process
| Category | Data |
|---|---|
| Account | Email address, password (stored in irreversibly encrypted form, never in plain text), sign-up and last sign-in dates, the weeks in which you used the app, the language of the app and emails. |
| Organisation and farm | Name of the organisation, type of farm (vineyard, market garden…), name and address of the farm, position on the map, members of the organisation. |
| Invitations | Email address of the person invited, who invited them and when, until they join the farm. |
| Fields | Name, outline and area, original RPG identifiers or Telepac block and parcel numbers, crop, status (growing, harvested, bare soil), irrigation and water source. |
| Alerts and tasks | Alerts raised on your fields and what was done about them: task created, alert dismissed with its reason and your comment; tasks (title, due date, notes, status). |
| Photos and observations | Photos taken in the app on your fields, what you say they show, your note, the date and, if you allow it on your phone, the position where they were taken. What the camera writes in the file (model, position) is removed before sending. |
| Farm documents | Files you add (PDFs, photos, pages photographed in the app), their kind, title, date and expiry, the field or task they belong to, who added them and whether they are kept to owners. They may hold personal data (identity, bank details, leases, staff): CropOwl does not read their content and passes it to no analysis service and no language model. |
| Plant protection register | Treatments you record: the product and its authorisation (AMM) number, date and time, dose, treated area, crop, the field and its position, target, stage and notes, with who recorded them; the weather at the time given, estimated by Open-Meteo; and the farm's SIRET, which the register carries. |
| Nitrogen fertilisation | Nitrogen applications you record: date and campaign, the field and its position, crop, area, the fertiliser's type and name, quantity, nitrogen content and nitrogen applied, whether it went on the catch crop, notes, with who recorded them. |
| Use of the application (if you accept it) | Pages and panels opened, clicks (without the text shown), actions taken (task created, alert dismissed and its reason, fields imported from Telepac, setting changed, app installed, action taken offline, photo taken or deleted, document added, changed, deleted or exported and its kind, never its title, treatment recorded, changed or deleted and register exported, without the product or the dose, nitrogen application recorded, changed or deleted and the fertiliser's type, without the product or the quantity, notifications turned on or off, finding which field you are in and its result, never your position), the email or notification a visit comes from, device and browser type, linked to a technical identifier of your account. Never the content of your fields, your notes, your comments or your email address. |
| Preferences | Email settings (daily or weekly digest, its time and the week on your fields on Mondays, urgent weather alerts), the farm's alerts and weather thresholds, paused fields, your choice about audience measurement; for each device where you turn notifications on, the address its browser gives for them and the keys that encrypt their messages. |
| Technical data | IP address (limiting sign-in attempts), the service's technical logs, session cookies. |
| Error reports | Message and technical context of an application error (page, browser), with your account's identifier, without what you typed or your email address. |
This data comes from you: you enter it, or you confirm it when the application pre-fills it (fields and crops from the RPG). The public weather, soil, terrain, water restriction and satellite data describes your fields, not you; its sources are detailed on the Data sources page.
If you import your Telepac declaration, CropOwl only reads its blocks and parcels (numbers, outlines, declared crops). The rest of the file (identity, tax number, bank details…) is not read, and the file itself is not kept.
“Which field am I in?” compares your phone's position with your fields on the phone itself: that position is neither sent nor kept.
3. Why we process it
| Purpose | Legal basis |
|---|---|
| Providing the service: account, map, field profiles, alerts, tasks, photos, documents and their expiry reminders, the plant protection register, nitrogen fertilisation, export | Performance of the contract (terms of use) |
| Checking how right the alerts (diseases, frost) are, from your photos and what they show | Legitimate interest: reducing false alerts |
| Sending you the daily digest and urgent weather alerts, which you can turn off at any time | Performance of the contract |
| Securing the service: limiting sign-in attempts, preventing abuse, technical logs | Legitimate interest: protecting your data and the service |
| Improving the relevance of alerts, from aggregated statistics on dismissed alerts and their reasons | Legitimate interest: reducing false alerts |
| Knowing whether the application is used regularly, from the weeks in which each account used it, without the pages viewed or the actions taken | Legitimate interest: checking that the service is useful before developing it |
| Measuring how the application is used in order to improve it (audience measurement), if you accept it | Consent, which you can withdraw at any time |
| Sending invitations to join a farm, at its owner's request | Legitimate interest: letting several people work on one farm |
| Detecting and fixing application errors | Legitimate interest: keeping the service working |
| Answering your requests and questions | Legitimate interest; legal obligation for the exercise of your rights |
| Meeting our accounting and legal obligations | Legal obligation |
Alerts are worked out automatically from rules published in the application (“Why this alert?”); they inform you and have no legal effect on you. Every decision about your fields remains yours.
4. Who has access to it
- The members of your organisation, who share the farm, fields, alerts, tasks, the plant protection register, nitrogen fertilisation and documents, except the documents an owner keeps to owners.
- Our team, to the extent needed for support and for running the service.
- Our processors, who act on our instructions and are bound by contract to confidentiality and security:
| Processor | Role | Data location |
|---|---|---|
| Cloudflare, Inc. | Hosting the application and the API, storing photos and documents | European Union |
| Neon, LLC (Databricks group) | Database | Frankfurt (Germany) |
| Sendinblue SAS (Brevo) | Sending emails | European Union |
| PostHog, Inc. | Audience measurement, if you accept it | Frankfurt (Germany) |
| Functional Software, Inc. (Sentry) | Tracking technical errors | Frankfurt (Germany) |
Your tasks and the outlines of your fields are also kept in a farmOS farm record, free software that CropOwl runs on its own hosting; no third party has access to it.
Notifications go through the push service of the device's browser (Google, Apple, Mozilla or Microsoft depending on the browser), encrypted end to end: it delivers them without being able to read them.
To obtain the public data, CropOwl sends the services concerned (IGN, Open-Meteo, VigiEau, ISRIC, Copernicus) the coordinates of your fields and, for the weather at the time of a treatment, its day, without your name or email address. The base map and the address search are loaded by your browser directly from IGN's Géoplateforme, which receives your IP address and the text searched for, as with any website you visit.
We do not share your data with any other third party, unless required by law (a court order, for example).
5. Transfers outside the European Union
Your data is hosted in the European Union. Cloudflare, Neon, PostHog and Sentry are American companies: any access to data from the United States (technical support, for example) is governed by the European Commission's standard contractual clauses and, for certified companies, by the EU–US Data Privacy Framework.
6. How long we keep it
| Data | Period |
|---|---|
| Account, farm, fields, alerts, tasks, photos, documents, the plant protection register and nitrogen fertilisation (the rules ask you to keep the register 5 years and the fertilisation records 5 campaigns: export them before closing your account) | While your account is open, then deleted within 30 days of its closure |
| Database backups | 30 days at most, then overwritten |
| Technical and security logs | 12 months at most |
| Weeks in which you used the app | 12 months at most |
| Accounting records, if your organisation takes out a paid plan | 10 years (Article L123-22 of the French Commercial Code) |
| Correspondence about exercising your rights | The time needed to handle the request, then 5 years as evidence |
| Audience measurement, if you accept it | 12 months at most |
| Your choice about audience measurement | 6 months, then we ask again |
| Invitations | Until the person joins the farm, 14 days at most |
| Devices where notifications are on | Until you turn them off or log out on the device, or its browser forgets it |
| Error reports | 90 days at most |
| Answers to actions sent from the app, so that an action sent again after a network cut is not applied twice | 30 days |
The statistics used to improve the alerts are aggregated and cannot identify you; they may be kept beyond these periods.
7. Security
- All connections are encrypted (HTTPS).
- Passwords are stored hashed and salted.
- Each organisation can only access its own data; access is checked on every request.
- Repeated sign-in attempts are limited.
- Photos and documents are encrypted at rest and served only by the application, after checking your organisation, never through a public link.
- The service's keys and secrets are kept outside the code and the database.
8. Your rights
You have the following rights over your data:
- access: obtain a copy of your data;
- rectification: correct inaccurate data, directly in the application for your fields;
- erasure: delete a field in the application, or your account on request;
- portability: receive your data in an open format; your tasks can also be exported as CSV from the application, and your documents as one archive;
- objection and restriction: object to processing based on our legitimate interest, or ask for it to be restricted;
- post-mortem instructions: decide what happens to your data after your death.
Write to us at contact@cropowl.com from your account's email address. We reply within one month, which may be extended by two months for complex requests; we will let you know if so. Emails can also be turned off in one click, in the notification settings or with the “Unsubscribe” link in each email.
You can withdraw your consent to audience measurement at any time with the “Usage analytics” link at the bottom of each page: it stops at once and its data is removed from your browser.
If you believe your rights are not being respected, you can lodge a complaint with the CNIL, the French data protection authority: cnil.fr/fr/plaintes, or 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France.
10. Changes
We may update this policy, for example when a new data source or a new processor is added. The date of the last update is shown at the top of the page; for any significant change, we will notify you by email before it takes effect.