Privacy Policy

01 Overview & Nature of the Protocol

eo-mcp ("the Project", "we", "us", or "our") is an open-source implementation of the Model Context Protocol (MCP) enabling artificial intelligence agents (such as Claude Desktop, Cursor IDE, Codex, Google Antigravity, and autonomous scripts) to interface with Earth observation data.

This Privacy Policy explains what information is (and is not) collected, processed, and stored when you visit our website (eo-mcp.github.io) or install and execute the eo-mcp protocol software.

02 Zero Telemetry & Local Protocol Execution

When you run eo-mcp locally (e.g. via uvx eo-mcp or pip install eo-mcp):

• No Telemetry or Tracking: eo-mcp contains no analytics SDKs, user telemetry, behavior tracking, or crash-reporting beacons.
• No Prompt Logging: Neither your user prompts nor the AI agent's reasoning chains are captured, collected, or uploaded to any project server.
• Local Standard I/O (stdio): Communication occurs locally over standard input/output streams between your AI assistant application and the local eo-mcp Python process.
• Local In-Memory Cache: Downloaded raster chunks (Cloud Optimized GeoTIFF subsets) are read directly into ephemeral local memory or temporary system files and are never routed through our infrastructure.

03 Direct Upstream Geospatial Endpoints

When an agent initiates a search or raster computation (such as stac_search, calculate_spectral_index, or eo_geocode), requests are sent directly from your local machine to public government or third-party geospatial APIs:

• AWS Earth Search (Element 84): Public STAC endpoint for Sentinel-2 L2A and Landsat archives.
• Copernicus Data Space Ecosystem (CDSE): European Space Agency public STAC and Copernicus DEM catalogs.
• NASA CMR STAC: Public metadata queries for MODIS and VIIRS products.
• OpenStreetMap / Nominatim: Public reverse-geocoding to translate place names into bounding boxes.

These external services may record technical metadata (such as your external IP address, timestamp, and HTTP user-agent header) in accordance with their respective privacy and data usage policies. eo-mcp does not act as an intermediary proxy for these requests.

04 Credentials & Environment Variables

Certain optional features—such as direct full-granule downloads from the Copernicus Data Space Ecosystem—may utilize user-provided credentials (e.g., CDSE_USERNAME and CDSE_PASSWORD).

• All credentials are read exclusively from your local environment variables or client configuration.
• Credentials are never stored, transmitted to, or intercepted by the eo-mcp maintainers.
• Credentials are transmitted only to the authentic CDSE OAuth authentication service over encrypted HTTPS.

05 Website Visitors (eo-mcp.github.io)

Our documentation website is hosted as a static site via GitHub Pages:

• No Tracking Cookies: The website does not use cookies, advertising identifiers, or analytics services (such as Google Analytics or Facebook Pixels).
• GitHub Server Logs: GitHub may collect basic connection information (including visitor IP addresses, browser user agent, and request timestamps) to maintain security and deliver content, in compliance with the GitHub Privacy Statement.

06 Open Source Licensing & Third-Party Satellite Data

The eo-mcp source code is distributed under the permissive Apache License, Version 2.0. Satellite imagery and metadata accessed through the protocol are distributed under the open data policies of their respective space agencies (e.g., Copernicus Sentinel Data Policy, USGS Landsat Open Data Policy).

07 Contact & Questions

For inquiries regarding this Privacy Policy or project transparency, you may reach out via the official repository issue tracker or website:

• GitHub Issues: github.com/eo-mcp/eo-mcp/issues
• Project Website: sounny.com