AssetPilot Connect data storage and privacy
AssetPilot Connect stores settings and logs in Forge storage and credentials in Forge secret storage. This page describes retention and external data flows for the pre-release companion to AssetPilot for Jira.
Pre-release
AssetPilot Connect is not on Atlassian Marketplace yet. It requires AssetPilot's app REST API, which is not in production. This page describes the release candidate.
Stored data
| Data | Stored | Kept |
|---|---|---|
| Connection settings (site, client id, scopes) | Forge storage in your Jira site's region | Until you disconnect or uninstall |
| OAuth client secret and refresh token, MDM credentials, webhook secrets, chat URLs | Forge secret storage | Until removed or uninstalled |
| OAuth access tokens | Function memory only | Until they expire or the function ends |
| Sync runs (counts; per-device errors with serial number and MDM id) | Forge storage | The last 50 per source |
| Deliveries (event, destination, status, attempts) | Forge storage | The last 500 |
| API keys (hash, prefix, scopes, last use) | Forge storage | Until revoked or uninstalled |
| Idempotent responses | Forge storage | 24 hours |
Uninstall starts the Forge storage deletion lifecycle: soft deletion followed by erasure within Atlassian's retention period for Forge hosted storage.
External data flows
Connect sends data outside Atlassian only to services you configure under your own contracts:
- Your MDM service receives read requests.
- Your Slack or Teams channels receive event cards.
- Your webhook URLs receive signed event payloads with Atlassian account ids.
Connect uses no analytics or AI.
Related information
Read subprocessors and data handling for more detail.