How Mermaid Diagrams for Confluence handles user data?
The Mermaid text you enter stays entirely within Atlassian Confluence. Our app does not send any diagram data to Stratus Add-ons servers or to any other external system. The rendering happens locally in your browser using the Mermaid JavaScript library.
How it works (data flow overview)
User input
When you add the Mermaid Diagrams macro in Confluence and type your Mermaid code, that text is stored inside the Confluence page content, within Atlassian’s infrastructure.
Rendering
When the page is viewed, Confluence loads our front-end code.
The code reads the Mermaid text directly from Confluence and renders it locally in your browser as an SVG/HTML diagram.
The diagram data never leaves Confluence and is not sent to us.
External library request (CDN)
The app uses the open-source Mermaid JS library, which is loaded from a public CDN.
This request only downloads the static JavaScript file of the Mermaid library.
No customer data or diagram content is transmitted in that process.
Saving and attachments
When you save a page, the Mermaid diagram remains stored within that Confluence page.
Stratus Add-ons servers
The app does not have any backend component that receives or stores your diagram content.
It runs fully inside the Atlassian and browser runtime.
We do not collect or log your Mermaid content in any way.
Security and compliance
Stratus Add-ons is SOC 2 Type II and GDPR compliant.
Our controls include encryption in transit, secure development practices, and strict access management.
You can review all documentation on our Trust Center:
https://app.eu.vanta.com/marketplace.atlassian.com/trust/c2l8fysnvxfh41l10qpoin
Summary
The data entered in the MermaidJS macro stays inside Confluence.
No content is sent to Stratus Add-ons or other external servers.
The only external request is to download the Mermaid JavaScript library from a CDN, which does not include any user data.