# Jira / Atlassian Intelligence

## Kurzbeschreibung
**“Projects that practically manage themselves.”**


**Jira **is a cloud and data center platform for project, task, and work management. 


In its AI-enabled form, Jira combines classic planning, tracking, and workflows with Rovo AI, for example to create work items from Slack/Teams, summarize content, break down complex work into tasks, and provide agentic assistance and search across the Teamwork Graph.

## Claim
Projects that practically manage themselves

## Geeignet für
- API Integration
- Automation / Workflows
- Productivity & Planning
- Programming / Software Development
- Project Management
- Knowledge Management / Internal Search

## Kernfunktionen
- Task Management
- Automation
- Project Management
- Text Generation
- Knowledge Base

## Preismodell
- **free:** For small teams; unlimited goals, projects, tasks, and forms, limited number of users and limited automations.
- **subscription:** **Standard** More user/team capability, Standard Support, more automations, data residency, and basic scaling.


**Premium **Everything in Standard plus unlimited storage, 99.9% SLA, 24/7 Premium Support, Project Archiving, Admin Insights, IP Allowlisting, Sandbox, Release Tracks, more automation, and Atlassian Intelligence.
- **other:** **Enterprise **Enterprise scaling, centralized administration, advanced security/compliance features, Enterprise support, and stronger data/AI control.


**Marketplace / Rovo / Atlassian Intelligenc**e Additional apps, AI features, agents, search, and automations depending on product and license scope.

## DSGVO und Datenschutz
**Gesamteinschätzung:** Conditional

**On-prem / local hosting: partially**

Jira can be operated as a self-managed product via Jira Data Center on the customer’s own hardware or through IaaS providers. However, the website does not clearly state that Atlassian Intelligence/Rovo AI runs entirely on-premises on the customer’s own hardware.

**Private Cloud / Data Center: Partially**

With Jira Data Center, operation is possible within a controlled, proprietary, or dedicated infrastructure. Regarding the AI features, the website does not clearly describe a dedicated private cloud configuration specifically for Atlassian Intelligence within the EU/EEA.

**EU SaaS / Managed: Covered**

Atlassian documents EU data residency for cloud products and explicitly for Rovo as well. The EU region corresponds to Europe (Frankfurt) and Europe (Dublin).

**Hybrid: Indirect / Not Available**

The website does not specifically describe an explicit hybrid deployment model for the AI features in which part of the system runs locally or on private infrastructure and another part runs as a managed service.

**DPA / AVV: Covered**

A DPA/AVV is documented on the website. Atlassian also describes obligations regarding subprocessors and notification of changes.

**No training: partially**

For Rovo, the website states that LLM providers do not use inputs and outputs to improve their own services. At the same time, Rovo’s list of subprocessors also includes infrastructure for machine learning, processing, and training; thus, a general, comprehensive exclusion of any training use at all levels is not fully and consistently substantiated.

**Open Source / Transparency Path: Partial**

Atlassian states that Rovo uses open-source models such as Mistral and LLaMA, as well as a mix of open-source, self-hosted, and third-party-hosted models. However, a true open-source or self-hostable transparency path for the overall Jira or Atlassian Intelligence product is not fully described on the website.

**Data Processing**

The website indicates mixed data processing for the cloud and AI features. Atlassian offers EU data residency and specifies Frankfurt and Dublin as the regions for the EU. For Rovo, when data residency is enabled, the relevant app data set remains in the selected region. At the same time, the list of subprocessors for Atlassian Intelligence and Rovo indicates AI service providers and processing locations outside the EU/EEA as well, particularly in the U.S.; for Google Vertex AI, EEA locations in Belgium, the Netherlands, and Finland are also listed. Jira Data Center is available for self-managed operation, but the website does not specify it as a fully on-premises end-to-end AI solution.

**Conclusion**

For the EU/EEA, Jira with Atlassian Intelligence can best be classified as *conditionally* GDPR-compliant: It offers strong compliance components, EU data residency, and a self-managed option for Jira. However, the situation regarding AI processing itself remains complex because the website documents both international processing and multiple external AI sub-processors, and does not clearly demonstrate consistently purely European or fully on-premises AI operations.

**Sources**

