Privacy policy
Last updated October 6, 2026
This policy explains what data Sprint Ledger (the "app"), provided by Steadyfield ("we"), handles when installed on an Atlassian Jira Cloud site.
Summary
Sprint Ledger runs entirely on Atlassian Forge. It does not send any data outside Atlassian's infrastructure, and we cannot see your Jira data.
What the app reads
- Issue ids, creation dates and the value and change history of the Sprint field.
- Sprint metadata: id, name, state, start, end and completion dates.
- The list of fields on your site, to find the Sprint field and the app's own fields.
- The time zone of the app's own Jira user, which Jira sets to your site's default time zone, so sprint dates land on the right day.
What the app stores
- Values of the app's five custom fields on your issues, stored in Jira.
- In Forge app storage on Atlassian's platform: the ids of the fields above, the site time zone, and the status of the latest history scan (counts and timestamps).
The app does not store personal data such as names, email addresses or account ids.
Where data is processed
All processing and storage happens within Atlassian Forge, in the region where your Jira site's data is hosted. The app makes no external network requests.
When the app hits an error, Atlassian records it in the app's logs. We can only read logs from your site if a Jira admin allows log access in the app's settings, and the app never logs issue content.
Retention and deletion
When the app is uninstalled, Atlassian marks its storage for deletion and deletes it permanently within 28 days. Field values remain in Jira until you delete the fields.
Data residency
The app supports Atlassian's data residency. In scope are the app's Forge storage (field ids, site time zone and history scan status) and the values of its five custom fields, which Jira stores with your other issue data. Nothing is stored outside Atlassian.
Third parties
We use no third-party processors for app data. Atlassian processes data as described in its own privacy policy.