Security and data
Public data deserves public-grade protection.
How ai krishi protects farmers, officers and institutions, and what we are open about.
Safeguards
How we protect the platform
Authenticated, role-based access
Every protected action checks who you are and what your role and jurisdiction allow.
Jurisdiction scoping
District and taluka users are confined to their own area. No implicit cross-department access.
Encrypted connections
All traffic to the platform uses HTTPS (TLS).
Explicit-confirmation workflows
Extracted land-record data is never saved to a farmer’s record without the farmer’s confirmation.
Separate, controlled data store
Platform data is held in its own database, separate from other products.
AI under governance
Agents are monitored in an AI operations centre, and answers are tied to evidence.
Honest limits
What we are open about
- Some AI features send the content of a request, such as a question or a photo, to a third-party AI model provider for processing. In institutional deployments the provider and region are selected with the institution.
- Weather, satellite and market data come from external data providers. We send them locations and dates, not personal details.
- Institution-hosted deployment is the design intent. Formal installation packages for isolated, offline environments are on our roadmap and are not yet claimed as available.
- We do not claim third-party security certifications on this page. If an engagement requires them, we will say plainly where we stand.
Responsible disclosure
Report a vulnerability
If you believe you have found a security issue, write to contact@aikrishi.in with the details. Please give us reasonable time to investigate before disclosing publicly.