Cookie and Local Storage Notice

1. Authentication and essential operation

Firebase Authentication uses browser or device persistence to keep you signed in and manage authentication state. The storage mechanism depends on the browser and client; it may use IndexedDB or browser local storage, and the Expo app uses device storage. Google and Apple sign-in pages may use their own cookies or storage under their policies.

Signing out ends the current app session but does not necessarily remove every provider cookie, saved check, downloaded file, or preference. On a shared device, also clear saved checks and relevant site or app data. Blocking essential storage can prevent sign-in and related features.

2. Saved checks and preferences

The web app stores recent diagnosis history under cropintel_history in browser local storage, including results and photo thumbnails, with up to 50 recent records. It also remembers a selected farm and display theme. Local records can remain after sign-out until cleared or replaced; they are separate from diagnosis records saved in Firebase.

The Expo app uses AsyncStorage for recent results and thumbnails, selected-farm context, and accessibility or display preferences. User-specific local records are cleared on sign-out, but some preferences remain. The native iOS app retrieves saved checks from Firebase rather than using the browser's history store. Storage and permission behavior can differ by client.

3. Website analytics

The website includes Vercel Web Analytics, which sends page views and technical usage information when enabled in the deployment. Information may include page URL, referrer, time, general region, and browser, operating-system, and device type. Vercel describes this analytics product as using a request-derived hash instead of third-party cookies, with its visitor-session identifier discarded after 24 hours. That period does not describe retention of CropIntel accounts, diagnoses, or prediction logs.

The current product does not include advertising pixels, session-replay recording, or Flash storage. It has no cookie preference dashboard. Cookie-free analytics is not a guarantee that no information is transmitted or that every browser privacy signal disables analytics.

4. Maps, fonts, and provider requests

Loading maps, searching addresses, signing in with a provider, or downloading website fonts sends requests to the relevant service. Google Maps, Apple Maps, OpenStreetMap services, Nominatim, Firebase, and Fontshare may receive technical request information and the input needed for that feature. These requests may occur without a cookie being set. Provider storage and cookies are governed by the provider's policies.

5. Your controls

Use browser settings to inspect, block, or delete cookies, local storage, and IndexedDB for CropIntel. Use Clear in saved checks to remove local diagnosis history where available. Clearing local history does not delete cloud records; account settings and verified privacy requests provide separate deletion paths.

Manage camera, photo, and location permissions in browser or device settings. Use app-data controls to remove local mobile storage. Apply choices on each browser and device you use. Clearing data may sign you out or remove saved preferences.

Browser privacy tools may block analytics requests or third-party resources, but results depend on the tool. Do Not Track and Global Privacy Control are not an in-product switch for all storage or analytics. CropIntel does not currently sell user data or use targeted advertising. Contact us about any applicable opt-out right or concern.

6. Changes and questions

We update this notice and its effective date when relevant technologies or practices change. For questions about device storage, analytics, or privacy requests, contact cropintelar@gmail.com.