Termsby GlyphAI Trust changed Atlassian, Oct 26, 2026
Atlassian · Oct 26, 2026 · 4 added, 11 removed · seen by the weekly check
- Added: Rovo combines open-source, self-hosted models, and third-party hosted models to deliver an artificial intelligence experience tailored to you, your teams, and your workflows. These LLM providers will not store customer inputs and outputs or use this data to train their services. This approach prioritizes the privacy of your data throughout the entire process. To learn more about the technology that underpins our Rovo capabilities, visit this page .
- Removed: Rovo combines open-source, self-hosted models, and third-party hosted models to deliver an artificial intelligence experience tailored to you, your teams, and your workflows.
- Removed: These LLM providers will not store customer inputs and outputs or use this data to train their services. This approach prioritizes the privacy of your data throughout the entire process.
- Removed: To learn more about the technology that underpins our Rovo capabilities, visit this page .
- Added: By default, Rovo leverages dynamic routing between models. This means Rovo uses a mixture of Atlassian-hosted and third-party LLM providers. Eligible customers can elect to use only Atlassian-hosted LLMs, restricting LLM usage to those within the Atlassian Cloud boundary. This functionality is available by request for Cloud Enterprise organizations. To initiate this request, please reach out to your account team or customer support.
- Removed: By default, Rovo leverages dynamic routing between models. This means Rovo uses a mixture of Atlassian-hosted and third-party LLM providers.
- Removed: Eligible customers can elect to use only Atlassian-hosted LLMs, restricting LLM usage to those within the Atlassian Cloud boundary. This functionality is available by request for Cloud Enterprise organizations. To initiate this request, please reach out to your account team or customer support.
- Added: Rovo respects all of your existing permissions. In fact, two users may receive different results based on the content they have access to. The data a user has access to is not limited to the app they're working on. Due to the connected nature of our apps, as long as a user has access to a Jira work item or Confluence page, information can be pulled from across those experiences to inform a response (or output). This policy extends to any third-party connector you have in Rovo. All permissions set in our platform and your third-party connector source will be respected as long as they are set accordingly.
- Removed: Rovo respects all of your existing permissions. In fact, two users may receive different results based on the content they have access to.
- Removed: The data a user has access to is not limited to the app they're working on. Due to the connected nature of our apps, as long as a user has access to a Jira work item or Confluence page, information can be pulled from across those experiences to inform a response (or output).
- Removed: This policy extends to any third-party connector you have in Rovo. All permissions set in our platform and your third-party connector source will be respected as long as they are set accordingly.
- Added: Rovo Agents are designed with security and privacy in mind: they can only access and act on information that you, as the user, already have permission to see or modify. To protect sensitive data and ensure agents respect your organization's security boundaries, your existing access controls govern all actions available to agents. Please note, when automation rules call agents, the agent's access to knowledge is determined by the permissions of the 'connecting' user specified in the Rovo node, meaning the agent will retrieve information that this user is permitted to access.
- Removed: Rovo Agents are designed with security and privacy in mind: they can only access and act on information that you, as the user, already have permission to see or modify.
- Removed: To protect sensitive data and ensure agents respect your organization's security boundaries, your existing access controls govern all actions available to agents.
- Removed: Please note, when automation rules call agents, the agent's access to knowledge is determined by the permissions of the 'connecting' user specified in the Rovo node, meaning the agent will retrieve information that this user is permitted to access.
2 paragraphs left out as page noise
- Added (spacing or invisible characters only): Rovo is thoughtfully designed and deployed to uphold our Responsible Technology Principles.
- Removed (spacing or invisible characters only): Rovo is thoughtfully designed and deployed to uphold our Responsible Technology Principles .
About this change
- Page
- atlassian.com/trust/atlassian-intelligence
- Kind
- Documentation
- Text hash
- 630c533c8ff4 to 428134ce103f
- Dated by
- the weekly check that first read the new text