Trust needs
clear answers.
Understand data access, integrations and hosting before choosing your setup.
Clear answers.
Useful next steps.
Who owns our operational data?
Your organisation retains ownership of its operational data. Rights relating to grower information, sharing and access are defined in the relevant agreements.
Where can iCrop be hosted?
AWS cloud infrastructure, EEA hosting and on-premise deployment are available options. Choose the model and agree operating responsibilities during the technical review.
What does the ISO 27001 reference mean?
It refers to the hosting provider’s certification. It is not a claim that iCrop or AppsforAgri is ISO 27001 certified. Review the applicable certificate and scope for the chosen hosting arrangement.
Can user access be restricted?
Yes. Role-based permissions support controlled access. Define the relevant roles and scope across agronomists, teams, crops and regions for your organisation.
Can iCrop connect to our existing systems?
Yes. The API-first platform supports ERP, CRM, farm-system and reporting integrations. The data flow, interface availability and development required are scoped per project.
What is the difference between offline capture and AI Assist?
Offline field capture and synchronisation support work away from connectivity. AI Assist adds voice-based structuring of input; its processing and connectivity requirements are confirmed for the available workflow.
Is Taro already the live AI Assist feature?
No. AI Assist is available as a capture capability. The broader Taro experience on this site is a separately labelled product preview.
Does iCrop certify our compliance?
iCrop supports record-keeping and operational workflows. Compliance or certification depends on the applicable programme, configured process and evidence.
Discuss your data and security requirements.
Review the workflow, the data and the system boundaries together. Agree a practical scope before implementation.