Privacy notice

Krishitaranga · Last updated 1 October 2026

Krishitaranga is a separate service operated by Dhivriddhi Consulting OPC Pvt Ltd. Its privacy terms apply to this service; the fact that it uses an indicofs.coffee subdomain does not make the INDICOFS website account or privacy settings control Krishitaranga.

Information we store

• Your sign-in account identifier, your phone number if you choose WhatsApp sign-in, and the basic identity information supplied by Google if you choose Google sign-in.
• Estate name, exact latitude/longitude, owner account identifier and creation/update times when you save an estate, and an estate contact number where supplied. A contact number is separate from a verified sign-in number.
• Weather/radar comparison records associated with saved estates, where collection is enabled, to evaluate forecast performance.
• Shared model forecast snapshots and a short-lived shared radar-motion cache. These shared weather caches are not estate address books.

Optional locality and browser storage

You may voluntarily save your district, taluk, hobli, gram panchayat and village while adding an estate in the dashboard. The app can suggest district, taluk, village and gram panchayat from estate coordinates using a dated Survey of India village-boundary dataset published by NWIC. The lookup runs on our server without sending your coordinates to a geocoding provider. You review or correct the dropdown selections before saving. Hobli is not supplied by that source. These user-confirmed details, their source and directory version are stored privately in your Supabase account metadata to understand pilot demand and support local guidance. The optional details are saved with your account when you save an estate. You can correct them in that form or remove previously saved locality details there. They are not verified boundaries and never determine eligibility or permissions. We do not collect cell-tower identifiers, infer village-level location from your IP address, or track device movement.

Essential browser storage keeps your sign-in session and app preferences. Locality details are not stored in tracking cookies. No optional advertising or analytics cookies are added by this feature. Using the estate form’s current-location button is a separate, browser-permission-based action to fill estate coordinates.

How we use it

We use estate coordinates to select and display local forecasts, radar and advisory information. Saved estate rows are protected by database policies that limit normal signed-in access to their owner. Authorized server processes can read coordinates to build shared model forecasts. We do not sell estate location data or expose your saved-estate list to other users.

Providers and storage

Authentication and application records use the app’s Supabase/Lovable cloud backend. Weather forecasts are obtained from Google Cloud BigQuery’s WeatherNext datasets; the lookup uses the nearest model grid cell (about 0.1°, or 10 km), not your estate name. Radar products come from IMD. The application retains radar frames briefly for motion estimation and removes old live-motion frames after about three hours. Separate private replay archives may retain deduplicated radar images for up to seven days and shared forecast snapshots for up to 90 days, subject to storage caps. Radar/model comparison records are linked to the saved farm for evaluation; the current interface does not apply a learned correction. Google and IMD process requests under their own service terms.

When Google’s short-range weather service is enabled, our server sends an approximately 1 km representative coordinate rounded from your estate location to the Google Weather API. The request does not include your estate name, phone number or account identifier. Nearby estates can share the same result. These Google Weather results stay in a disposable server-memory cache for at most ten minutes; we do not archive them, use them for training or add them to radar/model learning records. Shared usage counters contain only time-window request counts, with no coordinates or user identifiers.

When a Google map loads, your browser connects to Google Maps. Google receives normal request information such as your IP address and browser information, and map requests can reveal the area you view. Maps and authentication providers may process information outside India; a Mumbai weather archive does not mean every part of the service is hosted in India. We do not send your estate name or sign-in phone number in map requests.

Coffee advisor and optional connections

Questions, conversation context and any photos you choose to send to the coffee advisor are processed through Lovable’s AI gateway using a Google Gemini model to generate a reply. Do not include identity documents, passwords or private contact details in messages or photos. Conversations stay in memory while this page is open and clear when you leave or change accounts; use the chat’s delete control to clear them sooner. AI replies can be wrong and do not authenticate forwarded advisory messages.

If you create a private connection key and give it to Gemini or another compatible client, that client can retrieve the estates and weather/advisory data allowed by the key. This is optional. Treat the key and any connection link containing it as a password and revoke it in Settings when no longer needed. The receiving service handles retrieved information under its own privacy terms.

WhatsApp verification

You may optionally connect a verified Google account and verified WhatsApp sign-in to one grower account so both methods access the same estates. We store a private ownership mapping and short-lived linking requests; we do not store Google passwords or raw verification codes. An estate contact number alone does not grant login access. Accounts that both contain estates require a separately reviewed ownership merge.

When WhatsApp sign-in is enabled and you request a code, we send your phone number and a short-lived verification code to Authkey for delivery through WhatsApp. Authkey and WhatsApp/Meta process delivery information under their own terms. Estate coordinates and weather records are not included in these verification messages. Supabase verifies the code and manages your session; our app does not log verification codes. Limited security records help prevent abuse and excessive messaging. Requesting a sign-in code is not consent to marketing or a paid WhatsApp advisory subscription, which would require a separate choice. Google sign-in remains an alternative.

Your choices and deletion

You can remove an estate in the dashboard, which stops future forecast demand for it. For access to your account information, correction, account deletion, withdrawal of an optional choice, or a privacy complaint, email contact@dhivriddhi.in with enough information to identify your account. We will verify ownership of your sign-in phone number or Google account before acting, and delete or de-identify account-linked data unless retention is required for security or law. Shared model snapshots and radar frames are retained only to operate the service and are not associated with a named estate in the user interface.

This notice describes current app behavior and may be updated when the service changes. Read the service terms.