What EDDA collects

The short version: nothing that identifies you, ever. The long version is below, and it's genuinely short, because the list is genuinely short. EDDA is open source, so every claim on this page can be checked against the code.

EDDA's design law, written into the project's own rules: EDDA is not a surveillance tool. Nothing it collects, aggregates, or displays may identify a commander or reveal where any individual is or has been. When a feature would need that data to work, the feature changes shape or doesn't ship.

Anonymous usage data (on by default; one checkbox turns it off)

If you leave "Send anonymous usage data" enabled, EDDA sends:

App version and operating system — e.g. 0.3.0, windows x86_64.
Warning and error signals — which internal component warned or failed (a code location and severity), so bugs get found. Never the message text, because message text can mention star systems, and where you fly is your business.
Performance timings — how long route plotting, trade searches, data sync, and data loading took. Durations only.
Which features are switched on — the toggles, so we know what's actually used.
Two search settings, as plain numbers — the price-freshness window and the jump range you plot at (e.g. 2 h, 48 ly), pooled across everyone so the app can ship better defaults. The numbers only — never what you searched for, or where.

It never sends:

Your commander name, or any account, name, or ID of any kind.
Your position, your routes, or any star system or station name.
Anything from your journal — cargo, credits, scans, missions, none of it.

Reports carry no account, no name and no system. The server folds each one into running counters the moment it arrives and keeps nothing per report, so there is nothing to link back to anyone.

Problem reports (only when you press Send)

The Report tab sends what you typed, plus your app version, your OS and the time you pressed the button. Attaching the day's log is a separate checkbox, off by default, and labeled with exactly why: logs can contain the names of systems you visited. Nothing is sent until you press the button.

The live activity map

The galaxy heatmap is built from the community's public EDDN data feed that every Elite tool shares — not from EDDA users. EDDA only listens to that feed; it never uploads anything to EDDN. The map is deliberately blurry: cells are a hundred light years wide, nothing on it can name a system, and the map cannot be clicked to identify anything. It's weather, not surveillance.

Update checks

Now and then the app fetches our server's current version file, the same way a browser fetches a page. Nothing about you travels with that request. An update only downloads and installs when you choose to, and the app checks its signature before it will run it.

The ship computer (only with your own key)

The talking ship computer is off unless you add your own Anthropic or OpenAI API key in Settings. The key lives in your operating system's credential store, never in a file EDDA writes. When you ask it something, your question and the journal facts needed to answer it (your ship, where you are, what you carry) go to that provider, under your own account. None of it passes through EDDA's server, and we never see it.

Everything else stays home

Your journal, your settings and your marks live on your machine and are read there. Nothing in them is uploaded. The voices run on your machine too: choosing the Kokoro engine downloads it once from GitHub, and after that nothing it says or hears leaves your computer.

Changes to what's collected will be reflected on this page before they ship. EDDA is an unofficial third-party tool. Elite Dangerous © Frontier Developments plc.