Sprint Ledger is published by Yord Soft EOOD, a company registered in Bulgaria under EIK 203874601 at 12 Nikolay Liliev St., floor 1, office 2, 1421 Sofia, and this policy covers the Sprint Ledger app for Jira Cloud. It describes what the app stores, where it is stored, who can reach it and how to have it removed. Questions and requests: support@dyordanov.com.
To answer questions about sprint scope, the app reconstructs the membership history of your sprints from Jira's own changelog and keeps the result. That record holds:
The app does not store issue summaries, descriptions, comments, attachments, worklogs or any other issue content, and it does not store user names or email addresses.
The only personal data the app stores is the Atlassian account ID attached to a sprint membership change. It is kept so that a scope change can be attributed to the person who made it, which is the question teams ask of a scope report. No profile information is copied. An account ID becomes a name only where Jira shows it to someone who already has access: in Jira's own screens, and in the CSV export, where the app asks Jira for the names of the accounts on each page as the person exporting and writes them into the file on that person's computer without storing them. In the same way the issue panel asks Jira for the viewer's time zone, to show times as Jira's own fields do, and keeps nothing of it.
If you would rather the app did not keep account IDs at all, a Jira administrator turns off “Store account ids” on the app's admin page, and from then on the app stores nothing in their place. The same page has an “Anonymise user ids” action that removes every account ID already stored, from the sprint events and from the issue timelines, and turns capture off in the same step; counts, dates and query answers do not change.
Closed accounts. Once every reporting cycle that Atlassian sets (a week at present), the app reports the account IDs it stores, with the date each was last seen, to Atlassian's personal data reporting API, which answers whether any of them has been closed. A closed account's ID is erased from the sprint events and the issue timelines within that cycle, as “Anonymise user ids” would erase it, and the app stores nothing in its place.
The app also records the account ID of the administrator who opens its admin page for the length of that request, in order to check that they hold the Jira administrator permission. That check is not stored.
All of it lives in Forge storage — Forge SQL and the Forge key-value store — provisioned by Atlassian for your installation of the app and reachable only by that installation. It therefore sits inside Atlassian's infrastructure and follows your site's data residency. The app holds no database, no object store and no account of its own. Besides your own Jira site's API, the one call it makes is to Atlassian's personal data reporting API, part of the same platform, which receives only the stored account IDs and the date each was last seen (see Personal data).
Countries. Atlassian hosts Forge storage on Amazon Web Services in the data residency location of your Jira site: Australia, Canada, the European Union, Germany, India, Japan, Singapore, South Korea, Switzerland, the United Kingdom or the United States, as your site's administrators have chosen. A site with no location chosen is in Atlassian's global location, where Atlassian decides the region and may move data between regions. Atlassian's data residency documentation for Forge lists the regions behind each location.
Sprint Ledger is eligible for Atlassian's Runs on Atlassian programme, which is Atlassian's own check that an app stores its data on Atlassian infrastructure and egresses nothing.
Inside your site, the app shows a person only what Jira already lets them see: its JQL functions and custom fields run under the permissions of the user running the query, the admin page refuses anyone who is not a Jira administrator, the project settings page is open only to that project's administrators, and the dashboard gadget and the CSV export show a board's numbers only to people who can see the board.
As the app's developer we can read the app's runtime logs through Atlassian's developer console. The app writes IDs, counts, durations and error messages to those logs, deliberately never issue content; Atlassian retains them for a limited period and we use them only to see that installs and reconstructions are healthy and to diagnose faults. We cannot read your Forge storage, your issues or your sprints.
We do not sell, share or transfer any of this data, and there are no sub-processors: no analytics, no error-reporting service, no advertising, no tracking of any kind.
The record is kept for as long as the app is installed, because it is the app's whole purpose: a sprint closed in 2021 is still the answer to a question asked in 2026. Housekeeping trims only its own by-products — finished run records after 14 days, hourly usage counters after 48 hours.
When the app is uninstalled, its ten custom fields disappear from Jira at once, and Atlassian deletes the data that belonged to the installation after a retention period: the fields' values are permanently deleted after 30 days, and the app's Forge storage after 28 days. The period exists so that a site that uninstalled by mistake can recover: reinstalling within 30 days brings the fields back with their values, and the stored ledger can be relinked to the new installation on a request made within 21 days (write to us or to Atlassian support). After those periods neither can be recovered.
If you want the ledger deleted while keeping the app installed, a Jira administrator uses “Delete all ledger data” on the admin page: it removes every row the app holds for the site and keeps only the settings. The values already written into the ten custom fields stay on the issues until a new reconstruction rewrites them or the app is uninstalled.
To ask what is held about a particular account ID, to have it removed, or to exercise any other right you have under applicable data protection law, write to support@dyordanov.com. During the beta you get an answer the same day.
If what the app stores changes, this page changes with it and the date at the top moves. Beta sites are told by email when a change affects what is stored.
What changed on 17 September 2026: the countries where the data is stored; the retention periods Atlassian applies after an uninstall, which the previous version described as immediate deletion; the number of fields, ten since the app's 2.6.0 update. What the app stores did not change.
What changed on 24 September 2026, with the app's 3.0.0 update: closed accounts are now found through Atlassian's personal data reporting API and their IDs erased; the CSV export names people as Jira shows them to the person exporting, and the issue panel reads the viewer's time zone, neither of which the app stores. What the app stores did not change.
What changed on 23 September 2026: the publisher's full company name and registration details, and the contact address, which is now support@dyordanov.com. What the app stores did not change.