← Grounded Export for Jira

Security Policy

Last updated: 6 October 2026

Security by architecture: Grounded Export for Jira runs on Atlassian Forge, uses Atlassian-hosted compute and storage, and declares no external network egress. Jira data processed by the App does not leave Atlassian's infrastructure.

1. Scope

This Security Policy describes the security practices used for Grounded Export for Jira ("the App"), developed and distributed by Grounded.

2. Hosting and data handling

The App is built on Atlassian Forge and uses only Atlassian-hosted compute and storage. The App does not operate an external application server and does not declare external network egress permissions.

Jira issue data is accessed only when needed to perform an export requested by the user. Intermediate issue data is stored temporarily in Forge Object Store and deleted after the relevant processing batch is rendered. Finished export files are automatically deleted after 12 hours. Download links are pre-signed and expire after one hour.

3. Permissions and access control

The App requests only the permissions required to generate exports:

PermissionPurpose
read:jira-work Read the Jira issues, fields, comments and attachments selected by the user's JQL query for inclusion in an export.
read:jira-user Resolve Jira user information, such as assignee and reporter names, for display in exported files.
storage:app Read and write the App's own Atlassian-hosted Forge storage for temporary job state, intermediate processing data and generated export files.

The App does not request write permissions to Jira data and cannot create, modify or delete Jira issues, projects or other Jira content. Access to Jira information remains subject to Atlassian and Jira permission controls.

4. Authentication and secrets

The App relies on Atlassian's Forge platform and Jira authorization model. End users are not required to provide the App with Atlassian Personal Access Tokens, Atlassian account passwords, API keys or other shared authentication secrets.

5. Encryption and transport security

Network communication used by the App is provided through Atlassian Forge and Atlassian services. The App does not create a separate external data channel or send Jira content to infrastructure operated by Grounded. Protection of data within Forge, including platform transport and storage controls, is provided by Atlassian's infrastructure.

6. Third parties, analytics and tracking

The App does not send Jira data to third-party processors. It does not use third-party analytics, advertising, tracking or external error-reporting services within the App.

7. Vulnerability management

Security issues affecting the App are assessed based on their potential impact on confidentiality, integrity and availability. Confirmed vulnerabilities are prioritized for remediation according to severity and applicable Atlassian Marketplace security requirements. Dependencies and application code may be updated when needed to address relevant security issues.

8. Security incident response

If a security incident affecting the App is confirmed, we will investigate the issue, take appropriate containment and remediation measures, and coordinate with Atlassian where required. Affected customers will be informed when notification is appropriate or required.

9. Security certifications

Grounded does not currently claim independent security certifications for this App. The App relies on Atlassian Forge infrastructure for hosting, execution and application storage.

10. Reporting a security issue

To report a suspected security vulnerability, email support@groundedwp.com with the subject Security report — Grounded Export for Jira. Please include enough information to reproduce or assess the issue, but do not send confidential Jira data unless specifically requested through an appropriate secure channel.

11. Changes to this policy

This policy may be updated as the App or its security practices change. The current version will always be published at this address with an updated revision date.