Privacy Policy — OpenAPI Reference for Confluence

Effective 2026-08-20. Applies to the "OpenAPI Reference for Confluence" app by Chockablock, built on Atlassian Forge.

The design

The app is rendering-only and runs entirely on Atlassian-hosted infrastructure (Atlassian Forge). It declares no external egress permissions of any kind: no vendor servers, no content delivery networks, no analytics or telemetry, no external fonts, no outbound requests. This is enforced by the Forge platform, verifiable by Atlassian's own forge eligibility check, and the app is eligible for Atlassian's Runs on Atlassian program.

What data the app touches, and where it lives

• Your API specification documents. Stored by Confluence itself — either inside the macro's configuration (part of your page content) or as page attachments you choose. They are processed in your browser and on Atlassian infrastructure only, and are never transmitted to Chockablock or any third party.
• Page attachments. The app requests exactly one permission, read:attachment:confluence, used solely to list and read attachments on the page where you configure the macro, with the viewing user's own permissions.

What Chockablock receives

Nothing. We operate no servers for this app, set no cookies, and collect no personal data, usage data, or content through it. The only information we ever hold about you is what you choose to send us by email for support.

Subprocessors

None, beyond Atlassian itself as the hosting platform for your Confluence site and this app. Data residency follows your Atlassian site's configuration, since all processing and storage is Atlassian's.

Support correspondence

If you email [email protected], we keep the correspondence for as long as needed to help you and improve the app, and we do not share it. Please do not send credentials or confidential specification content; we never need them.

Changes

If a future version of the app ever changes any of the above — in particular, if any egress of any kind were introduced — this policy will be updated before release, the change will be visible in the app's Marketplace listing and permission prompts, and such a change would also be surfaced to your admins by Atlassian's own major-update approval flow.

Contact

Chockablock · [email protected] · chockablock.dev