Jira App Security & Data Residency: How It Works

This reference explains the security and data-handling architecture of Release Management, Roadmaps & Product Portfolio for Jira. It is a factual companion to the blog article Jira App Security & Data Residency for Admins and is intended for Jira administrators, security reviewers, and procurement teams evaluating the app.

The app is built on Atlassian Forge and carries the Runs on Atlassian and Cloud Fortified badges on its Atlassian Marketplace listing. The controls below are properties of the Forge platform, enforced by Atlassian, rather than vendor-managed infrastructure.

Hosting and data egress

The app runs exclusively on Atlassian-hosted compute and storage. It does not run on third-party servers operated by the vendor. Forge apps cannot make outbound network calls unless the destination is explicitly declared in the app manifest. This app declares no egress of customer issue data, which means your Jira data is not transmitted to an external system for processing.

Tenant isolation

Each app invocation executes inside an isolated Forge runtime. Atlassian's Tenant Context Service scopes every request to a single customer tenant, so data from one site cannot be accessed by another. App data is stored per tenant in Forge-hosted storage; there is no shared cross-customer data store.

Permission scopes

The app requests a least-privilege set of OAuth 2.0 scopes, declared in its manifest. Administrators see the full list of requested scopes on the installation screen before granting access, and each scope maps to a specific app capability. The app requests only the scopes required to read and plan against your Jira issues and Fix Versions.

Data residency

For data held in Forge-hosted storage, the app inherits the data residency of the host Atlassian product. Atlassian manages the hosting, pinning, and migration of that data between supported regions. No separate residency request to the vendor is required.

Security documentation for review

The Marketplace listing includes a completed Data Security Self-Assessment and a Data Security Statement. Reviewers can reference these documents directly when completing internal security questionnaires, since the underlying controls (encryption in transit and at rest, processing location, and retention) are governed by the Atlassian platform.

Control	Summary	Enforced by

Control	Summary	Enforced by
Hosting	Atlassian-hosted compute and storage only	Forge platform
Data egress	No egress of issue data; destinations declared in manifest	Forge platform
Tenant isolation	Per-tenant runtime and storage via Tenant Context Service	Forge platform
Permissions	Least-privilege OAuth scopes, visible at install	Forge manifest / admin review
Data residency	Inherited from the host Atlassian site	Forge platform

Try Advanced Release Planning for Jira Cloud free for 30 days