← Grounded Export for Jira

Privacy Policy

Last updated: 6 October 2026

In short: Grounded Export for Jira runs entirely inside Atlassian's cloud. Your issue data is never sent to us, to our servers, or to any third party. We cannot see it.

1. Who we are

Grounded Export for Jira ("the App") is developed and distributed by Grounded ("we", "us"), contactable at support@groundedwp.com.

The App is distributed exclusively through the Atlassian Marketplace and is installed by an administrator of your Atlassian site.

2. Where the App runs

The App is built on Atlassian Forge and carries the Runs on Atlassian designation. This is not a marketing claim but a technical constraint enforced by Atlassian: the App uses only Atlassian-hosted compute and storage, and declares no external network egress permissions in its manifest.

As a practical consequence, no data processed by the App ever leaves Atlassian's infrastructure. There is no server operated by us, no analytics service, no error-reporting service and no third-party processor involved in the operation of the App.

3. What the App accesses

When an administrator installs the App, it requests the following Atlassian permissions:

PermissionWhy it is needed
read:jira-work To read the issues you choose to export, including their summary, description, comments, custom fields and attachments.
read:jira-user To display assignee and reporter names in the exported file.
storage:app To hold the export while it is being produced, and the finished file until you download it.

The App requests no write permissions to Jira data. It cannot create, modify or delete Jira issues, projects or other Jira content. The storage:app permission allows the App to read and write only its own Atlassian-hosted Forge storage for temporary export processing.

The App only reads the issues matched by the JQL query that you type. It does not scan your site, and it respects the permissions of the Atlassian site it is installed on.

4. What the App stores, and for how long

Producing a large export takes several steps, so intermediate data is held briefly in Atlassian-hosted storage:

DataWhereRetention
Raw issue data for the batch being processed Forge Object Store Deleted immediately after that batch is rendered
Job state (progress counters, status) Forge Key-Value Store Kept so you can check progress. Contains no issue content and no user identifiers; the query text is discarded when the export completes
The finished export file Forge Object Store Automatically deleted after 12 hours

Download links are pre-signed and expire one hour after they are generated.

All of this storage is provided by Atlassian and follows the data residency configuration of your Atlassian site.

5. What we do not do

6. Support communications

If you contact us at support@groundedwp.com, we will process the contents of your message in order to answer it. Please do not include confidential issue data in a support request; a description of the problem and, where relevant, the app version are enough.

Billing and licensing are handled by Atlassian. We receive from Atlassian only the commercial information needed to administer the licence. We do not receive payment card details.

7. Your rights

Because we hold no personal data from your Jira site, requests to access, correct or delete issue data should be directed to the administrator of your Atlassian site, who controls that data. For any personal data contained in support correspondence with us, you may contact us at the address above to request access, correction or deletion.

Uninstalling the App removes its stored data in accordance with Atlassian's app lifecycle.

8. Changes to this policy

If this policy changes, the revised version will be published at this address with an updated date. Material changes affecting how data is handled will also be noted in the App's Marketplace release notes.

9. Contact

Questions about this policy: support@groundedwp.com