AssetPilot data storage, privacy and deletion
AssetPilot for Jira stores app data in Forge storage in your Jira site's region and makes no external calls. Review the retention details below before deleting records or uninstalling.
Stored data
| Data | Purpose | Stored | Kept |
|---|---|---|---|
| Asset records and custom field values | Core function | Forge storage in your Jira site's region | While installed |
| Asset types, lifecycle, locations, settings | Configuration | Same | While installed |
| External people (name, email, department), entered by your admins | Assigning assets to people without Jira accounts | Same | Until an admin deletes them, or through the Forge storage lifecycle after uninstall |
| Audit events (actor's account id, time, changes) | History and accountability | Same | The latest 500 per asset; all deleted through the Forge storage lifecycle after uninstall |
| Keys of linked issues | Issue panel and JQL | Same, and the assetpilot issue property in Jira | The property stays on issues until the asset is unlinked |
Data access and logs
- Not stored: display names, avatars and emails of Jira users. They are read when a page loads.
- Nothing leaves Atlassian. No analytics, AI or external calls.
- Logs: function logs contain error codes, request ids, durations and counts, with no personal data or asset content.
- Closed Atlassian accounts: Atlassian sends personal data reports for account ids we store, and we act on them.
Export and uninstall
Admins can export all assets and the audit log to CSV at any time.
On uninstall, Forge soft-deletes the app's storage and erases it within Atlassian's retention period for Forge hosted storage.
The assetpilot property (asset ids and tags, no personal data) remains on Jira issues. There is no bulk cleanup. To remove the property, unlink assets before uninstalling or delete it with the Jira REST API (DELETE /rest/api/3/issue/{issueKey}/properties/assetpilot).
Related information
Read data handling and the privacy policy.