
Documentation
Mermaid Diagram for ConfluenceBrowse
Documentation
Mermaid Diagram for ConfluenceData and Privacy
Mermaid Diagram for Confluence runs entirely on Atlassian Forge. Yamuno runs no servers for it and never receives your data.
By default the app reaches nothing outside Atlassian. It only contacts GitHub, GitLab, Bitbucket or other sites after a Confluence admin connects them or allows them, and Atlassian asks the admin to approve each address. This page lists exactly what the app stores, what it reads, and what it sends where.
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 |
| Linked file | For a diagram imported from GitHub, GitLab or Bitbucket: the service, repository, branch, file path and file version | Editors of the page |
| GitHub connection | The GitHub App's ID, name and owner, and its private key, stored encrypted as a Forge secret | Only the app; the key is never sent to the browser |
| GitLab and Bitbucket connections | The GitLab address or Bitbucket workspace, the token's name and expiry date, and the access token, stored encrypted as a Forge secret | Only the app; the token is never sent to the browser |
| Allowed sites | The addresses an admin allowed for Import from a URL | Editors see the list |
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 page
Every Confluence request runs as the signed-in user, with that user's Confluence permissions. People only see pages they can already view.
What the app sends outside Atlassian
Only after an admin connects a service or allows a site, and only from Atlassian's Forge platform:
| To | When | What is sent |
|---|---|---|
GitHub (api.github.com) |
An editor imports, refreshes or commits; an admin opens the GitHub settings; the weekly check of linked diagrams | Requests for repositories, branches and files. A commit sends the diagram's code and a message that names the Confluence editor ("Committed from Confluence by …") |
| Your GitLab address | Same, with GitLab | Same, with GitLab |
Bitbucket (api.bitbucket.org) |
Same, with Bitbucket | Same, with Bitbucket |
| A site allowed under Import from URL | An editor imports from a URL | A request for the file at that link. No Confluence data is sent |
Files are read with the site's own GitHub App or access token, so the app only reaches the repositories your organization gave it. Readers of a page never cause a request: they see the diagram saved in Confluence.
While an admin connects GitHub, GitHub sends them back to an address on Atlassian's Forge platform, which receives the new app's credentials and stores them as described above.
What the app doesn't do
- Send data to Yamuno, or to any service other than the ones an admin connected or allowed
- 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.
Disconnect in Settings → Repositories deletes that service's key or token from Forge storage and removes its address from the site's approved list. It doesn't change anything in GitHub, GitLab or Bitbucket: delete the GitHub App, or revoke the token, there too if you no longer need it. Remove in Settings → Import from URL takes a site off the list.
Stuck on something this page does not cover? Ask the developers.