Data Sources
Source And Freshness Matrix
WarpIntel separates official public EVE data, community public context, user-provided inputs, browser-local records, first-party operations data, optional AI inference, and future authorized EVE SSO data. This matrix explains what each lane is used for, how freshness should be treated, and what must stay private.
Official
EVE ESI Public Data
- Current Use
- Public identity, market, route, system, sovereignty, killmail, profile, and server-health context.
- Freshness Rule
- Fetched from documented public endpoints with bounded requests, provider cache respect, and visible source notes where data can be stale.
- Public Visibility
- Derived public facts and advisory summaries may appear on public pages.
- Private Boundary
- No OAuth tokens, private scopes, account identity, or corporation-only data belongs in public output.
Official
EVE Static Data Export
- Current Use
- Static item, blueprint, market group, map, PI, industry, dogma, and fitting reference data.
- Freshness Rule
- Versioned static-data refreshes should happen deliberately, with generated files treated as source-labeled references.
- Public Visibility
- Static names, categories, and calculated planning summaries may appear in public tools.
- Private Boundary
- Static reference data should not be mixed with private character skill or asset assumptions without consent.
Community
zKillboard Public Context
- Current Use
- Killmail enrichment, public combat profile summaries, loss context, and kill/loss reference links.
- Freshness Rule
- Used as supporting public context with caching discipline and human-review warnings.
- Public Visibility
- Public killmail and public profile context may appear when a user asks for it.
- Private Boundary
- Public killboard behavior is not proof of current intent, trust, membership, or private access rights.
Official
EVE Image Server
- Current Use
- Character portraits, corporation logos, alliance logos, and type renders where public-image use is allowed.
- Freshness Rule
- Images should be treated as public visual references and refreshed by provider URL behavior.
- Public Visibility
- Public images may appear beside public profile, corporation, alliance, or item context.
- Private Boundary
- Official EVE marks and imagery should not be combined into the WarpIntel logo or used to imply endorsement.
User-provided
User-Pasted Game Text
- Current Use
- Local chat, D-scan, fittings, killmail notes, item lists, PI notes, wormhole notes, watchlists, and questions.
- Freshness Rule
- Treated as the user's current evidence, with prompts to refresh time-sensitive intel before acting.
- Public Visibility
- Only the user's local browser output should show pasted content unless they explicitly save or submit a request.
- Private Boundary
- Raw pasted analyzer inputs are not stored in account reports or public analytics.
Browser-local
Browser-Local Records
- Current Use
- Local reports, fit comparisons, watchlists, plans, and import/export workflows before account save is enabled.
- Freshness Rule
- Freshness depends on the visitor's browser state and export/import choices.
- Public Visibility
- Browser-local records stay on the visitor's device and are not visible to other users.
- Private Boundary
- Local-only records should remain separate from server queues, ads, public screenshots, and shared logs.
First-party
First-Party Operations Data
- Current Use
- Route smoke checks, service readiness, support queues, manual review queues, pageview counts, and workflow clicks.
- Freshness Rule
- Protected ops views show the newest database-backed signals and public health exposes only safe aggregate readiness.
- Public Visibility
- Public health and status pages show sanitized readiness only.
- Private Boundary
- Raw IP addresses, raw user-agent strings, raw pasted inputs, provider secrets, and EVE tokens stay out of public analytics.
First-party
Optional AI Inference
- Current Use
- Optional explanation, summarization, and next-step suggestions after deterministic local analysis.
- Freshness Rule
- AI output is a current interpretation of supplied evidence, not a source of truth.
- Public Visibility
- Public tool output can show AI-assisted wording only when the feature is explicitly enabled.
- Private Boundary
- AI output must not expose hidden secrets, private EVE data, or provider credentials and cannot replace human review.
Future authorized
Future Authorized EVE SSO Data
- Current Use
- Character, corporation, alliance, fleet, wallet, industry, asset, and mail-adjacent features only after feature-specific consent.
- Freshness Rule
- Refresh cadence and expiry should be visible beside private dashboards when these features are enabled.
- Public Visibility
- Private authorized data should stay out of public pages, ads, screenshots, analytics, and logs.
- Private Boundary
- Every private scope should be consented to for a specific feature and revocable from the account dashboard.
No-Secret Source Rule
Source notes explain evidence and freshness, but never expose OAuth tokens, API keys, database URLs, provider secrets, or raw private EVE data.