Diagrams for Jira · Legal

Security Policy

How Diagrams for Jira is hosted, how your data is protected, and how to report a security problem.

Effective date: 17 November 2026 · Last updated: 17 November 2026

1. Scope

This policy covers Diagrams for Jira, an app for Jira Cloud made by Fortimus Technologies LLP ("Fortimus", "we") and sold on the Atlassian Marketplace. For what data the app handles and how long it is kept, see the Diagrams for Jira privacy policy.

2. Hosting architecture

Diagrams for Jira is fully hosted on Atlassian Forge. It uses Atlassian's compute and Atlassian's storage, and nothing else to hold data:

  • Compute: the app's backend runs as Forge functions on Atlassian's infrastructure.
  • Storage: every diagram, version, setting and usage count is kept in Forge hosted storage, which follows your Jira site's data residency location.
  • Interface: the app's screens run inside Jira in Forge's sandboxed frames.
  • No external servers: the app does not use Forge Remote, and Fortimus runs no servers or databases for it. No customer data is stored outside Atlassian.

The app connects outside Atlassian only for the features below. Forge blocks any other connection, because an app can only reach domains it declares in its manifest.

ConnectionFromWhyData sent
api.anthropic.comThe app's Forge backendAI diagram generation, only when someone uses AI and an admin has it turned onThe person's prompt, the issue summary and description if they opt in and an admin allows it, and the current diagram when changing it. Not stored by the app
embed.diagrams.net, app.diagrams.net, viewer.diagrams.netThe person's browserLoads the draw.io editor and viewerA normal page load. Diagrams are opened in the browser and saved only to Forge storage
libraries.excalidraw.comThe person's browserExcalidraw shape libraries, when someone browses themA normal page load. No diagram content

The key the app uses to call Anthropic stays in the Forge backend and is never sent to browsers. The app does not use or ask for Atlassian API tokens or passwords.

3. Data protection and encryption

  • In transit: all traffic is encrypted with HTTPS using TLS 1.2 or higher. That covers browsers to Jira and Forge, the Forge backend to Anthropic, and browsers to diagrams.net.
  • At rest: Forge hosted storage is encrypted at rest by Atlassian with AES-256, under Atlassian's key management on Amazon Web Services. The app keeps no data anywhere else.
  • Logs: the app does not write customer data, such as diagram content, prompts or issue text, to its logs.
  • Browser copies: unsaved changes kept in a person's browser after a tab closes are removed after 14 days.
  • Deletion: deleting a diagram removes it and its history at once. Uninstalling deletes all app data from Forge storage after Atlassian's 28-day safety period.

4. Access control

  • Jira permissions: the app checks Jira's own permissions before showing or changing a diagram. Viewing needs Browse projects. Creating, editing, deleting or using AI needs Edit issues. Changing app settings needs Administer Jira. People without edit rights see diagrams as view only.
  • Least privilege: the app asks only for the Jira scopes its features need: reading issues and their attachments, adding the diagram image to an issue description, and its own app storage. The full list is shown on the app's Marketplace listing.
  • Admin controls: Jira admins can turn AI off, stop issue details from being sent to AI, set AI limits for the site and per person, and choose which editors people can use.
  • Abuse limits: saves are rate limited, diagram size is capped, and AI use is limited per site each month and per person each hour.
  • Our staff: Fortimus has no direct access to the diagrams on your site. We see your data only if you choose to send it to us in a support request.

5. Secure development

  • We build the app to Atlassian's security requirements for cloud apps.
  • We keep the app's open-source dependencies up to date and fix known vulnerabilities in them.
  • New versions are released only through Atlassian Forge, which deploys the code to Atlassian's infrastructure.

6. Reporting a vulnerability

If you find a security problem in Diagrams for Jira, email support@fortimus.co with the subject "Security report: Diagrams for Jira". Tell us what you found and the steps to reproduce it. Please don't access other people's data, and give us time to fix the problem before you make it public.

We confirm receipt within 2 business days, assess the severity with CVSS, and keep you updated until it is fixed. We fix vulnerabilities within the timeframes of Atlassian's Security Bug Fix Policy for cloud apps:

SeverityCVSS scoreFixed within
Critical9.0 – 10.010 days
High7.0 – 8.94 weeks
Medium4.0 – 6.912 weeks
LowBelow 4.025 weeks

7. Security incident response

If we learn of a security incident that may affect customer data, we follow these steps:

  1. Assess: confirm what happened, which sites and data are affected, and how severe it is.
  2. Contain: stop the cause straight away, for example by releasing a fix or turning off the affected feature.
  3. Tell Atlassian: report it to Atlassian through the Developer and Marketplace Support portal within 24 hours, and keep Atlassian updated until it is resolved.
  4. Tell customers: email the admins of affected sites without undue delay, and within 72 hours where possible, with what happened, what data was involved, what we are doing and what they should do.
  5. Fix and review: fix the root cause, check the fix works, and write up what we changed to stop it happening again.

8. Platform compliance

Fortimus does not hold its own security certifications. The app runs on Atlassian Forge, which is covered by Atlassian's security and compliance program, including SOC 2 and ISO/IEC 27001. See the Atlassian Trust Center.

9. Contact

Security reports and questions: support@fortimus.co. Fortimus Technologies LLP, SNO 1415 A-11 S.NO 14, COMFORT ZONE BALEWADI, Baner Gaon, BANER GAON, Haveli, Pune – 411045, Maharashtra, India.