OpenAPI & Swagger Viewer security policy
This page describes how OpenAPI & Swagger Viewer for Confluence ("the App") protects your data: where it runs, what it can access, how data is encrypted, and how we find, fix and report vulnerabilities. What personal data the App touches is covered separately in the privacy policy. Security questions and reports go to contact@jimapps.dev.
Architecture
The App is built on Atlassian Forge and qualifies for Atlassian's Runs on Atlassian program. In practice this means:
- No servers of our own. All code runs on Atlassian's infrastructure. There is no Jim Apps backend, database or file storage that your content could reach.
- No egress. The App declares no external hosts, so the Forge platform blocks any request from the App to the internet. Your specifications never leave your Confluence site.
- No backend functions. The App is a Custom UI that runs in a sandboxed iframe under the Forge Content Security Policy.
Data handling
- Where specifications live. A specification is either text stored in the macro on a Confluence page or a YAML or JSON file attached to the page. Both are stored by Confluence itself, under your site's existing permissions, retention and backups.
- What the App stores. Nothing outside Confluence. The App keeps no copies, caches or logs of your content.
- Who the App acts as. Every Confluence API call is made from the browser through Forge as the person viewing the page. The App can never see a page or attachment that this person cannot see.
- Rendering. Specifications are parsed with a safe YAML and JSON parser and rendered by Swagger UI, which sanitizes descriptions before display. The "Try it out" button is disabled, so no request is ever sent from a rendered specification.
- Migration. The page that moves macros from retired Swagger apps is available only to Confluence administrators and runs only when an administrator starts it. Every change it makes is saved as a normal page version, so it can be reverted from page history.
Encryption
Because the App stores no data of its own, encryption is provided by Atlassian's platform. Content is encrypted in transit with TLS and encrypted at rest in Confluence, as described in the Atlassian Trust Center. The App never handles passwords, API tokens or other secrets, and none are stored in its code or configuration.
Access and permissions
The App requests only the Confluence permissions it needs:
read:page:confluence,read:blogpost:confluence- read the page or blog post the macro sits on.read:attachment:confluence- read the YAML or JSON file chosen as the source.search:confluence- find pages that still use macros from the retired apps.write:page:confluence,write:blogpost:confluence- replace those macros, only when an administrator starts the migration.
Vulnerability management
- Dependencies. Before every release we check all production dependencies for known vulnerabilities and ship only with none outstanding.
- Fix timelines. We follow the Atlassian Marketplace Security Bug Fix Policy: critical issues are fixed within 10 days, high within 4 weeks, medium within 12 weeks and low within 25 weeks of being reported or triaged.
- Releases. Fixes reach every site automatically through Forge, with no action needed from administrators.
Reporting a vulnerability
Write to contact@jimapps.dev with a description of the issue and the steps to reproduce it. We acknowledge every report within 2 business days, keep you informed while we work on it, and credit you once it is fixed if you wish. Please give us a reasonable time to fix an issue before disclosing it publicly.
Incident response
If a security incident affects the App or its users, we contain it first, then notify affected customers and Atlassian without undue delay, following Atlassian's security incident guidelines. The notice says what happened, what data was affected, what we have done and what, if anything, administrators need to do.
Certifications
We are an independent software studio and the App holds no certifications of its own, such as SOC 2 or ISO 27001. Because it runs entirely on Atlassian's infrastructure and stores nothing elsewhere, your data stays within the environment covered by Atlassian's own certifications, listed in the Atlassian Trust Center.