EveDeck IntelEveDeckPrivacy Policy
PRIVACY

Privacy Policy

Last updated: 17 September 2026

The short version

EveDeck Intel runs entirely on hardware you own. The daemon runs on your PC, the app runs on your tablet, and they talk to each other across your own local network. There are no accounts, no sign-up, and no analytics or telemetry of any kind. The EveDeck project operates no server that receives anything from either half.

What the daemon reads

The chat log files EVE Online writes to your own disk, and nothing else. It does not read the game's memory, does not attach to the client, and sends no input to it. It reads only the channels you tick in the settings window, plus Local, which is how it knows where your characters are.

What is stored, and where

  • Settings — an eveintel.properties file beside the daemon launcher, holding your channel selection, regions, port and log folder.
  • A diagnostic log — eveintel.log, also beside the launcher, rewritten each time the daemon starts. It is never uploaded anywhere.
  • A name cache — character names and portraits looked up from EVE's public ESI service for the pilots named in intel, cached so they are not fetched twice.
  • On the tablet — the address you typed, the character you are following, and your alert settings.

All of it is on your own devices. Deleting the daemon folder and uninstalling the app removes everything.

The one outbound connection

The daemon contacts EVE Online's public ESI service to turn character names into portraits and to check server status. Those requests carry a character or type name and nothing about you — no identifier, no account, no authentication, because the endpoints used are public and require none. If the daemon cannot reach ESI, everything else keeps working without portraits.

This website

This site has no analytics, no tracking scripts, no advertising and no cookies. It sets no cookie of any kind. Downloads are served from GitHub, so following a download link is a request to GitHub and subject to their privacy policy, not ours.

The web server keeps standard access logs — IP address, time, page requested — for operational purposes, as any web server does.

Your network

The connection between the daemon and the tablet is unauthenticated and unencrypted by design, because it carries information already visible to everyone in the channel and lives on a network you control. Anyone who is already on your LAN can read it. That is the reason the documentation says, in several places, not to forward its port to the internet.

Changes

If this policy changes, the date at the top changes with it. Since nothing is collected, there is nothing here we could quietly start doing more of.