AgriBhai Field - Privacy Policy

The app processes farm operational records owned by the organisation you work in. These include Farms, Blocks, Sections, mapped operational boundaries, crop context, Work assignments, Activities, Issues, evidence metadata and review or history records.

These records belong to the organisation, not to an individual user. Deleting one user account does not automatically erase an organisation’s operational or audit history.

The app may request foreground location for explicit actions you take, such as centring the Map, mapping or walking a boundary, recording field evidence, reporting an Issue, or other explicit evidence workflows.

When you explicitly capture or attach location, it can include latitude, longitude, accuracy and capture time.

You may capture or choose photos and short videos as operational evidence. Camera, microphone and photo-picker permissions are used only for those explicit capture or selection flows.

Evidence files are currently stored in private Cloudflare R2 object storage. Metadata and authorisation are held in the application backend, and access uses short-lived signed URLs rather than public evidence links.

Supabase is used for authentication, PostgreSQL operational data, row-level access control and server or Edge Functions.

For weather context, the Google Weather API may receive the farm, field or device coordinate needed to return weather for that place. The app routes this request server-side and the Google Weather server key is not shipped in the APK. Only the coordinate and context needed for weather is sent.

Tell Bijak and Smart Entry let you submit a natural-language field note so it can be interpreted into an editable structured draft.

The request is sent through the authenticated AgriBhai server boundary to Google Gemini using a server-side key. Gemini receives the note you submitted plus bounded organisation-authorised context needed to interpret it.

The AI does not write the operational record directly. You review and confirm the draft before it is saved through the normal flow.

The current server request disables provider-side interaction storage where the provider API supports it. This is not a guarantee about how the provider processes data under its own terms. Third-party AI processing is subject to the provider’s applicable service and data terms.

AgriBhai does not sell app data for advertising.

Data may be processed by infrastructure and service providers only as needed to operate app features, including Supabase, Cloudflare R2 and Google APIs such as the Weather API and Gemini. That processing is subject to those providers’ applicable terms.

Organisation scope and roles control access to operational records. Private evidence is not intended to be publicly browsable.

Reasonable technical safeguards are used. No system connected to the internet can be described as perfectly secure.

The categories below describe what the app may handle. Permissions such as location, camera, microphone and photo access are used on explicit actions, not collected continuously in the background.

You can request deletion of your personal app account data. Personal account data is different from organisation-owned operational and audit records, which may legitimately remain with the organisation.

Information is retained only where legitimately required for security, fraud prevention, legal or regulatory duties, accounting, or dispute and audit obligations. No retention period or turnaround time is published here.