Security & trust
A short, honest answer to "what happens to my data, how do I actually hear about a problem, and does anyone watch CertWatch itself" — see also our full status page.
What we collect
Account info (email, hashed password, alert settings), the hostnames/domains you configure and the check history we generate for them, billing details (handled by Stripe — we never see full card numbers), and standard request metadata for rate-limiting and abuse prevention. We don't sell your data or use your monitored hostnames for advertising. Full detail, including retention periods and third-party processors, is in our Privacy Policy.
How alerts are delivered
Email alerts ship on every plan over SMTP via Postmark. Starter and Pro accounts can additionally connect Slack, whose bot token we store encrypted and use to post to the channel you choose, and Pro accounts a generic webhook — that payload is sent directly from our servers to the URL you provide, so its handling past that point is subject to whatever you've connected it to (see the Privacy Policy's "Third-party processors" section).
Here's an actual alert, using the same wording CertWatch sends in production:
- From
- CertWatch Alerts <alerts@certwatch.sh>
- Subject
- Late: api.example.com — certificate expires in 12 days
The certificate served by api.example.com expires on September 28, 2026. Check its renewal and deployment before it expires.
We monitor our own monitor
A monitoring product that silently stops monitoring is worse than having none — so CertWatch's own reachability is checked continuously from outside our infrastructure (Grafana Cloud Synthetic Monitoring), independent of the servers being monitored. See our status page for the live checks: homepage, API health, login, and signup validation.
We go one step further for the monitoring pipeline itself: a dedicated canary check is pointed at a permanently-expired public test certificate, so it's designed to fail on every single run. We don't alert on that failure — it's expected — we alert if that check's result ever stops reporting entirely. That's how we'd notice our own monitoring had gone dark, rather than trusting that "no alerts" always means "everything's fine."
Data security
Connections to CertWatch use TLS in transit, and passwords are stored hashed, never in plain text. Our infrastructure runs on Fly.io, with Grafana Labs (Grafana Cloud, United States) processing our server logs, which include IP addresses, and metrics, Stripe handling payment data, and Postmark handling transactional email delivery — see the Privacy Policy for the full list of processors.
Email support@certwatch.sh, or use Support in the app. We aim to reply within one business day (Monday to Friday, US Pacific time).