Everything we do with your data, on one page.
No badges in place of specifics. This page documents exactly what Cluware plugins do with the data they touch, where it lives, and who else sees it. If a detail is missing, email security@cluware.com .
Data flow
Forge runs our plugin UI inside Atlassian's infrastructure. Your Jira data does not leave your tenant. A narrow slice of non-tenant data reaches our backend for specific, documented reasons.
Via Forge runtime
Runs inside Atlassian's sandboxed infrastructure. Covered by Atlassian's SOC 2, ISO 27001, and regional compliance posture — we never see the data, and we can't.
- Jira issue, project, and user data
- Plugin UI state & user preferences
- OAuth identity (never seen by us)
- Audit events inside your tenant
Only for specific features
Hosted on AWS (region configurable on Enterprise). Encrypted in transit with TLS 1.3 and at rest with AES-256. Every item below is documented, with a reason.
- Anonymized usage metricsProduct improvement · 30-day retention
- License check (instance ID only)Billing · no personal data
- AI inference payloads (opt-in)Only when you enable AI features
No training on customer data · No selling to third parties · DPA available on request
Subprocessors
Everyone we share a byte with, and why. We'll notify subscribers at least 30 days before adding or changing any entry on this list.
| Processor | Purpose | Region |
|---|---|---|
| Atlassian (Forge runtime) | App hosting inside your tenant | Inherits tenant region |
| AWS | Backend services for non-tenant features | us-east-1 (default) |
| Sentry | Error monitoring — redacted payloads | EU |
| Stripe | Billing | US |
| Resend | Transactional email | EU |
Responsible disclosure
Email security@cluware.com with a description and reproduction steps. We'll acknowledge within one business day and work with you on a coordinated disclosure timeline. We do not pursue legal action against researchers acting in good faith.