Capacity Trail for Jira · last updated 20 August 2026
This app stores nothing about any person. Not a name, not an account id, not anybody's working hours. What it keeps is a Jira group name and one number, how many hours a working day is for that group, plus a version count and the time that setting was last changed so that two administrators editing at once cannot silently overwrite one another. If you set that number before August 2026, an older copy of it is also still there: the upgrade deliberately leaves the earlier entry alone rather than risk deleting somebody's setting. That is the whole of it.
Capacity Trail reads your Jira issues and the membership of the Jira group you choose. It reads as you, using the permission you grant it the first time you run a report. That is a deliberate choice rather than a technical one: it means a report can never show you work you could not already open yourself, and it means two colleagues running the same report may honestly see different figures. Every report says so on its face.
It is read-only. There is no write permission in the list, so it cannot change an issue, an estimate or an assignment even by accident.
| Data | Stored? | Where |
|---|---|---|
| Group name and hours per working day | Yes | Atlassian's app storage, inside your own site |
| A version count and when that setting last changed | Yes | Stored beside it, so simultaneous edits cannot overwrite each other unnoticed |
| An older copy of that same number, if you set one before August 2026 | Yes | The earlier storage entry is left in place rather than deleted, so an upgrade cannot lose your setting. It is not read once the newer one exists |
| Your issues, estimates and assignees | No | Read for the length of one report and discarded |
| Names or account ids of your people | No | Never stored. Shown to you on the page while a report is open, and included if you copy the report out |
| Availability exceptions (who is part-time or away) | No | Supplied per run, held in memory, never persisted |
Telling the app that somebody works three hours a day, or is away next week, is information about a person. We do not want it and we do not keep it. You supply it when you run a report, the app uses it to do the arithmetic, and it is gone when the report is finished.
So that this does not mean retyping your team every time, the app hands that list back to you as a block of plain text. Keep it in your own file and paste it back next time. The data stays with you, which is the only place it genuinely belongs.
Nowhere, unless you take it there yourself. The app runs on Atlassian Forge, inside Atlassian's own infrastructure. It makes no request to any server of ours, because there is no server of ours. It sends nothing to any third party, uses no analytics, and sets no cookies of its own.
Two things it shows you do contain people's names and Jira account ids, and they are worth being precise about, because "nothing leaves your site" would not be exactly true once you copy them:
Both are read live from your Jira using your own permission, shown in your browser, and never written to the app's storage. If you copy them into a spreadsheet, that copy is yours and it is outside Atlassian, exactly as it would be if you copied the same names out of Jira itself.
Uninstalling the app puts the group name and the number beyond its reach immediately, and that is everything it holds. There is nothing else of yours in the app's storage to request, export or erase.
To be exact rather than reassuring: Atlassian, not us, keeps Forge app storage for 28 days after an uninstall before deleting it, and within 21 days a reinstalled app can ask Atlassian to reconnect it. That is Atlassian's platform behaviour and it applies to every Forge app. We cannot read the data during that window and we do not ask for it back unless you ask us to. Saying "uninstalling deletes it" would have been simpler and slightly untrue, which is not a trade this product makes.
Anything you copied out of a report is in your own files rather than ours, so it is yours to delete in the same way you would delete any other spreadsheet.
Ace Foundry is responsible for the data this app processes. Contact is hello@acefoundry.io.
The app runs on Atlassian Forge and stores what it stores in Atlassian's own hosted storage, inside your site's region as Atlassian allocates it. We operate no servers and hold no copy: there is nowhere else for it to be. Atlassian publishes where Forge data is hosted, and their answer is the answer for this app.
Questions about this policy or anything else go to hello@acefoundry.io and are answered by a person.