Privacy Policy

1. Information you provide

Account information includes your name, email address, account identifier, verification status, and account creation time. Firebase Authentication handles password credentials. If you choose Google or Apple sign-in where offered, we receive the account information made available by that provider, such as your name, email address, and provider identifier.

Farm information includes farm name, address, state, crops grown, acreage, optional coordinates, ownership, join codes, membership, and access requests. A farm access request includes the requester's name and email address for the farm owner to review.

Diagnosis information includes the crop photo you submit, selected crop, and prediction results. Saved diagnosis records include account and farm references, crop, disease match, confidence, and detection time. Browser and Expo local history can also contain photo thumbnails and results on your device.

Crop trouble reports include the author identifier, optional farm reference, crop, issue, severity, description, location, status, timestamps, acknowledgements, moderation reports, and any photo you choose to share. Support messages and feedback contain the information you send us. Do not include unnecessary personal information or information you lack permission to share.

2. Information from devices and service use

Our hosting, authentication, map, font, and other service providers receive technical request information such as IP address, browser or device information, and request time when your device connects to them. We use request information to operate the service, investigate failures, and limit abuse.

The website includes Vercel Web Analytics. When enabled in the deployment, it sends page-view and usage information such as page URLs, referrer, time, browser, operating system, device type, and general region. Vercel describes this product as using a request-derived hash rather than third-party analytics cookies. Cookie-free analytics still involves sending usage information to a provider.

The prediction service records operational information including request time, selected crop, model version, result, confidence, image quality measures, latency, and a cryptographic image digest. The digest is a fingerprint used to distinguish image inputs; it is not the photo itself. See the Cookie and Local Storage Notice for authentication persistence, preferences, and saved checks.

3. Why we use information and how predictions work

We use information to create and maintain accounts, send verification and password-reset messages, manage farms and access requests, return crop predictions, save checks, show local crop reports, respond to support, measure website use, improve reliability, and prevent fraud and abuse. We may also use information to comply with legal obligations and protect legal rights.

Crop diagnosis uses remote processing: submitting a photo sends it and the selected crop to CropIntel's server-side prediction service and the infrastructure hosting it. Predictions are not performed entirely on your device. The current diagnosis flow processes photo bytes for the request without saving the original diagnosis photo as a server-side photo record. Optional shared report photos are stored separately, as described below.

The current diagnosis flow does not automatically add submitted photos to a model-training dataset. Operational prediction records may be reviewed for reliability and model quality. This policy does not grant permission to reuse identifiable customer photos for unrelated training; any new photo-training program needs a separate explanation and any consent required by law.

4. What other users can see

The farm discovery directory makes farm names, addresses, states, crops, and owner identifiers available to other signed-in users so they can find a farm and request access. Entering a farm address is not a promise that it will be visible only to farm members. Farm owners can review access requests and membership information. Saved diagnosis records are associated with their creator; membership alone does not make every member's saved diagnoses visible.

Other signed-in users can read crop trouble reports, including descriptions, location information, author identifiers, acknowledgements, and shared photo links. Depending on the client and the values submitted, report coordinates may identify a precise place even when the interface describes the location as approximate. Do not post an exact location, personal address, or identifying photograph that you do not want other users to see.

A shared photo download link can be copied and accessed by someone who has the link. Other people may keep copies, screenshots, or exports of information you share. Removing a report or account cannot retrieve copies already obtained by others.

5. Service providers and other disclosures

Google Firebase provides Authentication, Firestore database storage, and Storage for optional shared report photos. CropIntel's hosting and inference infrastructure processes website requests and diagnosis uploads. Vercel receives website analytics information when enabled. Google and Apple receive sign-in requests when you choose their sign-in options.

Map and address features may contact Google Maps, OpenStreetMap tile services, Nominatim for address searches, and Apple Maps in the native iOS app. These providers receive the addresses, coordinates, map area, and technical requests needed for the feature you use. The website also requests fonts from Fontshare and related delivery services. These third parties have their own privacy practices.

We may disclose information when legally required, to protect rights and investigate abuse, to professional advisers assisting us, or as part of a business transfer subject to applicable law. CropIntel does not sell user data or use the current service for targeted advertising. Providing information to a service provider to operate a requested feature is described above.

