Security & Trust
You’re letting us watch production. Here’s what we collect, how we store it, and how we think about escalation.
Data we collect
- Targets you ask us to monitor (hostnames, ports, URLs, expected strings in responses).
- Probe results (latency, HTTP code, “socket refused,” etc.).
- Alert routing info (Discord webhook URL / channel, browser push subscription, email, escalation contact points).
How we handle it
- All traffic is encrypted in transit; stored data is access-controlled at rest.
- We do not publish or resell your outage data as marketing content.
- Role-based access lets you choose who inside your org can see monitors, alerts, and timelines.
- You control escalation policy (who gets paged, and under what conditions).
Why this matters
- Most “status pages” are built for PR. We’re built for ops, postmortems, and compliance.
- If something breaks at 02:00, we will wake the right humans — not just turn a box red on a dashboard.
- We preserve the incident timeline so leadership can brief accurately instead of guessing.
For full legal terms, see our Privacy, ToS, and Acceptable Use.