Subprocessors
1. Core service subprocessors
| Provider | Purpose | Data |
|---|---|---|
| Render (Render Services, Inc., USA) | Application hosting, database storage, backups | All stored account and monitoring data |
| Resend (email delivery) | Sending verification, reset, and alert emails | Recipient email address, message content |
| Stripe | Subscription billing (Pro) | Billing identifiers, payment details (handled by Stripe) |
| Browser push services (Apple, Google, Mozilla, Microsoft) | Delivering Web Push alerts | Push subscription endpoint, alert content |
2. User-selected integrations
These are optional and activated only when you connect them. Data is sent at your instruction and governed by that provider's terms and privacy policy. For how we process personal data on your behalf, see our Data Processing Agreement.
| Provider | Triggered when | Data sent |
|---|---|---|
| OpenAI / Anthropic / Google (Gemini) / your Custom AI endpoint | You request an AI incident diagnosis | Incident evidence, timeline, recent results, cached runbook excerpts (never your stored API key inside the prompt) |
| Slack / Discord / your webhook endpoint | You enable that alert channel | Alert title, summary, and incident link |
| Your monitored targets | Each scheduled or manual check | The request you configured, from Calmping's probe |
3. Changes
We will update this page before adding a new core subprocessor. Material changes will be announced where required.
4. Contact
For questions about our subprocessors, use the contact page.