Skip to main content
Our primary web application, Slack integration, and other related components are deployed onto the Google Cloud Platform (GCP).Any data we store is kept either in our PostgreSQL database (also securely hosted and managed by GCP) or in GCP’s BigQuery platform. All data is encrypted at rest in both Postgres and BigQuery.Two-factor authentication and IAM policies are applied to restrict access to resources within the Google Cloud Platform.
Yes. We are happy to provide access to our SOC2 data room on request (help@incident.io).
For transactional data processing (interacting with the Slackbot, and viewing the dashboard), the data is hosted in GCPs Belgium region, in europe-west1. We additionally have a hot standby in the Netherlands region, europe-west4.For analytical data processing (for our internal analytical use case), data is stored within Europe.We currently don’t send any data outside of Europe.
If you decide to stop using incident.io, we’re happy to delete application data upon request. Just let us know at help@incident.io.For removing specific sensitive data from alerts, escalations, incidents, or AI processing, see Managing sensitive data.
We currently use Slack as our sole authentication mechanism, meaning no additional authentication strategy or provider is required.However, your organisation chooses to authenticate with Slack — whether that’s directly or with a single sign-on provider — that same authentication mechanism is used to access incident.io.For the web application, temporary sessions are granted when you sign in with Slack. These periodically expire and are refreshed by redirecting the user through the OAuth flow. We can also revoke these tokens.
Yes, incident.io has been approved by Slack and can be found in the Slack App Store here.
You may need to delete your incident.io account or organization for various reasons, such as completing a trial period, discontinuing service, or wanting to start fresh.Since account deletion requires administrative verification, you’ll need to contact the incident.io support team to delete your account or organization. Here’s how to do it:
  1. If you’re requesting deletion of your entire organization:
    • Ensure you are the organization owner or have appropriate permissions (and are contacting us from your registered accounts email address or Slack)
    • Provide us with your organization URL (e.g. https://app.incident.io/your-org-name)
    • We’ll handle the deletion of your org, and cancellation of your plan
  2. If you’re requesting deletion of just your user account:
    • Unfortunately you can’t delete your account from incident.io, as it’s synced to your Slack profile. Whilst an org Owner/Admin can remove your permissions and set you back to just a Viewer role, the only way to completely delete the account would be deactivating your Slack profile.
If you’re an Enterprise customer using SCIM, you can de-provision users via SCIM.After your deletion request is processed, you will:
  • Receive confirmation from the support team that the deletion is complete
  • No longer have access to the account or organization
  • Stop receiving any automated emails or notifications
If you wish to use the service again in the future, you’ll need to create a new account - please reach out to us if you have any questions about getting it set up, and we’ll be happy to help!