Security
Our apps are built on Atlassian Forge and, wherever possible, run entirely on Atlassian's own infrastructure. Here is how they are protected, and how to report a problem.
How our apps are built
- Built on Atlassian Forge; encryption in transit and at rest, tenant isolation and hosting security come from the platform
- Least privilege: each app requests only the permissions it needs, listed below
- User interfaces run under Atlassian's Content-Security-Policy, which blocks inline and injected scripts
- Actions on your content are checked against the current user's Confluence or Jira permissions
Platform and permissions
Pearl – Mermaid Diagrams for Confluence
- Runs on
- Atlassian Forge, Runs on Atlassian
- Permissions
- App storage; a read-only check of whether the current user can edit a page; reading and writing a page only when a user converts its code blocks, as that user; AI models hosted by Atlassian; an admin settings page
- Sent outside Atlassian
- Nothing. AI features use models hosted by Atlassian (Forge LLMs)
Opal – Markdown for Confluence
- Runs on
- Atlassian Forge, Runs on Atlassian
- Permissions
- App storage; a read-only check of whether the current user can edit a page; reading Markdown files attached to the page a block is on; reading and writing a page only when a user runs one of Opal's page actions, as that user
- Sent outside Atlassian
- Nothing
Secure development
Every release passes unit tests, browser tests and a dependency vulnerability check before deployment. Releases with known critical or high-severity dependency issues are not shipped. Multi-factor authentication protects the source code, Atlassian and email accounts.
Report a vulnerability
Email security@notechdebt.dev with the app and the steps to reproduce. We acknowledge reports within 2 business days, and also accept reports that reach us through Atlassian's Marketplace security process.
| Severity (CVSS) | Fixed within |
|---|---|
| Critical (9.0 and above) | 10 days |
| High (7.0–8.9) | 4 weeks |
| Medium (4.0–6.9) | 12 weeks |
| Low (below 4.0) | 25 weeks |
Times run from when a report is confirmed.
If something goes wrong
If a security incident affects customer data, we notify Atlassian and affected customers promptly, and publish what happened and what we changed.