Privacy Policy — CloudScript Mermaid Diagrams for Confluence
This policy explains what the CloudScript Mermaid Diagrams for Confluence app does and does not do with data when it runs inside your Confluence Cloud site. It describes the behaviour of the app as built, and the wording reflects the permissions the app actually requests and the way it processes diagram content.
Summary
CloudScript Mermaid Diagrams for Confluence renders Mermaid diagrams inline on Confluence pages. The app runs on Atlassian's Forge platform, inside your own Atlassian environment. It draws each diagram in your browser, and when a page is exported to Word, a function of the app running on Atlassian's Forge platform supplies an image of the diagram for the Word document. The app does not send your content to CloudScript.io or to any third party, it does not store your content on any CloudScript.io system, and it does not use analytics, cookies, or trackers. The one thing that can reach us is a short technical log line written during a Word export, which contains no diagram code and no page text (see "Technical logs" below). This is consistent with our Atlassian Marketplace declaration that the app does not store personal data.
What the app is
CloudScript Mermaid Diagrams for Confluence is a Confluence macro. When you add the macro to a page and enter Mermaid diagram code, the macro converts that code into a diagram and displays it where the macro sits. When you save the macro, it keeps the following, all entered or chosen by you when you configure it:
- the diagram code, including any settings you add at the top of the code (its "front matter"), such as the look and layout of a Mermaid diagram, or the diagram colour (
pele: color:) and CSS theme (pele: css:) of a Pele diagram; - the engine that draws the diagram: Mermaid 12, Mermaid 11 or Pele;
- the selected theme, and the option to show the diagram source;
- an image (PNG) of the diagram, which the macro makes in your browser when you save it and which is used when the page is exported to Word. If the image cannot be made, the macro keeps a short note of the reason instead.
Where processing happens
The app is built on Atlassian Forge and runs entirely within Atlassian's hosted environment and your browser.
On the page. When a page containing the macro is viewed or edited, the selected engine is loaded into the macro's frame in your browser and converts your diagram code into a diagram on the spot. The image kept for Word export is made the same way, in your browser, when you save the macro. Your diagram content is not transmitted to CloudScript.io in order to be drawn.
Word export. When someone exports a page to Word, Confluence calls the app's export function once for each diagram on the page. The function runs on Atlassian's Forge platform, on compute that Atlassian hosts, not on any CloudScript.io system. Confluence passes it the macro's saved settings described above, including the diagram code and the stored image. If the stored image matches the diagram as it is now, the function returns that image. Otherwise it draws the diagram itself with the Pele engine, within the Forge platform, and returns that drawing; if the diagram cannot be drawn, it returns the diagram code as text. Confluence places what the function returns into the Word document, which is produced by Confluence and downloaded by the person exporting. The function stores nothing: apart from the log line described under "Technical logs" below, nothing of the export remains once it has returned.
PDF export. The export function does not process PDF exports: Confluence captures the diagram as it is displayed on the page.
What the app can access
The app requests a single Confluence permission, read access to page content (read:page:confluence), which is the access Forge requires for the macro to operate within the page it is placed on. The app does not request permission to modify pages, to administer your site, or to read user account details, email addresses, or directory information. In normal operation the app works with the diagram code you type into the macro and the settings saved with it.
Forge also tells the macro, and the export function, whether your site's subscription to the app is active, and the address of your site. The app uses these only to show a notice in place of the diagram when the subscription is not active. That notice includes your site's address, so that a user can pass it to an administrator, and names nothing else about the page, space, user or account.
What the app does not do
The app does not send data out of your Atlassian environment. On the Forge platform, an app can only make external network calls to destinations that it declares in advance in its manifest, and CloudScript Mermaid Diagrams for Confluence declares no external destinations, which means the app is not permitted to transmit your diagram content, page content, or any other data to CloudScript.io or to any other external service. This applies to the export function as well as to the macro in your browser. The app does not load images from the internet while drawing a diagram: an image placed in a diagram must be embedded in the diagram code itself. The app also declares no Forge storage, so CloudScript.io does not retain copies of your diagrams or any other content on its own systems. The app sets no cookies of its own and includes no analytics or third-party tracking code.
How your diagram content is stored
Everything the macro keeps (the diagram code and its front matter, the engine, the theme, the show-source option, and the image of the diagram) is saved as part of the macro's configuration on the Confluence page, which lives within your own Confluence Cloud site and is hosted and controlled by Atlassian. The image shows the diagram as drawn, so it contains whatever text the diagram displays. Storage and handling of that page content is governed by your agreement with Atlassian and by Atlassian's own privacy and security commitments rather than by CloudScript.io. The app reads that configuration back in order to redraw the diagram when the page is viewed, and Confluence passes it to the export function when the page is exported to Word.
Technical logs
Each time a diagram is exported to Word, the export function writes one line to the app's log on the Forge platform, so that we can diagnose a failed or unexpected export. The line records which route the export took (the stored image, a drawing made by the function, the diagram code as text, or the subscription notice), the Confluence identifiers of the page and of the macro on that page, the engine and its version, your site's subscription details for the app as Atlassian supplies them, image sizes and how long the export took, and, if something failed, the kind of error and the first few characters of an internal checksum. It never records the diagram code, the text of the page, or the wording of an error message.
These logs are kept by Atlassian on the Forge platform, and Atlassian makes those from the past 30 days available to us in its developer console, where we use them only to diagnose problems with the app. Developer access to an app's logs is on by default. Your organisation or site administrators can turn it off in Atlassian Administration: under Apps, select your site, then Connected apps, open this app's Details tab and switch off Logs access. Once it is off, we can no longer see any logs created on your site. Turning it off does not affect how the app works.
Personal data
The app is designed to operate on diagram code rather than on personal information, and it does not request, collect, or store names, email addresses, or other personal data on CloudScript.io systems. You control what you type into a diagram; if you choose to put personal data into the text of a diagram, that text, and the image of the diagram that shows it, is stored with the page in your Confluence site (as described above), appears in any Word or PDF export of the page, and is subject to your organisation's own handling of that page, not to any CloudScript.io system. The technical logs described above contain no diagram or page text.
Atlassian Forge and the underlying platform
Because the app runs on Atlassian Forge, the platform itself is operated by Atlassian, and Atlassian's infrastructure, security model, and data residency arrangements apply to how the app executes within your environment, including the export function. For information about how Atlassian handles data on Forge and within Confluence Cloud, refer to Atlassian's own privacy and trust documentation.
Support
If you contact us for support, through our help centre at support.cloudscript.io or at support@cloudscript.io, we receive the details you provide and any information you choose to include, and we use them only to respond to and resolve your request. Support requests are handled in Atlassian's customer service platform and their content is stored in Australia. Some related data, including your help-centre account details and email in transit through our email provider, Google, is held or processed outside Australia. Our Trust Center sets out which data this is and links to Atlassian's own documentation.
This section last updated 9 October 2026.
Changes to this policy
If a future version of the app changes what it accesses, stores, or transmits (for example, if a later release introduces a feature that requires sending data to an external service), this policy will be updated to describe that behaviour before that version is released, and the effective date above will change accordingly.
Contact
For questions about this policy or the app's handling of data, contact CloudScript.io at support@cloudscript.io (see also the Support page).