Data and Privacy

Mermaid Diagram for Confluence runs entirely on Atlassian Forge. It has no external servers, so your diagrams never leave Atlassian. This page lists exactly what the app stores and what it only reads.

What the app stores

Everything below is kept in Forge storage for your Confluence site, inside Atlassian's infrastructure. Yamuno has no access to it.

Data	Contents	Who can see it
Diagrams	Title, Mermaid code, the page and macro it belongs to, creator's Atlassian account ID, created and updated dates	Anyone who can view the page
PDF images	A light-colour image of each diagram, for Confluence's PDF export	Anyone who can export the page
Colour themes	Name, colours, dark-mode colours, font, and the account IDs of who created and last changed it	Everyone who uses the editor; only admins can change them

Diagrams under about 20 KB are also saved in the macro's own settings on the page, with their title, zoom and search text, so the page can draw them without a lookup. The search text (the title and the words in the diagram) is indexed by Confluence search.

The app stores Atlassian account IDs only. It doesn't store names, email addresses or other personal details.

What the app only reads

None of this is stored:

• Whether the signed-in user is a Confluence admin, before theme changes and on the settings page
• Page titles, spaces and child pages, when you search for a page, build a page tree or open the Usage tab

Every request runs as the signed-in user, with that user's Confluence permissions. People only see pages they can already view.

What the app doesn't do

• Send data to external servers or third-party services
• Include analytics or tracking inside the app
• Change your Confluence pages, other than the diagram macros people edit

Removing your data

Deleting a diagram's macro removes it from the page; its stored copy stays in Forge storage until the app is uninstalled. When the app is uninstalled, Atlassian deletes everything it stored in Forge storage, as for every Forge app.