Privacy Policy
Effective date: 31 July 2026
Applies to: the GeoEDGE-MCP desktop extension (the MCP server you run locally in Claude Desktop) and the GeoEDGE licensing service it connects to.
Summary
GeoEDGE-MCP runs GIS operations locally, on your machine. We collect the minimum needed to validate your subscription — a random device identifier and your licence key’s activation history — and nothing else. The record of which tools you’ve called stays on your own computer and is never sent to us. When a tool fetches data on your behalf (satellite imagery, OpenStreetMap data, or your own database), that request goes directly from your machine to the service you pointed it at — we don’t see or store it.
What we collect
When you activate a GeoEDGE licence in the desktop extension, we collect:
- A device identifier — a random UUID generated on your machine the first time you activate. It is not a hardware fingerprint and is not derived from any personal or machine-identifying information. It exists so one licence key can be bound to a limited number of devices.
- Your licence key and its activation history — timestamps and status (active, past due, cancelled, and so on) each time the extension checks in with our servers, which happens on launch and roughly hourly while it runs.
- Account information, if you register an account to manage your licence: your email address and a securely hashed password. We never store your password in plain text.
We do not collect, and have no access to:
- The GIS data you work with — files, layers, geometries, raster pixels, database contents, or anything a tool reads, writes or computes. All of it stays on your machine, or goes directly to a service you configured yourself (see below).
- Your conversation with Claude, or the tool-call history the extension keeps for its own use.
- Any hardware fingerprint, IP-based tracking, or analytics and telemetry beyond what is listed above.
How we use it
- To validate that your subscription is active before enabling the GIS tools.
- To enforce the number of devices a single licence may be activated on.
- To let you and our support team manage your licence — view status, reset a device binding, and so on.
Local-only data (never sent to us)
Two separate places on your own machine hold data the extension keeps. Neither is ever transmitted to GeoEDGE.
- Your data storage folder — the folder you chose when installing the extension. Alongside the GIS files you work with, it holds a tool-call audit log at
_audit/audit.jsonl, which exists so the assistant can show its own recent work back to you inside a conversation. - A small configuration folder, holding your device identifier and your cached licence token:
- Windows:
%LOCALAPPDATA%\GeoEDGE - macOS:
~/Library/Application Support/GeoEDGE - Linux:
~/.config/geoedge
- Windows:
You can delete either at any time. Deleting the configuration folder simply means re-activating your licence key on next launch.
The map editor and its local web server
When you ask to see your data on a map, GeoEDGE starts a small web server on your own machine, bound to 127.0.0.1 (localhost) only, and opens an interactive map in your browser. It is reachable from no other computer, is protected by a token minted fresh for that session, and starts only when you ask for it — it stops when you close the editor, after 30 minutes idle, or when the application exits. Your spatial data is read from and written to your own storage folder and goes nowhere else.
One exception is worth stating plainly: if you choose a background map, your browser fetches map tiles directly from that provider — OpenStreetMap, Esri, EOX (Sentinel-2), or CARTO, depending on which you select, or any XYZ/WMS service you add yourself. That provider therefore sees the map area you are looking at, in the same way it would if you opened any web map. No tiles are fetched for a background you have not selected, and none of your own data is sent to them.
Third-party services you may connect through tools
Some tools fetch data from, or connect to, services you specify or invoke. GeoEDGE is a pass-through here, not a party to that exchange:
- Public open-data providers — OpenStreetMap (via OSMnx), GBIF (species occurrence data), Microsoft Planetary Computer/STAC (satellite imagery, ESA WorldCover land cover), GADM (administrative boundaries) and climate data providers (ERA5/CDS). These calls go directly from your machine to the provider using the parameters you or Claude supply. We never see the request or its result.
- Databases and services you configure — your own PostGIS connection string, or an ArcGIS REST endpoint you point a tool at. Your credentials and query results go directly between your machine and that service; GeoEDGE never receives them.
Each of these providers has its own privacy practices, which we don’t control. Check theirs if you have concerns about a specific one.
Data retention
- Licence, activation and account records are retained for the life of your subscription, and for 90 days after cancellation for support and billing-dispute purposes, after which they are deleted or anonymised.
- Local data — the audit log, device identifier and cached token — stays on your machine for as long as you keep the extension installed, and is removed when you delete the folders above.
Security
Licence tokens are cryptographically signed (Ed25519) and verified on your machine before any tool is enabled, so a network compromise in transit cannot forge a valid licence. All communication with our licensing backend uses HTTPS. Account passwords are stored using bcrypt hashing, never in plain text.
Children’s privacy
GeoEDGE-MCP is a professional GIS tool. It is not directed at, and not knowingly used by, children.
Changes to this policy
We will update the effective date above when this policy changes, and post material changes on this same page.
Contact
Questions about this policy or your data: support@geoedge.com.au