Effective October 18, 2026

Earth Pro Privacy Policy

Earth Pro is provided by Zac Henson. This policy covers the Earth Pro Mac application and these dedicated support pages.

Data stored on your Mac

Earth Pro stores your saved places, paths, polygons, image overlays, recent searches, imported address lists and their matches, and preferences locally. The optional Google Maps API key is stored in macOS Keychain. Imported files are read to provide the features you request. Exported images, KML files, and silent video recordings are saved to locations you choose. Earth Pro does not operate a developer-hosted account, geographic-content storage service, advertising system, or app analytics service.

Online maps and data providers

Online features make requests directly from your Mac to third-party services. Those services receive your IP address and the request data needed to provide the selected feature. Map locations are locations you view or search for; they are not necessarily your physical location.

• Apple Maps: Apple receives requests for maps, imagery, and searches made using Apple’s mapping services.
• OpenStreetMap: the tile service receives tile coordinates for the map areas you view.
• Google Maps: when you select Google, Google receives map and search requests and your supplied API key, and provides imagery or 3D content. The key is made available to the embedded Google map to authenticate those requests.
• NASA GIBS: imagery requests include the geographic area, imagery layer, and selected date.
• Wikimedia Commons and Wikipedia: nearby-content requests include the current view center and search radius. Images and linked articles may be loaded from Wikimedia servers.
• USGS: earthquake layers request a public earthquake feed.
• Open-Meteo: elevation requests include the coordinates being inspected, rounded to four decimal places.

When you search Data libraries, the selected ArcGIS, STAC (Earth Search, USGS or Copernicus), OpenAerialMap, Socrata or OpenDataSoft service receives your search text, selected geographic bounds, and any filters or dates needed for that request. Opening a source or asset link contacts that destination. Adding a supported layer requests its bounded geometry; discovery does not upload your saved project library. Providers may retain request or usage data under their own policies. Earth Pro does not control those services’ retention. Review Apple Maps privacy, Google privacy, OpenStreetMap Foundation privacy, Wikimedia privacy, NASA privacy, USGS privacy, and Open-Meteo’s terms and privacy information.

Google features are also governed by Google’s Terms of Service and the Google Maps/Google Earth Additional Terms. See Earth Pro terms for service and content restrictions.

In particular, Google Maps Platform logs may include your API account identifier, search terms and request parameters, IP address, request time, browser/operating-system headers, and response status. Google uses those logs for service improvement, support, monitoring, security, and capacity planning, and may retain them under its policies. Because you supply your own key, requests can be associated with your Google API account. Earth Pro does not use these requests for advertising or cross-app tracking.

Public and custom data sources

Opening Data discovers public-source metadata around your map center or a named area. Topic searches, area coordinates, and enabled-layer bounds are sent to the relevant ArcGIS/public publisher endpoints. NASA GIBS and Esri World Imagery/Wayback receive imagery tile and metadata requests for the selected area and date. Custom remote connections contact the source you enter. Imported files and location notes are stored locally unless you export them or share their contents with a connected client. Source update and imagery capture dates are displayed when supplied; lookup times and archive release dates are identified separately.

Optional local LLM control

The MCP server starts enabled unless you have switched it off, and remembers your preference. It opens an authenticated endpoint bound only to your Mac’s loopback address. A connected client with the session token can access supported app state and tools, including map navigation, searches, geometry, image overlays, and recording controls. Earth Pro does not itself send your app state to a cloud LLM. A client you connect may send tool results to its own service or model provider under that client’s policies. Disabling local control stops the server. Do not share its token with an untrusted client.

Choices, retention, and deletion

Choose a map provider, disable online layers, remove your Google key, and turn off local MCP control through the app. Remove saved places and overlays in their respective controls and clear recent search history through the history menu. Local app support data and preferences remain until removed. To remove all local data, quit Earth Pro, remove its EarthPro application-support data and preferences from your user Library or sandbox container, and remove its key using the app’s Google settings or Keychain Access. Exported files, videos, backups, and copies shared with another app remain until you delete them from those locations. There is no Earth Pro developer-held account or geographic library to delete.

Support and website

If you email support, your email address and any information you choose to send are received by the developer and email providers to handle your request. Please do not send credentials or sensitive map files. These dedicated Earth Pro support and privacy pages do not include analytics scripts. Other pages on zachenson.com may use website analytics under their own notices.

Changes and contact

This policy will be updated when Earth Pro’s data practices change. Send privacy questions and deletion requests for support correspondence to feed-20.coal@icloud.com.

Open-source code and commercial-use limits

The distributed app’s included data/service configuration is not cleared for commercial use as-is. Earth Pro’s original code and artwork remain open source under MIT, which permits commercial use of that code. MIT does not license third-party maps, datasets, imagery, APIs, or services.

The app’s online elevation feature uses Open-Meteo’s free API, which permits noncommercial use only. Commercial deployments must replace or properly license restricted services and verify every enabled data source and intended export, screenshot, or recording. The stock app does not offer a commercial Open-Meteo endpoint/key setting; a compliant alternative requires an adapted build or service configuration. An API key for another provider does not remove these obligations.

Some sources permit commercial use, including public-domain datasets; others carry service, attribution, redistribution, or other conditions. Public access or catalog inclusion is not permission for commercial reuse. This notice does not add restrictions to MIT-licensed code. See the full third-party notices and code license.