CropExplorer privacy notice

27 October 2026 · Teaching and exploratory crop modelling

Google connection

Google handles sign-in and your password. CropExplorer requests Earth Engine read-only permission. Your short-lived access token and chosen project ID stay in browser memory. The browser sends Earth Engine requests directly to Google using your own registered project. CropExplorer does not send your Google credentials to a computation server, write them to browser storage, or retain refresh tokens.

Sign out or close the tab to clear the connection. An Earth Engine request already sent to Google may finish. Connections expire automatically.

Inputs and results

Google receives the coordinates, dates and dataset requests needed to retrieve your environmental inputs. Crop simulations, uploaded weather CSVs, crop Excel workbooks and exported reports are processed locally in an isolated browser worker. Cloudflare hosts the website files and does not run the crop calculations or receive your uploaded files. Results live in browser memory until downloaded; reloading or closing the tab loses unsaved work.

Other services

Cloudflare delivers the website and scientific runtime files. Esri delivers map tiles and Google delivers fonts and sign-in resources. These providers receive ordinary network information and may retain infrastructure/security logs under their policies. Google tokens are not sent to the map or font providers. No analytics or results database is added by CropExplorer.

Your choices

You may sign out, close the page or remove the app’s authorization in your Google account. Revocation can affect other Explorer teaching apps that share Google consent branding. Contact the site operator through your course or institutional channel for questions.

Manage Google connections · Cloudflare privacy · Google privacy · Account setup