Where our services run
Two separate questions hide inside "where is our data". Storage is one, processing is the other, and they have different answers.
Content lives in your Confluence site, which means Atlassian's hosting and data residency choices apply to it. Some processing happens in services we run.
#The split
Part | Runs where |
|---|---|
Content storage | Your Confluence site, under Atlassian's hosting and residency |
Permissions and identity | Confluence, always |
Browser-rendered features | Your browser. Nothing leaves the machine |
Server-rendered features, such as diagram rendering | Services we run |
AI features, when used | OpenAI through Capable in the United States, or your own OpenAI or Anthropic account if an admin adds a key, and only when you invoke them |
#Removing the parts that leave
External diagram rendering can be turned off by an admin, which keeps diagram source in the reader's browser. Types that need the service are then not offered.
AI features can be switched off site-wide, which removes the surfaces entirely rather than hiding them.
Everything else is storage in your own tenant, which does not leave in the first place.
Data Capable keeps outside Confluence follows your Atlassian data residency region: the EU for sites pinned to the EU or Germany, the United States otherwise. See Data residency.
#A few things worth knowing
The residency answer for storage is Atlassian's answer, because that is where the content is.
External diagram rendering runs in the United States for every site. Turning it off answers the processing question for diagrams.
Per-product documentation carries the precise list of what leaves and when.
#Related
Storage is Atlassian's. Processing follows your region.
