OpenAPI & Swagger Viewer security policy

Last updated 20 October 2026

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:

Data handling

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:

Vulnerability management

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.