Recap is built to have the smallest possible security footprint. This page explains how Recap authenticates, what it accesses, and how it handles data — see also the Privacy Policy for what data is read and why.
Authentication & authorization
Recap authenticates entirely through Atlassian Forge using OAuth 2.0 — there is no
separate login, password, or API key for Recap itself. The app requests a single,
minimal permission scope, read:jira-work, and every Jira request runs as
the requesting user (Forge asUser). Recap can never see or report on an
issue the user could not already see themselves, and it holds no elevated or app-level
access beyond that one scope.
Data flow
When a user clicks “Generate my report,” a Forge resolver queries Jira
(/rest/api/3/search/jql) as that user, groups the returned issues in
memory, and sends a compact list of issue titles and epic/project names to Atlassian’s
own Forge LLMs API to generate the report text. The result is returned directly to the
user’s browser. Nothing is written to storage at any point in this flow.
Hosting & subprocessors
Recap runs entirely on Atlassian Forge — there are no partner-operated servers, databases, or third-party subprocessors. AI text generation uses Atlassian-hosted Forge LLMs; prompts are processed inside Atlassian’s platform and never leave it. Recap makes no network calls to any non-Atlassian domain, and uses no external analytics or logging services.
Data storage & encryption
Recap has no database and uses none of Forge’s storage services (no Key-Value Store, no SQL, no entity storage). All processing happens in memory for the duration of a single invocation, so there is no data at rest to encrypt. All requests use the Forge platform’s TLS-encrypted channels in transit.
Logging
Recap writes only operational logs through Forge’s platform logging — for example, a line noting that AI generation fell back to the built-in template. Logs do not contain full issue content beyond what’s needed to diagnose a failure, and never contain credentials.
Vulnerability & dependency management
Recap pins Atlassian Forge SDK dependencies to released, non-prerelease versions and adds no third-party runtime dependencies of its own. Updates are reviewed and redeployed through the Forge CLI.
Access control
Recap is built and operated by a single developer. No systems holding customer data are operated by the partner, because none exist — Recap stores nothing. Source and deployment access is limited to the developer’s Atlassian developer account, protected with two-factor authentication.
Reporting a security issue
If you believe you’ve found a security vulnerability in Recap, please report it to support@isogunlabs.com. We aim to acknowledge reports promptly and will work with you on responsible disclosure.