Privacy Policy

Privacy

We respect your privacy. This page explains the small amount of data we collect and why.

What we collect

We use Plausible Analytics, a privacy-friendly web analytics tool that we self-host on our own infrastructure. Plausible is cookie-free and GDPR-compliant by default: it does not use cookies, does not track you across sites, does not assign you a persistent identifier, and does not collect personal data.

For each page visit, Plausible records:

  • The page URL you visited
  • The HTTP referrer (the site that sent you here, if any)
  • A hashed signal derived from your IP address, the day, and the current site, used only to count unique daily visitors. The hash is rotated daily, cannot be reversed to recover your IP, and is discarded after the day ends.
  • Your browser, OS, and device type (parsed from the User-Agent header your browser sends with every request)
  • Your country and region (derived from your IP address; your IP itself is not stored)
  • The screen size of your browser

That’s it. No cookies, no fingerprinting, no cross-site tracking, no sale of data to third parties. The full list of what Plausible collects is documented at plausible.io/data-policy.

Where the data lives

The Plausible instance runs on our own hardware. The data never leaves our infrastructure. We do not share it with anyone.

Opting out

Our analytics are served first-party (same-origin), so most ad-blockers won’t catch them. We give you two opt-outs that work regardless; both stop the analytics script from ever loading:

  • Enable Do Not Track in your browser. When it’s on, we load nothing and send nothing.
  • Set a local opt-out flag: run localStorage.plausible_ignore = "true" in your browser console. We honor it on every page, on every visit.

What we do not do

  • We do not use Google Analytics or any third-party tracker.
  • We do not show advertisements.
  • We do not sell, share, or rent any visitor data.
  • We do not use cross-site cookies or any persistent identifier.

ICDB (the product)

The released ICDB binary reports two things by default, both to infrastructure we run ourselves. Neither ever includes your threat data, indicators, uploads, queries, or account details.

Usage analytics. The same anonymous, cookie-free Plausible described above: page views inside the app, plus a small set of product events — that a server started, that a query ran, that an update was applied, which release you are on, and whether you run SQLite or Postgres. These carry no identifier that persists from one day to the next, so we can count installs but cannot follow one over time. Self-hosted installs report separately from our own hosted instance.

Crash reports. When something breaks, the error message and stack trace are sent to our self-hosted GlitchTip so we can fix it. This is how we learn an install failed to start.

Turning it off

Any organization admin can turn either off, independently, at Settings → Profile → Telemetry in the app. The change takes effect immediately for anything the browser sends; the server stops reporting crashes at its next restart.

You can also disable them before the first boot:

  • --analytics-domain "" disables usage analytics.
  • --sentry-dsn "" disables crash reports.

A binary you build yourself from source has neither configured, and sends nothing at all.

Contact

Questions: contact@pid4.io.