Providers may process information in the United States or other countries where they operate. Privacy protections can differ by country. We do not promise a particular storage region or that information stays in your state or country.

6. Photos, location, and device permissions

Camera, photo-library, and device-location access are used for the features you choose and depend on your browser or operating-system permissions. You can deny or revoke permission in device settings, enter location information manually where supported, or choose not to use those features. Entering an address manually still supplies that address for processing.

Photos can contain embedded metadata, including location information. Some clients resize or re-encode images, but metadata removal is not guaranteed for every upload, especially shared report photos. Remove sensitive metadata and avoid photographing people, identifying documents, or private property details before uploading.

7. Storage, retention, and deletion

Account, farm, membership, and saved diagnosis records are stored in Firebase while needed for your account and requested features, unless removed through available controls or a verified request. Shared report photos are stored in Firebase Storage. Local history remains on the device according to the client and its clearing controls; browser saved checks are not automatically removed by signing out.

You can delete your account directly from account settings after identity verification and recent authentication. The deletion process removes the authentication account, profile, owned farms, memberships, access requests, saved diagnoses, authored crop reports, and report photos handled by that process. Deleting an owned farm also removes diagnoses and reports attached to that farm, including records created by collaborators. Save any records you need before deletion.

Account deletion does not automatically erase all operational logs, backups, copies on other devices, or acknowledgements and moderation entries on other people's reports. Individual report deletion and photo cleanup can depend on the client and whether cleanup succeeds. Contact us if a report or shared photo remains after a deletion attempt. You may also request removal of remaining information linked to you.

Operational logs, support correspondence, and backup copies may remain after account deletion. Retention depends on operational needs, configured rotation and backup schedules, and applicable legal or security requirements. The current service does not enforce one fixed retention period across these records. Contact us for a specific retention or deletion request; do not assume account deletion immediately removes every backup or log entry.

Browser and device data must also be cleared on each device. Use Clear in saved checks where available, clear browser site data, or use the device's app-data controls. Expo clears user-specific local records on sign-out, while display preferences may remain. Exports and copies held outside CropIntel are under the holder's control.

8. Your choices and privacy requests

You can review available account and farm settings, choose whether to post a report or photo, manage device permissions, clear local history, and delete your account. Withholding information required for a feature may prevent that feature from working. Service-related messages, such as password resets, are separate from any optional marketing communications.

For access, correction, export, deletion, a retention question, or an appeal of a request decision, email cropintelar@gmail.com. Using your account email helps us verify you, but you can contact us if you cannot access it or do not have an account. Describe the request without sending a password, access token, or unnecessary sensitive documents. We may ask for information reasonably needed to verify your identity and authority before releasing or changing protected information.

Depending on your residence and whether a privacy law applies to CropIntel, you may have rights to know about, access, correct, delete, or obtain a portable copy of personal information, appeal a decision, and opt out of legally defined sale, targeted advertising, or certain profiling. Authorized agents may submit requests with evidence of authority; we may also verify the account holder. We respond within applicable legal deadlines and do not discriminate for exercising protected rights.

We do not use crop predictions to make decisions about employment, credit, housing, insurance, or similar eligibility. The current service has no sale or targeted-advertising flow for an opt-out signal to disable. Browser Do Not Track or Global Privacy Control settings do not turn off essential storage, requested map services, or all analytics. This statement does not limit rights provided by applicable law.

9. Security and children

We use authentication, access rules, server-side validation, upload limits, and rate limits to reduce unauthorized access and abuse. No service or transmission is guaranteed secure. Use a strong password, protect your device, and contact us if you suspect unauthorized use.

CropIntel is not intended for children under 13. Do not submit a child's personal information. If you believe a child under 13 has provided personal information, contact us so we can investigate and take appropriate steps, including deletion where required. This policy does not represent that every user's age has been verified.

10. Changes and contact

We update the visible effective date when this policy changes. Material changes may also be communicated through an in-product notice or email, and we obtain consent where required before using information for a new purpose. A policy update does not by itself authorize previously undisclosed processing.

Contact CropIntel at cropintelar@gmail.com for privacy questions, requests, or concerns. If you need a postal contact for a formal request, ask us by email. Links to third-party services are provided for information and do not mean those providers have reviewed CropIntel.