Security & Trust Overview
Architectural Safeguards
| Control Area | ClearStack Works Implementation |
|---|---|
| External Network Egress | Zero external egress. No external APIs, external databases, CDN trackers, or telemetry domains are declared in manifest.yml. |
| Authentication & Authorization | Relies strictly on Atlassian Forge user context via @forge/bridge and @forge/api (asUser()). Users can only read or write spaces and pages they are already permitted to access in Confluence. |
| GitHub / Git Credentials | Not required. Local folder/ZIP upload eliminates the need to grant third-party OAuth read access to private corporate Git repositories. |
| Least-Privilege Scopes | Requests only granular Confluence space, page, attachment, and content-property scopes; never requests site-admin or space-deletion scopes. |
| Data Lock-in Prevention | Writes standard native Confluence ADF pages and native attachments — never wraps customer documentation in proprietary closed macros. |
Vulnerability Disclosure
If you identify a security concern in any ClearStack Works website or Forge application, please email security@clearstackworks.com with reproduction details. We acknowledge all security reports within 24 hours and coordinate remediation promptly.