Opsgenie for Incident Management
Opsgenie is a modern incident management platform which empowers Dev & Ops teams to plan for service disruptions and stay in control during incidents. Opsgenie provides the tools needed to design actionable alerts, manage on-call schedules and escalations, and orchestrate communication & collaboration during incident resolution process.With Opsgenie’s incident management app for Slack, you can use Slack to communicate during incidents. By connecting Slack workspaces with Opsgenie, you can create Slack channels for your Opsgenie incidents, add incident responders to your Slack channels, update incident priorities, take incident actions, and help your team step in faster during incidents.Opsgenie’s Incident Management app for Slack enables you to:
* Create Slack channels for your incidents.
* Automatically invite the incident responders to the channel created.
* View incident details from the Slack channel.
* Take actions on the incident from the Slack channel.
* Add your Slack messages to the incident timeline in Opsgenie.
* Create Slack channels for your incidents.
* Automatically invite the incident responders to the channel created.
* View incident details from the Slack channel.
* Take actions on the incident from the Slack channel.
* Add your Slack messages to the incident timeline in Opsgenie.
Permissions
Opsgenie for Incident Management will be able to view:
Opsgenie for Incident Management will be able to do:
Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.
General
Developer
Atlassian
Company headquarters location
Australia
Terms of service
Privacy & data governance
Data retention policy
Please refer to this for more details:
https://www.atlassian.com/legal/privacy-policy#how-we-store-and-secure-information-we-collect
How long we keep information we collect about you depends on the type of information, as described in further detail below. After such time, we will either delete or de-identify your information or, if this is not possible (for example, because the information has been stored in backup archives), then we will securely store your information and isolate it from any further use until deletion is possible.
Account information: We retain your account information for as long as your account is active and a reasonable period thereafter in case you decide to re-activate the Services. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.
Information you share on the Services: If your account is deactivated or disabled, some of your information and the content you have provided will remain in order to allow your team members or other users to make full use of the Services. For example, we continue to display messages you sent to the users that received them and continue to display content you provided, but when requested details that can identify you will be removed.
Managed accounts: If the Services are made available to you through an organization (e.g., your employer), we retain your information as long as required by the administrator of your account. For more information, see "Managed accounts and administrators" above.
Marketing information: If you have elected to receive marketing emails from us, we retain information about your marketing preferences for a reasonable period of time from the date you last expressed interest in our Services, such as when you last opened an email from us or ceased using your Atlassian account. We retain information derived from cookies and other tracking technologies for a reasonable period of time from the date such information was created.
Data archiving and removal policy
Please refer to this for more details:
https://www.atlassian.com/legal/privacy-policy#how-we-store-and-secure-information-we-collect
How long we keep information we collect about you depends on the type of information, as described in further detail below. After such time, we will either delete or de-identify your information or, if this is not possible (for example, because the information has been stored in backup archives), then we will securely store your information and isolate it from any further use until deletion is possible.
Account information: We retain your account information for as long as your account is active and a reasonable period thereafter in case you decide to re-activate the Services. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.
Information you share on the Services: If your account is deactivated or disabled, some of your information and the content you have provided will remain in order to allow your team members or other users to make full use of the Services. For example, we continue to display messages you sent to the users that received them and continue to display content you provided, but when requested details that can identify you will be removed.
Managed accounts: If the Services are made available to you through an organization (e.g., your employer), we retain your information as long as required by the administrator of your account. For more information, see "Managed accounts and administrators" above.
Marketing information: If you have elected to receive marketing emails from us, we retain information about your marketing preferences for a reasonable period of time from the date you last expressed interest in our Services, such as when you last opened an email from us or ceased using your Atlassian account. We retain information derived from cookies and other tracking technologies for a reasonable period of time from the date such information was created.
Data storage policy
Please refer to this for more details:
https://www.atlassian.com/legal/privacy-policy#how-we-store-and-secure-information-we-collect
We use industry standard technical and organizational measures to secure the information we store. For more information on where and how we store your information, please see the Atlassian Trust, Trello Trust, and Jira Align Trust pages.
While we implement safeguards designed to protect your information, no security system is impenetrable and due to the inherent nature of the Internet, we cannot guarantee that information, during transmission through the Internet or while stored on our systems or otherwise in our care, is absolutely safe from intrusion by others.
App/service has sub-processors
no
Certifications & compliance
Data deletion request procedure
HIPAA compliant
no
While this app may offer HIPAA compliance, Slack does not have a business associate agreement with any third-party application providers, including those in the Slack App Directory, so you are responsible for validating the provider's compliance and executing an appropriate agreement before enabling.
Security
Supports Single Sign On (SSO) with the following providers
Google, Microsoft, Apple
Supports Security Assertion Markup Language (SAML)
yes
Has a dedicated security team
yes
Contact for security issues
security@atlassian.com
Has a vulnerability disclosure program
yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
yes
Has a bug bounty program
yes
Bug bounty program URL
Requires third party authorization/connections
no
Uses token rotation
no