← Back to blog

PagerDuty Β· Dev Tools

PagerDuty's Terms: Who Signs Matters Most

July 1, 2026

B
Safe

PagerDuty handles incident alerts and on-call scheduling for dev teams. We read their terms so you don't have to.

πŸ”΄ Whoever signs up needs actual authority to bind your company. This isn't a footnote. If the wrong person accepts these terms, your company might not be legally boundβ€”or worse, bound by someone who shouldn't have signed.

🟑 PagerDuty owns everything built into the service. The technology, the interface, the infrastructure. You're licensing it, not owning it.

🟑 Your contact info for alerts gets stored by PagerDuty. Phone numbers, emails, whatever you use for incident notifications. Standard practice, but it's there.

🟒 If you signed before December 21, 2023, your old agreement still applies. Not retroactively rewritten. That's how it should work.

🟑 Different flavors have different rules. Their hosted service, on-premise deployments, and third-party integrations don't all follow the same terms. Check which version you're using.

B-grade safety. Nothing catastrophic, but the authority issue at signup is real.

This breakdown is based on PagerDuty's publicly available Terms of Service and/or Privacy Policy. It may contain mistakes. Spot one? Let us know.