Security statement

Security statement — OpenAPI Viewer & Macro Migrator for Confluence

Last updated: 22 October 2026

Architecture, in one line

The app is an Atlassian Forge app. All of its code runs on Atlassian’s infrastructure. There is no vendor-hosted server, no database and no analytics.

Egress, and why it is open

The app declares permissions.external.fetch with *, both for its server-side function and for the browser. We state this plainly because it is the first thing a security review looks for.

What the app contacts in practice: the address configured in each macro, and the API a user calls with Try it out. Nothing is sent to us. Only https is possible: the Forge runtime refuses plain http.

Credentials for private repositories

Specifications attached to a page

When a macro shows a specification attached to its page, the app reads the attachment with its own identity, so that people reading the page are not asked to grant the app access. Before it does, it asks Confluence whether the person viewing the page can read that page, and refuses otherwise, anonymous viewers included. The page is the one Forge reports the macro is rendered on, never one named in the request. This check was added in version 3.0.0 (22 October 2026).

The migration page

Permissions requested, and why

Data handled

Specifications, macro configuration, and — on the migration page — the body of the pages being converted, processed in memory inside the Forge runtime. The only data stored is repository credentials, as described above. No personal data is stored. When reading a specification fails, the app logs the host and the HTTP status code, never the path, query, credentials or content. Details in the privacy policy.

Content in the page

Swagger UI is bundled with the app and served by Atlassian. Nothing is loaded from a third-party CDN. Styles are shipped as files, compatible with the Content Security Policy Forge applies to app pages.

Vulnerability handling

Report to support@pieranlab.cloud. We aim to acknowledge within 3 working days. Because the app has no server of ours, remediation always means publishing a new app version through the Marketplace.

Dependencies

Atlassian’s Forge packages (@forge/api, @forge/bridge, @forge/kvs, @forge/resolver), React, swagger-ui-react to render specifications, and js-yaml to read YAML.

Verification

See also

The privacy policy and the support page.