Jira (Government) & Slack Integration

Jira (Government)

Description Features Permissions Security & Compliance

Jira for Government is a FedRAMP Moderate-compliant version of the trusted Jira Cloud integration for Slack, designed specifically to meet the rigorous security and compliance requirements of public sector agencies and regulated organizations.
Effortlessly connect Jira projects with Slack channels and direct messages for streamlined collaboration.
Instantly receive critical issue updates, create new tickets, and manage workflows—all without leaving Slack.
Designed for government teams to accelerate resolution times, enable advanced issue previews, and stay aligned with federal regulations.
An active subscription to Jira is required to use this app in Slack.

Jira (Government) will be able to view:

Jira (Government) 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

Privacy & data governance

Data retention policy

For the most up to date policy information, always refer to: https://www.atlassian.com/legal/privacy-policy 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 anonymize 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

For the most up to date policy information, always refer to: https://www.atlassian.com/legal/privacy-policy Deactivate your account: If you no longer wish to use our Services, you or your administrator may be able to deactivate your Services account. If you can deactivate your own account, that setting is available to you in your account settings. Otherwise, please contact your administrator. If you are an administrator and are unable to deactivate an account through your administrator settings, please contact the appropriate support team (see Atlassian, Jira Align, or Trello support pages). Please be aware that deactivating your account does not delete your information; your information remains visible to other Service users based on your past participation within the Services. For more information on how to delete your information, see below. Delete your information: Our Services and related documentation (see Atlassian Documentation and Trello Help) give you the ability to delete certain information about you from within the Service. For example, you can remove content that contains information about you using the key word search and editing tools associated with that content, and you can remove certain profile information within your profile settings. Please note, however, that we may need to retain certain information for record keeping purposes, to complete transactions or to comply with our legal obligations. Request that we stop using your information: In some cases, you may ask us to stop accessing, storing, using and otherwise processing your information where you believe we don't have the appropriate rights to do so. For example, if you believe a Services account was created for you without your permission or you are no longer an active user, you can request that we delete your account as provided in this policy. Where you gave us consent to use your

Data storage policy

For the most up to date policy information, always refer to: https://www.atlassian.com/legal/privacy-policy 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. If you use our server or data center Services, responsibility for securing storage and access to the information you put into the Services rests with you and not Atlassian. We strongly recommend that server or data center users configure SSL to prevent interception of information transmitted over networks and to restrict access to the databases and other storage points used.

Data center location(s)

United States

Data hosting details

Cloud hosted

Data hosting company

AWS

App/service has sub-processors

yes

Guidelines for sub-processors

https://www.atlassian.com/legal/sub-processors

App/service uses large language models (LLM)

yes

LLM model(s) used

Gemini

LLM retention settings

Data residency gives you control over where your in-scope app data for Jira, Jira Service Management, and Jira Product Discovery is hosted. Details - https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/

LLM data tenancy policy

While our customers share a common cloud-based IT infrastructure when using Atlassian’s products, we have measures in place to ensure they are logically separated. More details - https://www.atlassian.com/trust/security/security-practices

LLM data residency policy

Certifications & compliance

Security