Atlassian Rovo & Intelligence
Atlassian says customer inputs and outputs are not retained or used by third-party LLM providers for training, while Atlassian may use contributed metadata to fine-tune Atlassian-hosted open-source models subject to data contribution settings.
A support article states that Rovo and Atlassian Intelligence customer data is never used to train, fine-tune, or improve AI models. Atlassian's AI Trust FAQ separately says metadata contribution for Atlassian-hosted open-source model fine-tuning is subject to data contribution settings.
Organisation admins can deactivate AI-powered features and should review current data contribution settings. Eligible Cloud Enterprise customers can request Atlassian-hosted-only LLM routing.
Rovo can process organisational content the user can already access, including connected third-party sources. Permissions and connector scope remain material even when third-party LLM providers operate under zero retention.
Atlassian says Chat and agents retain inputs and outputs for 30 days for safety and security; indexed connector content is stored to serve Search, Chat, and agents.
The reviewed sources focus on provider retention, contribution settings, and permissions rather than one general human-review statement.
Foundational reference pages for teams adopting, deploying, and operating production AI with inspectable controls.