Privacy

We don't collect personal information

Last updated: September 3, 2026

The short version: no accounts, no cookies, no third-party analytics or trackers, no personal data collected or stored. easysiem.com keeps exactly one number — a total page-view count, with nothing tying any view to who made it. Downloading a build doesn't send anything back to us, and the EasySIEM software you run never phones home to easysiem.com or anywhere else — every byte it handles stays on your own infrastructure.

What this site actually stores

A single self-hosted counter, incremented once per page load — the "X visits since launch" line in the footer. It has no third-party analytics service behind it (no Google Analytics, no Plausible, no anything) — just a small script on this server that reads one number, adds one, and writes it back. There's no cookie, no session, no per-visitor record of any kind — every page load counts the same whether it's you, a bot, or a page reload, and there's no way to tell those apart from the stored data because nothing distinguishing is ever stored. Nothing else on this site is tracked: no click tracking, no scroll depth, no page-to-page journeys, no device fingerprinting.

Google Fonts

This site loads two typefaces (Inter and JetBrains Mono) from Google Fonts, so your browser makes a direct request to Google's servers to fetch them — meaning Google sees your IP address for that request, the same as it would for any site using Google Fonts. We don't receive or see any of that; it's a direct connection between your browser and Google. See Google's own privacy policy for how they handle it.

Standard web server logs

Like effectively every website, the web server hosting easysiem.com keeps its own standard access logs (IP address, requested page, timestamp, user agent) as a normal part of running a web server — that's the hosting platform's own infrastructure, not something EasySIEM adds, accesses, analyzes, or exports. We're not going to claim a web server generates zero logs anywhere in the stack when we don't fully control that layer; what we can say is that nothing in this project reads, aggregates, or uses them for anything.

The EasySIEM software itself

This is the part that actually matters most for a security tool: the agents, ingest-api, and detect-engine you install never send data to easysiem.com or any third party. Everything they collect — Windows Event Log / Sysmon / auditd / journald data, Sigma detection alerts, agent heartbeats — goes straight to the OpenSearch instance you point them at, which you run, on infrastructure you control. There's no built-in telemetry, update-check, or license-phone-home of any kind.

The optional Tempo tracing integration uses OpenTelemetry, but only sends traces to a Tempo instance you configure via tempo_url — with that setting unset (the default), every trace call is a genuine no-op, confirmed directly in the source (server/ingest/tracing.go).
OpenSearch's and Loki's own built-in usage-reporting features are explicitly disabled in the config this project ships (server/opensearch/opensearch.yml, server/loki/loki-config.yaml).
Software updates aren't automatic — a new version means downloading a new installer yourself from this site (or building from source), the same one-time, anonymous request as any other page load here.

Changes to this page

If this ever changes — say, a future feature that genuinely needs to talk to an external service — it'll be reflected here first, with the "last updated" date above moved forward.

Questions

tyson@easysiem.com. The source is available (see the Download section) if you'd rather verify any of this yourself against the actual code than take it on faith.