In short
| Where your data lives | Inside the Confluence page, as part of the macro. Diagramaid has no server and no database of its own. |
|---|---|
| Where diagrams are drawn | In the reader's browser. Nothing is sent away to draw them. |
| Network access | None. The app makes no calls to the internet, loads no external scripts, fonts or images, and declares no external hosts. |
| Tracking | None. No analytics, cookies, telemetry or third-party scripts. |
| Reporting a problem | Contact us. We acknowledge reports within 24 hours. |
1. How the app is built
No backend. Diagramaid is a Forge app with a Custom UI macro. It has no server, no Forge storage and no database. The diagram code and the display settings are stored by Confluence in the page itself, so they follow the page's permissions, history, retention and backups.
No egress. Every library the app needs is bundled with it. Nothing is loaded from a CDN or any other outside address at run time. Icon packs and images from the web are not supported in diagrams, on purpose.
Diagram code is treated as untrusted input. Mermaid runs in its strict security level. In this mode HTML in labels is encoded instead of executed and click handlers in diagrams are disabled, so the text of a diagram cannot run code in a reader's browser.
Content Security Policy. Diagramaid runs inside Atlassian's sandboxed frame with a restrictive policy. The one relaxation is unsafe-inline for styles, which Mermaid needs to apply its own formatting. Scripts are not relaxed.
Local actions only. Copy and download (SVG, PNG) happen in the user's browser, only when the user chooses them.
2. Data we handle
Diagramaid only handles what page authors put into the macro:
- the Mermaid diagram code, and
- the macro's display settings (theme, size, caption and so on).
We do not collect, store or process personal data about users, and nothing is sold or shared with any third party. See the privacy policy for the full statement.
Technical error messages
When something in the app fails, a short technical error message is sent to KODICE through Atlassian's platform, so we can find and fix the problem. It never contains your diagram, your page content or personal data. Your Confluence site administrator can turn this off, as described in the privacy policy.
3. Who is responsible for what
Security is shared between Atlassian, your organisation and KODICE.
| Who | Responsible for |
|---|---|
| Atlassian | The Forge and Confluence platforms: hosting, authentication, encryption in transit and at rest, tenant separation, and the sandbox the app runs in. See Atlassian's trust centre. |
| Your organisation | Who can view and edit pages, who may install apps, user accounts and sign-in settings, and retention of Confluence content. |
| KODICE | The security of the Diagramaid code, its dependencies, and how quickly we fix problems that affect it. |
Because the diagrams are stored in the page, anyone who can view a page can see the diagram code on it, and anyone who can edit the page can change it. Page restrictions work exactly as they do for the rest of the page.
4. Dependencies and updates
- Third-party libraries are bundled with the app, and the version of each one is pinned, so a release always contains exactly what we tested.
- The Mermaid version is pinned and stated in the user guide. We update it deliberately, and test the app before each release.
- We review our dependencies for known vulnerabilities and update them when a fix is available.
- Diagramaid is updated centrally through Forge. Updates reach every installed site, with nothing to download or run on your side.
5. Reporting a vulnerability
If you believe you have found a security problem in Diagramaid, please tell us before sharing it publicly, so we can fix it first.
Report it: contact us. Please use the same channel for questions about this policy.
What to include
- A description of the problem and why you think it is a security issue.
- The steps to reproduce it, including the Mermaid code or settings involved.
- The app version, shown in the bottom-left corner of the macro editor, and your browser and operating system.
- Screenshots or a short recording, if they help.
- Do not include real customer data, passwords or access tokens.
What you can expect from us
- Acknowledgement within 24 hours.
- An assessment of the report, and a first answer on whether we can reproduce it, within 5 working days.
- Updates while we work on a fix, and a note when it has been released.
- Credit, if you would like it, once the problem is fixed.
How fast we fix a problem depends on its severity. We fix the most serious ones first.
Scope
In scope:
- The Diagramaid app, including the macro view, the editor, the full-screen viewer and the export functions.
- Ways to run script or leak data through a diagram's code or settings.
- Ways to read or change data in a way that Confluence permissions should prevent.
Out of scope:
- Problems in Confluence, Forge or other Atlassian products. Please report those to Atlassian. If Diagramaid is involved, tell us as well.
- Problems in Mermaid itself with no effect on Diagramaid. Please report those to the Mermaid project.
- Denial of service through very large or complex diagrams in your own browser.
- Social engineering, physical attacks, and attacks on KODICE's staff, accounts or website.
- Automated scanner output with no demonstrated effect.
- Missing hardening headers that Atlassian controls on the platform.
Safe harbour
We will not take legal action against you for research on Diagramaid that follows this policy. Please:
- test only on your own Confluence site or a test site,
- do not access, change or delete other people's data,
- do not disrupt Confluence or the service for others, and
- give us a reasonable time to fix the problem before you disclose it.
6. If something goes wrong
If we confirm a vulnerability that puts customer data at risk, we will fix it, release the update through Forge, and tell affected customers without undue delay, through the Marketplace listing and by email where we have a contact.
Because the app keeps no customer data on KODICE systems, a problem in Diagramaid cannot expose data that we hold. It could only affect what is shown or processed in the reader's browser.
7. Supported versions
Only the latest version of Diagramaid is supported. Forge updates installed sites automatically, so every site runs the latest version.
Contact
Report a security problem or ask about this policy: contact us (the link opens your email app). Support requests that are not about security are on the support page.
Report a security problem