> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# AI data handling

> How incident.io uses AI and handles AI data

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 and Anthropic. We send data on-demand to their API when required by a feature — this includes (but is not limited to) incident updates, summaries, and custom fields. This data is not stored by OpenAI or Anthropic and is not used for any reason other than to provide these services. This means it is explicitly *not* used for training purposes.

OpenAI and Anthropic are 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 or Anthropic, and therefore disable all AI features, contact us at [help@incident.io](mailto:help@incident.io).

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](/admin/managing-sensitive-data#ai-data-redaction) for details.

For more on how we store and handle data, see our [Trust Center](https://incident.io/security).