Skip to main content
incident.io uses AI to help take away some of the overhead of incident response — whether that’s digesting huge amounts of information, communicating clearly to stakeholders, or distilling previous incidents into powerful learnings. Think of it like a helpful colleague chipping in or taking tasks off your hands when it can. Our AI features are powered by OpenAI, Anthropic, and Google Vertex. We send data on-demand to their APIs when required by a feature — this includes (but is not limited to) incident updates, summaries, and custom fields. This data is not stored by them and is not used for any reason other than to provide these services. This means it is explicitly not used for training purposes. Audio is handled by two further providers. Scribe joins your incident calls through Recall.ai, and ElevenLabs transcribes the call audio. We store the resulting transcript, not the audio. ElevenLabs also transcribes voicemail left on your call routes. Voicemail works differently: we store the recording as well as the transcript, so you can listen back to it. OpenAI, Anthropic, Google Vertex, Recall.ai, and ElevenLabs are all listed as our data sub-processors, so all customers automatically consent during sign up. However, if you’d like for us to stop sending data to OpenAI, Anthropic, or Google Vertex, and therefore disable all AI features, contact us at help@incident.io. You can also opt out of ElevenLabs on its own, which limits transcription to what your meeting provider’s captions give us. If your organization has opted out of any subprocessor, Settings → AI governance shows which ones and what that means for the AI features you can use. If your incident channels may contain sensitive data like credit card numbers or Social Security numbers, you can enable automatic redaction to strip this before it reaches AI providers. See Managing sensitive data for details. For more on how we store and handle data, see our Trust Center.