This page explains where AssetPilot for Jira and AssetPilot Connect store data, what they log, and what happens when data is deleted. Connect is in beta; its details describe the release candidate.
Per-app details are in AssetPilot data and privacy and Connect data and privacy.
Storage
App data is stored in Forge storage, including the key-value store and secret storage, in the location Atlassian uses for your Jira site. This includes a pinned data residency location.
We operate no other database, file store or server. Atlassian handles data residency pinning and migration for Forge storage.
Encryption at rest
Atlassian encrypts Forge storage at rest. We keep no customer app data in another store.
Connect keeps credentials in Forge secret storage and stores API keys only as SHA-256 hashes.
Encryption in transit
Every connection uses TLS 1.2 or higher. This includes Forge platform calls, Atlassian APIs, and Connect’s calls to MDM, chat and webhook hosts.
Connect accepts only https webhook URLs and refuses private, loopback and link-local addresses.
Logging
| Log | Contains | Never contains | Kept |
|---|---|---|---|
| Forge function logs | Error codes, request ids, durations, counts | Personal data, asset content, credentials, tokens | Atlassian’s Forge log retention |
| AssetPilot audit log (a product feature) | Actor’s Atlassian account id, time, changed fields | Display names, emails | The latest 500 events per asset; deleted through the Forge storage lifecycle after uninstall |
| Connect sync runs | Counts and per-device errors (serial number, MDM id, error code) | Credentials | The last 50 runs per source |
| Connect deliveries | Event type, destination, HTTP status, attempts | Payload body, secrets | The last 500 deliveries |
Our engineers can access function logs through the Atlassian developer console only for Jira sites that allow log access.
Retention and deletion
| Event | What happens |
|---|---|
| Normal use | Data is kept while the app is installed. Admins and managers can delete assets and people at any time. |
| Export | Admins can export assets and the audit log to CSV at any time. |
| Uninstall | Forge soft-deletes the app’s storage and erases it within Atlassian’s retention period for Forge hosted storage. The assetpilot issue property (asset ids and tags, no personal data) stays on Jira issues; unlinking an asset removes it. |
| Disconnect Connect from AssetPilot | The OAuth refresh token and client secret are deleted at once. |
| Revoke an API key | The key hash is deleted at once and the key stops working. |
| Closed Atlassian account | Atlassian sends personal data reports for account ids we store. We erase or anonymise them as Atlassian requires. |
| Data sent by Connect to your services | Your policies in those services determine retention. We keep no copy beyond the delivery log above. |
| Idempotent API writes (Connect) | The stored response is deleted after 24 hours. |
See Atlassian’s Data lifecycle for Forge-hosted storage.