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 | The model provider, and only when you invoke them |
#Removing the parts that leave
Diagram rendering can be pointed at a Kroki-compatible server you host yourself, which keeps diagram source inside your network.
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.
Current hosting specifics live on our published trust pages, which are kept up to date. A wiki page that names regions will age badly, so this one deliberately does not.
#A few things worth knowing
The residency answer for storage is Atlassian's answer, because that is where the content is.
Self-hosting the renderer answers the processing question completely for diagrams.
Per-product documentation carries the precise list of what leaves and when.
#Related
Storage is Atlassian's. Processing is ours, or yours.
