Overview
IncidentFlow helps teams investigate incidents by connecting operational signals from tools such as Slack, alerts, status pages, and engineering systems. We collect only the information needed to provide, secure, and improve the service.
Information We Process
We may process account details, workspace metadata, authentication records, integration configuration, product usage events, support requests, and technical logs. When you connect Slack, we store Slack workspace identifiers, bot metadata, granted scopes, allowed channel configuration, and encrypted bot credentials.
Slack Data
IncidentFlow reads Slack content only when a configured workflow or user action requires it, such as fetching an alert message or summarizing an incident thread. Slack access is limited to channels enabled by your workspace administrator. We do not sell Slack data, and we do not use Slack message content for advertising.
Slack message content is not used to train general-purpose AI or large language models. Where AI features are used, Slack content is processed only to provide the requested incident investigation or summary experience for your workspace.
Cookies And Analytics
We use essential cookies for site and application functionality. Optional analytics tools may be used only after consent, where required. See the Cookie Policy for details.
Your Controls
Workspace administrators can disconnect Slack, disable channel access, or remove the IncidentFlow app from Slack. If you uninstall IncidentFlow or request deletion, we will delete or de-identify associated Slack integration data within 14 business days unless retention is required for security, legal, or abuse-prevention reasons.
Security
We use access controls, encryption, audit logging, and tenant isolation controls to protect customer data. Slack bot tokens are stored encrypted and are never shown in the product UI.
Contact
For privacy questions or data requests, contact us at incidentflowio@gmail.com.