- [https://www.atlassian.com/de/software/rovo/guides/admin-guide/rovo-data-usage-privacy](https://www.atlassian.com/de/software/rovo/guides/admin-guide/rovo-data-usage-privacy)
- [https://www.atlassian.com/trust/ai](https://www.atlassian.com/trust/ai)
- [https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/](https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/)
- [https://www.atlassian.com/legal/sub-processors](https://www.atlassian.com/legal/sub-processors)
- [https://www.atlassian.com/software/jira/guides/more/jira-hosting](https://www.atlassian.com/software/jira/guides/more/jira-hosting)
- [https://www.atlassian.com/trust/privacy/how-we-handle-your-data](https://www.atlassian.com/trust/privacy/how-we-handle-your-data)
- [https://www.atlassian.com/dam/jcr%3A1595b3d1-3b51-4435-84c3-e493d35f96ba/Atlassian%20Customer%20DPA_September%202022.pdf?cdnVersion=797](https://www.atlassian.com/dam/jcr%3A1595b3d1-3b51-4435-84c3-e493d35f96ba/Atlassian%20Customer%20DPA_September%202022.pdf?cdnVersion=797)
- [https://www.atlassian.com/trust/compliance](https://www.atlassian.com/trust/compliance)
- [https://www.atlassian.com/trust/compliance/resources/soc2](https://www.atlassian.com/trust/compliance/resources/soc2)
- [https://www.atlassian.com/legal/privacy-policy?tid=312074573](https://www.atlassian.com/legal/privacy-policy?tid=312074573)

For users throughout the EU/EEA, using Jira with Atlassian Intelligence in compliance with the GDPR is generally possible, but only under certain conditions. Positive aspects include the documented privacy policy, a DPA/AVV, a list of subprocessors, the explicit GDPR commitment, EU data residency for Rovo, and self-managed hosting for Jira Data Center. At the same time, the website indicates that processing for Atlassian Intelligence/Rovo features may also take place outside the EU/EEA—particularly in the U.S.—and that not all components are equally EU-resident. Therefore, to ensure compliant GDPR usage within the EU/EEA, the appropriate deployment model, data residency configuration, and a review of international data transfers are required.

**Positive**

Atlassian refers to its privacy policy, DPA/AVV, security measures, and list of subprocessors. For Rovo, EU data residency is documented, and Jira can also be operated as a self-managed variant via Jira Data Center on the customer’s own hardware or with IaaS providers. Rovo also mentions SOC 2 and ISO 27001, as well as the statement that LLM providers do not use inputs and outputs to improve their own services.

**Negative**

The website documents subprocessors and processing locations for Atlassian Intelligence and Rovo that are outside the EU/EEA, including the U.S. Furthermore, data residency is not equally available for all related components; according to the website, it is not available for Forge apps built in Studio. The website does not consistently demonstrate that AI functions operate exclusively within the EU.

**Server Location**

For cloud data residency, Atlassian lists the regions Europe (Frankfurt) and Europe (Dublin) for the EU. Data residency is available for Rovo. However, the list of subprocessors also includes the U.S. and, in some cases, EEA locations such as Belgium, the Netherlands, and Finland for AI-related processing, depending on the provider. For Jira Data Center, customers can choose the hosting environment themselves.

## Hosting und Daten
- **On-Prem / lokales Hosting:** teilweise / indirekt
- **Private Cloud / Rechenzentrum:** teilweise / indirekt
- **EU SaaS / Managed:** abgedeckt
- **Hybrid:** unknown
- **AVV / DPA:** abgedeckt
- **Kein Training auf Kundendaten:** teilweise / indirekt
- **Open-Source / Transparenz-Pfad:** teilweise / indirekt

## Standort
**Land:** Australia

**Taxonomie:** Australia

Global HQ: Level 6, 341 George Street, Sydney, NSW 2000, Australia. Service provider according to the legal notice: Atlassian Pty Ltd, c/o Atlassian, 350 Bush St, Floor 13, San Francisco, CA 94104, USA.

## Vorteile
- Very strong integration into Atlassian workflows and integrations
- AI directly in the project flow instead of as a separate tool
- Good scalability from small teams to enterprise
- Data Residency, Audit Logs, SLA, Sandbox, and IP allowlisting for cloud customers
- For enterprise, additionally centralized governance and multi-instance operation.

## Nachteile
- The full AI value-add is officially documented primarily for Cloud Premium / Enterprise; for Data Center there is no equivalent native AI deployment.
- Standard/Free users get significantly fewer governance, support, and AI capabilities.
- When using AI, data processing may by default take place outside the current site and in some cases outside the EU.
- Data Residency covers only in-scope data; without pinning, Atlassian can move data dynamically across AWS regions.

## Quellen
- Offizielle Website: https://www.atlassian.com/

## Letzter Datenstand
2026-04-28

## Originalseite
https://kifox.ai/en/ki-tools/jira-atlassian-intelligence-en/