Security & Privacy
Local-first data ownership, auditable open source, and a short list of things EDK deliberately does not do.
Documentation navigation
Data ownership
EDK is local-first. In local and offline modes, searches, routes, and compute run against a SQLite index on your machine. Your queries, your uploads, and your results never leave your environment. There is no telemetry in the SDK, CLI, or MCP server, and the data files are ordinary SQLite you can inspect, back up, or delete.
Open source
EDK is open source. You can read the code that handles your queries, run audits, pin an exact version, and file issues in the open. See the repository at github.com/edk-earth/edk.
Auth and accounts
Accounts use better-auth with server-side sessions. Sessions are revocable, and API keys are scoped per project so a leaked key never implies account access. EDK loads no third-party trackers or analytics scripts in the docs or dashboard, and the SDK ships no telemetry.
Payments
Payments are processed by Stripe. EDK never sees or stores your card details; it keeps only the subscription and billing state Stripe reports.
Hosted queries and responsible use
| Mode | What the EDK hosted service sees |
|---|---|
| Local / offline | Nothing. No requests are made. |
| Hosted / remote | The request body: features, areas, filters, and your API key. Results are yours to cache and store. |
Hosted requests are used to serve the request and to protect the service from abuse, not to profile end users. If even request-level privacy is a concern, run local mode. When you build with EDK, you remain responsible for what your own application collects from its users.