EVE Tools Suite's online tools run only on public, well-identified APIs. Here's exactly where the data comes from, how we cache it, and what we don't do.
Data sources
Item names and attributes, adjusted prices (EIV), order books, killmails, LP-store offers, dynamic (abyssal) items.
Killmail resolution (hash) and ISK values (total, destroyed, dropped), recent losses by character or ship.
Abyssal module resale estimates and per-type estimator reliability.
Aggregated market quotes (best buy/sell, volume) per station for the five major hubs.
CCP compliance
- Every ESI call carries an explicit User-Agent (name, version, contact, repository link), as required by CCP's Developer License Agreement.
- We respect the ESI error-limit budget (and stop before the floor), the "expires" cache header, and target datasource=tranquility.
- Read-only, public endpoints only. No interaction with the EVE client — no injection, memory reading, OCR or automation.
Caching
To stay fast and avoid hammering the providers, we cache server-side (in-memory) and via the CDN. Rough figures:
- Market data (appraisal, LP): ~5–10 min.
- Killmails and abyssal rolls: long-lived (these don't change).
- Adjusted prices (EIV): ~30 min; item names: session-long.
Privacy & security
- Nothing you paste or type is stored. No IP or request-body logging on our side.
- Rate limiting uses a SHA-256 hash of the IP, in memory only (never stored or logged).
- Pasted links are never fetched: we only extract an id from them, then query fixed hosts (anti-SSRF). Security headers are enabled (CSP, X-Frame-Options, etc.).
- Anonymous, cookieless usage analytics (Vercel), aggregated — no profiling.
- The roadmap poll stores only per-option vote counters — never who voted. One vote per browser (a localStorage flag).
Open source
All the code (desktop app and website) is open under the MIT license. You can verify exactly what the tools do: github.com/lacausecrypto/eve-tools-suite.