Sub-processors
These are the third parties that can touch what you put into your workspace about other people — the addresses of the people you page and the subscribers to your status page. For that data we are your processor, so the data processing terms require us to keep this list current and to give 30 days notice before adding to it.
Tools that measure or support our own site — analytics, error reporting, a login provider, whatever we test a page with — are not on this list and do not belong on it. They never see workspace content, and for the data they do see we are the controller rather than your processor, which the privacy policy covers by category. Anything that needs a cookie asks you first regardless.
A row with no name is a job we do not currently use anyone for. The rows for hosting and email delivery must be filled in before the hosted service accepts signups.
| What for | Who | Where | What they see |
|---|---|---|---|
| Hosting: servers, database and backups | Nobody — not in use | European Union | Everything stored in the product |
| Email delivery | Nobody — not in use | European Union | Recipient address and the content of the message we send |
| Telegram paging, only for workspaces that add a Telegram channel | Telegram Messenger Inc. | Outside the EU; standard contractual clauses | The chat id you configure and the text of the alert |
| Machine learning features, only where a feature sends data to a model | Nobody — not in use | — | Only the text that feature needs; never used to train a model |
| Browser push, only for devices where somebody turned notifications on | Google, Mozilla or Apple, whichever made the browser | Outside the EU; standard contractual clauses | The device address their browser issued, and an alert encrypted so they cannot read it |
What the table means
The table above is the whole list as it stands today. If a provider is not on it, we are not using one for that job with your workspace data — and if we start, it appears here first, with the notice period below.
Not sub-processors at all
Integrations you connect are not on this list and never will be. When Sentry, Grafana or your own script opens an incident here, they send us data — we send them nothing. When an alert goes to Slack, Telegram or a webhook, it goes where you told it to go. Either way the other service is a party you chose and control, not somebody we hired to process your data, so adding one to the catalogue changes nothing here and triggers no notice.
The same is true of a two-way integration, where we hold a credential you issued: we are acting on your instruction inside your own account, under whatever terms you agreed with that service.
Google and GitHub are not sub-processors. If you choose to sign in with one of them, you send yourself to a service you already have an account with, and it hands back your email address and name. We send them nothing about you that they did not already hold. Sign in with a password instead and neither is involved.
Being told about changes
This list changes when we hire somebody new to run part of the service, which is rare — a different host, a different mail provider. Account holders are emailed at least 30 days before that happens, which is what gives you time to object. To follow changes without an account, ask at [email protected] and we will add you to that notice.