Atlassian's model providers keep no inputs or outputs, and Atlassian keeps Chat and agent inputs and outputs for 30 days. From August 17, 2026, Free and Standard organizations contribute in-app data by default unless an admin opts out. Before security signs off on Rovo, put four decisions on record: the data contribution default, residency, connector scope, and agent web access.
When you need this
- Security, legal, or a works council reviews Rovo before a wider rollout.
- Confluence holds regulated or customer-confidential content.
- You plan to connect Google Drive, SharePoint, or Slack to Rovo.
Evaluation criteria
Data contribution by plan
Is your organization contributing in-app data, and can it stop?
Look forCheck the highest active plan, including trials, because it sets the contribution default. Free and Standard default in-app data to on, and Premium defaults it to off. All three always contribute metadata. Enterprise admins can change both. Set any exclusions for apps, spaces, or connectors.
Model providers and retention
Who processes prompts, and who keeps them?
Look forRovo runs on Atlassian-hosted open models and on OpenAI, Anthropic, and Google models under zero data retention. Atlassian keeps its own copy of Chat and agent inputs and outputs for safety review. Enterprise customers can request Atlassian-hosted LLMs only, which Atlassian says brings slight differences in performance and latency.
Where data lives
Is Confluence data pinned to your region, and does Rovo follow it?
Look forPin Confluence data on Standard, Premium, or Enterprise, and Rovo pins its in-scope data the same way. A live-site move takes up to 24 hours of downtime and up to 3 days of re-indexing. Check model processing separately, because Atlassian says providers such as OpenAI can process data outside the EU.
Connector scope and deletion
What will each connector index, and how is it removed?
Look forSet a blocklist or allowlist for Google Drive and SharePoint before connectors index the whole workspace. Confirm that source permissions sync and that indexed content is deleted within 30 days of a disconnect. One Hacker News admin fielded a question about an AWS address downloading every company document after Rovo connected.
Agent and prompt injection risk
Can an agent be tricked into sending data outside the company?
Look forGet the fix status from Atlassian in writing. On August 5, 2026, PromptArmor reported that a prompt hidden in a file made Rovo send Jira and Confluence content to an outside URL. Rovo's URL retrieval tool stayed available with web search off. PromptArmor disclosed the issue on May 23, 2026. Atlassian acknowledged it on May 25 and, according to PromptArmor, sent nothing further before publication. Atlassian's security advisories and monthly bulletins through September 2026, list no Rovo entry or fix. Keep web access off where agents do not need it, and limit which agents read untrusted uploads.
Certifications
Which audits cover Rovo?
Look forConfirm that the SOC 2 and ISO 27001 assessments cover Rovo. For HIPAA use, ask Atlassian Support to provision access within the listed boundaries. Review the Atlassian Customer Agreement and the Data Processing Addendum that cover Rovo.
Questions to ask vendors
- Which in-app data, spaces, and connectors are we excluding from contribution, and who approved that?
- Can we get Atlassian-hosted LLMs only, and what changes for users if we do?
- Has Atlassian fixed the URL retrieval issue PromptArmor reported on August 5, 2026, and where is the fix documented?
- Which Rovo features are out of scope for protected health information in our environment?
Red flags
- Assuming zero retention at the model providers means nothing about your pages is used or kept.
- Pinning Confluence data to a region without checking where the AI providers process prompts.
- Connecting whole Google Drive or SharePoint tenants with no blocklist.
- Leaving web access and file uploads open to agents that read untrusted content.
Products in this piece
Sources
- Official documentation
- 7
- Public source
- 4
- Atlassian Support: Data contribution settings
- Atlassian Support: Rovo data, privacy, and usage guidelines
- Atlassian Trust Center: Rovo AI security and trust
- Atlassian Support: Understand data residency
- Atlassian Support: Manage Rovo access
- Atlassian: Available Rovo connectors
- Hacker News comment on the data contribution setting missing from admin (Apr 20, 2026)
- Hacker News comment on Rovo indexing Google Docs and SharePoint (Aug 5, 2026)
- Hacker News comment on regulated reports in Confluence (Apr 20, 2026)
- PromptArmor: Atlassian Rovo exfiltrates data, bypassing controls (Aug 5, 2026)
- Atlassian Trust Center: Security advisories and monthly security bulletins, January to October 2026