Privacy
Last updated: 2026.
This website
fatalguard.com is a static marketing site. It sets no cookies and stores nothing in your browser. We count visits with PostHog (EU cloud), cookie-free: events go through this site's own /ingest route, not straight to a third party, and no identifier is kept on your device. There is no advertising or cross-site tracking. Fonts are loaded from Google Fonts; your browser contacts Google's servers to fetch them.
The plugin
FatalGuard runs entirely inside your own WordPress installation. Your error data — logs, captured fatals, and history — stays on your server. FatalGuard does not phone home with your site's error contents.
Alerts are delivered through the channels you configure (Telegram, Slack, Discord, email, or a webhook). When an alert fires, the error details are sent to that provider so it can deliver the message — that is the point of the feature, and it happens only for channels you turn on.
The optional AI access (MCP) endpoint is read-only and protected by a scoped key you generate and can revoke at any time. It is off until you generate a key. It exposes your logs and captured fatals only to clients you connect, and FatalGuard never contacts an AI service itself.
Purchases
Paid licenses are processed by our payment provider, which handles your billing details under its own privacy policy. We never see or store your full card number.
Questions
Reach us on the wordpress.org support forum.