Data & privacy commitments
Farm data is not marketing inventory.
These are the minimum operational commitments for a future pilot. This prototype collects no personal or farm data and is not yet a formal legal privacy policy.
Before any pilot data is collected
- Agree in writing what is collected, which devices and zones contribute it, why it is needed and who can access it.
- Give the grower access to their raw and exported pilot records, with a clear contact for corrections and incident reporting.
- Apply retention, deletion and backup periods appropriate to the signed pilot agreement. Do not retain data “just in case.”
Before any model is trained
- Separate identifiable farm information from the dataset wherever possible and document the lawful basis and scope of any training use.
- Require an explicit pilot agreement before using farm observations or images to improve a model beyond that farm's service.
- Keep a model register: intended use, training data scope, limitations, evaluation results, version, owner and rollback path.
Before any result becomes public
Obtain written permission, remove farm identifiers unless the grower requests attribution, and publish only outcomes that match the agreed protocol. Concept visuals and examples must remain labelled as such.
What still needs to be completed
Before external lead collection or a live pilot, LivingShield needs a monitored contact channel, a formal privacy notice, terms for pilot participants, a data-processing agreement and an incident-response process reviewed for the jurisdiction and partners involved.