Security Overview
1. Application architecture
Integration Helper for Jira runs entirely on the Atlassian Forge platform — it has no self-hosted infrastructure, servers, or containers of its own. For how Atlassian builds and operates the underlying cloud platform, see Atlassian's own Cloud architecture and operational practices.
2. Data access and storage
All Jira and Jira Service Management data is read through @forge/bridge's requestJira(), called
from the app's frontend, as the currently signed-in user — never with elevated app-level
permissions (no asApp() call anywhere in the app). The app has no database and no Forge Storage: it
never persists Jira/JSM data anywhere, on Atlassian's infrastructure or elsewhere. Jira applies that
user's own permissions to every request and decides what each specific endpoint returns; when Jira
responds 401/403 for a request, the app surfaces that instead of showing stale or assumed data —
in a multi-part export, that section is marked as not loaded rather than silently skipped.
See Permissions summary below for the exact Forge OAuth scopes the app requests, and Access model for who can open each surface of the app.
3. Data privacy
No Jira or Jira Service Management data leaves Atlassian's own infrastructure. The app makes no calls to any host other than Atlassian's APIs, and has no analytics or third-party integrations.
4. Data retention and removal
Because the app does not store any data of its own, there is nothing to retain or delete beyond what Atlassian retains for any installed Forge app (standard Forge platform logs, outside this app's control). Uninstalling the app removes it and its manifest-declared permissions from the site.
5. Network and connectivity
Every API call the app makes goes through Atlassian's own Forge-to-Jira proxy. The app does not open connections to any other host.
6. Permissions summary
Surface access (which parts of the app a user can open) is controlled by the app's manifest
displayConditions. Data access is a separate matter: every requestJira() call runs in the context
of the current user, and Jira itself applies that user's real permissions and decides what each
specific endpoint can return — holding a Forge scope never grants access beyond what the user's own
permissions already allow. See Access model for the full access table.
The app requests the following Forge OAuth scopes:
| Scope | Category |
|---|---|
read:jira-work | Core Jira Platform read access |
read:jira-user | User search |
manage:jira-configuration | Read-only access to configuration-reference endpoints (priorities, custom-field contexts, workflows, statuses) |
manage:jira-project | Read-only access to screen fields and project roles |
read:servicedesk-request | Core JSM Service Desk read access |
manage:servicedesk-customer | Read-only access to JSM organizations |
read:board-scope:jira-software | Jira Software boards |
read:sprint:jira-software | Jira Software sprints |
read:project:jira | Required alongside the board scope for board listing |
read:knowledgebase:jira-service-management | JSM knowledge base search |
These scopes bound which Atlassian REST APIs the app can call at all. They are distinct from Jira
user permissions, which the Atlassian platform still enforces independently on every requestJira()
call for the current user — holding a scope never grants access beyond what that user's own Jira
permissions already allow. Despite the manage:* naming on some scopes (an Atlassian scope-taxonomy
category for certain configuration-reference endpoints, not a statement about write access), the app
never calls endpoints that modify Jira data.
7. Vendor information
The only infrastructure provider involved in running this app is Atlassian, via the Forge platform. There are no additional subprocessors, since the app has no backend or storage of its own.
8. FAQ for security assessment
Does the app store our Jira data? No. It has no database or Storage of any kind; every screen is rendered from data fetched live for that page view.
Does the app make network calls to hosts other than Atlassian? No. All calls go through Atlassian's own Forge-to-Jira proxy.
Can the app modify Jira configuration or issues?
No. The app never calls endpoints that modify Jira data, even for scopes whose Atlassian-assigned
category name includes manage:*.
Does the app require a Jira administrator to install it? Installing any Forge app on a site requires a Jira administrator, per Atlassian's own platform rules. Once installed, which parts of the app a given user can open follows the access table in Access model.
What happens to a Project LLM Context file after it's downloaded? It is generated and downloaded entirely in the browser. The app does not keep a copy or transmit it anywhere — see Project LLM Context.