← Back to Home

Security Policy

Last updated: June 2026

1. Architecture & Execution Environment

Confluence Macro Toolkit runs entirely on the Atlassian Forge platform — a sandboxed, serverless execution environment managed by Atlassian.

No custom backend servers. All resolver logic executes in Forge's sandboxed Node.js runtime. We do not operate any servers, databases, or infrastructure.

Sandboxed execution. Forge enforces strict isolation between apps. Our code cannot access other apps' data, file systems, or network beyond declared permissions.

Custom UI isolation. All macro UIs run in sandboxed iframes with strict Content Security Policy (CSP) headers enforced by Atlassian.

2. Network Security

Encryption in transitAll communication uses TLS 1.2+ (enforced by Forge)
Encryption at restForge Storage uses AES-256 encryption
Outbound connectionsOnly embed.diagrams.net and plantuml.com — both disabled by default
Inbound connectionsNone — no webhooks, no public endpoints
DNS/egress filteringForge restricts egress to declared domains in manifest.yml only

3. Content Security Policy (CSP)

All Custom UI resources are served with Atlassian's strict CSP headers:

4. Authentication & Authorization

5. Input Validation & XSS Prevention

6. Supply Chain Security

7. Vulnerability Reporting

Responsible Disclosure

If you discover a security vulnerability, please do not open a public GitHub issue.

Instead:

  1. Use GitHub's private vulnerability reporting feature on the repository
  2. Or email security@vectored.dev

We aim to acknowledge reports within 48 hours and provide a fix timeline within 7 days.

8. Incident Response

9. Compliance

SOC 2Inherited from Atlassian Forge infrastructure
GDPRNo personal data processed — see Privacy Policy
CCPANo personal information sold or shared
Forge Security ReviewSubject to Atlassian's Marketplace security scanning