Last updated: 15/09/2026
This privacy policy covers the Atlassian Marketplace apps “Bulk Excel & CSV Exporter for Jira”, “Hide from Export for Confluence”, “Initiative Timeline for Jira”, “User Access Audit for Jira” and “Label Colors for Jira”. Each app has its own section below.
Data processing terms. For these apps, our Data Processing Addendum sets out how we process personal data on your behalf.
Neither app collects, stores, or transmits any personal data.
For each initiative, the app stores:
It also stores one record noting when it last checked for data to migrate, and how many records it migrated and skipped.
The account IDs are recorded by the app’s server-side code. They are never sent to the page. Issue summaries and statuses are read from Jira each time the page loads.
In Atlassian’s Forge hosted storage, for the app’s installation on your site. The app runs entirely on Atlassian’s infrastructure.
In scope: all of the End-User Data the app stores — initiative records: name, start and end dates, linked Jira issue keys, created and last-updated times, and the Atlassian account IDs of the creator and last editor.
Out of scope: none. The app stores no End-User Data outside Forge hosted storage.
Forge hosted storage is covered by Atlassian’s data residency: per Atlassian’s Forge documentation, if an app stores its data on Forge persistent storage, an admin can control where that data is stored.
Nothing. The app declares no external network permissions and makes no calls to any external service. It uses no analytics, tracking, cookies or third-party services.
An initiative is kept until someone deletes it in the app. Deleting it removes its record.
Nothing. The app has no storage permission and no server-side code. It does not keep any record between visits.
When a Jira user runs the audit, the app reads from Jira:
It shows the results in that user’s browser. They include each account’s display name and account ID. Where Jira returns it, they also include the email address. They are gone when the page is closed.
If the user downloads the CSV file, it is created in their browser and saved to their own computer. That file contains the same account details. Once downloaded, it is under your organisation’s control, not the app’s.
Nothing is sent to any external service. The app declares no external network permissions. It uses no analytics, tracking, cookies or third-party services. The only data that leaves Jira is a CSV file a user chooses to download to their own computer.
Inside Jira, the app’s panel and settings page are titled Label Colors.
For each label a Jira administrator gives a color, the app stores:
The account ID is recorded by the app’s server-side code and is never sent to any page. It reads an issue’s labels from Jira when the issue panel loads.
In Atlassian’s Forge hosted storage, for the app’s installation on your site. The app runs entirely on Atlassian’s infrastructure.
In scope: all of the End-User Data the app stores — label color settings: the label name, the chosen color, when the color was set, and the Atlassian account ID of the administrator who set it.
Out of scope: none. The app stores no End-User Data outside Forge hosted storage.
Forge hosted storage is covered by Atlassian’s data residency: per Atlassian’s Forge documentation, if an app stores its data on Forge persistent storage, an admin can control where that data is stored.
Nothing. The app declares no external network permissions and makes no calls to any external service. It uses no analytics, tracking, cookies or third-party services.
A color is kept until an administrator removes it in the app. Removing it deletes its record.
bevelpine.support@proton.me
This policy may be updated from time to time. Any changes will be posted here.