Understand Rovo data handling and residency
10 min
Intermediate
By the end of this lesson, you'll be able to:
- Explore how Rovo handles your data
- Explain how data residency works for Rovo
- Set app data residency to a specific region
How Rovo’s AI models handle your data
Rovo uses multiple AI models to power features like Rovo Search, Chat, and agents. Some of these models are developed and operated by Atlassian. Others are third-party models such as ChatGPT, Claude, and Gemini.
Rovo sends requests to different AI models depending on what you are doing (for example, asking a question in Chat, summarizing a page, or generating an agent action plan). Using different models means Rovo always uses the most suitable one for each task, so you get the best possible response.
How your data is handled by AI providers
When Rovo sends content to an AI model, that content is used only to generate a response to you. Third-party AI providers do not store or retain your data, cannot use it to train their AI models, and do not own it. Your organization's permissions control data access, and Atlassian controls how content is transmitted.
👇 Click the boxes to explore how Rovo handles your data.
What is data residency?
Data residency means app data is stored in a specific location. Organization administrators can make choices about where to store app data. It’s important to know where your data is stored so you can meet local regulations and company security requirements
Every Atlassian app that supports data residency gives you two options:
- Use a global location: Atlassian moves data between regions for best performance. Choose this if you do not have specific regional requirements.
- Pin to a region: You choose a specific region, such as the USA, EU, or the United Kingdom, and lock your data to that location. Pinning means your data stays in that region and does not move. Choose this if your organization has regulatory or security requirements that specify where data must be stored.
The apps you can pin to a specific data residency location are Jira, Jira Service Management, Jira Product Discovery, Confluence, and Loom. Apps that do not support pinning, including Rovo, use the same residency location as the apps they depend on.
How does data residency work for Rovo?
Rovo does not have its own data residency setting. It uses the same region as your Jira data. If you do not use Jira, it uses the same region as your Confluence data.
👉 For example: If your Jira data is pinned to the EU, your Rovo chat logs and agent configurations will also be stored in the EU.
User account information, such as names and email addresses, cannot be pinned. Atlassian stores this data globally so that account lookups work quickly for users in any region.
App analytics and system logs cannot be pinned to a region.
Viewing Rovo’s data residency details
You can view the data residency details for any app on your sites, including Rovo. Checking this helps you confirm your data is stored in the location that meets your organization's regulatory or security requirements before you enable Rovo for your users.
To view residency details for Rovo:
- Go to Atlassian Administration and select your organization.
- Expand Data management and select Data residency.
- Locate Jira and select the More Actions menu (represented by …), then select View app details.
If the location value for Rovo shows not set, your data is stored across Atlassian's global cloud regions with no specific location set.
👇 Click the icons below to explore the Jira app details in the Data Residency page.
1
2
3
4
5
Pin Rovo data
You cannot pin Rovo data directly. Instead, Rovo follows the pin settings of Jira and Confluence. To control where Rovo data is stored, pin Jira or Confluence to your required region.
To pin Jira data to a location so that Rovo data follows it:
- Go to Atlassian Administration and select your organization.
- Expand Data management and select Data residency.
- Find the Jira app, then select Set location.
- Read the required steps, then select Next.
- Choose a residency location and select Next.
- Choose when you want the move to happen and select Next.
- Review the Marketplace apps that will also move to the new location and select Next.
- Review the summary of changes and read any warnings.
- Select Submit request.
Atlassian will schedule the move to your new data residency location based on the time you selected.
Which Rovo data is pinned?
Knowing which data is pinned helps you answer questions from your security or compliance team, such as whether chat logs and agent configurations are stored in the region you selected.
👇 Click the tabs below to explore which Rovo data is pinned when you pin Jira to a region.
Chat session logs record your Rovo chat interactions. They provide conversation history across your organization.
Data residency and Rovo data backups
Atlassian automatically backs up your Rovo data every day. These backups help Atlassian restore your Rovo data if something goes wrong.
👇 Click the tabs below to explore the two ways the backups are stored.
How was this lesson?
next lesson
Monitor Rovo using insights
- Monitor Rovo user and admin activity using the Audit log
- Access Rovo usage statistics with Analytics in Insights
- Monitor organization usage with Platform usage