Data and Privacy

Mermaid Diagrams for Jira 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

Data	Where	Contents	Who can see it
Saved diagrams	An issue property on each issue (yamuno-mermaid)	Title, Mermaid code, saved zoom, last changed date and the Atlassian account ID of who changed it	Anyone who can view the issue
Colour themes	The app's Forge storage for your site	Name, colours, dark-mode colours, font, and the account IDs of who created and last changed it	Everyone who uses the editor; only Jira admins can change them

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

Each person's view choice (Tabs, List or Grid) and their zoom on a diagram are kept in their own browser, not in Jira.

What the app only reads

None of this is stored:

• The issue's description and comments, to find Mermaid code blocks
• Whether the signed-in user can edit the issue, before saving or deleting a diagram
• Whether the signed-in user is a Jira admin, before saving a theme

Reading and saving run as the signed-in user, with that user's Jira permissions. The count on the collapsed section is worked out by the app itself and leaves out comments restricted to a group or role.

What the app doesn't do

• Send data to external servers or third-party services
• Include analytics or tracking inside the app
• Change issues, other than the diagrams property on the issues people save diagrams to

Removing your data

Deleting a diagram removes it from the issue property. Uninstalling the app doesn't remove issue properties from issues; when it's uninstalled, Atlassian deletes the app's Forge storage (the themes), as for every Forge app.

Scopes

read:jira-work (issues, comments, the diagrams property, permission checks), write:jira-work (saving the diagrams property) and storage:app (themes).