Approved Bulk Actions privacy
This section describes how Approved Bulk Actions handles data. It supplements the site-wide privacy policy.
Security policy
Our application-specific security policy describes access controls, vulnerability reporting and incident handling.
Where the application runs
Approved Bulk Actions is an Atlassian Forge application. Its interface and its functions run on infrastructure operated by Atlassian, and it stores data only in Atlassian-hosted storage provisioned for your own installation. Atesen Software operates no server and no database for it.
What it talks to
The app uses Atlassian Forge services and your Jira site, including Atlassian's Privacy API to report stored account identifiers. Its manifest configures no external egress destination or remote backend. The app has no external analytics integration.
What it stores
- Saved actions: the name, service spaces, JQL filter, changes, limit and the groups or project roles allowed to run them. Configured changes can include comment text and participant account IDs.
- Run records: the selected action and its change snapshot, space, acting Atlassian account ID, effective search, counts, frozen request identifiers and each request outcome. Jira error messages are stored up to 300 characters and can contain field values.
- The app does not copy the request description or other current request fields into its run records. Values are read during a run to build the preview or apply changes, then are not kept as separate request-content records.
How long it is kept
Run records become eligible for cleanup once they are no longer running and more than 30 days have passed since their last update. Cleanup removes up to 20 expired runs at each subsequent run start and up to 200 per weekly scheduled invocation. Deletion is not guaranteed at exactly 30 days; running jobs are excluded. Saved actions are retained until changed or the installation's data is removed. Uninstall cleanup follows Atlassian's hosted storage retention and deletion process.
Data residency
The application uses Atlassian-hosted storage, which follows the residency of your Jira site. If your organisation pins its Atlassian data to a region, the application’s data is pinned with it.